PageRenderTime 39ms CodeModel.GetById 17ms RepoModel.GetById 0ms app.codeStats 0ms

/trunk/Examples/test-suite/csharp/README

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