Attendance at the lab session on Wednesday, April 9 is worth 20 points.

This is an individual / team activity. Every student is expected to write the test cases by themselves and submit before the lab period. Then the team is supposed to combine the individual test cases to get a better set of test cases and submit that as the Team result.

Educational goals of this activity - verify that every student can

• work with their team
• understand the programming assignment well enough to write test cases

INSTRUCTIONS:

Please read this page on testing files.

1. (10 points on Program 4 grade) Individual Problem:
   • As stated in the program assignment each student is supposed to write some test cases and submit them through the program assignment link below.

   • Testing

     Read the assignment carefully. Look at how the program is supposed to behave. You do not know what the code looks like yet - that is fine. The assignment gives an example of normal runs. Consider if the user can cause failures. How can the file cause problems?

     As the form describes, do some hand work and turn in two text files also.
     "Choose 40 or 50 random numbers in the range 0 to 255. (If you don't want to do that by hand, you can write a little program to do it for you.) Save them in a text file called data.txt.
     Choose a 4-5 letter message - any ASCII characters are allowed. ASCII chart
     Go through the insertion process as described in the assignment. It is easier to use the description which uses every number instead of every third number (just so you don't have to make up so many random numbers).
     Save the final state of the data - all of it, not just the ones you changed - in another text file, called coded.txt
     Submit the two textfiles - the before and the after - for 10 lab points. This also counts as one of your test cases. You should save the files for use later with the actual program. You can use the same submit link as for the program - just use Program 4 and Other as the type.
     Now extract the message from the coded.txt file using the extraction algorithm. Verify that you get the message back that you inserted."

     Make a test plan for this program.
     Save this doc file and fill in the table with test cases. You should have at least 16 non-redundant cases (that counts all the ones you make in all tables).

   • Put your name and the section at the top.

     Submit this .doc file with your individual test cases at the link here.

     Choose the menu choices of "TestCases" and "Program 4". This will be due on Tuesday April 8, midnight before the team development of test cases in lab on Wednesday . Remember to bring this file with you to lab the next day to contribute to your team's effort.

2. (15 points on Program 4 grade) Team Problem: Done during session on Wednesday April 9
   • Save this form.
   • Combine the test cases of all team members into this form. Your test cases should be thorough but not redundant. You don't want a lot of cases that test the same thing. Note that there are three tables to have some test cases in.
   • It is assumed that the team will come up with more and better quality test cases than each individual member. You should have at least 18 non-redundant test cases.
   • Put the name of each team member who is present in the form.
   • Make sure each member gets a copy of the team test cases and that they understand the test cases.
   • Submit the team result with this link. Use menu choices "Test Cases" and "Program 4".
3. Listen to the lab instructor discuss test cases for Program 4. You are allowed/encouraged to ask questions and take notes during this discussion.

When you are finished with this activity, you should have:

• (everyone!) submitted your individual test cases
• (one per team) submitted your team test cases

Log off properly - you don't want your account misused by someone else!

Remember NOT to leave files on the local hard drives in this lab or anywhere else on campus! Make sure you save your projects on the Locker drive or onto a portable storage device you take with you!

Submission Deadlines:

Individual Test Cases, Tuesday April 8, midnight
Team Test Cases, Wednesday April 9, deadline given by instructor during the lab period