microsoft / microsoft/playwright-java
[Feature]: Split automatic trace files for parametrized tests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 298
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 14
Description
🚀 Feature Request
I would like to have ability to automatically save multiple trace files for parametrized tests.
Example
I have Option .setTrace(Options.Trace.RETAIN_ON_FAILURE) and parametrized test that fails. Separate trace files shall be created.
Motivation
I can have a parametrized test that fails for multiple parameters. Currently I'm not able to collect all failed cases but the last one.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Options.Trace.RETAIN_ON_FAILURE handles trace output when a parametrized test runs. Compare the current behavior for multiple failing parameters with the requested behavior, and verify completion by confirming that each failed parameter produces a separate trace file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100