https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35042
Bug ID: 35042 Summary: Members.t: should not set datelastseen to NULL everywhere Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: ch...@bigballofwax.co.nz Reporter: m.de.r...@rijksmuseum.nl QA Contact: testo...@bugs.koha-community.org It can be tempting to remove all records from a table or just set one column to NULL in a whole table to get a test working quickly. But we should better avoid that, or replace it by something less drastic (if reasonably possible). An example from Members.t: $dbh->do(q|UPDATE borrowers SET lastseen=NULL|); Surely you should not run such tests on a production db. But when someone forgets a rollback here or there, you might have some troubled data on your test system, and often needless. Note that I still often see test branches or item types appear in my test data after spending some time on a test db with master (running some tests). -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/