Jacek Nakonieczny

For example I have following parametrized test method. It's run in CI/CD pipeline with multiple `ConfigRecord configRecord` parameters. When more than one fails it produces only 1 trace file `CustomMetadataTest.testSetCustomMetadata-chromium/trace.zip`...

When I want to save success executions then yes, It generates file with multiple traces. For case described in the ticket trace file is executed only wen test fails. From...

Test framework is JUnit 5, here's minimal working example. It generates single trace file with only 1 failed test case. Regardless of `group/groupEnd` or `startChunk/stopChunk` in test method. Moving `groupEnd/stopChunk`...

I'd suggest to store all traces of a test method in single directory with trace filename combined with JUnit execution index. ```test-results\SomeClass.someMethod-chromium\{index}-trace.zip``` ``` test-results\SomeClass.someMethod-chromium\01-trace.zip test-results\SomeClass.someMethod-chromium\02-trace.zip test-results\SomeClass.someMethod-chromium\03-trace.zip ``` Latest update to...

Hi @yury-s @uchagani, any updates?