Lines Matching refs:lit

1 lit - LLVM Integrated Tester
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.
57  test suites, instead of :file:`lit.cfg` and :file:`lit.site.cfg`.
102  When this option is enabled, :program:`lit` will also automatically provide a
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.
161 :program:`lit` will exit with an exit code of 1 if there are any FAIL or XPASS
171 The inputs passed to :program:`lit` can be either individual tests, or entire
172 directories or hierarchies of tests to run.  When :program:`lit` starts up, the
176 In the :program:`lit` model, every test must exist inside some *test suite*.
177 :program:`lit` resolves the inputs specified on the command line to test suites
178 by searching upwards from the input path until it finds a :file:`lit.cfg` or
179 :file:`lit.site.cfg` file.  These files serve as both a marker of test suites
180 and as configuration files which :program:`lit` loads in order to understand
183 Once :program:`lit` has mapped the inputs into test suites it traverses the
189 interpreted.  In addition, :program:`lit` always identifies tests by the test
191 appropriately configured projects, this allows :program:`lit` to provide
240 This section describes the :program:`lit` testing architecture for users interested in
241 creating a new :program:`lit` testing implementation, or extending an existing one.
243 :program:`lit` proper is primarily an infrastructure for discovering and running
245 tests. :program:`lit` itself doesn't know how to run tests, rather this logic is
255 :program:`lit` identifies test suites as directories containing ``lit.cfg`` or
256 ``lit.site.cfg`` files (see also :option:`--config-prefix`).  Test suites are
265 **lit**
267  The global **lit** configuration object (a *LitConfig* instance), which defines
283  format available from the *lit.formats* module.
295  **suffixes** For **lit** test formats which scan directories for tests, this
298  **substitutions** For **lit** test formats which substitute variables into a test
307  **root** The root configuration.  This is the top-most :program:`lit` configuration in
325 Once test suites are located, :program:`lit` recursively traverses the source
326 directory (following *test_source_root*) looking for tests.  When :program:`lit`
343 When :program:`lit` loads a subdirectory in a test suite, it instantiates a
346 test configuration is cloned :program:`lit` checks for a *lit.local.cfg* file
356 The :program:`lit` output for a test run conforms to the following schema, in
408 The :program:`lit` distribution contains several example implementations of