Collect the reports
Download JUnit XML from repeated CI runs. Reports must contain the same test identity to be compared.
CI TEST INVESTIGATION
When tests disagree,
start with evidence.
Compare JUnit reports from repeated runs of the same commit. See the tests that changed, then share a clear case with your team.
01Add reportsJUnit XML
02Compare runsSame commit
03Share evidenceIssue-ready
YOUR WORKSPACE
Investigate a test run
Add one or more reports. Two or more executions can reveal changes.
01 / INPUT
Add your reports
Upload JUnit XML reports from CI runs. Each report represents one run.
Choose reports to compareJUnit XML · up to 12 files · 512 KB each
Used for all reports by default. You can edit each run’s commit below.
Your reports are sent to this service for analysis and are not saved. Avoid uploading reports containing secrets.
02 / FINDINGS
Investigation
A clearer view starts here.
Add reports from the same commit to see where their outcomes differ.
Comparing your reports
Checking each test across your supplied runs.
Comparison complete
Sample reports · These results are illustrative.
No tests match your search. Try another filter.
SELECTED TEST
A change in outcome on a user-supplied commit is evidence of inconsistency, not proof of a flaky test or its cause. Environment and test data can also differ.
THE WORKFLOW
From noisy runs
to a useful conversation.
Give your team the context to reproduce an inconsistent test, without making a guess about its cause.
Check the commit
Enter the commit for each run. These identifiers are supplied by you and are not independently verified.
Share what you observed
Inspect the outcomes and failure messages, then copy an issue draft with the evidence your team needs.
BUILT FOR THE WORK AFTER CODE
Less guessing. Better questions.
Flakewise helps developers investigate inconsistent test outcomes using reports they already have. It does not execute tests, connect to your repository, or automatically fix or quarantine them.