By project, I am referring to a playwright TestProject
For example, take this playwright config shown in the docs. It has 3 projects. In this case, each project runs on a different browser. So when you do:
npx playwright test ./mytest.test.ts
your test is run three times- once for each project. These may have different results (your chrome and firefox tests may pass, but your safari test could fail). While different browser's are the most common use case for creating multiple project's, a project is just essential another config to run tests with. Other common examples for using multiple projects include running tests with different auth/role states, different locales, etc.
This PR is still a WIP, but the general plan is to enhance the results of treesitter's test node discovery with data from the playwright.config.ts. This would enable us to depict a more accurate representation of the test tree in neotest's summary window.
For example, take this playwright config shown in the docs. It has 3 projects. In this case, each project runs on a different browser. So when you do:
npx playwright test ./mytest.test.ts
your test is run three times- once for each project. These may have different results (your chrome and firefox tests may pass, but your safari test could fail). While different browser's are the most common use case for creating multiple project's, a project is just essential another config to run tests with. Other common examples for using multiple projects include running tests with different auth/role states, different locales, etc.
This PR is still a WIP, but the general plan is to enhance the results of treesitter's test node discovery with data from the
playwright.config.ts. This would enable us to depict a more accurate representation of the test tree in neotest's summary window.closes #5 closes #8 closes #9