Consider the following Java class. PrimeNumbers.java has three methods.

• computePrimes(), takes one integer input and computes that many prime numbers.
• iterator() returns an Iterator that will iterate through the primes
• toString() returns a string representation

public class PrimeNumbers implements Iterable<Integer>
{
   private List<Integer> primes = new ArrayList<Integer>();
   public void computePrimes(int n)
   {
      int count = 1;        // count of primes
      int number = 2;       // number tested for primeness
      boolean isPrime;      // is this number a prime

      while (count <= n)
      {
         isPrime = true;
         for (int divisor = 2; divisor <= number / 2; divisor++)
         {
            if (number % divisor == 0)
            {
               isPrime = false;
               break;      // for loop
            }
         }
         if (isPrime && (number % 10 != 9))        // FAULT
         {
            primes.add(number);
            count++; 
         }
         number++; 
      }
   }
   
   @Override public Iterator<Integer> iterator()
   {
      return primes.iterator();
   }
    
   @Override public String toString()
   {
      return primes.toString();
   }
}  

computePrimes() has a fault that causes it not to include prime numbers whose last digit is 9 (for example, it omits 19, 29, 59, 79, 89, 109, ...).

If possible, describe the following five tests. You can describe the tests as sequences of calls to the above methods, or briefly describe them in words. Be sure to include test input values and expected outputs.

Note: For the last two tests, in addition to the test input values and the corresponding expected outputs, you are required to describe the test oracle. You may describe them in words or as JUnit assertion statements.

1. (2 points) A test case that does not reach the fault
2. (2 points) A test case that reaches the fault, but does not infect
3. (2 points) A test case that infects the state, but does not propagate
4. (2 points) A test case that propagates, but does not reveal
5. (2 points) A test case that propagates and reveals the failure

[Reminder: Two mandatory components of each test case: input value(s) and expected output — point(s) will always be deducted if any of these is missing]

If a test cannot be created, explain why.

Use PrimeNumbers.java from part 1.

Develop JUnit tests for the computePrimes() method.

Although we do not expect you to satisfy any specific test criterion, at minimum, your tests must reach every line of code in the method.

For each test, include comments (directly in your JUnit test file) that specify

• The purpose of the test
• Which part(s) of your automated tests address observability, if applicable
• Which part(s) of your automated tests address controllability, if applicable

Your JUnit tests must include the two tests you designed in part 1

• The test you designed for question 4 (not reveal the fault)
• The test you designed for question 5 (reveal the fault)

Do NOT modify or refactor the given Java source file.

• If you organize your file(s) in a package, please update the package name to match yours.
• If you do not use a package, please comment or remove the package package_name; line.

Run your tests and take a screenshot showing the test results. You will later include the screenshot in your report.

If the tests fail, analyze and briefly describe/discuss what causes the failure.

Consider the computeRangeSum() method of someOps.java.

Note: There exists a fault in the subject under test. At least one of your tests must detect it.

Do NOT modify or refactor the given Java source file.

• If you organize your file(s) in a package, please update the package name to match yours.
• If you do not use a package, please comment or remove the package package_name; line.

Apply RIPR model to design tests, develop JUnit data-driven tests for the computeRangeSum() method.

Although we do not expect you to satisfy any specific test criterion, at minimum, your tests must reach every line of code in the method.

You are required to develop JUnit data-driven tests.

• No points will be awarded for non-data-driven tests.

Run your tests and take a screenshot showing the test results. You will later include the screenshot in your report.

If the tests fail, analyze and briefly describe/discuss what causes the failure.