THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
If adding a new feature, then check that it is either covered by an existing regression test or add a new test to an existing test suite.
Test Suites
Location: core/sql/regress
| Directory | Usage |
|---|---|
| catman1 | Tests the Catalog Manager. |
| charsets | Tests Character Sets. |
| compGeneral | Compiler test suite; tests optimizer-specific features. |
| core | Tests a subset/sample of all features from all the test suites. |
| executor | Tests the SQL Executor. |
| fullstack2 | Similar to core but a very limited subset. |
| hive | Tests HDFS access to Hive tables. |
| newregr | Unused/Saved repository for some unpublished features. These are not run. |
| qat | Tests basic DDL and DML syntax. |
| privs1 | Privilege tests part 1 - authorization setup, utilities, misc |
| privs2 | Privilege tests part 2 - grants and revokes |
| seabase | Tests JNI interface to HBase. |
| tools | Regression driver scripts and general regression scripts. |
| udr | ests Tests the User Defined Routines (UDR) and TMUDF functionality. |
Check Test Results
On completion, the test run prints out a test summary. All tests should pass, or pass with known differences.
Test results are written to the runregr-sb.log file in each component’s directory. Therefore, you can check the test results after the fact as follows:
...