https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19821 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|BLOCKED |Signed Off --- Comment #38 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- I am not sure if we should have coupled the option of a test database and the selenium test environment on this report. The two config options database and database_test do not seem a good idea to me, intuitively. It looks more like a hack? (Also taken in consideration that git grep shows me that the database config variable is used in more places.) On another report we already had a discussion about the rollback of changes for selenium tests. I think we'd better separate the test suite from the selenium tests. And actually, we have already the tools to create separate instances for selenium and testing. With a separate KOHA_CONF in the webserver configuration selenium can be run on its own. Same for t/db_dependent. Only thing is that we want to do it faster. But does that justify a bunch of code changes that might jeopardize code quality? This needs (imo) more serious thought and a broader discussion. -- You are receiving this mail because: You are watching all bug changes.