Opened at 2011-07-23T00:30:38Z
Last modified at 2014-09-23T23:08:07Z
#1439 new task
add docs/tests.rst documenting how to run tests and how to interpret the output — at Version 1
| Reported by: | davidsarah | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | documentation | Version: | 1.8.2 |
| Keywords: | docs test | Cc: | |
| Launchpad Bug: |
Description (last modified by zooko)
In ticket:145#comment:26, Zooko wrote about various ways to run the Tahoe-LAFS test suite, some of which work and some of which do not. He suggested adding a docs/tests.rst to document this.
tests.rst should also document cases in which the tests are known to fail (such as when we're not testing the right code), how to interpret skips, todos, and other sources of noise, and how to get Twisted log output from test cases.
Note: See
TracTickets for help on using
tickets.
See also Nathan's comments about "How To Run Tests" during a Nuts & Bolts meeting.