Lines Matching refs:subtests
121 // Subtests and Sub-benchmarks
123 // The Run methods of T and B allow defining subtests and sub-benchmarks,
142 // elements, such as subtests, the argument is itself slash-separated, with
149 // go test -run Foo/A= # For top-level tests matching "Foo", run subtests matching "A=".
150 // go test -run /A=1 # For all top-level tests, run subtests matching "A=1".
152 // Subtests can also be used to control parallelism. A parent test will only
153 // complete once all of its subtests complete. In this example, all tests are
167 // Run does not return until parallel subtests have completed, providing a way
266 ran bool // Test or benchmark (or one of its subtests) was executed.
270 done bool // Test is finished and all subtests have completed.
279 barrier chan bool // To signal parallel subtests they may start.
281 sub []*T // Queue of subtests to be run in parallel.
417 context *testContext // For running tests and subtests.
626 // Run parallel subtests.
629 // Release the parallel subtests.
631 // Wait for subtests to complete.
644 t.report() // Report after all subtests have finished.
662 // Run will block until all its parallel subtests have completed.
713 // This does not include tests that are waiting for subtests to complete.
