Opened 18 years ago
Closed 17 years ago
#4223 closed (fixed)
Document how to create tests for Django framework itself
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
It's extremely helpful for django-developers to have tests that recreate bugs in Django. This helps us to squish those bugs. It's not immediately clear how to do this (e.g.), and we should briefly describe how to do this to help people provide write tests when the file bug reports.
Change History (3)
comment:1 by , 18 years ago
comment:2 by , 17 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Simon, I'm going to close this as fixed because the sprint added notes to contributing.txt about including tests with your patches, where different types of tests should go and how to run them, along with a link to the testing docs for an explanation of how the test system works. If you think something's missing from that, could you open a new ticket with specifics?
Note:
See TracTickets
for help on using tickets.
TestingDjango has a brief guide.