Lines Matching full:suite

2 LLVM test-suite Guide
12 test-suite as well as the cmake based replacement. This way of interacting
13 with the test-suite is deprecated in favor of running the test-suite using LNT,
15 Guide's :ref:`test-suite Quickstart <test-suite-quickstart>` section for more
18 Test suite Structure
21 The ``test-suite`` module contains a number of programs that can be
37 In addition for testing correctness, the ``test-suite`` directory also
43 ``test-suite`` tests are divided into three types of tests: MultiSource,
46 -  ``test-suite/SingleSource``
53 -  ``test-suite/MultiSource``
59 -  ``test-suite/External``
67    external programs is configured by the test-suite ``configure``
81 The tests in the test suite have no such feature at this time. If the
87 Running the test suite via CMake
90 To run the test suite, you need to use the following steps:
92 #. The test suite uses the lit test runner to run the test-suite,
108 #. Check out the ``test-suite`` module with:
112        % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
114 #. Use CMake to configure the test suite in a new directory. You cannot build
115    the test suite in the source tree.
119        % mkdir test-suite-build
120        % cd test-suite-build
121        % cmake ../test-suite
146     PASS: test-suite :: MultiSource/Applications/ALAC/decode/alacconvert-decode.test (1 of 474)
147 …********** TEST 'test-suite :: MultiSource/Applications/ALAC/decode/alacconvert-decode.test' RESUL…
153     PASS: test-suite :: MultiSource/Applications/ALAC/encode/alacconvert-encode.test (2 of 474)
156 Running the test suite via Makefiles (deprecated)
161 the test suite creates temporary files during execution.
163 To run the test suite, you need to use the following steps:
166 #. Check out the ``test-suite`` module with:
170        % svn co http://llvm.org/svn/llvm-project/test-suite/trunk test-suite
172    This will get the test suite into ``llvm/projects/test-suite``.
181    object directory tree) in which you want to run the test suite, just
189    You must also tell the configure machinery that the test suite is
199 #. You can now run the test suite from your build tree as follows:
203        % cd $LLVM_OBJ_ROOT/projects/test-suite
207 you have the suite checked out and configured, you don't need to do it
213 In order to run the External tests in the ``test-suite`` module, you
243 In addition to the regular "whole program" tests, the ``test-suite``
286 Writing custom tests for the test suite
289 Assuming you can run the test suite, (e.g.
303 "``test-suite/TEST.XXX.Makefile``" fragment (where XXX is the name of
304 your test) and a "``test-suite/TEST.XXX.report``" file that indicates
306 various levels of sophistication included with the test suite, and the
314     % cd llvm/projects/test-suite/MultiSource/Benchmarks  # or some other level
341 The source for this is in ``test-suite/TEST.libcalls.*``. The format is