Skip to content

add info about test failures#64

Open
michalszynkiewicz wants to merge 1 commit intoquarkusio:mainfrom
michalszynkiewicz:flaky-test-data
Open

add info about test failures#64
michalszynkiewicz wants to merge 1 commit intoquarkusio:mainfrom
michalszynkiewicz:flaky-test-data

Conversation

@michalszynkiewicz
Copy link
Copy Markdown
Member

This change requires adding a postgresql database for the quarkus-status application and configuring security for the resource for feeding flaky tests data.

Corresponding PR for the quarkus-bot: quarkusio/quarkus-github-bot#148

flaky-tests
flaky-tets-search-by-substring
flaky-tests-details
flaky-tets-search-by-substring

Comment thread src/main/java/io/quarkus/status/flaky/TestStatisticsResource.java Outdated
@famod
Copy link
Copy Markdown
Member

famod commented Nov 17, 2021

How important is it for this feature that those uploaded build reports contain successful test runs? Thing is that those archives can become really big now and we are seeing download issues, so I'm thinking about including only the report files with actual failures/errors...

@michalszynkiewicz
Copy link
Copy Markdown
Member Author

How important is it for this feature that those uploaded build reports contain successful test runs? Thing is that those archives can become really big now and we are seeing download issues, so I'm thinking about including only the report files with actual failures/errors...

We discussed it with @gsmet a while back and the conclusion was we'd like to have it.

This change assumes we're pushing all the surefire reports from actions. We could optimize it by extracting just the test names for failed and successful tests in actions so that there is much less data going through the wires

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants