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

e2e tests #1

Open
nabuskey opened this issue May 16, 2024 · 0 comments
Open

e2e tests #1

nabuskey opened this issue May 16, 2024 · 0 comments

Comments

@nabuskey
Copy link
Contributor

We need e2e tests for things we put here. I don't think we have to confine ourselves to Go but all stacks should use the same language and a chosen format.

Tests should:

  • Verify functionalities of things that was deployed by stacks. For example, if it deploys Argo Workflows, it should test argo workflows functionalities that are enabled by the stack.
  • Verify user workflows. If you instruct users to do things in readme, we should test as much as we can. e.g. Can you login with Keycloak? Can you login to Backstage?

Tests should not:

  • Test the core functionalities of things that deploy the stacks. eg. No point in testing idpbuilder's --kind-confgi or --port flags.

Maybe we can mess with https://github.com/microsoft/playwright to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant