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

Add logging to e2e tests #242

Open
3 tasks
pablochacin opened this issue Jun 28, 2023 · 0 comments
Open
3 tasks

Add logging to e2e tests #242

pablochacin opened this issue Jun 28, 2023 · 0 comments
Labels
internal improvement improves code quality or organization

Comments

@pablochacin
Copy link
Collaborator

pablochacin commented Jun 28, 2023

Presently the e2e tests run mostly silently. In case of failure, there's little if any indication of what went wrong.

Even with the changes recently introduced in #233 and #236 intended to improve the ability of contributors to debug failures found in the e2e tests, it is not clear for the developers for example what namespace was used by the failed test.

Therefore it would be convenient to add logs to the execution of e2e that offers hints about:

  • Namespace used for the failing test
  • Indications of how to reproduce the failed test and preserve resources (including the cluster) for further analysis
  • Links to relevant documentation
@pablochacin pablochacin added the internal improvement improves code quality or organization label Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal improvement improves code quality or organization
Projects
None yet
Development

No branches or pull requests

1 participant