Lines Matching full:program
7 :program:`lit` [*options*] [*tests*]
12 :program:`lit` is a portable tool for executing LLVM and Clang style test
14 :program:`lit` is designed to be a lightweight testing tool with as simple a
17 :program:`lit` should be run with one or more *tests* to run specified on the
22 tests have been run :program:`lit` will print summary information on the number
24 :program:`lit` program will execute with a non-zero exit code if any tests
27 By default :program:`lit` will use a succinct progress display and will only
29 options controlling the :program:`lit` progress display and output.
31 :program:`lit` also includes a number of options for controlling how tests are
35 Finally, :program:`lit` also supports additional options for only running a
39 Users interested in the :program:`lit` architecture or designing a
40 :program:`lit` testing implementation should see :ref:`lit-infrastructure`.
47 Show the :program:`lit` help message.
100 will cause the program to exit with a non-zero status.
102 When this option is enabled, :program:`lit` will also automatically provide a
109 :program:`valgrind` itself.
114 enabled, :program:`lit` will also automatically provide a "``vg_leak``"
147 Run :program:`lit` in debug mode, for debugging configuration issues and
148 :program:`lit` itself.
162 :program:`lit` will exit with an exit code of 1 if there are any FAIL or XPASS
164 for non-test related failures (for example a user error or an internal program
172 The inputs passed to :program:`lit` can be either individual tests, or entire
173 directories or hierarchies of tests to run. When :program:`lit` starts up, the
177 In the :program:`lit` model, every test must exist inside some *test suite*.
178 :program:`lit` resolves the inputs specified on the command line to test suites
181 and as configuration files which :program:`lit` loads in order to understand
184 Once :program:`lit` has mapped the inputs into test suites it traverses the
190 interpreted. In addition, :program:`lit` always identifies tests by the test
192 appropriately configured projects, this allows :program:`lit` to provide
241 This section describes the :program:`lit` testing architecture for users interested in
242 creating a new :program:`lit` testing implementation, or extending an existing one.
244 :program:`lit` proper is primarily an infrastructure for discovering and running
246 tests. :program:`lit` itself doesn't know how to run tests, rather this logic is
256 :program:`lit` identifies test suites as directories containing ``lit.cfg`` or
308 **root** The root configuration. This is the top-most :program:`lit` configuration in
326 Once test suites are located, :program:`lit` recursively traverses the source
327 directory (following *test_source_root*) looking for tests. When :program:`lit`
344 When :program:`lit` loads a subdirectory in a test suite, it instantiates a
347 test configuration is cloned :program:`lit` checks for a *lit.local.cfg* file
357 The :program:`lit` output for a test run conforms to the following schema, in
409 The :program:`lit` distribution contains several example implementations of
