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

[Feature] Capture FAILED test output into a log file to review #737

Open
agentpoyo opened this issue Apr 23, 2021 · 3 comments
Open

[Feature] Capture FAILED test output into a log file to review #737

agentpoyo opened this issue Apr 23, 2021 · 3 comments
Labels

Comments

@agentpoyo
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Need to capture the FAILED test output into some type of log file to provide the ability to review later which could create links to documentation for the suggested remediation.

Describe the solution you'd like
Just like the results end up in a results.yml, capture the FAILED tests into their own failed.yml with the information needed as the information might display with STDOUT during the test run, an operator should be able to review what exactly FAILED at a later time if their CLI scroll buffer gets wiped, etc.

Describe alternatives you've considered
LOG the FAILED output in the k8s cluster to view or review. But this could lead to premature wiping when cleanup is invoked, etc.

@agentpoyo agentpoyo added the enhancement New feature or request label Apr 23, 2021
@lixuna
Copy link
Collaborator

lixuna commented Feb 28, 2024

hi @agentpoyo is this issue still relevant for cnti?

@agentpoyo
Copy link
Collaborator Author

I think this would be useful, could be a good outside contributor issue and feature for one to work on. @lixuna

@kosstennbl
Copy link
Collaborator

Partially resolved by #2008, log only for errors likely wouldn't be much helpful (as it will miss a lot of info from different parts of code, looking through full log still would be needed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: To do
Status: Todo
Development

No branches or pull requests

3 participants