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
To produce Serenity BDD reports, your test suite must:
182
-
- download the Serenity BDD CLI, by calling `serenity-bdd update` (which caches the CLI `jar` locally)
183
182
- produce intermediate Serenity BDD `.json` reports, by registering [`SerenityBDDReporter`](/api/serenity-bdd/class/SerenityBDDReporter/) as per the [configuration instructions](#configuring-serenityjs)
184
183
- invoke the Serenity BDD CLI when you want to produce the report, by calling `serenity-bdd run`
185
184
186
185
The pattern used by all the [Serenity/JS Project Templates](/handbook/getting-started/project-templates/) relies
187
-
on using:
188
-
- a [`postinstall`](https://docs.npmjs.com/cli/v9/using-npm/scripts#life-cycle-operation-order) NPM script to download the Serenity BDD CLI
186
+
on using the following Node modules:
189
187
-[`npm-failsafe`](https://www.npmjs.com/package/npm-failsafe) to run the reporting process even if the test suite itself has failed (which is precisely when you need test reports the most...).
190
188
-[`rimraf`](https://www.npmjs.com/package/rimraf) as a convenience method to remove any test reports left over from the previous run
Copy file name to clipboardExpand all lines: src/docs/handbook/getting-started/serenity-js-with-protractor.mdx
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,26 +224,23 @@ and complete [`protractor.conf.js`](https://github.com/serenity-js/serenity-js-m
224
224
## Producing Serenity BDD reports and living documentation
225
225
226
226
[Serenity BDD reports and living documentation](https://serenity-bdd.github.io/docs/reporting/the_serenity_reports) are generated by [Serenity BDD CLI](https://github.com/serenity-bdd/serenity-core/tree/main/serenity-cli),
227
-
a Java program downloaded and managed by the [`@serenity-js/serenity-bdd`](/api/serenity-bdd/) module.
227
+
a Java program provided by the [`@serenity-js/serenity-bdd`](/api/serenity-bdd/) module.
228
228
229
229
To produce Serenity BDD reports, your test suite must:
230
-
- download the Serenity BDD CLI, by calling `serenity-bdd update` which caches the CLI `jar` locally
231
-
- produce intermediate Serenity BDD `.json` reports, by registering [`SerenityBDDReporter`](/api/serenity-bdd/class/SerenityBDDReporter/) as per the [configuration instructions](#configuring-serenityjs-and-protractor)
230
+
- produce intermediate Serenity BDD `.json` reports, by registering [`SerenityBDDReporter`](/api/serenity-bdd/class/SerenityBDDReporter/) as per the [configuration instructions](#configuring-serenityjs-and-webdriverio)
232
231
- invoke the Serenity BDD CLI when you want to produce the report, by calling `serenity-bdd run`
233
232
234
233
The pattern used by all the [Serenity/JS Project Templates](/handbook/getting-started/project-templates/) relies
235
-
on using:
236
-
- a [`postinstall`](https://docs.npmjs.com/cli/v9/using-npm/scripts#life-cycle-operation-order) NPM script to download the Serenity BDD CLI
234
+
on using the following Node modules:
237
235
-[`npm-failsafe`](https://www.npmjs.com/package/npm-failsafe) to run the reporting process even if the test suite itself has failed (which is precisely when you need test reports the most...).
238
236
-[`rimraf`](https://www.npmjs.com/package/rimraf) as a convenience method to remove any test reports left over from the previous run
Copy file name to clipboardExpand all lines: src/docs/handbook/getting-started/serenity-js-with-webdriverio.mdx
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -172,23 +172,20 @@ Learn more about:
172
172
## Producing Serenity BDD reports and living documentation
173
173
174
174
[Serenity BDD reports and living documentation](https://serenity-bdd.github.io/docs/reporting/the_serenity_reports) are generated by [Serenity BDD CLI](https://github.com/serenity-bdd/serenity-core/tree/main/serenity-cli),
175
-
a Java program downloaded and managed by the [`@serenity-js/serenity-bdd`](/api/serenity-bdd/) module.
175
+
a Java program provided by the [`@serenity-js/serenity-bdd`](/api/serenity-bdd/) module.
176
176
177
177
To produce Serenity BDD reports, your test suite must:
178
-
- download the Serenity BDD CLI, by calling `serenity-bdd update` which caches the CLI `jar` locally
179
178
- produce intermediate Serenity BDD `.json` reports, by registering [`SerenityBDDReporter`](/api/serenity-bdd/class/SerenityBDDReporter/) as per the [configuration instructions](#configuring-serenityjs-and-webdriverio)
180
179
- invoke the Serenity BDD CLI when you want to produce the report, by calling `serenity-bdd run`
181
180
182
181
The pattern used by all the [Serenity/JS Project Templates](/handbook/getting-started/project-templates/) relies
183
-
on using:
184
-
- a [`postinstall`](https://docs.npmjs.com/cli/v9/using-npm/scripts#life-cycle-operation-order) NPM script to download the Serenity BDD CLI
182
+
on using the following Node modules:
185
183
-[`npm-failsafe`](https://www.npmjs.com/package/npm-failsafe) to run the reporting process even if the test suite itself has failed (which is precisely when you need test reports the most...).
186
184
-[`rimraf`](https://www.npmjs.com/package/rimraf) as a convenience method to remove any test reports left over from the previous run
0 commit comments