Mutation activity

Instructions

The required software is already installed on attu.cs.washington.edu, if you prefer to do the exercise there.

1. Team up in groups of size 2.

2. Clone https://bitbucket.org/rjust/mutation and read its README.md file and ASSIGNMENT.md file. Please read the ENTIRETY of both these files before you begin programming.

3. One team member should submit the exercise to gradescope and add the other on the submission. Deliverables:

   • Your responses to the short answer questions #1-4 in a file writeup.txt. Please also include your names in the writeup.
   • Your updated test suite, TriangleTest.java.

   This time around, we have some light sanity checks implemented on Gradescope which you should ensure are passing before considering the assignment complete. You may resubmit as many times as you like before the deadline.

Tips / Clarifications

• It helps to read the “Background” section at the end of ASSIGNMENT.md before the rest of that file.
• Review the lecture slides on Mutation Testing.
• “Unproductive mutants” refers to those that are broadly not useful for improving the test suite or don’t offer any new insight about the codebase.
• Note that the original Triangle.java may not necessarily be completely correct for the task of classifying triangles. For the purposes of this exercise though, we define this original code to be correct. In other words, you should only consider mutants in relation to this original code, rather than to idealized triangle-classifying algorithms – try to get the mutant to return something different than what the original code returns.