Criterion B - Solution Overview

Instructions and Advice - Testing Plan

(Overall key point from past grading: Try not to have any full sentences at all, or this could count as part of the word count. Try in general to make all of section B to be diagramatic, so here with testing, keep the descriptions as short and not sentences.)

(Repeat of Overall key point from past grading: Keep up with your Record of Tasks; now would be a good time to make sure you have all of the things you have done for Criterion B recorded.)

For each of your tab panels, take a screen shot of it (and probably re-size it a bit), and discuss the things that the user will do with that tab, and include sections about normal functioning, as well as situations that might cause problems.

Use the following example to guide you, and do use exactly the same sub-sections ("Things Done on this Tab" etc.), though note that the example is not exhaustive of all the things you might put here. Think about all the different things that could go wrong, and note them along with what should happen, such as an error dialog showing.

And do pay attention the important note at the bottom of this page regarding the expectations of this assignment.


This can be done as bullet points, but better might be a table, so that sentences and word count do not become as much of a potential issue.


Another thing to consider is whether or not you want to put the hoped for result.

Example (one tab only):

Enter Player Details Tab

GUI tab

Approach 1 - Table

Things Done on this Tab

- Inputs:

• Basketball player names are input.
• The numbers associated with each player are also input.

- Internal Functioning

• Instances of the Player class are made and assigned to an array of players.

Input Normal Border Abnormal Extreme
Name John Smith

Short name like JR

No name input

- Short names are OK, but no name results in a re-entry Warning message

Czech etc. characters


- Warning Message, and not taken in/parsed

Very long name - 30+characters

- No limit on what allowed here.

Player Number 25


No number input

- 0 is OK, but warning message and re-entry if no number

String input; ex. Two

Negative number

Real number

- In all cases re-entry required

Really big number.

- Limit to two digits, re-entry warning

Player instances made An instance with a name and a number set. N/A N/A N/A

Make sure to include what should happen with each border/abnormal/extreme situation. (Above, italics points are the style for these.)


Approach 2 - Bullet Points

Things Done on this Tab

• Basketball player names are input.
• The numbers associated with each player are also input.
• Instances of the Player class are made and assigned to an array of players.

Normal Functioning

• A name such as Bobby Smith is input, and a number, like 24 is input. So the Player instance can be properly made.

Border Cases
(if any):

• Inputting a 0 for the player number is a border case, but it should be accepted. But numbers with three digits should not be.

Abnormal/Extreme Situations

• If no name is input, an error dialog box should be given, and the same with the player number.
• If a number is inupt for the name, or if a String is input for the number, an error dialog box should show.
Other Potential Problems (if any):
• If the array is full, let the user know with a dialog box.

Important Note
: If you find it is taking more than the 45 minute - one hour limit (of non-multitasking time), don't rush through all the tabs, rather do that much work and submit it, but completely and well done for those tabs. And then you can continue next class with the other tabs, along with the actual Tests table.