Repository navigation
Publish JUnit reports for all test suites in GitHub Checks - #65
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Test results currently remain in console output or downloadable evidence. Produce JUnit XML for native Go unit/container integration and Python unittest suites, reuse Gradle JVM XML, and keep emulator API 26/35 JUnit separate from UI hierarchy evidence. Publish results as GitHub Checks and Actions Summary with collapsible groups, all test names/statuses, timing, and failure details.
Each suite has an independent publisher that starts as soon as its corresponding test job finishes. Upload seven-day junit-* artifacts on success or failure. Only publisher jobs receive Checks write access; fork PRs use the trusted workflow_run after it reaches main, without checking out or executing PR code. Skipped suites have no new report. Existing required suite checks remain the merge gates.
Use pinned gotestsum v1.13.0, xmlrunner 4.0.0 and commit-pinned test-reporter v3. Keep Fastlane entry points and synchronized EN/RU documentation.
Validation: CI passes, including published reports for Python (48), Android JVM (184), API 26 (8) and API 35 (9). Native unit/container integration and its published report (94 tests) passed on the preceding ancestor; only emulator report timing changed afterward. Confirmed that Go/Python Checks appeared while Android jobs were still running. All published reports include disclosure blocks and finite durations. Temporary failing/skipped Go and Python fixtures verify XML statuses and nonzero failure exits. Ruby syntax and actionlint pass.
APK artifacts
Built from commit
cf029623by CI run #220.Artifacts expire after 14 days. Neither APK uses the MegaProxy release key.