The test summary, charts that display quarantine or error status, count, and dates of failures help
you determine where to start your investigation. Each unique failure reason can also be expanded to
show all historical stack traces for that failure type:
This means that all the information you need to start debugging flaky tests is in a single place.
Developers don’t have to manually dig through historical CI logs to unearth various stack traces and
logs.
Have questions or feedback on the updates?
Reach out on our community Slack.