https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29285
--- Comment #4 from Victor Grousset/tuxayo <[email protected]> --- Moving here a discussion where I erroneously thought Bug 38503 would allow to replace TestBuilder. > Bug 38503 won't help much here. Now that there is an easy way to have well populated json objects (in sync with the tables because the API is kept well in sync) in the Cypress tests, is there much to do to feed them to the API? Most TestBuilder usage should be on tables that are well covered by the API. Here is what I found in the Selenium tests: - Koha::Patrons - biblio record - Koha::Libraries - Koha::Virtualshelves (Bug 38050) - items - Koha::ItemTypes - Koha::Patron::Categories "that are well covered by the API" => nope >_< Only the 1st group has the add endpoint and only one of the others has work in progress on it. There is also the need to have something else added to easily cleanup data. Like truncating tables. And since it seems not possible to use transactions there nor mock sysprefs, the more subtle data to cleanup like circ rules and sysprefs need more crafty ways. Maybe using an SQL connector[1], getting an SQL dump of a table and on cleanup truncating and inserting would do the trick? [1] https://www.npmjs.com/package/mariadb or maybe there is a more generic one. To not add yet another DBMS specific thing. Is there a shorter path forward? Whether it's using Bug 38503 or not. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] 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/
