Silvan_WMDE removed Silvan_WMDE as the assignee of this task. Silvan_WMDE moved this task from Doing to To Do on the Mismatch Finder (Mismatch Finder - sprint 2) board. Silvan_WMDE added a comment.
There are two ways for handling the database in feature tests: second container with a "testing" instance of mariadb vs. in-memory sqlite. I have created branches (without a PR) for both <https://github.com/wmde/wikidata-mismatch-finder/tree/testing> approaches <https://github.com/wmde/wikidata-mismatch-finder/tree/testing-sqlite>. The latter seems much easier in combination with GitHub actions, since it avoids a multi-container setup. There are voices <https://www.aaronsaray.com/2019/stop-using-sqlite-in-laravel-unit-tests>, however, who believe that testing with sqlite is bad if you run mariadb in production. I do like the ease-of-use of the throwaway sqlite db, though and would hope that we can minimise the risk. Moving this back to ToDo, as a few tests are left to implement and GitHub Actions still need to be configured. TASK DETAIL https://phabricator.wikimedia.org/T286053 WORKBOARD https://phabricator.wikimedia.org/project/board/5422/ EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Silvan_WMDE Cc: Silvan_WMDE, Aklapper, ItamarWMDE, karapayneWMDE, Invadibot, maantietaja, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected]
