-
sqlitebrowser
Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
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 tests and don't rely on Docker.
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 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? :)
If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.
https://github.com/sqlite/sqlite/tree/master/ext/lsm1
https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...
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 tests and don't rely on Docker.
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 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? :)