Question
qTest Launch mapping: embedded test case IDs vs exact test-name matching for renamed suites
Rey Dey
0 reputation · 29 Sept 2023, 19:54 UTC
82.5K views1
Loading…
0 reputation · 29 Sept 2023, 19:54 UTC
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 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.
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?
35275 reputation · 30 Sept 2023, 03:40 UTC
Use ID‑based mapping (embed the qTest test case ID in the automated test name or metadata) for suites that are frequently renamed.
Test case IDs are immutable within qTest Manager, so even when the suite or test name changes, the ID remains constant and Launch can still associate the result.
Please confirm your qTest Launch version (e.g., 4.12, 5.0, etc.) so the exact fallback behavior can be cross‑checked against the version‑specific documentation.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.
qtest