Lines Matching full:suite

75  string if not given).  The meaning and use of these parameters is test suite
160  suite take the most time to execute.
259   suite. The environment variable ``LIT_XFAIL`` can be also used in place of
263   A test name can specified as a file name relative to the test suite directory.
331 In the :program:`lit` model, every test must exist inside some *test suite*.
336 how to find and run the tests inside the test suite.
343 allowing the test suite configuration to control exactly how tests are
345 suite they are in, and their relative path inside the test suite.  For
369  suite.
417 suite*.  Test suites serve to define the format of the tests they contain, the
426 Once a test suite is discovered, its config file is loaded.  Config files
438  This is the config object (a *TestingConfig* instance) for the test suite,
443  **name** *[required]* The name of the test suite, for use in reports and
447  discover and run tests in the test suite.  Generally this will be a builtin test
450  **test_source_root** The filesystem path to the test suite root.  For out-of-dir
453  **test_exec_root** For out-of-dir builds, the path to the test suite root inside
458  tests in the suite.
475  containing the test suite, or None.
492 enters a sub-directory, it first checks to see if a nested test suite is
493 defined in that directory.  If so, it loads that test suite recursively,
497 Tests are identified by the test suite they are contained within, and the
498 relative path inside that suite.  Note that the relative path may not refer to
508 When :program:`lit` loads a subdirectory in a test suite, it instantiates a
510 --- the root of this configuration chain will always be a test suite.  Once the