Skip to content

Commit 93de676

Browse files
authoredMar 6, 2023
Improve Documentation and fix typo (#1158)
1 parent 2470852 commit 93de676

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed
 

‎docs/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3429,7 +3429,7 @@ The closure passed to `ReportBeforeSuite` is called exactly once at the beginnin
34293429

34303430
Finally, and most importantly, when running in parallel both `ReportBeforeSuite` and `ReportAfterSuite` **only run on process #1**. Gingko guarantess that no other processes will start running their specs until after `ReportBeforeSuite` on process #1 has completed. Similarly, Ginkgo will only run `ReportAfterSuite` on process #1 after all other processes have finished and exited. Ginkgo provides a sinle `Report` that aggregates the `SpecReports` from all processes. This allows you to perform any custom suite reporting in one place after all specs have run and not have to worry about aggregating information across multiple parallel processes.
34313431

3432-
Givne all this, we can rewrite our invalid `ReportAfterEach` example from above into a valid `ReportAfterSuite` example:
3432+
Given all this, we can rewrite our invalid `ReportAfterEach` example from above into a valid `ReportAfterSuite` example:
34333433

34343434
```go
34353435
ReportAfterSuite("custom report", func(report Report) {

0 commit comments

Comments
 (0)