/tags/rel-1-3-25/SWIG/Examples/test-suite/csharp/README

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