You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It lists all the minimum needed features, requirements and tests needed for an e2e testsuite that suits the several stakeholders and can help development (not only testing RCs).
Some of these features are complimentary and inform greatly the architecture, for example being able to run airgap testscases at the same time we are able to test any helm-chart commit or any container-image tag. This unblocks the possibility of running the e2e tests against any PR and codebase if it is needed.
approach used to run those testcases (some shipped with the helm chart at https://helm.sh/docs/topics/chart_tests/, running otel deps, running load testing tools, etc)
Way of scheduling the testsuite to run:
CI and local runs
Possibility to use any helm-chart tgz or version
Possibility to run testcases in any order or not
Time and resources needed per e2e test run.
List of nice-to-haves.
The text was updated successfully, but these errors were encountered:
We would like to refactor
kubewarden-end-to-end-tests
to run them more and increase coverage.See https://github.com/kubewarden/rfc/blob/main/rfc/0004-tests-arch.md (simplistic), #68, #22, #30, kubewarden/kubewarden-controller#134 for ideas and possible projects that can be reused.
Acceptance criteria
Some of these features are complimentary and inform greatly the architecture, for example being able to run airgap testscases at the same time we are able to test any helm-chart commit or any container-image tag. This unblocks the possibility of running the e2e tests against any PR and codebase if it is needed.
For example:
The text was updated successfully, but these errors were encountered: