Skip to content

Commit

Permalink
Per feature flag test
Browse files Browse the repository at this point in the history
This commit releases the per feature flag test. It currently utilize
minimum end-to-end tests for stable features while mocking stable, beta
and alpha stability with different test envs.

/kind misc
  • Loading branch information
JeromeJu authored and tekton-robot committed Feb 9, 2024
1 parent 858883f commit 0cf8d03
Show file tree
Hide file tree
Showing 2 changed files with 514 additions and 0 deletions.
20 changes: 20 additions & 0 deletions test/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -438,3 +438,23 @@ setup a cluster for you:
export PROJECT_ID=my_gcp_project
test/presubmit-tests.sh --integration-tests
```
## Per Feature flag tests
Per-feature flag tests verify that the combinations of feature flags work together
correctly, ensuring that individual flags don't interfere with each other's
functionality and that overall outcomes remain consistent.
Per [TEP0138](https://github.com/tektoncd/community/blob/main/teps/0138-decouple-api-and-feature-versioning.md#additional-ci-tests),
minimum end-to-end tests for stable features are utilized, mocking stable, beta,
and alpha stability levels within different test environments.
To run these tests, you must provide `go` with `-tags=featureflags`. By default, the tests
run against your current kubeconfig context, but you can change that and other settings with the flags like
the end to end tests:
```shell
go test -v -count=1 -tags=featureflags -timeout=60m ./test -run ^TestPerFeatureFlag
```
Flags that could be set in featureflags tests are exactly the same as [flags in end to end tests](#flags).
Just note that the build tags should be `-tags=featureflags`.
Loading

0 comments on commit 0cf8d03

Please sign in to comment.