1 lit - LLVM Integrated Tester
2 ============================
7 :program:`lit` [*options*] [*tests*]
12 :program:`lit` is a portable tool for executing LLVM and Clang style test
13 suites, summarizing their results, and providing indication of failures.
14 :program:`lit` is designed to be a lightweight testing tool with as simple a
15 user interface as possible.
17 :program:`lit` should be run with one or more *tests* to run specified on the
18 command line. Tests can be either individual test files or directories to
19 search for tests (see :ref:`test-discovery`).
21 Each specified test will be executed (potentially in parallel) and once all
22 tests have been run :program:`lit` will print summary information on the number
23 of tests which passed or failed (see :ref:`test-status-results`). The
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
28 print summary information for test failures. See :ref:`output-options` for
29 options controlling the :program:`lit` progress display and output.
31 :program:`lit` also includes a number of options for controlling how tests are
32 executed (specific features may depend on the particular test format). See
33 :ref:`execution-options` for more information.
35 Finally, :program:`lit` also supports additional options for only running a
36 subset of the options specified on the command line, see
37 :ref:`selection-options` for more information.
39 Users interested in the :program:`lit` architecture or designing a
40 :program:`lit` testing implementation should see :ref:`lit-infrastructure`.
45 .. option:: -h, --help
47 Show the :program:`lit` help message.
49 .. option:: -j N, --threads=N
51 Run ``N`` tests in parallel. By default, this is automatically chosen to
52 match the number of detected available CPUs.
54 .. option:: --config-prefix=NAME
56 Search for :file:`{NAME}.cfg` and :file:`{NAME}.site.cfg` when searching for
57 test suites, instead of :file:`lit.cfg` and :file:`lit.site.cfg`.
59 .. option:: --param NAME, --param NAME=VALUE
61 Add a user defined parameter ``NAME`` with the given ``VALUE`` (or the empty
62 string if not given). The meaning and use of these parameters is test suite
70 .. option:: -q, --quiet
72 Suppress any output except for test failures.
74 .. option:: -s, --succinct
76 Show less output, for example don't show information on tests that pass.
78 .. option:: -v, --verbose
80 Show more information on test failures, for example the entire test output
81 instead of just the test result.
83 .. option:: --no-progress-bar
85 Do not use curses based progress bar.
87 .. option:: --show-unsupported
89 Show the names of unsupported tests.
91 .. option:: --show-xfail
93 Show the names of tests that were expected to fail.
95 .. _execution-options:
100 .. option:: --path=PATH
102 Specify an additional ``PATH`` to use when searching for executables in tests.
106 Run individual tests under valgrind (using the memcheck tool). The
107 ``--error-exitcode`` argument for valgrind is used so that valgrind failures
108 will cause the program to exit with a non-zero status.
110 When this option is enabled, :program:`lit` will also automatically provide a
111 "``valgrind``" feature that can be used to conditionally disable (or expect
112 failure in) certain tests.
114 .. option:: --vg-arg=ARG
116 When :option:`--vg` is used, specify an additional argument to pass to
117 :program:`valgrind` itself.
119 .. option:: --vg-leak
121 When :option:`--vg` is used, enable memory leak checks. When this option is
122 enabled, :program:`lit` will also automatically provide a "``vg_leak``"
123 feature that can be used to conditionally disable (or expect failure in)
126 .. option:: --time-tests
128 Track the wall time individual tests take to execute and includes the results
129 in the summary output. This is useful for determining which tests in a test
130 suite take the most time to execute. Note that this option is most useful
133 .. _selection-options:
138 .. option:: --max-tests=N
140 Run at most ``N`` tests and then terminate.
142 .. option:: --max-time=N
144 Spend at most ``N`` seconds (approximately) running tests and then terminate.
146 .. option:: --shuffle
148 Run the tests in a random order.
155 Run :program:`lit` in debug mode, for debugging configuration issues and
156 :program:`lit` itself.
158 .. option:: --show-suites
160 List the discovered test suites and exit.
162 .. option:: --show-tests
164 List all of the the discovered tests and exit.
169 :program:`lit` will exit with an exit code of 1 if there are any FAIL or XPASS
170 results. Otherwise, it will exit with the status 0. Other exit codes are used
171 for non-test related failures (for example a user error or an internal program
179 The inputs passed to :program:`lit` can be either individual tests, or entire
180 directories or hierarchies of tests to run. When :program:`lit` starts up, the
181 first thing it does is convert the inputs into a complete list of tests to run
182 as part of *test discovery*.
184 In the :program:`lit` model, every test must exist inside some *test suite*.
185 :program:`lit` resolves the inputs specified on the command line to test suites
186 by searching upwards from the input path until it finds a :file:`lit.cfg` or
187 :file:`lit.site.cfg` file. These files serve as both a marker of test suites
188 and as configuration files which :program:`lit` loads in order to understand
189 how to find and run the tests inside the test suite.
191 Once :program:`lit` has mapped the inputs into test suites it traverses the
192 list of inputs adding tests for individual files and recursively searching for
193 tests in directories.
195 This behavior makes it easy to specify a subset of tests to run, while still
196 allowing the test suite configuration to control exactly how tests are
197 interpreted. In addition, :program:`lit` always identifies tests by the test
198 suite they are in, and their relative path inside the test suite. For
199 appropriately configured projects, this allows :program:`lit` to provide
200 convenient and flexible support for out-of-tree builds.
202 .. _test-status-results:
207 Each test ultimately produces one of the following six results:
215 The test failed, but that is expected. This is used for test formats which allow
216 specifying that a test does not currently work, but wish to leave it in the test
221 The test succeeded, but it was expected to fail. This is used for tests which
222 were specified as expected to fail, but are now succeeding (generally because
223 the feature they test was broken and has been fixed).
231 The test result could not be determined. For example, this occurs when the test
232 could not be run, the test itself is invalid, or the test was interrupted.
236 The test is not supported in this environment. This is used by test formats
237 which can report unsupported tests.
239 Depending on the test format tests may produce additional information about
240 their status (generally only for failures). See the :ref:`output-options`
241 section for more information.
243 .. _lit-infrastructure:
248 This section describes the :program:`lit` testing architecture for users interested in
249 creating a new :program:`lit` testing implementation, or extending an existing one.
251 :program:`lit` proper is primarily an infrastructure for discovering and running
252 arbitrary tests, and to expose a single convenient interface to these
253 tests. :program:`lit` itself doesn't know how to run tests, rather this logic is
254 defined by *test suites*.
259 As described in :ref:`test-discovery`, tests are always located inside a *test
260 suite*. Test suites serve to define the format of the tests they contain, the
261 logic for finding those tests, and any additional information to run the tests.
263 :program:`lit` identifies test suites as directories containing ``lit.cfg`` or
264 ``lit.site.cfg`` files (see also :option:`--config-prefix`). Test suites are
265 initially discovered by recursively searching up the directory hierarchy for
266 all the input files passed on the command line. You can use
267 :option:`--show-suites` to display the discovered test suites at startup.
269 Once a test suite is discovered, its config file is loaded. Config files
270 themselves are Python modules which will be executed. When the config file is
271 executed, two important global variables are predefined:
275 The global **lit** configuration object (a *LitConfig* instance), which defines
276 the builtin test formats, global configuration parameters, and other helper
277 routines for implementing test configurations.
281 This is the config object (a *TestingConfig* instance) for the test suite,
282 which the config file is expected to populate. The following variables are also
283 available on the *config* object, some of which must be set by the config and
284 others are optional or predefined:
286 **name** *[required]* The name of the test suite, for use in reports and
289 **test_format** *[required]* The test format object which will be used to
290 discover and run tests in the test suite. Generally this will be a builtin test
291 format available from the *lit.formats* module.
293 **test_source_root** The filesystem path to the test suite root. For out-of-dir
294 builds this is the directory that will be scanned for tests.
296 **test_exec_root** For out-of-dir builds, the path to the test suite root inside
297 the object directory. This is where tests will be run and temporary output files
300 **environment** A dictionary representing the environment to use when executing
303 **suffixes** For **lit** test formats which scan directories for tests, this
304 variable is a list of suffixes to identify test files. Used by: *ShTest*.
306 **substitutions** For **lit** test formats which substitute variables into a test
307 script, the list of substitutions to perform. Used by: *ShTest*.
309 **unsupported** Mark an unsupported directory, all tests within it will be
310 reported as unsupported. Used by: *ShTest*.
312 **parent** The parent configuration, this is the config object for the directory
313 containing the test suite, or None.
315 **root** The root configuration. This is the top-most :program:`lit` configuration in
318 **on_clone** The config is actually cloned for every subdirectory inside a test
319 suite, to allow local configuration on a per-directory basis. The *on_clone*
320 variable can be set to a Python function which will be called whenever a
321 configuration is cloned (for a subdirectory). The function should takes three
322 arguments: (1) the parent configuration, (2) the new configuration (which the
323 *on_clone* function will generally modify), and (3) the test path to the new
324 directory being scanned.
326 **pipefail** Normally a test using a shell pipe fails if any of the commands
327 on the pipe fail. If this is not desired, setting this variable to false
328 makes the test fail only if the last command in the pipe fails.
333 Once test suites are located, :program:`lit` recursively traverses the source
334 directory (following *test_source_root*) looking for tests. When :program:`lit`
335 enters a sub-directory, it first checks to see if a nested test suite is
336 defined in that directory. If so, it loads that test suite recursively,
337 otherwise it instantiates a local test config for the directory (see
338 :ref:`local-configuration-files`).
340 Tests are identified by the test suite they are contained within, and the
341 relative path inside that suite. Note that the relative path may not refer to
342 an actual file on disk; some test formats (such as *GoogleTest*) define
343 "virtual tests" which have a path that contains both the path to the actual
344 test file and a subpath to identify the virtual test.
346 .. _local-configuration-files:
348 LOCAL CONFIGURATION FILES
349 ~~~~~~~~~~~~~~~~~~~~~~~~~
351 When :program:`lit` loads a subdirectory in a test suite, it instantiates a
352 local test configuration by cloning the configuration for the parent direction
353 --- the root of this configuration chain will always be a test suite. Once the
354 test configuration is cloned :program:`lit` checks for a *lit.local.cfg* file
355 in the subdirectory. If present, this file will be loaded and can be used to
356 specialize the configuration for each individual directory. This facility can
357 be used to define subdirectories of optional tests, or to change other
358 configuration parameters --- for example, to change the test format, or the
359 suffixes which identify test files.
361 TEST RUN OUTPUT FORMAT
362 ~~~~~~~~~~~~~~~~~~~~~~
364 The :program:`lit` output for a test run conforms to the following schema, in
365 both short and verbose modes (although in short mode no PASS lines will be
366 shown). This schema has been chosen to be relatively easy to reliably parse by
367 a machine (for example in buildbot log scraping), and for other tools to
370 Each test result is expected to appear on a line that matches:
374 <result code>: <test name> (<progress info>)
376 where ``<result-code>`` is a standard test result such as PASS, FAIL, XFAIL,
377 XPASS, UNRESOLVED, or UNSUPPORTED. The performance result codes of IMPROVED and
378 REGRESSED are also allowed.
380 The ``<test name>`` field can consist of an arbitrary string containing no
383 The ``<progress info>`` field can be used to report progress information such
384 as (1/300) or can be empty, but even when empty the parentheses are required.
386 Each test result may include additional (multiline) log information in the
391 <log delineator> TEST '(<test name>)' <trailing delineator>
395 where ``<test name>`` should be the name of a preceding reported test, ``<log
396 delineator>`` is a string of "*" characters *at least* four characters long
397 (the recommended length is 20), and ``<trailing delineator>`` is an arbitrary
400 The following is an example of a test run output which consists of four tests A,
401 B, C, and D, and a log message for the failing test C:
408 ******************** TEST 'C' FAILED ********************
409 Test 'C' failed as a result of exit code 1.
416 The :program:`lit` distribution contains several example implementations of
417 test suites in the *ExampleTests* directory.