Testing CG/SQL
Basic testing commands you should know.
While standing in the /sources directory you may use test.sh and with these important options.
| Command | Details |
|---|---|
./test.sh | Build the compiler and run the suite. This is the bread an butter of the dev cycle. |
--use_amalgam | Build the compiler from the amalgam and then tests it as above. |
--use_asan | Enable address sanitizer. Great for finding memory safety issues. |
--use_clang | Clang finds more warnings than GCC in general, recommened before any PR. |
--use_gcc | If cc maps to clang, you should also try gcc before any PR. |
--non_interactive | Used when calling from a script file. Disables prompting for diffs. |
--coverage | Triggers coverage options needed by cov.sh. Not intended for direct use. |
cov.sh | See Code Coverage |
See details in our Developer Guide
NOTE: For productivity it’s not uncommon to tweak
test.shso that the test you care about runs first. But don’t submit a PR with the tests reordered. Not that the author has ever made that mistake or anything. But it could happen – you know – to other people…