#15154 closed (fixed)
Remove sample doctest from startapp tests.py stub
| Reported by: | Carl Meyer | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Given the problems Django itself has experienced using doctests as a primary testing strategy, and the effort that's recently gone into removing them, do we really want to be encouraging Django users to adopt practices that have served us so poorly?
Seems like the sample doctest in the stub tests.py generated by startapp should probably go away.
Optionally, the Django testing docs could also be given a quick once-over to see if there are places we should be warning users against the siren song of using doctests as a primary test strategy.
Change History (3)
comment:1 by , 14 years ago
| milestone: | → 1.3 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Sounds good to me. After all, we've always been at war with doctests. :-)
The second optional point has already been done; unittest is listed in the docs before doctests, and the "which should I use" section has been beefed up to clarify the preference for unittests. Of course, if you have more specific suggestions, let's have 'em.