https://tomatool.github.io/blog/posts/databases/Recent content in Databases in a tomato suite: migrations, resets and clean state on tomato blogHugoen-USWed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/migrations/Wed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/migrations/Whether your service migrates itself, or a tool like Flyway, golang-migrate, Alembic or Prisma does it before the service starts, the schema is made once per run, before the first scenario. Each case, in each language and tool, and the one line most tools need: keep their history table.https://tomatool.github.io/blog/posts/databases/postgres/Wed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/postgres/Every table emptied in one TRUNCATE … RESTART IDENTITY CASCADE before each scenario, migration history kept, schemas and excludes for the rest.https://tomatool.github.io/blog/posts/databases/scylladb/Wed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/scylladb/tomato creates the keyspace, runs your CQL schema once, and truncates every table in the keyspace before each scenario, except the ones you exclude.https://tomatool.github.io/blog/posts/databases/redis/Wed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/redis/Redis holds the state that leaks most easily: counters, sessions, caches. tomato flushes it before every scenario, or deletes only the keys matching a pattern.https://tomatool.github.io/blog/posts/databases/other-databases/Wed, 21 Oct 2026 06:20:00 +0200https://tomatool.github.io/blog/posts/databases/other-databases/MongoDB, MySQL, Elasticsearch: tomato has no resource for them, but the rule still holds. A before_scenario hook empties them, and scenarios check them through your service.