COMP 122 Lab 4 Lab Report and Source Code

FB8B5ADBDC9
Published on July 1, 2015

COMP 122 Week 4 Lab Part 1 Part 1 of this week’s lab will give you an opportunity to use the debugging capabilities of Visual Studio. Part 2 will present a problem for which you will need to create a test plan and actually test an executable program to determine if it behaves correctly. Part 1 – Using the Debugger To begin this exercise, create a VC++ project and copy the following code into your project. Make sure that the project compiles successfully. #include using namespace std; int main() { int input; int , ; int ; cout<"enter="" which="" number="" in="" the="" fibonacci="" number="" sequence="" you="" want="" to="" find."=""><endl;=""> cout<"the="" first="" and="" second="" fibonacci="" numbers="" are="" 1."=""><endl;=""> cin>> input; while (input < 1)=""> { cout<"you="" must="" enter="" a="" value="" greater="" than="" 0,="" try="" again."=""><endl;=""> cin>> input; } if (input > 2) { for(int ; i < input;="" i++)=""> { ; ; + back2; } } cout<"the="" value="" of="" fibonacci="" number="""="">< input=""><"="" is="""="">< current=""><endl;=""> cin.ignore(2); return 0; } Part 2 – Black Box Testing A customer has requested a program be developed to meet the following criterion: 1. The program needs to convert from celcius temperatures to fahrenheit temperatures. 2. The user should be able to enter temperatures containing fractional degrees (ie. 12.3) 3. The converted temperatures should be accurate to within 1/10th of a degree. 4. The user should be able to enter the number of temperatures to be converted up to a maximum of 10. 5. The output should be tabular with each row including the input and converted temperature. Write a test plan to thoroughly test this program. The executable for this program is included in with this lab. You should have test cases which verify that the program does all of what is required in the problem specification above. You should also test to see how robust the program is, that is, how does it handle inputs outside the expected ranges. Document your test plan in a table. For each test case, document the expected program behavior and the actual program behavior. If the program does not behave according to your prediction, write a brief explanation of what the program did wrong.