1
SWIG testsuite README file
2
--------------------------
4
This testsuite is here to ensure SWIG can handle a wide range of c/c++
5
syntax. The testsuite comprises many testcases in this directory. Each
6
test case is tested under each of the language modules thereby
7
thoroughly testing all of SWIG. It ensures that each of the language
8
modules are at a similar standard.
10
Those modules that support shadow classes run the tests producing
11
shadow classes to test the full language module functionality.
13
Some test cases need a runtime test. These need implementing in each
14
of the language modules. The language modules look for a file in the
15
language specific test-suite directory which has _runme appended after
16
the testcase name. If one is found it will be run as part of the test.
18
Some language modules add to this common set of test cases for
19
language specific tests. These can be found in the appropriate
20
language test-suite directory. There is also a README in each of the
21
language module directories.
23
For each testcase a message showing which testcase is being tested is
24
displayed. Nothing else is printed unless the test fails.
27
Some Developer Guidelines
28
-------------------------
30
Note that the whole test suite need not be run each time a testcase is
31
modified. An individual testcase may be run by going to the language
32
module test-suite directory and using make testcasename.xxx where xxx
33
is the type of test (eg cpptest). See common.mk. make -s doesn't print
34
any junk on the screen and is useful for emulating the way make check
35
works from the SWIG root directory.
37
If there are runtime tests needed, don't print anything unless there
38
is an error in which case stderr is suggested.
40
Please set the name of the module to the same name as the testcase,
41
otherwise modules will not be found.