Required Trace File Naming Standard
4 min
All-in-one execution rule:
When a single execution produces multiple trace files, traces are matched by their file names. Files with raw names such as trace.zip cannot be reliably matched to the related test method or scenario.
Each trace ZIP file must therefore use the related method name or scenario name as its file name.
Required format:
<method-or-scenario-name>.zip
Examples:
successfulLogin.zip
User logs in.zip
Kullanıcı giriş yapar.zip
The exact scenario name may contain spaces or Unicode characters when that value is required for matching. The important requirement is that the ZIP name must correspond to the method or scenario reported by the execution.
Cucumber example
String scenarioName = scenario.getName();
Path tracePath = Paths.get(
"test-results",
"traces",
scenarioName + ".zip"
);
Gauge example
String scenarioName = executionContext
.getCurrentScenario()
.getName();
Path tracePath = Paths.get(
"test-results",
"traces",
scenarioName + ".zip"
);
Do not use: Generic names such as trace.zip, trace-1.zip, or random UUID-only names when the platform expects to match multiple traces in an all-in-one execution.
test-results/
└── traces/
├── successfulLogin.zip
├── User logs in.zip
└── Kullanıcı giriş yapar.zip