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
This does not work for the e2e tests, since go test -list works only for top level tests, and all our tests are sub tests under single top level TestSuites test. This makes testing much harder since there is no way to find which tests we already have.
The only way to discover the tests is the run all of them, which takes about 10 minutes:
Using go test, one can list tests using:
This does not work for the e2e tests, since
go test -list
works only for top level tests, and all our tests are sub tests under single top level TestSuites test. This makes testing much harder since there is no way to find which tests we already have.The only way to discover the tests is the run all of them, which takes about 10 minutes:
When looking in test files (e.g. exhaustive_suite_test.go) we don't see any tests, since even the sub tests are constructed dynyamically:
Possible fix
Remove the concept of test suites - it is harmful
A test suites in go is the regex selecting group of tests when running `go test -run {suite-regex}. For example:
Running basic suite:
go test -run TestBasic
Running validation suite:
go test -run TestValidation
Create all tests statically e.g.
With this
The text was updated successfully, but these errors were encountered: