Changes between Version 17 and Version 18 of Development/Patches


Ignore:
Timestamp:
Dec 5, 2012, 12:47:36 PM (7 years ago)
Author:
benl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Development/Patches

    v17 v18  
    3535 * We don't like having failures in the main test suite.
    3636 * If the nightly buildbot encounters a failure when running a test in a non-standard way (like with "opt") then someone should move that test into the {{{test/Broken-skip}}} directory and file a bug report.
    37  * Don't push other, non-fixing patches into a repo that has test failures.
     37 * Don't push non-fixing patches into a repo that has test failures.
    3838
    3939== Fixing Bugs ==
    4040 * Most of the bugs in the issue tracker should have a failing test case in {{{test/Broken-skip}}}
    41  * When you fix a bug, mark it as resolved on the tracker then either move its test from {{{test/Broken-skip}}} into the main testsuite, or create a new test.
     41 * When you fix a bug, mark it as resolved on the trac then either move its test from {{{test/Broken-skip}}} into the main testsuite, or create a new test.
    4242 * If you find it too hard to create a new test, then we might need to extend the {{{war}}} test driver.
    4343