Opened 16 years ago
#63 new enhancement
Document test procedures
Reported by: | VincentMcIntyre | Owned by: | VincentMcIntyre |
---|---|---|---|
Priority: | major | Milestone: | 7. Stage 1 - available for testing |
Component: | miriad4cabb project | Version: | |
Keywords: | Cc: | ||
Estimated Number of Hours: | 0 | Add Hours to Ticket: | 0 |
Billable?: | yes | Total Hours: | 0 |
Description
After reading about session-based test management, it seems like we need a little structure to keep track of what we have tested. The link gives a reasonable way to add enough structure on top of what we're expecting will be a fairly ad-hoc process.
Deliverables:
- template for test report
- code to summarise the pile of reports and gather stats
Probably we can use the ticketing system to good effect here - assign the tests in a ticket, and have people attach their report when they are done (close the ticket).
Note: See
TracTickets for help on using
tickets.