Better unit tests for auto tracing
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The system automatically figures out which models need to be monitored for changes.
I'm calling that feature auto tracing for now.
We need more testing for that feature.
- [ ] Test ManyToMany with the field defined on model A
- [ ] Test ManyToMany with the field defined on model B
- [ ] Test ManyToMany with related_name (both direction)
- [ ] Test ManyToMany with related_query_name (both directions)
- [ ] Test ForeignKey with the field defined on model A
- [ ] Test ForeignKey with the field defined on model B
- [ ] Test ForeignKey with related_name (both direction)
- [ ] Test ForeignKey with related_query_name (both directions)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the auto-tracing implementation and its existing test suite in the repository. Add coverage for each listed ManyToMany and ForeignKey relationship, including both field directions, related_name, and related_query_name. Done means all eight relationship cases are tested and pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100