leancodepl / leancodepl/corelibrary
Shared database for integration tests
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 30
- Forks
- 4
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 3
Description
Currently, we force a fresh database for each and every test. It would be good to:
- Document how we suggest tests should be structured (a test per class, basically),
- Allow to re-use database across tests.
Contributor guide
No contributing guide indexed for this repository
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 in the issue. Start by locating the integration-test setup and current per-test database creation, then review how tests are structured and isolated. Done means the recommended test structure is documented and integration tests can safely reuse a database without cross-test interference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, database, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100