When using CodeceptJS with JUnit XML reporters (like mocha-junit-reporter), test case names were inconsistent depending on whether scenario retries were used:

• Without retries or retries that pass on first attempt: "JUnit reporting: Test 1" (with colon)
• With retries that fail and retry: "JUnit reporting Test 1" (missing colon)

This inconsistency made automated processing of JUnit XML files unreliable.

Root Cause

The issue occurred because during test retries, CodeceptJS clones tests using the cloneTest() function, which calls deserializeTest(). The deserializeTest() function was not restoring the custom fullTitle() method that CodeceptJS sets up to format test names as "${suite.title}: ${test.title}". This caused retried tests to fall back to Mocha's default fullTitle() implementation, which doesn't include the colon separator.

Solution

Updated the deserializeTest() function in lib/mocha/test.js to restore the custom fullTitle() method that maintains the consistent format. The fix ensures that cloned tests preserve the same title formatting as their originals.

Testing

• Added comprehensive unit tests to verify the fix works across different scenarios
• Verified all existing tests still pass
• Tested edge cases including empty suite titles and special characters
• Confirmed retry functionality remains unaffected

This change ensures JUnit XML output has consistent test case names regardless of retry behavior, making test result processing more reliable.

Fixes #4983.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.