prove -r t/db_dependent/api/v1 will modify DB data, they should not
Created attachment 65012 [details] [review] Bug 18826: rollback transaction for api tests The holds.t tests for the REST api do no rollback properly and modify the DB (no cleanup). This comes from a bug caused by SessionStorage = mysql (default) The error is: "rollback ineffective with AutoCommit enabled" Test plan: select count(*) from borrowers; prove t/db_dependent/api/v1/holds.t select count(*) from borrowers; => The number of entry must be the same before and after the tests have been executed
Created attachment 65143 [details] [review] [SIGNED-OFF] Bug 18826: rollback transaction for api tests The holds.t tests for the REST api do no rollback properly and modify the DB (no cleanup). This comes from a bug caused by SessionStorage = mysql (default) The error is: "rollback ineffective with AutoCommit enabled" Test plan: select count(*) from borrowers; prove t/db_dependent/api/v1/holds.t select count(*) from borrowers; => The number of entry must be the same before and after the tests have been executed Signed-off-by: Josef Moravec <josef.moravec@gmail.com>
Created attachment 65177 [details] [review] Bug 18826: rollback transaction for api tests The holds.t tests for the REST api do no rollback properly and modify the DB (no cleanup). This comes from a bug caused by SessionStorage = mysql (default) The error is: "rollback ineffective with AutoCommit enabled" Test plan: select count(*) from borrowers; prove t/db_dependent/api/v1/holds.t select count(*) from borrowers; => The number of entry must be the same before and after the tests have been executed Signed-off-by: Josef Moravec <josef.moravec@gmail.com> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Created attachment 65178 [details] [review] Bug 18826 - (QA Followup) Add mock SessionStorage to patrons.t
Pushed to master for 17.11, thanks to everybody involved!
Pushed to 17.05.x, will be in 17.05.02.
These patches have been pushed to 16.11.x and will be in 16.11.10.
*** Bug 16977 has been marked as a duplicate of this bug. ***