Demo ProjectSample JUnit XML runs
Go to DashboardDemo: Flaky Login Tests
0 XML files • 0 folders • 0 testcases
Passed
0(0%)
Failed
0(0%)
Skipped
0(0%)
Total
0
Status Overview
0
total
Passed 0 (0%)
Failed 0 (0%)
Skipped 0 (0%)
Most failed testcase
—
Flaky tests
Detected across loaded reports
0
Longest testcase
—
Next Action: Persist XML content so reports survive refresh
Do this next
- •Re drop one XML file and confirm it parses (numbers > 0).
- •Ensure your importer saves file text into item.content.text when dropping or importing.
- •Once content.text is persisted, refresh and confirm results still show.
Why
- •File objects are not serializable; after refresh, only persisted text can be parsed.
- •Explorer structure can exist without the underlying XML content being available.
Quick checks
- •In Explorer, XML nodes should have content.text (warning icons indicate when it’s missing).
- •If you see 'No <testcase>' warnings, the XML may not be JUnit format.
This recommendation is deterministic (rule-based).
Flaky Tests (Top 10)
0 flaky total
No flaky tests detected in the currently loaded reports.
CI-runs_24.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_24.12.2025
junit-report.xml
Not parsed yet.
CI-runs_25.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_25.12.2025
junit-report.xml
Not parsed yet.
CI-runs_26.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_26.12.2025
junit-report.xml
Not parsed yet.
CI-runs_27.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_27.12.2025
junit-report.xml
Not parsed yet.
CI-runs_28.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_28.12.2025
junit-report.xml
Not parsed yet.
CI-runs_29.12.2025 0 (0%) 0 (0%) 0 (0%)
CI-runs_29.12.2025
junit-report.xml
Not parsed yet.