qTest Launch mapping: embedded test case IDs vs exact test-name matching for renamed suites

qTest Launch associates automated results with qTest Manager test cases, and that association is a configuration choice rather than a single fixed behavior. Two documented approaches are commonly used: embedding the qTest test case ID in the automated test name or metadata and extracting it in the parser, or matching the exact automated test name to the qTest test case name.

The constraint

The suite in question is frequently renamed or data-driven, so automated test names change between runs. ID-based mapping keeps traceability stable but requires code or metadata upkeep. Name-based mapping avoids code changes but can break when a test is renamed, parameterized, or localized.

Unresolved behavior

What remains unclear is what qTest Launch does when no match is found. Depending on configuration and qTest release, an unmatched result may create a new test case, be skipped, or remain unlinked. Because that fallback can be version-sensitive, it should be confirmed in a non-production project before committing to a mapping strategy.

Which mapping approach suits a frequently renamed suite, and how should the no-match fallback be verified for a specific qTest version?