1 * Organization of Test Cases:
3 There are three different kinds of mbas Test Cases
5 * Positive Tests: These test cases should compile and run
6 without failure. Any failure during compile and run is
7 deemed as a bug in the compiler or run time.
9 * Negative Tests: These test cases trigger a compile time
10 failure with a pre-determined error number at pre-determined
11 location within the source file. A successful compilation or
12 a failure at a different line or with a different error
13 number is deemed as a bug in the compiler.
15 * Negative Run Time Tests: These test cases should trigger a
16 pre-determined run time error. A successful execution or a
17 run-time error that is any different is deemed as a bug in
20 * Contributing Test Cases:
22 * All test cases are listed in the file Test.Sources under one
23 of TEST_SOURCES, TEST_NGTIVE_COMPILATION_SOURCES,
24 TEST_NGTIVE_RUNTIME_SOURCES as appropriate. Refer the
25 previous paragraph to understand what these exactly mean.
29 * To run tests do a 'make'.
30 * All log messages are stored in mcs/btests/logs directory.
31 * Positive tests messages are stored in mbas-positive.results
32 * Negative compilation tests messages are stored in
33 mbas-negative-compile.results file
34 * Negative execution tests messages are stored in
35 mbas-negative-runtime.results file
36 * Log messages for any failed test are stored in corresponding
37 test log file, say, <mbas-*>-<testname>.log.