Student Resources > CMPT 275 > assignment schedule > Test Cases Document

Test Cases Document

Deliverable 7 will be your Test Cases Document will contain the following sections:

• Cover page
• Revision History
• Table of contents
• Test plan for one significant method using white (glass) box testing
• Test plan for one (different) significant method using black box testing

This document is expected to be significantly shorter than previous documents.
This document should be written WHILE you are implementing your prototype

Some Helpful Instructions for Document Preparation

1) You MUST use the title page provided as the first page of your Implementation / Test Plan and Test Cases Document.

2) Your revision history MUST be on the page following your title page. Be sure to update your revision history. Provide information on which sections have been updated and by whom.

3) Your table of contents MUST include all section and subsection titles, as well as the page numbers on which each section or subsection starts.

4) To develop a test plan for a single method using Glass (White) box testing strategy select a method of a class you will write / wrote as part of this project. A get or set method is not an acceptable choice. For the selected method develop a test plan by following these steps:

• Describe the purpose of the method
• Analyze the code for the method and break it into appropriate numbered blocks
• Develop a flow chart for your method based on the blocks of code the method was broken into in the previous step
• Comment on the types of coverage needed to test the method
• Develop a list of test cases that will adequately test the method. Do not fully develop each test case. ONLY list the coverage of each test and explain why the test is needed/useful
• Choose one of the test cases and describe it in detail in terms of the test case format used in class
• Demonstrate how your selected test case (input values) will help test the intended coverage.

5) To develop a test plan for a single method using Black box testing strategy select a method of a class you will write / wrote as part of this project. A get or set method is not an acceptable choice. The method may not be the same method you used for white box testing. For the selected method develop a test plan by following these steps:

• Describe the purpose of the method, its parameters (arguments), and any preconditions necessary for successful execution of the method
• Describe the equivalence classes for each of the inputs and preconditions of this method
• Describe how you would choose representative input values to test this method
• Briefly describe how you would use the representative values to construct a set of test cases to test the method. DO NOT develop these test cases beyond describing them in terms of the values of the parameters and the preconditions.
• Select a single test case from those discussed in the previous item
• Describe your test case using the test case format seen in class.

6) The electronic copy of your project planning document must be checked into your subversion repository. Each team member should post their own contributions to the document (before incorporation into the document and any necessary edits made during incorporation) to the teams SVN repository

Marking Scheme - out of 50

• 23 marks for the clarity and completeness of the discussion of white box testing
• 22 marks for the clarity and completeness of the discussion of black box testing
• 3 marks for submitting 3 team members contributions to the teams SVN repository. Each team member contributing to the document should submit their own contributions to the document (including any revisions to their own or other team members work) to the teams SVN repository
• 2 marks for checking the submitted version of your requirements document into your subversion repository