[SOLVED] CS6300 Assignment 6: White-Box Testing FALL26

● : Class FaultyClass contains the following method faultyMethod4: public static int faultyMethod4(int a, int b, int c, int d, boolean e) {

    int result = 0;     if (a > b) {         result = 1;     } else {

        if (((c != 0) || (d == 0)) && (e)) {             result = 2;         } else {             result = 3;

        }     }

    return result;

}  

Create two JUnit test classes as follows, where each test case performs a single invocation of faultyMethod4. o FaultyClassTestSC4 should achieve 100% statement coverage of faultyMethod4 and contain at most 3 test cases. o FaultyClassTestMCDC4 should achieve 100% Modified

Condition/Decision Coverage (MC/DC) of faultyMethod4 and contain at most 8 test cases.

o   Partial credit will NOT be awarded if FaultyClassTestSC4 and

FaultyClassTestMCDC4 do not satisfy their respective requirements.  o Bonus Points: If FaultyClassTestMCDC4 achieves 100% MC/DC coverage with the minimum possible number of test cases, then you will receive 10 bonus points.  Determining the actual minimum is part of the bonus task (but you may safely assume the minimum is less than or equal to 8).

o   Both classes should be saved in the directory <dir>/test.

● Task 5: Method faultyMethod5 in the provided class FaultyClass contains:

○ The code below, commented out:

          /*-

public static boolean faultyMethod5(boolean a, boolean b) {      int x = 2;       int y = -4;   

       if(a)           x -= 2;        else           y += 1;       if(b)           x -= 1;      else            y += 3;  

    return (y/x < 0);  

}

*/

○ The following table, where you can provide your responses as strings (please note that the table in the code has a slightly different format because we want to be able to run that part of the code):

//  

//

// Replace the “?” in column “output” with “T”, “F”, or “E”:

//

// | a | b |output|

// ================

// | T | T |   ?  |

// | T | F |   ?  |

// | F | T |   ?  |

// | F | F |   ?  |

// ================

○ The following sentences, where you can again provide your responses as strings (also in this case, the format in the code is different to make the code executable):  

//

// Replace the “?” in the following sentences with “NEVER”, // “SOMETIMES” or “ALWAYS”:

//

// – Test suites with 100% statement coverage “?” //   reveal the fault in this method.

// – Test suites with 100% branch coverage “?”

//   reveal the fault in this method. // – Test suites with 100% path coverage “?” //   reveal the fault in this method.

// ================

Fill in your answers in the method, as follows:

○ For every possible input, replace the “?” in column “output” of the table, with “T” to indicate that the return value is true, or “F” to indicate that the return value is false, or “E” to indicate that the method exits with a division by zero error.

○ In the sentences following the table, replace the “?” with “NEVER”, “SOMETIMES”, or “ALWAYS” to indicate whether a test suite with 100% coverage for the specified criterion NEVER reveals the fault, SOMETIMES reveals the fault, or ALWAYS reveals the fault in the faultyMethod^[1] method.

Notes (important–make sure to read carefully):

1.      When we say “create in class FaultyClass a method called faultyMethod N”, we mean that you should complete the placeholder for that method provided in the skeleton class, by either modifying its code (and possibly method parameter(s)) or providing a suitable comment and an empty body.

2.      Explanations of why a method cannot be created, if any, must be written using the format provided in the method examples in the FaultyClass skeleton class.

3.      Committing (or omitting) class ExampleTestSC1 has no effect on your grade.

4.      Similarly, leaving or removing the example methods provided in the FaultyClass skeleton has no effect on your grade.

^6.          For tasks 1 through 3, if the task is possible, every one of these methods can be written with simple, short code. For these 3 tasks, you cannot use any of the following constructs in your solution:^[2]

a.    Compound Predicates.  That is, only use simple predicates in the form

(<operand1> <operator> <operand2>), such as “if (x > 5)” or “if (a >

b)”. In other words, you cannot use logical operators (such as &&, ||) in your predicates.

b.   Nested if statements and “else if” constructions.

c.    throw new ArithmeticException. The code should naturally fail due to an arithmetic operation that results in a divide-by-zero exception.

d.   Loops.  (while, for, do, etc.)

e.   Method calls.  Your method should be self-contained and not call any other methods (including itself).

f.    Conditional (trinary) operators.  (No use of the “<condition> ? <case if true> : <case if false>” construct.)

g.    Switch statements.

h.   Streams, lambdas, or other newer complex features of the language.

i.     Dead or unreachable code.

j.    Static variables or class variables.

^7.          A single if/else statement already creates 2 branches. You do not need multiple if statements to satisfy the “at least 2 branches” requirement.

^8.          You should not modify the methods provided in tasks 4 and 5.

^9.          Read the requirements carefully. For example, “Every possible test suite…” means all conceivable test suites for your method, not only the example test suite you write. 

^10.        Your code should compile and run out of the box with Java 17.

^11.        Use the provided JUnit library for your JUnit tests.

^12.        Unlike normal tests, an assertion is unnecessary. However, if you choose to include one, ensure that it does not interfere with the expected coverage results.

^13.        We strongly recommend computing coverage manually, as tools sometimes use slightly different definitions of coverage and may have some quirks. Given that the solutions typically consist of very simple methods, it should be easy to compute coverage by hand (which is how we do it when we grade the assignment). Although the lectures imply that braces count as statements with regard to coverage, you may ignore braces while determining your coverage.

^14.        This is an individual assignment. You are not supposed to collaborate with your team members (or any other person) to solve it. We will enforce this by running a plagiarism detection tool on all assignments. Given the numerous different ways in which the assignment can be solved, similar solutions will be (1) easily spotted and (2) hard to justify.

^15.        Similarly, make sure not to post on Ed Discussion any solution, whether complete or partial, and also to avoid questions that are too specific and may reveal information about a specific solution, or imply which tasks you believe are possible. You can obviously ask these types of questions privately to the instructors.

Submission:

●     As usual, commit and push your code to your individual, assigned private repository.

●     Make sure that all Java files are committed and pushed (i.e., class FaultyClass and any created JUnit test classes). Also make sure to commit and push the provided libraries (lib directory), which are typically excluded by the “.gitignore” file. To do so, you may need to force add the jar files (i.e., “git add -f lib/*”).

●     You can check that you committed and pushed all the files you needed by doing the following:

○ Clone a fresh copy of your personal repo in another directory ○ Go to directory Assignment6 in this fresh clone of your repo

○ Compile your code. One way to do is to run, from a Unix-like shell:

javac -cp lib/\* -d classes src/edu/gatech/seclass/FaultyClass.java test/edu/gatech/seclass/*.java

○ Run one or more of your tests. Again, from a Unix-like shell, you can run:

java -cp classes:lib/\* org.junit.platform.console.ConsoleLauncher -select-class edu.gatech.seclass.<test class name>^[3]

(at least one of the tests should fail with an ArithmeticException)

●     Submit on Gradescope a file called submission.txt that contains, in two separate lines, (1) your GT username and (2) the commit ID for your submission. For example, the content of file submission.txt for George P. Burdell could look something like the following:

submission.txt

As soon as you submit, Gradescope will check your assignment by making sure that your files are present and in the correct location, compiling the code,

running your tests, and performing some sanity checks on the outcome of such tests. If you pass all these checks, you will see a placeholder grade of 10 and a positive message from Gradescope. Otherwise, you will see a grade of 0 and an error message with some diagnostic information. Please note that a positive response from Gradescope only indicates that you passed the sanity checks and is meant to prevent a number of trivial errors. Please also note that if your submission does not pass the Gradescope checks, it will not be graded and will receive a 0, so please make sure to pay attention to the feedback you receive when you submit.^[4]