You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create our own libray/schema to hold test tables, procedures, etc
No longer use QIWS.QCUSTCDT for insert tests (Use our own test tables)
Add after/afterEach hooks to delete data inserted by test cases (remove created tables, etc)
I've noticed when running the test suite multiple times this test case in asyncStatementTest.js leads to assertion error here this is because it inserts into the QIWS.QCUSTCDT table each time and the number results increase. Therefore no way to assert that value is 1. One way to workaround this would be to check is the results are > 0. I would rather not insert into that table at all though and use our own tables. Cleaning up after the case is finished.
The text was updated successfully, but these errors were encountered:
I've noticed when running the test suite multiple times this test case in asyncStatementTest.js leads to assertion error here this is because it inserts into the QIWS.QCUSTCDT table each time and the number results increase. Therefore no way to assert that value is 1. One way to workaround this would be to check is the results are > 0. I would rather not insert into that table at all though and use our own tables. Cleaning up after the case is finished.
The text was updated successfully, but these errors were encountered: