Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce testing suite #27

Open
maxpert opened this issue Oct 22, 2022 · 2 comments
Open

Introduce testing suite #27

maxpert opened this issue Oct 22, 2022 · 2 comments
Labels
testing Testing related issues

Comments

@maxpert
Copy link
Owner

maxpert commented Oct 22, 2022

Following are required to be done:

  • Integration tests on CDC watching and publishing to NATS
  • Integration tests of reapplying change logs from NATS
  • Snapshot save/restore testing
  • SQLite Tcl level testing suite integration
@maxpert maxpert added enhancement New feature or request testing Testing related issues and removed enhancement New feature or request labels Oct 22, 2022
@mindreframer
Copy link

This is a very good issue! Having some kind of testing suite for a foundational building block of distributed systems + data storage is a "MUST" feature, if we care about our users data.

I could observe long delays in change propagation locally, it required another change for all changes to become visible on all nodes.

Embedding NATS Jet Stream is genius, and I think it's possible to get away with a smaller test suite, because we can assume that NATS is doing its job correctly.

@gedw99
Copy link

gedw99 commented Nov 14, 2023

yep agree that development needs a system to consistently see bugs.

also devs that experience bugs can supply seed data for reproduction of bug, so that we can both track down bugs but add them into seed data and tests to avoid regressions.

Are there any proposals for how to do this ?

  • seed data into SQL
  • Tests that work against the seed data
  • Nats cluster setup and tear down
  • Chaos on nats Cluster like loosing one or upgrading using lame duck mode, so we related failure modes.

Do we presume Linus only ? Some users might be running SQLite on desktops with marmot on Linus server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Testing related issues
Projects
None yet
Development

No branches or pull requests

3 participants