practicalli / practicalli/clojure-web-services
refine test speed using transaction rollback
Open
Nobody has claimed this yet.
database
testing
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Use transaction rollback so any database updated done by the unit tests is not committed permanently.
Create two fixtures,
:once drop/create database
:every run tests in transaction
The transaction is set to rollback regardless, leaving the database in the previous state (just the empty database tables)
https://purelyfunctional.tv/mini-guide/clojure-database-test-faster/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Inspect the unit-test database setup and fixture lifecycle first; done means one setup fixture creates the empty schema, each test runs inside a transaction, and every transaction rolls back.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- database, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100