Closed
Bug 1205013
Opened 9 years ago
Closed 9 years ago
document comprehensive test plan
Categories
(Input Graveyard :: Code Quality, defect)
Input Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: p=2 s=input.2015q3)
Periodically, we do substantive changes that affect the whole codebase. We have a unit test suite and a set of smoketests, but there's a lot of stuff that isn't covered by those.
We need a test plan for the Django 1.8 upgrade. However, instead of writing up a test plan every time we do a substantive change, this is an attempt at writing a comprehensive test plan covering all the important things that we can reuse every time we do a substantive change.
Assignee | ||
Comment 1•9 years ago
|
||
For now this test plan should live in the docs.
Grabbing this to do today.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•9 years ago
|
||
Assignee | ||
Comment 3•9 years ago
|
||
Landed in master: https://github.com/mozilla/fjord/commit/6e7caf607d6743aaefbb12b75678bf7b3f729d92
This is docs and don't need to be deployed. Marking as FIXED.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•