| We have a spread of different GitHub Actions based workflows that do stuff whenever a PR is proposed or merged: https://github.com/sqlitebrowser/sqlitebrowser/tree/master/.... Most of those are oriented around building packages for various OS's (Linux, macOS, Windows) so people can try the latest code. While there are some tests, they're more like extremely basic sanity checks and they don't use containers. Those tests rely on whichever version of SQLite was downloaded and compiled into the GUI (as per above code snippet). --- That being said, that's for the client side GUI application. There's a server side of things too (https://github.com/sqlitebrowser/dbhub.io -> dbhub.io) that does use containers (docker) for it's automated tests: https://github.com/sqlitebrowser/dbhub.io/tree/master/.githu... Those are integration tests though (eg "make sure we didn't bust communication with our cli", "make sure our go library still works 100% with the server"), and a reasonably decent set of End to End (E2E) tests of the web interface using Cypress. --- Does that help? :) |