Software Testing Lab - A First Exercise

Along with writing posts about Software Testing, thought it would help if I could design a laboratory framework for students in parallel.  So, in the Software Testing Lab Series, the objective is to look at aiding students applying techniques of testing in a laboratory set up.  The scope involves defining objectives, links to reading material, exercises and evaluation.

Session I :

1.  The best way to get an idea of the skills of 'customers' in the software lab, is to test their knowledge in Software Testing.  This can be done through a test, an objective test, which serves as a self-assessment mechanism for students and also gives the faculty an idea of student knowledge.  It would be better that papers are interchanged and students themselves correct.  It serves as reinforcement where correct answers are given, and a correction mechanism in cases of errors.  Usually, I give fifteen questions, at three levels of difficulty - tough, medium, easy.  The reason behind such a scheme is that even the weakest in the class will feel that through continuous work, (s)he can succeed in the lab - even then, some get intimidated :(                A sample is given.

2.  Give an outline of what is to be covered in the lab in 3 minutes.  If there is a syllabi defined, introduce the syllabi. Otherwise, give an outline on the plan for the lab.  Do remember to get a feedback.

3.  Write a Java program called Compute that does the following operations on two integer inputs a and b.

    

     add(int a, int b)

     subtract(int a, int b)

     multiply(int a, int b)

     divide (int a, int b)

     Write test cases for the above. Formulate the test cases in a table. 

Evaluation :  Check if the students have used Equivalence Class Partitioning techniques for designing test cases.  If yes, they are on the right track.  If not, discuss the technique and motivate them to rewrite.  Exhaustive testing through large number of test cases must be dissuaded.  Being the first exercise, possible test cases maybe listed and discussed.

4.  Manual testing may be done and results noted.

Addendum :  Please leave a comment.  Suggestions, comments, discussions and queries are most welcome.