Training Assessment #4
Defect Reporting and Repair
Objective
In
this exercise you will demonstrate correct use of the Defect
Repair Procedure.
Prerequisites
You must know how to create JUnit tests.
Read and understand the Defect
Repair Procedure. Be sure you are clear about how to perform
all the steps before you begin.
Your team QA manager must have created an account for
you on the team defect tracking system before you can complete this
exercise. Refer to the QA plan. Be sure Trac is configured
to notify you when a ticket is created.
Your team Configuration Manager must have added ComplexNumber.java and ComplexNumberTest.java in
your team source code repository.
Directions
- Checkout the source code for ComplexNumber.java.
from your team repository.
- The class contains seven seeded defects.
- Compile the source code file (It should compile without error).
- Study the source code and identify one of the
seven defects. You may find it helpful to consult a mathematics
reference on Complex Numbers such as MathWorld.
- Follow steps 2 - 14 in the Defect
Repair Procedure
- For step 3-4 in the procedure assign the defect to yourself.
- For step 8, write your JUnit test as a new method in the ComplexNumberTest.java
file. Include an @author tag for yourself in the javadoc for this
method.
Large Teams (8-10 people)
There are only seven seeded defects in the source code. If you have
more than seven people on your team, then have
each extra person treat one of the unimplemented methods in the
ComplexNumber class as a defect.
These methods are:
-
Power of a complex number to a positive integer exponent.
-
Complex exponentiation.
-
Complex argument.
Submission
A copy of the email message that was sent to you automatically by
the defect tracking system when you created the issue.
A printout of your repaired source code to ComplexNumber class.
Use a highlighter to emphasize the lines you changed or added.
A printout of the source code for your JUnit test case in the
ComplexNumberTest class.
A printout showing the successful execution of your JUnit test case
(using the text-based TestRunner).
309 Home