Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per-feature Flag Test Suite #7627

Merged
merged 2 commits into from
Feb 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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