HomeSort by relevance Sort by last modified time
    Searched refs:subtests (Results 1 - 10 of 10) sorted by null

  /external/ltp/tools/pounder21/
pounder 36 Usage: ./pounder [-g logdir] [-x] [-d duration] [-n ipaddr] [-m max_failures] [-f] [-h|-u|-r|-k|-l|-e subtests|-i subtests|-c scheduler] [-s]
40 All subtests to be packaged with this scheduler must first be placed in the pounder/tests folder.
49 -l List (both included and excluded) subtests that came with the test scheduler
50 -e subtests Exclude subtests from next pounder run
51 -i subtests Include previously excluded subtests in the next pounder run
54 run "./pounder" to run all subtests
95 echo "$i is not a subtest included in the current scheduler. Use ./pounder -l for list of valid, excludable subtests.
    [all...]
  /prebuilts/go/darwin-x86/src/testing/
match_test.go 92 // Behavior without subtests.
101 // with subtests
115 // subtests only
testing.go 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
    [all...]
sub_test.go 233 // Otherwise, if one runs parallel subtests in sequential tests that are
234 // itself subtests of parallel tests, the counts can get askew.
252 // Otherwise, if one runs parallel subtests in sequential tests that are
253 // itself subtests of parallel tests, the counts can get askew.
494 // All tests are run as subtests
match.go 15 // matcher sanitizes, uniques, and filters names of subtests and subbenchmarks.
  /prebuilts/go/linux-x86/src/testing/
match_test.go 92 // Behavior without subtests.
101 // with subtests
115 // subtests only
testing.go 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
    [all...]
sub_test.go 233 // Otherwise, if one runs parallel subtests in sequential tests that are
234 // itself subtests of parallel tests, the counts can get askew.
252 // Otherwise, if one runs parallel subtests in sequential tests that are
253 // itself subtests of parallel tests, the counts can get askew.
494 // All tests are run as subtests
match.go 15 // matcher sanitizes, uniques, and filters names of subtests and subbenchmarks.
  /external/autotest/client/site_tests/graphics_Stress/
graphics_Stress.py 191 subtests = { variable in class:graphics_Stress
220 self.subtests[subtest](self)

Completed in 3319 milliseconds