Lines Matching full:suite
62 string if not given). The meaning and use of these parameters is test suite
122 suite take the most time to execute. Note that this option is most useful
177 In the :program:`lit` model, every test must exist inside some *test suite*.
182 how to find and run the tests inside the test suite.
189 allowing the test suite configuration to control exactly how tests are
191 suite they are in, and their relative path inside the test suite. For
210 suite.
253 suite*. Test suites serve to define the format of the tests they contain, the
262 Once a test suite is discovered, its config file is loaded. Config files
274 This is the config object (a *TestingConfig* instance) for the test suite,
279 **name** *[required]* The name of the test suite, for use in reports and
283 discover and run tests in the test suite. Generally this will be a builtin test
286 **test_source_root** The filesystem path to the test suite root. For out-of-dir
289 **test_exec_root** For out-of-dir builds, the path to the test suite root inside
294 tests in the suite.
306 containing the test suite, or None.
312 suite, to allow local configuration on a per-directory basis. The *on_clone*
328 enters a sub-directory, it first checks to see if a nested test suite is
329 defined in that directory. If so, it loads that test suite recursively,
333 Tests are identified by the test suite they are contained within, and the
334 relative path inside that suite. Note that the relative path may not refer to
344 When :program:`lit` loads a subdirectory in a test suite, it instantiates a
346 --- the root of this configuration chain will always be a test suite. Once the
