Filip/playwright
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: note about sharded projects in the merged config

Browse source 
Fixed https://github.com/microsoft/playwright/issues/29841
This commit is contained in:
Yury Semikhatsky 2024-03-29 16:33:42 -07:00
parent 1602548c10
commit 859240b158
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docs/src/test-reporters-js.md
View file

@ -349,6 +349,19 @@ Or just pass the reporter file path as `--reporter` command line option:
npx playwright test --reporter="./myreporter/my-awesome-reporter.ts"
```
## Merged report API notes
When merging mutliple [`blob`](./test-reporters#blob-reporter) reports via [`merge-reports`](./test-sharding#merge-reports-cli) CLI
command, the same [Reporter] API is called to produce final reports and all existing reporters
should work without any changes. There some subtle differences though which might affect some custom
reporters.
**Merging projects**
Projects from different shards are always kept as separate [TestProject] objects. E.g. if project
'Desktop Chrome' was sharded across 5 machines then there will be 5 instances of projects with the
same name in the config passed to [`method: Reporter.onBegin`].
## Third party reporter showcase
* [Allure](https://www.npmjs.com/package/allure-playwright)