@@ -28,6 +28,16 @@ You’ll get:
2828
2929report.html – a clean, styled HTML report
3030
31+ ---
32+ ## Available Options
33+ | Option | Description | Default | Choices |
34+ | ----------------------- | ------------------------------------------------------------------ | ------------------------ | ----------------------------------|
35+ | ` --json-report ` | Path to save individual JSON test reports | ` playwright_report.json ` | * Any valid file path* |
36+ | ` --automation-tool ` | Specify automation tool used for testing | ` playwright ` | ` playwright ` , ` selenium ` , ` other ` |
37+ | ` --capture-screenshots ` | When to capture screenshots | ` failed ` | ` failed ` , ` all ` , ` none ` |
38+ | ` --html-output ` | Directory to output HTML reports | ` report_output ` | * Any valid directory* |
39+ | ` --screenshots ` | Directory where screenshots will be stored | ` screenshots ` | * Any valid directory* |
40+ | ` --send-email ` | Send HTML report via email after the test run | ` False ` | ` True ` , ` False ` |
3141---
3242
3343## ✨ Features
@@ -71,28 +81,12 @@ Just start typing, and the dashboard will instantly filter tests by:
7181
7282![ Screen Recording 2025-06-01 at 2 48 08 PM] ( https://github.com/user-attachments/assets/057441ac-06a3-421f-aafc-915968a90463 )
7383
74-
75-
76-
77- ---
78-
7984## Why use pytest-reporter-plus?
8085Stop wasting time writing and maintaining custom pytest reporter hooks like pytest_runtest_makereport!
8186With pytest-reporter-plus, you get a beautiful, lightweight HTML report out of the box — no extra coding needed.
8287
8388Just install, run your tests, and let the plugin handle all the reporting magic. Focus on what matters: writing and running your tests.
8489
85- ## Available Options
86- | Option | Description | Default | Choices |
87- | ----------------------- | ------------------------------------------------------------------ | ------------------------ | ------------------------ |
88- | ` --json-report ` | Path to save individual JSON test reports | ` playwright_report.json ` | * Any valid file path* |
89- | ` --automation-tool ` | Specify automation tool used for testing | ` playwright ` | ` playwright ` , ` selenium ` |
90- | ` --capture-screenshots ` | When to capture screenshots | ` failed ` | ` failed ` , ` all ` , ` none ` |
91- | ` --html-output ` | Directory to output HTML reports | ` report_output ` | * Any valid directory* |
92- | ` --screenshots ` | Directory where screenshots will be stored | ` screenshots ` | * Any valid directory* |
93- | ` --send-email ` | Send HTML report via email after the test run | ` False ` | ` True ` , ` False ` |
94- | ` --detect-flake ` | Detect flaky tests based on reruns in the current or last few runs | ` False ` | ` True ` , ` False ` |
95-
9690
9791## 🔁 Flaky Test Detection
9892If a test is retried multiple times (e.g. due to a --reruns plugin), the report will flag it as FLAKY.
@@ -103,9 +97,8 @@ In the HTML report, you’ll see a badge like:
10397
10498
10599## 📧 Email Report (Optional)
106- Send the HTML report via email using --send-email.
100+ Send the HTML report via email using --send-email. Please note you will need your own sendgrid setup to use this feature
107101
108- ### Setup Environment Variables
109102Create an emailenv file in your project folder that has the following
110103
111104``` commandline
0 commit comments