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
When we finish to run the tests we want to have a machine and human readable summary of the test run. The summary should be written to the report directory.
It is nice but contains lot of redundant info and noise, and not machine readable.
Since our tests are serial (deploy, protect, failover, ...) we don't need to show all the steps to describe the failure. The name of the failed step is enough. However the timing info is useful. Maybe we can do this:
When we finish to run the tests we want to have a machine and human readable summary of the test run. The summary should be written to the report directory.
Initial draft of the summary file:
Issues
How to describe setup and cleanup
Test run contains:
Test clean contains
The report should describe this flow, including errors in test or in the setup/cleanup steps.
Test run:
Test clean:
How to describe failures
Need to think how to describe the failure with enough details.
In go test we have this output:
It is nice but contains lot of redundant info and noise, and not machine readable.
Since our tests are serial (deploy, protect, failover, ...) we don't need to show all the steps to describe the failure. The name of the failed step is enough. However the timing info is useful. Maybe we can do this:
The text was updated successfully, but these errors were encountered: