You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since I'm using the option trace: 'retain-on-first-failure' with retries: 3 and screenshot: 'only-on-failure', I am oftentimes left with artifacts for tests that have retried and only contain screenshots without traces. This isn't a problem but more so, I'd prefer to omit those screenshots that don't have corresponding traces, as they don't really give me much to debug a test failure on, as opposed to the combination of a screenshot and a trace. I'd be awesome to have the option of screenshot: 'retain-on-first-failure' so that all artifacts retained contain both screenshots and traces.
I believe this will make Playwright better by providing a larger set of options that allows it's consumers to configure exactly how they'd like to digest artifacts. For example, I'm highly motivated to reduce the size of artifacts created by Playwright tests without sacrificing the tooling provided by Playwright to debug, therefore, having just artifacts with screenshots isn't super helpful and just increases artifacts size. A win win situation would be having the option screenshot: 'retain-on-first-failure' to go along with trace: 'retain-on-first-failure' 馃槂.
The text was updated successfully, but these errors were encountered:
馃殌 Feature Request
Since I'm using the option
trace: 'retain-on-first-failure'
withretries: 3
andscreenshot: 'only-on-failure'
, I am oftentimes left with artifacts for tests that have retried and only contain screenshots without traces. This isn't a problem but more so, I'd prefer to omit those screenshots that don't have corresponding traces, as they don't really give me much to debug a test failure on, as opposed to the combination of a screenshot and a trace. I'd be awesome to have the option ofscreenshot: 'retain-on-first-failure'
so that all artifacts retained contain both screenshots and traces.Example
Motivation
I believe this will make Playwright better by providing a larger set of options that allows it's consumers to configure exactly how they'd like to digest artifacts. For example, I'm highly motivated to reduce the size of artifacts created by Playwright tests without sacrificing the tooling provided by Playwright to debug, therefore, having just artifacts with screenshots isn't super helpful and just increases artifacts size. A win win situation would be having the option
screenshot: 'retain-on-first-failure'
to go along withtrace: 'retain-on-first-failure'
馃槂.The text was updated successfully, but these errors were encountered: