Description
🚀 Feature Request
Playwright currently has a search in HTML report that works with query formats such as p: - project name, s: - status, and @ - for the label name.
I wish to have support for reverse queries to exclude tests with p: and @, to be able to refine them in a better way.
I see this as a separate field with the label 'exclude', where I can put for example p: de-DE, XL viewport, Chrome or @HOME_MAIN_CAROUSEL_1 to exclude those tests from the refined view.
Example
Use case 1:
Precondition: The test has a unique label, e.g. @HOME_MAIN_CAROUSEL_1
While overviewing a lot of failed tests in the HTML report, I am fixing them 1 by 1. I wish to exclude fixed tests from the generated report to see what is left to fix.
Use case 2:
The engineer sees that different tests fail for the same reason - add to cart stops working for different tests and the root cause is the same (let's say - the selector is changed for one locale). After fixing the first test, the engineer investigated the second and realized, that it was fixed already in the previous one. The engineer can't add what is fixed in the query to refine already fixed tests (it could be both the project name or test label)
Use case 3:
Users overview test reports with a lot of projects (let's say 10+), but some users are interested in just part of the tests (for example: in 8 of 10 of them). The way to refine them at the current moment is to enter 8 project labels, instead of just to exclude 2.
Same with labels. 1 report can be used by different users for different purposes - they need to refine the report in different ways to find different results
Use case 4 (similar to Use case 3):
Reviewing of all UI tests is under the responsibility of manual QA on the project. He needs to find in 1 big report all tests labeled '@visual' and can refine them by label search in the report. But the rest of the users can't reverse refine tests with such a label - there is no inverted ability to inverted search.
I realize that I can do grepInvert in the project for all @visual and make a separate one just for @visual, but it forces me to create extra projects, that I want to avoid.
Motivation
I am working with many configured Playwright projects (because of the many different locales in the shop). I wish to have a better HTML report narrow search to be able to faster look through reports for me and other people to find what they need. I understand that some 3rd party reporters could resolve this issue, but this feature will make Playwright report better as it exists out of the box and adds one more advantage in comparison with other paid reporter providers.