Lines Matching full:suite

2 LLVM test-suite Makefile Guide
12 test-suite. This way of interacting with the test-suite is deprecated in
13 favor of running the test-suite using LNT, but may continue to prove
14 useful for some users. See the Testing Guide's :ref:`test-suite Quickstart
15 <test-suite-quickstart>` section for more information.
17 Test suite Structure
20 The ``test-suite`` module contains a number of programs that can be
36 In addition for testing correctness, the ``test-suite`` directory also
42 ``test-suite`` tests are divided into three types of tests: MultiSource,
45 - ``test-suite/SingleSource``
52 - ``test-suite/MultiSource``
58 - ``test-suite/External``
66 external programs is configured by the test-suite ``configure``
80 The tests in the test suite have no such feature at this time. If the
86 Running the test suite
91 the test suite creates temporary files during execution.
93 To run the test suite, you need to use the following steps:
96 #. Check out the ``test-suite`` module with:
100 % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
102 This will get the test suite into ``llvm/projects/test-suite``.
111 object directory tree) in which you want to run the test suite, just
119 You must also tell the configure machinery that the test suite is
129 #. You can now run the test suite from your build tree as follows:
133 % cd $LLVM_OBJ_ROOT/projects/test-suite
137 you have the suite checked out and configured, you don't need to do it
143 In order to run the External tests in the ``test-suite`` module, you
173 In addition to the regular "whole program" tests, the ``test-suite``
216 Writing custom tests for the test suite
219 Assuming you can run the test suite, (e.g.
233 "``test-suite/TEST.XXX.Makefile``" fragment (where XXX is the name of
234 your test) and a "``test-suite/TEST.XXX.report``" file that indicates
236 various levels of sophistication included with the test suite, and the
244 % cd llvm/projects/test-suite/MultiSource/Benchmarks # or some other level
271 The source for this is in ``test-suite/TEST.libcalls.*``. The format is