opensafely-core / opensafely-core/opencodelists
Update test data for local development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 60
- Forks
- 16
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 17
Description
Why are we doing this?
just build-dbs-for-local-development sets up a lightweight local development environment using test fixture data. This data is sufficient for tasks that don't involve modifications to the builder tree (e.g., editing the Version card or the navbar). However, to test changes to the builder tree more thoroughly, we need more complex data scenarios.
How will we know when it's done?
We'll be able to perform local development with richer test data that includes more complex codes, improving our confidence in related updates to the builder tree.
What are we doing?
Updating the local development fixtures to include more complex codes, such as:
- Codes with long descriptions (longer than can be fully displayed on screen)-
- Multiple parent-child relationships
- Codes designed to trigger inclusion/exclusion conflict scenarios
This may involve creating new fixture files to populate the local databases. As part of this work, just build-dbs-for-local-development could be updated to incorporate these new fixtures.
Considerations:
This work may be affected by #2523 and may have implications for #2543.
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
Start with the just build-dbs-for-local-development command and inspect the existing local-development fixture files and database population flow. Check how issues #2523 and #2543 affect the work, then verify that the command produces richer data covering long descriptions, multiple parent-child relationships, and inclusion/exclusion conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100