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
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: