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: docs/index.md
+2Lines changed: 2 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -5340,6 +5340,8 @@ Since `GinkgoT()` implements `Cleanup()` (using `DeferCleanup()` under the hood)
5340
5340
5341
5341
When using Gomock you may want to run `ginkgo` with the `-trace` flag to print out stack traces forfailures which will help you trace down where,in your code, invalid calls occurred.
5342
5342
5343
+
`GinkgoT()` also provides additional methods that are Ginkgo-specific. This allows rich third-party integrations to be built on top of Ginkgo - with GinkgoT() serving as a single connection point.
5344
+
5343
5345
### IDE Support
5344
5346
Ginkgo works best from the command-line, and [`ginkgo watch`](#watching-for-changes) makes it easy to rerun tests on the command line whenever changes are detected.
GinkgoT() implements an interface analogous to *testing.T and can be used with
7
-
third-party libraries that accept *testing.T through an interface.
8
+
GinkgoT() implements an interface that allows third party libraries to integrate with and build on top of Ginkgo.
9
+
10
+
GinkgoT() is analogous to *testing.T and implements the majority of *testing.T's methods. It can be typically be used a a drop-in replacement with third-party libraries that accept *testing.T through an interface.
8
11
9
12
GinkgoT() takes an optional offset argument that can be used to get the
10
13
correct line number associated with the failure - though you do not need to use this if you call GinkgoHelper() or GinkgoT().Helper() appropriately
11
14
12
15
You can learn more here: https://onsi.github.io/ginkgo/#using-third-party-libraries
0 commit comments