Question

Define black box and white box testing. What are the advantages of each approach? Why are both necessary? Why Is it Important to be able to partition the test space into equivalence classes? For the following code fragment, describe 3 different test cases, and for each, describe the class of test cases It represents. The below code might or might not have any issue(s) public String print Triangle Type (Int x, y, z) {I* requires: The parameters are in ascending order (i. e. x <= y < = z) effects: If x, y and z are the lengths of the sides of a triangle, this function classifies the triangle using one of the three strings, "scalene", "Isosceles" or "equilateral". If x, y, and z do not form a triangle, the empty string Is returned. */String r; r="scalene"; If (x == y || y == z) {r="equilateral"; return r;} If (x == z) {r="isosceles"; return r;} If (x <= 0|| (x + y) <= z) {r=""; return r;} return (r);} Compute the Cyclometric complexity of the method. Full path coverage testing requires that every possible path through the code be tested at least once. For the code fragment above, how many test cases would be needed for full path coverage? Why might full path coverage be impossible to achieve for some programs Statement coverage testing requires that all statements in the program executed at least once. Provide a test set which has a complete statement coverage. What kinds of error might this testing miss?

Answer 1

1) BlackBox Testing : It is the testing method where testing is focused on examining functionality of application without worrying about its internal workings or structure. This approach can be implemented on all the levels of testing like unit, integration, and acceptance. The test cases to perform testing are build considering requirement and specification which means on the basis of what the application need to do .And both valid invalid scenarios are considered.

White Box Testing - It is the approach which focuses on internal working of applications and not focuses on only its functionality. In this process knowledge of internal perspective of whole system as well as programming knowledge is required to build the required test cases. This approach can be applied to unit, integration and system testing, like at unit testing level its done to ensure code is working as expected before we proceed to integration testing and then in integration testing it helps to check how does it work with other systems in place.