You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Browser tests using [puppeteer](https://pptr.dev/) benefit from special support
8
8
9
9
Depending on the environment (you can set up configurations to run the same tests against dev, stage, prod etc.), tests can be skipped, or marked as _expected to fail_ for test driven development where you write tests first before fixing a bug or implementing a feature.
10
10
A locking system prevents two tests or the same tests on two different machines from accessing a shared resource, e.g. a test account.
11
-
You can review test results in a PDF report.
11
+
You can review test results in a PDF report or create a JUnit report file to be consumed by CI systems.
12
12
13
13
## Installation
14
14
@@ -391,6 +391,9 @@ The keys are up to you; for example you probably want to have a main entry point
391
391
-J, --json Write tests results as a JSON file.
392
392
--json-file FILE.json
393
393
JSON file to write to. Defaults to results.json .
394
+
--junit Write tests results as a JUnit XML file.
395
+
--junit-file FILE.xml
396
+
JUnit XML file to write to. Defaults to results.xml .
394
397
-H, --html Write test results as an HTML file.
395
398
--html-file FILE.html
396
399
HTML file to write a report to. Defaults to results.html .
0 commit comments