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
I have several cases where I have to execute tests scattered through multiple tests plans.
A simple example : I update the POM & fixtures, so I perform a npx playwright test --only-changed that are used in several tests cases across multiple test plans & suites
Unfortunately I can't make use of the reporter in this case, but it could be solved by adding support for multiple planId, such as testPointMapper already does for configurations.
Another method that would ensure backwards compatibility, would be to keep the exisiting planId, and use it as the default one, but adding the capability to override it locally.
Either with title/tags , by adding a prefix separated with . (PlanId.CaseId) :
Hello,
I have several cases where I have to execute tests scattered through multiple tests plans.
A simple example : I update the POM & fixtures, so I perform a
npx playwright test --only-changed
that are used in several tests cases across multiple test plans & suitesUnfortunately I can't make use of the reporter in this case, but it could be solved by adding support for multiple planId, such as
testPointMapper
already does for configurations.Another method that would ensure backwards compatibility, would be to keep the exisiting planId, and use it as the default one, but adding the capability to override it locally.
.
(PlanId.CaseId
) :Both methods may only be supported with
publishTestResultsMode: 'testResult'
though.Would it be possible considering the actual architecture of the reporter ?
Thanks and have a nice day
The text was updated successfully, but these errors were encountered: