- Notifications
You must be signed in to change notification settings - Fork5.7k
Introduce Codecov's Test Analysis#4487
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecovbot commentedSep 19, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to theTest Analytics Dashboard |
The PR comment is a downside IMO but one that I can live with. I've already pointed out that I'd like to have an option to disable it:codecov/feedback#304 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
really like the codecov overview of the tests, test durations is something we can work on directly, and failure rate is cumulative, an insight which is hard to gather using local pytest runs.
Uh oh!
There was an error while loading.Please reload this page.
3409f51
intomasterUh oh!
There was an error while loading.Please reload this page.
Seehttps://docs.codecov.com/docs/test-result-ingestion-beta andhttps://about.codecov.io/blog/find-failing-and-flaky-tests-with-codecov-test-analytics/
In light of the discussion in#4324 and related threads, it seemed like a good idea to try it out :)