THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Copy the test to a new file under
ql/src/test/queries/clientpositive/<filename>.q
(or/clientnegative
if it is a negative test).- If the new test creates any table, view, function, etc., make sure that the name is unique across tests. For instance, name a table in the test file
foo.q
,foo_t1
instead of simplyt1
. This will help reduce flakiness in the test runs, since Jenkins will run tests and batches, and currently it does not restore to former state after running each of the q files. - If there is any interaction with file system, use unique folders for the test to avoid any collision with other tests.
- If the new test creates any table, view, function, etc., make sure that the name is unique across tests. For instance, name a table in the test file
- Add the
<filename.q>
toitests/src/test/resources/testconfiguration.properties
to the appropriate variable (ex.minimr.query.files
).
...