Integrate aql tests into testing process

We can consider aql files that exit with 0/non-zero values as tests. Integrate them into ctest.

a28d13f0 (comment 110302)

mentioned in commit a28d13f0

added D-tests P-high labels

mentioned in issue #201 (closed)

created branch 198-integrate-aql-tests-into-testing-process to address this issue

Roadmap:

• move alib2integrationtest to tests/
• add tests/aql directory and run all aql scripts from this file. It would actually be nice to have one file = one unit test entry. Consult with catch2 whether we can dynamically add tests
• try to rewrite as many tests as possible from C++ to aql

added T-feature label

mentioned in commit 6d004881

mentioned in commit d79fe028

mentioned in merge request !155 (merged)

Done, merged into dev-tp-cmake-ci branch -- not yet in master.

assigned to @peckato1

closed via merge request !154 (merged)

If you want to add an aql script to the testing suite, add it into tests/aql/ directory. The test fails if the script returns nonzero value, just like aql.

Re-run of cmake is neccessary after adding, however, with Make and ninja it happens automatically when you invoke make or ninja commands, respectively. of course you can always use our build.sh script.