Changes between Version 1 and Version 2 of DefectRepairProcedure


Ignore:
Timestamp:
04/16/2019 06:27:38 AM (7 years ago)
Author:
jdalbey
Comment:

trying to add image

Legend:

Unmodified
Added
Removed
Modified

  • DefectRepairProcedure

    v1 v2  
    2323 1. Programmer uses Trac to "accept" the defect. (If the person reporting the defect is the programmer who will fix it, you don't have to wait for the Implementation manager to assign it to you.) 
    2424 1. Programmer obtains current version of system source code from SVN. 
    25  1. Programmer writes an automated Unit test (or System Test) which reveals the defect.      If it is infeasible to write an automated test, write a manual test and add  it to the system test cases.  Cross-reference the test case to the defect number, e.g. put the defect number in the test case method name (E.g., `TestDeckBug26`).  
     25 1. Programmer writes an automated Unit test (or System Test) which reveals the defect.      If it is infeasible to write an automated test, write a manual test and add  it to the system test cases.  Cross-reference the test case to the defect number, e.g. put the defect number in the test case method name (E.g., `TestDeckBug26`). 
    2626 1. Programmer isolates and repairs defect. Write a comment with the defect number. 
    2727 1. Programmer runs Unit test (or System Test) on repaired code.  Optionally, Programmer runs any relevant integration or system tests. 
    … …  
    3232 
    3333---- 
     34[[Image(http://git.tokomak.net:8888/attachment/wiki/DefectRepairProcedure/DefectRepairXref.png)]] 
     35