Edited online
parent
ecdc463d15
commit
b9f8fc9fa8
|
@ -74,8 +74,8 @@ In your plan, be sure to include the following:
|
||||||
-----------------------------------------------------------------------------------------------------------------
|
-----------------------------------------------------------------------------------------------------------------
|
||||||
|
|
||||||
## **How will the bugs and their changes be tracked over time?** ##
|
## **How will the bugs and their changes be tracked over time?** ##
|
||||||
|
|
||||||
-----------------------------------------------------------------------------------------------------------------
|
|
||||||
* As previously mentioned, bugs will be tracked over time using the issue tracker in Bitbucket.
|
* As previously mentioned, bugs will be tracked over time using the issue tracker in Bitbucket.
|
||||||
* Once a bug is resolved, it will be marked as resolved within the issue tracker.
|
* Once a bug is resolved, it will be marked as resolved within the issue tracker.
|
||||||
* Also previously mentioned, we will be recording bugs and their changes using a Google Docs sheet. This sheet is formatted as an Excel document. The sheet contains a traceability matrix, and separate pages for each stage of testing (Alpha, Beta, and Code Release). All team members will be able to edit these sheets. We can record test results here as well as changes that were made to resolve bugs.
|
* Also previously mentioned, we will be recording bugs and their changes using a Google Docs sheet. This sheet is formatted as an Excel document. The sheet contains a traceability matrix, and separate pages for each stage of testing (Alpha, Beta, and Code Release). All team members will be able to edit these sheets. We can record test results here as well as changes that were made to resolve bugs.
|
||||||
|
|
||||||
|
-----------------------------------------------------------------------------------------------------------------
|
Loading…
Reference in New Issue