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
Problem: When writing tests that take >3 minutes each, the tests should be parallelized. If your tests are also amenable to being written in a table-driven format, you have to resort to goroutines to make things parallel (rather than t.Parallel()). If you do that, then your logs get interleaved, and go test run .* can't help you out to isolate particular failures, and you lose the benefits of t.Parallel(), like setting number of parallel lines at CLI, ensuring non-parallel ones don't run with it...
Solution: A proposed solution discussed involves the ability for tests to create their own subtests.
The text was updated successfully, but these errors were encountered:
Problem: When writing tests that take >3 minutes each, the tests should be parallelized. If your tests are also amenable to being written in a table-driven format, you have to resort to goroutines to make things parallel (rather than
t.Parallel()
). If you do that, then your logs get interleaved, andgo test run .*
can't help you out to isolate particular failures, and you lose the benefits oft.Parallel()
, like setting number of parallel lines at CLI, ensuring non-parallel ones don't run with it...Solution: A proposed solution discussed involves the ability for tests to create their own subtests.
The text was updated successfully, but these errors were encountered: