Improve handling of retrying tests | Fix wrong merging if test-name is equal

[mikepenz]

Add tests for flaky test scenarios and enhance retry logic in parser

• FIX Similarly-named test incorrectly treated as a successful retry of a previous test #1463
• FIX Test that has both a <failure> and an <error> is reported as failure even when successfully retried #1480

[github-actions]

	Tests	Passed ☑️	Skipped	Failed ❌️
Example Pytest Report	4 ran	2 passed	0 skipped	2 failed

Test	Result
Example Pytest Report
test_sample.test_which_succeeds	✅ passed
test_sample.test_which_fails	❌ failure
test_sample.test_with_error	❌ failure
test_sample.test_with_flaky_success	✅ passed

• View Example Pytest Report

[github-actions]

	Tests	Passed ☑️	Skipped ⚠️	Failed ❌️
Example Ungrouped Test Report | test_10.xml	3 ran	3 passed	0 skipped	0 failed
Example Ungrouped Test Report | test_11.xml	3 ran	2 passed	0 skipped	1 failed
Example Ungrouped Test Report | test_12.xml	3 ran	2 passed	1 skipped	0 failed

• View Example Ungrouped Test Report | test_10.xml
• View Example Ungrouped Test Report | test_11.xml
• View Example Ungrouped Test Report | test_12.xml

[github-actions]

	Tests	Passed ✅	Skipped	Failed
Example Nested JUnit Test Report	3 ran	3 passed	0 skipped	0 failed

Test	Result
Example Nested JUnit Test Report
ABC-0199: XMPP Ping
PingIntegrationTest.pingAsync (Normal)	✅ passed
PingIntegrationTest.pingServer (Normal)	✅ passed
ABC-0045: Multi-User Chat
MultiUserIntegrationTest.mucRoleTestForReceivingModerator (Normal)	✅ passed

[Copilot]

Pull request overview

This PR enhances the handling of flaky test retries and fixes a critical bug where tests with the same name but different classnames/files were incorrectly merged. The solution introduces a compound key strategy and improves the retry detection logic.

Key changes:

• Implements compound key (name|classname|file) to uniquely identify tests and prevent incorrect merging
• Refactors retry handling logic to properly track flaky tests in all scenarios (success after failure, failure after success, all failures)
• Adds comprehensive test coverage for flaky test scenarios

Reviewed changes

Copilot reviewed 5 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
test_results/flaky_retries/flaky_with_classname_file.xml	Test data file demonstrating flaky test with multiple failures then success, plus separate tests with same name but different classnames
test_results/flaky_retries/flaky_success_first.xml	Test data file for edge case where success occurs before failures in execution order
test_results/flaky_retries/flaky_all_failures.xml	Test data file for scenario where a flaky test never succeeds across all retries
src/testParser.ts	Core fix implementing compound key strategy and improved retry handling logic
dist/index.js	Compiled JavaScript matching the TypeScript source changes
__tests__/testParser.test.ts	Four new comprehensive test cases validating the flaky test handling improvements

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.