From b01525f809bccc0d329f4e6c1193c2f2af950a6b Mon Sep 17 00:00:00 2001
From: Playwright Service <89237858+playwrightmachine@users.noreply.github.com>
Date: Fri, 18 Aug 2023 11:00:06 -0700
Subject: [PATCH] cherry-pick(#26508): docs: blob reporter options (#26545)

This PR cherry-picks the following commits:

- 4f9bf63259d20a85097382d354f0dc88f519b2b1
---
 docs/src/test-reporters-js.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/docs/src/test-reporters-js.md b/docs/src/test-reporters-js.md
index d3bf180685a0b..e7b15c207e2b2 100644
--- a/docs/src/test-reporters-js.md
+++ b/docs/src/test-reporters-js.md
@@ -205,8 +205,23 @@ Or if there is a custom folder name:
 npx playwright show-report my-report
 ```
 
-> The `html` reporter currently does not support merging reports generated across multiple [`--shards`](./test-parallel.md#shard-tests-between-multiple-machines) into a single report. See [this](https://github.com/microsoft/playwright/issues/10437) issue for available third party solutions.
+### Blob reporter
 
+Blob reports contain all the details about the test run and can be used later to produce any other report. Their primary function is to facilitate the merging of reports from [sharded tests](./test-sharding.md).
+
+```bash
+npx playwright test --reporter=blob
+```
+
+By default, the report is written into the `blob-report` directory in the package.json directory or current working directory (if no package.json is found). The output directory can be overridden in the configuration file:
+
+```js title="playwright.config.ts"
+import { defineConfig } from '@playwright/test';
+
+export default defineConfig({
+  reporter: [['blob', { outputDir: 'my-report' }]],
+});
+```
 
 ### JSON reporter