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

Compile requirements for E2E testsuite refactor #112

Closed
viccuad opened this issue Aug 1, 2024 · 0 comments
Closed

Compile requirements for E2E testsuite refactor #112

viccuad opened this issue Aug 1, 2024 · 0 comments

Comments

@viccuad
Copy link
Member

viccuad commented Aug 1, 2024

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

  • A new epic issue or RFC is opened.
  • 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.

For example:

  • Types of testscases:
    • monitoring, audit-scanner, smokes, airgap, load tests, upgrade tests
    • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants