podman
537 строк · 25.2 Кб
1/*
2Gomega is the Ginkgo BDD-style testing framework's preferred matcher library.
3
4The godoc documentation describes Gomega's API. More comprehensive documentation (with examples!) is available at http://onsi.github.io/gomega/
5
6Gomega on Github: http://github.com/onsi/gomega
7
8Learn more about Ginkgo online: http://onsi.github.io/ginkgo
9
10Ginkgo on Github: http://github.com/onsi/ginkgo
11
12Gomega is MIT-Licensed
13*/
14package gomega
15
16import (
17"errors"
18"fmt"
19"time"
20
21"github.com/onsi/gomega/internal"
22"github.com/onsi/gomega/types"
23)
24
25const GOMEGA_VERSION = "1.33.0"
26
27const nilGomegaPanic = `You are trying to make an assertion, but haven't registered Gomega's fail handler.
28If you're using Ginkgo then you probably forgot to put your assertion in an It().
29Alternatively, you may have forgotten to register a fail handler with RegisterFailHandler() or RegisterTestingT().
30Depending on your vendoring solution you may be inadvertently importing gomega and subpackages (e.g. ghhtp, gexec,...) from different locations.
31`
32
33// Gomega describes the essential Gomega DSL. This interface allows libraries
34// to abstract between the standard package-level function implementations
35// and alternatives like *WithT.
36//
37// The types in the top-level DSL have gotten a bit messy due to earlier deprecations that avoid stuttering
38// and due to an accidental use of a concrete type (*WithT) in an earlier release.
39//
40// As of 1.15 both the WithT and Ginkgo variants of Gomega are implemented by the same underlying object
41// however one (the Ginkgo variant) is exported as an interface (types.Gomega) whereas the other (the withT variant)
42// is shared as a concrete type (*WithT, which is aliased to *internal.Gomega). 1.15 did not clean this mess up to ensure
43// that declarations of *WithT in existing code are not broken by the upgrade to 1.15.
44type Gomega = types.Gomega
45
46// DefaultGomega supplies the standard package-level implementation
47var Default = Gomega(internal.NewGomega(internal.FetchDefaultDurationBundle()))
48
49// NewGomega returns an instance of Gomega wired into the passed-in fail handler.
50// You generally don't need to use this when using Ginkgo - RegisterFailHandler will wire up the global gomega
51// However creating a NewGomega with a custom fail handler can be useful in contexts where you want to use Gomega's
52// rich ecosystem of matchers without causing a test to fail. For example, to aggregate a series of potential failures
53// or for use in a non-test setting.
54func NewGomega(fail types.GomegaFailHandler) Gomega {
55return internal.NewGomega(internalGomega(Default).DurationBundle).ConfigureWithFailHandler(fail)
56}
57
58// WithT wraps a *testing.T and provides `Expect`, `Eventually`, and `Consistently` methods. This allows you to leverage
59// Gomega's rich ecosystem of matchers in standard `testing` test suites.
60//
61// Use `NewWithT` to instantiate a `WithT`
62//
63// As of 1.15 both the WithT and Ginkgo variants of Gomega are implemented by the same underlying object
64// however one (the Ginkgo variant) is exported as an interface (types.Gomega) whereas the other (the withT variant)
65// is shared as a concrete type (*WithT, which is aliased to *internal.Gomega). 1.15 did not clean this mess up to ensure
66// that declarations of *WithT in existing code are not broken by the upgrade to 1.15.
67type WithT = internal.Gomega
68
69// GomegaWithT is deprecated in favor of gomega.WithT, which does not stutter.
70type GomegaWithT = WithT
71
72// inner is an interface that allows users to provide a wrapper around Default. The wrapper
73// must implement the inner interface and return either the original Default or the result of
74// a call to NewGomega().
75type inner interface {
76Inner() Gomega
77}
78
79func internalGomega(g Gomega) *internal.Gomega {
80if v, ok := g.(inner); ok {
81return v.Inner().(*internal.Gomega)
82}
83return g.(*internal.Gomega)
84}
85
86// NewWithT takes a *testing.T and returns a `gomega.WithT` allowing you to use `Expect`, `Eventually`, and `Consistently` along with
87// Gomega's rich ecosystem of matchers in standard `testing` test suits.
88//
89// func TestFarmHasCow(t *testing.T) {
90// g := gomega.NewWithT(t)
91//
92// f := farm.New([]string{"Cow", "Horse"})
93// g.Expect(f.HasCow()).To(BeTrue(), "Farm should have cow")
94// }
95func NewWithT(t types.GomegaTestingT) *WithT {
96return internal.NewGomega(internalGomega(Default).DurationBundle).ConfigureWithT(t)
97}
98
99// NewGomegaWithT is deprecated in favor of gomega.NewWithT, which does not stutter.
100var NewGomegaWithT = NewWithT
101
102// RegisterFailHandler connects Ginkgo to Gomega. When a matcher fails
103// the fail handler passed into RegisterFailHandler is called.
104func RegisterFailHandler(fail types.GomegaFailHandler) {
105internalGomega(Default).ConfigureWithFailHandler(fail)
106}
107
108// RegisterFailHandlerWithT is deprecated and will be removed in a future release.
109// users should use RegisterFailHandler, or RegisterTestingT
110func RegisterFailHandlerWithT(_ types.GomegaTestingT, fail types.GomegaFailHandler) {
111fmt.Println("RegisterFailHandlerWithT is deprecated. Please use RegisterFailHandler or RegisterTestingT instead.")
112internalGomega(Default).ConfigureWithFailHandler(fail)
113}
114
115// RegisterTestingT connects Gomega to Golang's XUnit style
116// Testing.T tests. It is now deprecated and you should use NewWithT() instead to get a fresh instance of Gomega for each test.
117func RegisterTestingT(t types.GomegaTestingT) {
118internalGomega(Default).ConfigureWithT(t)
119}
120
121// InterceptGomegaFailures runs a given callback and returns an array of
122// failure messages generated by any Gomega assertions within the callback.
123// Execution continues after the first failure allowing users to collect all failures
124// in the callback.
125//
126// This is most useful when testing custom matchers, but can also be used to check
127// on a value using a Gomega assertion without causing a test failure.
128func InterceptGomegaFailures(f func()) []string {
129originalHandler := internalGomega(Default).Fail
130failures := []string{}
131internalGomega(Default).Fail = func(message string, callerSkip ...int) {
132failures = append(failures, message)
133}
134defer func() {
135internalGomega(Default).Fail = originalHandler
136}()
137f()
138return failures
139}
140
141// InterceptGomegaFailure runs a given callback and returns the first
142// failure message generated by any Gomega assertions within the callback, wrapped in an error.
143//
144// The callback ceases execution as soon as the first failed assertion occurs, however Gomega
145// does not register a failure with the FailHandler registered via RegisterFailHandler - it is up
146// to the user to decide what to do with the returned error
147func InterceptGomegaFailure(f func()) (err error) {
148originalHandler := internalGomega(Default).Fail
149internalGomega(Default).Fail = func(message string, callerSkip ...int) {
150err = errors.New(message)
151panic("stop execution")
152}
153
154defer func() {
155internalGomega(Default).Fail = originalHandler
156if e := recover(); e != nil {
157if err == nil {
158panic(e)
159}
160}
161}()
162
163f()
164return err
165}
166
167func ensureDefaultGomegaIsConfigured() {
168if !internalGomega(Default).IsConfigured() {
169panic(nilGomegaPanic)
170}
171}
172
173// Ω wraps an actual value allowing assertions to be made on it:
174//
175// Ω("foo").Should(Equal("foo"))
176//
177// If Ω is passed more than one argument it will pass the *first* argument to the matcher.
178// All subsequent arguments will be required to be nil/zero.
179//
180// This is convenient if you want to make an assertion on a method/function that returns
181// a value and an error - a common patter in Go.
182//
183// For example, given a function with signature:
184//
185// func MyAmazingThing() (int, error)
186//
187// Then:
188//
189// Ω(MyAmazingThing()).Should(Equal(3))
190//
191// Will succeed only if `MyAmazingThing()` returns `(3, nil)`
192//
193// Ω and Expect are identical
194func Ω(actual interface{}, extra ...interface{}) Assertion {
195ensureDefaultGomegaIsConfigured()
196return Default.Ω(actual, extra...)
197}
198
199// Expect wraps an actual value allowing assertions to be made on it:
200//
201// Expect("foo").To(Equal("foo"))
202//
203// If Expect is passed more than one argument it will pass the *first* argument to the matcher.
204// All subsequent arguments will be required to be nil/zero.
205//
206// This is convenient if you want to make an assertion on a method/function that returns
207// a value and an error - a common pattern in Go.
208//
209// For example, given a function with signature:
210//
211// func MyAmazingThing() (int, error)
212//
213// Then:
214//
215// Expect(MyAmazingThing()).Should(Equal(3))
216//
217// Will succeed only if `MyAmazingThing()` returns `(3, nil)`
218//
219// Expect and Ω are identical
220func Expect(actual interface{}, extra ...interface{}) Assertion {
221ensureDefaultGomegaIsConfigured()
222return Default.Expect(actual, extra...)
223}
224
225// ExpectWithOffset wraps an actual value allowing assertions to be made on it:
226//
227// ExpectWithOffset(1, "foo").To(Equal("foo"))
228//
229// Unlike `Expect` and `Ω`, `ExpectWithOffset` takes an additional integer argument
230// that is used to modify the call-stack offset when computing line numbers. It is
231// the same as `Expect(...).WithOffset`.
232//
233// This is most useful in helper functions that make assertions. If you want Gomega's
234// error message to refer to the calling line in the test (as opposed to the line in the helper function)
235// set the first argument of `ExpectWithOffset` appropriately.
236func ExpectWithOffset(offset int, actual interface{}, extra ...interface{}) Assertion {
237ensureDefaultGomegaIsConfigured()
238return Default.ExpectWithOffset(offset, actual, extra...)
239}
240
241/*
242Eventually enables making assertions on asynchronous behavior.
243
244Eventually checks that an assertion *eventually* passes. Eventually blocks when called and attempts an assertion periodically until it passes or a timeout occurs. Both the timeout and polling interval are configurable as optional arguments.
245The first optional argument is the timeout (which defaults to 1s), the second is the polling interval (which defaults to 10ms). Both intervals can be specified as time.Duration, parsable duration strings or floats/integers (in which case they are interpreted as seconds). In addition an optional context.Context can be passed in - Eventually will keep trying until either the timeout expires or the context is cancelled, whichever comes first.
246
247Eventually works with any Gomega compatible matcher and supports making assertions against three categories of actual value:
248
249**Category 1: Making Eventually assertions on values**
250
251There are several examples of values that can change over time. These can be passed in to Eventually and will be passed to the matcher repeatedly until a match occurs. For example:
252
253c := make(chan bool)
254go DoStuff(c)
255Eventually(c, "50ms").Should(BeClosed())
256
257will poll the channel repeatedly until it is closed. In this example `Eventually` will block until either the specified timeout of 50ms has elapsed or the channel is closed, whichever comes first.
258
259Several Gomega libraries allow you to use Eventually in this way. For example, the gomega/gexec package allows you to block until a *gexec.Session exits successfully via:
260
261Eventually(session).Should(gexec.Exit(0))
262
263And the gomega/gbytes package allows you to monitor a streaming *gbytes.Buffer until a given string is seen:
264
265Eventually(buffer).Should(gbytes.Say("hello there"))
266
267In these examples, both `session` and `buffer` are designed to be thread-safe when polled by the `Exit` and `Say` matchers. This is not true in general of most raw values, so while it is tempting to do something like:
268
269// THIS IS NOT THREAD-SAFE
270var s *string
271go mutateStringEventually(s)
272Eventually(s).Should(Equal("I've changed"))
273
274this will trigger Go's race detector as the goroutine polling via Eventually will race over the value of s with the goroutine mutating the string. For cases like this you can use channels or introduce your own locking around s by passing Eventually a function.
275
276**Category 2: Make Eventually assertions on functions**
277
278Eventually can be passed functions that **return at least one value**. When configured this way, Eventually will poll the function repeatedly and pass the first returned value to the matcher.
279
280For example:
281
282Eventually(func() int {
283return client.FetchCount()
284}).Should(BeNumerically(">=", 17))
285
286will repeatedly poll client.FetchCount until the BeNumerically matcher is satisfied. (Note that this example could have been written as Eventually(client.FetchCount).Should(BeNumerically(">=", 17)))
287
288If multiple values are returned by the function, Eventually will pass the first value to the matcher and require that all others are zero-valued. This allows you to pass Eventually a function that returns a value and an error - a common pattern in Go.
289
290For example, consider a method that returns a value and an error:
291
292func FetchFromDB() (string, error)
293
294Then
295
296Eventually(FetchFromDB).Should(Equal("got it"))
297
298will pass only if and when the returned error is nil *and* the returned string satisfies the matcher.
299
300Eventually can also accept functions that take arguments, however you must provide those arguments using .WithArguments(). For example, consider a function that takes a user-id and makes a network request to fetch a full name:
301
302func FetchFullName(userId int) (string, error)
303
304You can poll this function like so:
305
306Eventually(FetchFullName).WithArguments(1138).Should(Equal("Wookie"))
307
308It is important to note that the function passed into Eventually is invoked *synchronously* when polled. Eventually does not (in fact, it cannot) kill the function if it takes longer to return than Eventually's configured timeout. A common practice here is to use a context. Here's an example that combines Ginkgo's spec timeout support with Eventually:
309
310It("fetches the correct count", func(ctx SpecContext) {
311Eventually(ctx, func() int {
312return client.FetchCount(ctx, "/users")
313}).Should(BeNumerically(">=", 17))
314}, SpecTimeout(time.Second))
315
316you an also use Eventually().WithContext(ctx) to pass in the context. Passed-in contexts play nicely with passed-in arguments as long as the context appears first. You can rewrite the above example as:
317
318It("fetches the correct count", func(ctx SpecContext) {
319Eventually(client.FetchCount).WithContext(ctx).WithArguments("/users").Should(BeNumerically(">=", 17))
320}, SpecTimeout(time.Second))
321
322Either way the context passd to Eventually is also passed to the underlying function. Now, when Ginkgo cancels the context both the FetchCount client and Gomega will be informed and can exit.
323
324**Category 3: Making assertions _in_ the function passed into Eventually**
325
326When testing complex systems it can be valuable to assert that a _set_ of assertions passes Eventually. Eventually supports this by accepting functions that take a single Gomega argument and return zero or more values.
327
328Here's an example that makes some assertions and returns a value and error:
329
330Eventually(func(g Gomega) (Widget, error) {
331ids, err := client.FetchIDs()
332g.Expect(err).NotTo(HaveOccurred())
333g.Expect(ids).To(ContainElement(1138))
334return client.FetchWidget(1138)
335}).Should(Equal(expectedWidget))
336
337will pass only if all the assertions in the polled function pass and the return value satisfied the matcher.
338
339Eventually also supports a special case polling function that takes a single Gomega argument and returns no values. Eventually assumes such a function is making assertions and is designed to work with the Succeed matcher to validate that all assertions have passed.
340For example:
341
342Eventually(func(g Gomega) {
343model, err := client.Find(1138)
344g.Expect(err).NotTo(HaveOccurred())
345g.Expect(model.Reticulate()).To(Succeed())
346g.Expect(model.IsReticulated()).To(BeTrue())
347g.Expect(model.Save()).To(Succeed())
348}).Should(Succeed())
349
350will rerun the function until all assertions pass.
351
352You can also pass additional arguments to functions that take a Gomega. The only rule is that the Gomega argument must be first. If you also want to pass the context attached to Eventually you must ensure that is the second argument. For example:
353
354Eventually(func(g Gomega, ctx context.Context, path string, expected ...string){
355tok, err := client.GetToken(ctx)
356g.Expect(err).NotTo(HaveOccurred())
357
358elements, err := client.Fetch(ctx, tok, path)
359g.Expect(err).NotTo(HaveOccurred())
360g.Expect(elements).To(ConsistOf(expected))
361}).WithContext(ctx).WithArguments("/names", "Joe", "Jane", "Sam").Should(Succeed())
362
363You can ensure that you get a number of consecutive successful tries before succeeding using `MustPassRepeatedly(int)`. For Example:
364
365int count := 0
366Eventually(func() bool {
367count++
368return count > 2
369}).MustPassRepeatedly(2).Should(BeTrue())
370// Because we had to wait for 2 calls that returned true
371Expect(count).To(Equal(3))
372
373Finally, in addition to passing timeouts and a context to Eventually you can be more explicit with Eventually's chaining configuration methods:
374
375Eventually(..., "1s", "2s", ctx).Should(...)
376
377is equivalent to
378
379Eventually(...).WithTimeout(time.Second).WithPolling(2*time.Second).WithContext(ctx).Should(...)
380*/
381func Eventually(actualOrCtx interface{}, args ...interface{}) AsyncAssertion {
382ensureDefaultGomegaIsConfigured()
383return Default.Eventually(actualOrCtx, args...)
384}
385
386// EventuallyWithOffset operates like Eventually but takes an additional
387// initial argument to indicate an offset in the call stack. This is useful when building helper
388// functions that contain matchers. To learn more, read about `ExpectWithOffset`.
389//
390// `EventuallyWithOffset` is the same as `Eventually(...).WithOffset`.
391//
392// `EventuallyWithOffset` specifying a timeout interval (and an optional polling interval) are
393// the same as `Eventually(...).WithOffset(...).WithTimeout` or
394// `Eventually(...).WithOffset(...).WithTimeout(...).WithPolling`.
395func EventuallyWithOffset(offset int, actualOrCtx interface{}, args ...interface{}) AsyncAssertion {
396ensureDefaultGomegaIsConfigured()
397return Default.EventuallyWithOffset(offset, actualOrCtx, args...)
398}
399
400/*
401Consistently, like Eventually, enables making assertions on asynchronous behavior.
402
403Consistently blocks when called for a specified duration. During that duration Consistently repeatedly polls its matcher and ensures that it is satisfied. If the matcher is consistently satisfied, then Consistently will pass. Otherwise Consistently will fail.
404
405Both the total waiting duration and the polling interval are configurable as optional arguments. The first optional argument is the duration that Consistently will run for (defaults to 100ms), and the second argument is the polling interval (defaults to 10ms). As with Eventually, these intervals can be passed in as time.Duration, parsable duration strings or an integer or float number of seconds. You can also pass in an optional context.Context - Consistently will exit early (with a failure) if the context is cancelled before the waiting duration expires.
406
407Consistently accepts the same three categories of actual as Eventually, check the Eventually docs to learn more.
408
409Consistently is useful in cases where you want to assert that something *does not happen* for a period of time. For example, you may want to assert that a goroutine does *not* send data down a channel. In this case you could write:
410
411Consistently(channel, "200ms").ShouldNot(Receive())
412
413This will block for 200 milliseconds and repeatedly check the channel and ensure nothing has been received.
414*/
415func Consistently(actualOrCtx interface{}, args ...interface{}) AsyncAssertion {
416ensureDefaultGomegaIsConfigured()
417return Default.Consistently(actualOrCtx, args...)
418}
419
420// ConsistentlyWithOffset operates like Consistently but takes an additional
421// initial argument to indicate an offset in the call stack. This is useful when building helper
422// functions that contain matchers. To learn more, read about `ExpectWithOffset`.
423//
424// `ConsistentlyWithOffset` is the same as `Consistently(...).WithOffset` and
425// optional `WithTimeout` and `WithPolling`.
426func ConsistentlyWithOffset(offset int, actualOrCtx interface{}, args ...interface{}) AsyncAssertion {
427ensureDefaultGomegaIsConfigured()
428return Default.ConsistentlyWithOffset(offset, actualOrCtx, args...)
429}
430
431/*
432StopTrying can be used to signal to Eventually and Consistentlythat they should abort and stop trying. This always results in a failure of the assertion - and the failure message is the content of the StopTrying signal.
433
434You can send the StopTrying signal by either returning StopTrying("message") as an error from your passed-in function _or_ by calling StopTrying("message").Now() to trigger a panic and end execution.
435
436You can also wrap StopTrying around an error with `StopTrying("message").Wrap(err)` and can attach additional objects via `StopTrying("message").Attach("description", object). When rendered, the signal will include the wrapped error and any attached objects rendered using Gomega's default formatting.
437
438Here are a couple of examples. This is how you might use StopTrying() as an error to signal that Eventually should stop:
439
440playerIndex, numPlayers := 0, 11
441Eventually(func() (string, error) {
442if playerIndex == numPlayers {
443return "", StopTrying("no more players left")
444}
445name := client.FetchPlayer(playerIndex)
446playerIndex += 1
447return name, nil
448}).Should(Equal("Patrick Mahomes"))
449
450And here's an example where `StopTrying().Now()` is called to halt execution immediately:
451
452Eventually(func() []string {
453names, err := client.FetchAllPlayers()
454if err == client.IRRECOVERABLE_ERROR {
455StopTrying("Irrecoverable error occurred").Wrap(err).Now()
456}
457return names
458}).Should(ContainElement("Patrick Mahomes"))
459*/
460var StopTrying = internal.StopTrying
461
462/*
463TryAgainAfter(<duration>) allows you to adjust the polling interval for the _next_ iteration of `Eventually` or `Consistently`. Like `StopTrying` you can either return `TryAgainAfter` as an error or trigger it immedieately with `.Now()`
464
465When `TryAgainAfter(<duration>` is triggered `Eventually` and `Consistently` will wait for that duration. If a timeout occurs before the next poll is triggered both `Eventually` and `Consistently` will always fail with the content of the TryAgainAfter message. As with StopTrying you can `.Wrap()` and error and `.Attach()` additional objects to `TryAgainAfter`.
466*/
467var TryAgainAfter = internal.TryAgainAfter
468
469/*
470PollingSignalError is the error returned by StopTrying() and TryAgainAfter()
471*/
472type PollingSignalError = internal.PollingSignalError
473
474// SetDefaultEventuallyTimeout sets the default timeout duration for Eventually. Eventually will repeatedly poll your condition until it succeeds, or until this timeout elapses.
475func SetDefaultEventuallyTimeout(t time.Duration) {
476Default.SetDefaultEventuallyTimeout(t)
477}
478
479// SetDefaultEventuallyPollingInterval sets the default polling interval for Eventually.
480func SetDefaultEventuallyPollingInterval(t time.Duration) {
481Default.SetDefaultEventuallyPollingInterval(t)
482}
483
484// SetDefaultConsistentlyDuration sets the default duration for Consistently. Consistently will verify that your condition is satisfied for this long.
485func SetDefaultConsistentlyDuration(t time.Duration) {
486Default.SetDefaultConsistentlyDuration(t)
487}
488
489// SetDefaultConsistentlyPollingInterval sets the default polling interval for Consistently.
490func SetDefaultConsistentlyPollingInterval(t time.Duration) {
491Default.SetDefaultConsistentlyPollingInterval(t)
492}
493
494// AsyncAssertion is returned by Eventually and Consistently and polls the actual value passed into Eventually against
495// the matcher passed to the Should and ShouldNot methods.
496//
497// Both Should and ShouldNot take a variadic optionalDescription argument.
498// This argument allows you to make your failure messages more descriptive.
499// If a single argument of type `func() string` is passed, this function will be lazily evaluated if a failure occurs
500// and the returned string is used to annotate the failure message.
501// Otherwise, this argument is passed on to fmt.Sprintf() and then used to annotate the failure message.
502//
503// Both Should and ShouldNot return a boolean that is true if the assertion passed and false if it failed.
504//
505// Example:
506//
507// Eventually(myChannel).Should(Receive(), "Something should have come down the pipe.")
508// Consistently(myChannel).ShouldNot(Receive(), func() string { return "Nothing should have come down the pipe." })
509type AsyncAssertion = types.AsyncAssertion
510
511// GomegaAsyncAssertion is deprecated in favor of AsyncAssertion, which does not stutter.
512type GomegaAsyncAssertion = types.AsyncAssertion
513
514// Assertion is returned by Ω and Expect and compares the actual value to the matcher
515// passed to the Should/ShouldNot and To/ToNot/NotTo methods.
516//
517// Typically Should/ShouldNot are used with Ω and To/ToNot/NotTo are used with Expect
518// though this is not enforced.
519//
520// All methods take a variadic optionalDescription argument.
521// This argument allows you to make your failure messages more descriptive.
522// If a single argument of type `func() string` is passed, this function will be lazily evaluated if a failure occurs
523// and the returned string is used to annotate the failure message.
524// Otherwise, this argument is passed on to fmt.Sprintf() and then used to annotate the failure message.
525//
526// All methods return a bool that is true if the assertion passed and false if it failed.
527//
528// Example:
529//
530// Ω(farm.HasCow()).Should(BeTrue(), "Farm %v should have a cow", farm)
531type Assertion = types.Assertion
532
533// GomegaAssertion is deprecated in favor of Assertion, which does not stutter.
534type GomegaAssertion = types.Assertion
535
536// OmegaMatcher is deprecated in favor of the better-named and better-organized types.GomegaMatcher but sticks around to support existing code that uses it
537type OmegaMatcher = types.GomegaMatcher
538