grafana / grafana/k6-operator

Show that a TestRun failed if the test fails - In ArgoCD and in TestRun conditions

Open
#577 4 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
800
Forks
214
Avg merge
5d 5h
Merged PRs (30d)
17

Description

### Feature Description

Usecase is that I want to deploy a new version of an API, then run x TestRuns on this api to verify it's still working.

The current [conditions](https://github.com/grafana/k6-operator/blob/14179cb9052fa0cead148d40e1f6cbaf421a2837/pkg/types/conditions.go) does not differenciate between a successful TestRun or a failing TestRun (in the example image below, thresholds of the k6 test is reached, the exit code is 99)

If we had a condition like this, we could make ArgoCD make these TestRun CRDs unhealthy with a "resource customization", preferably ready-to-use by everyone in [the ArgoCD repo](https://github.com/argoproj/argo-cd/tree/master/resource_customizations)

Image for reference:
![Image](https://github.com/user-attachments/assets/b3aed1e9-65ac-4381-9834-ce193ade357a)

### Suggested Solution (optional)

_No response_

### Already existing or connected issues / PRs (optional)

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with pkg/types/conditions.go and inspect how TestRun conditions represent success or failure. Then review the ArgoCD resource_customizations repository; done means a failed k6 threshold produces a distinct unhealthy TestRun condition that ArgoCD can recognize.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.