Example System Test Cases for Critique


Test Case 7

Revision History
Author Description Date
David G Created 11/16/08
Nathan T Updated Test Case 03/09/08
     

Requirement Traceability: Purpose:
  1. Verify that users can enter a single player game in Beginner Mode.
  2. Verify that users can enter a single player game in Easy Mode.
  3. Verify that users can enter a single player game in Medium Mode.
  4. Verify that users can enter a single player game in Hard Mode.
  5. Verify that users can enter a single player game in Competitive Mode
  6. Vertify that users can enter a multi player game with 2 players.
  7. Verify that users can enter a multi player game with 3 players.
  8. Verify that users can enter a multi player game with 4 players.
Procedure:
Follow the steps below:
 

Test Data:
 

Action
Input
Expected Output
Start the application.   The start button appears.
Click the "Start" button.   The game begins.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "Beginner"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "Easy"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "Medium"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "Hard"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "2 Player"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "3 Player"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.
Click "4 Player"   The Main Menu closes and the Main Window opens.
Click "Menu" button on the menu bar   Menu window is displayed
Click "New Game"   The Main Menu appears and the In Game Menu goes away.



Test #6: Adding an employee

Purpose:

  1. Verify you can add an employee through the GUI

  2. Verify when selecting an employee it displays the employees correct information.

Procedure

Launch Lemming Schedler.

Add Skills for “Baker” “Stocker” and “Cleaner” .

Click “Databases” and then “Employee” to access Employee Window.


Action

Input

Output

Click Add button


The first name, last name, phone, checkboxes, and availability become modifiable.

Select first name

Type “Joe”

“Joe” is now in the first name

Select last name

Type “Jack”

“Joe” is now in the last name

Select phone name

Type “555-555-5555”

“555-555-5555” is now in the phone field.

Check skill for stocker and cleaner


Checks are in stocker and cleaner fields, baker is unchecked.

Drag hours in availability for Mon from 0600-1100


“X” is placed in the hours for Monday from 0600-1100

Click Done button


“Joe Jack” is added to the list of employees

Click on “Joe Jack” in the employee list


First name displays “Joe” Last name displays “Jack”

Phone displays “555-555-5555”

Skills baker is unchecked, stocker and cleaner are checked

There are X’s in hours M 0600-1100, all the rest are clear.

All these fields are not editable



Test Case#7:  Save and Load

Purpose: Procedure:

Start lemming scheduler then add a piece of data. Then save and quit. Then start and load.

Test Data:

Action

Input

Expected Output

Start the scheduler

OS dependent

Sunday day view of this week with the schedule for Sunday.

Click the database menu

Menu click

Database menu drops down and shows skill, employee, and shift.

Click the skill menu item

Menu Item click

The skill user interface.

Click add

Button click

A pop up prompting for a skill name.

Type “Test” in the box

Test

“Test” is in the input box.

Click ok

Button click

The dialog closes and the skill frame has focus again.

Click done

Button click

The dialog closes itself and the main scheduler window has focus with the Sunday day view.

Click the file menu

Menu click

The menu drops down and display new, load, save, and quit.

Click the save menu item

Menu Item click

A dialog prompting you about the dangers of saving presents itself.

Click yes

Button click

The dialog closes itself and the main scheduler window should have focus again with the Sunday day view.

Click the file menu

Menu click

The menu drops down and display new, load, save, and quit.

Click the quit menu item.

Menu Item click

A dialog confirming the quit pops up.

Click yes

Button click

The program closes itself cleanly.

Start the scheduler

OS dependent

The Sunday day view of this week is in the main view.

Click the file menu

Menu click

The menu should drop down and display new, load, save, and quit.

Click the load menu item.

Menu Item click.

A dialog prompting the user about the dangers of loading presents itself.

Click yes

Button click

The dialog closes itself and the main frame has focus with the Sunday day view.

Click the database menu

Menu click

Database menu drops down and shows skill, employee, and shift.

Click the skill menu item

Menu Item click

The skill user interface. Examine the list of skills. “Test” should be in the list.

Close the windows until none are open.

OS button clicks

Everything is closed.





Section 2 - Managing Skills

Purpose:
     1. Verify a window with an empty name field pops up when the user clicks the 'Add'
     button.
     2. Verify adding a skill works (2.1).
     3. Verify a window with a filled in name field pops up when the user clicks the 'Edit'
     button.
     4. Verify editing a skill works (2.2).
     5. Verify a window pops up asking if the user wants to remove the selected skill when
     the user clicks the 'Remove' button.
     6. Verify removing a skill works (2.3).
     7. Verify the 'Skills' window closes when the user clicks the 'Done' button.
Procedure:
     Open a command window and change to the directory where EmployeeScheduler.jar
     is located.
     Run the jar file.
     Click on 'Edit' in the top left.
     Click on 'Skills'.
     Follow the steps below:
Test Data:

Action         
Input      
Expected Output
Click the 'Add' button

A window should pop up with a blank name field.
Type 'Manager' into the name field
'Manager' Manager should appear in name field.
Click the 'Ok' button

'Manager' should appear in list of skills on the left.
Click the 'Edit button

A window should pop up with a blank text box.
Change 'Manager' to 'Cook'
'Cook'
'Cook' should appear in the name field.
Click the 'Ok' button

'Cook' should now appear in the list of skills on the left and 'Manager' should not.
Click the 'Remove' button

A window should pop up asking if you want to remove 'Cook'.
Click the 'Ok' button

The list of Skills should now be empty
Click the 'Done' button
The 'Skills' window should close and the user should be back at the main window.

                                                             
     

Section 4 - Managing Preferences


Purpose:
     1. Verify that a new window opens for editing a project and that it closes when user
         clicks OK
     2. Verify that the user can input data and change settings within the edit project
         window.
     3. Verify that the program adapts to the user's settings after they click OK
Procedure:
After having run Section 1, there should be a saved file called preferences in the directory of
the program. Start the program with this file in the current directory.
                                               


    Action
Expected Output
From the main window click on the word  "Edit" in the top menu, and then click preferences from that menu.                  


Click on the text field next to the words
 "Company Name"

 Delete the characters "G1"

 Enter the word "Poly Cron" 

 Click on the combo-box, currently showing 5:00, next to the words "Earliest shift begins at"

Click on the time "3:00" 

Click on the combo-box, currently showing 7:00, next to the words "Latest shift ends at"

Click on the time "2:00"

Click the button labeled "OK"


Click on the combo-box, currently showing 2:00, next to the words "Latest shift ends at"

Click on the time "24:00"                     

Click the button labeled "OK"  



 The preferences editor window appears, it does not say that preferences need to be set up. The company name text field  contains "G1", the Earliest shift begins at 5:00, and the latest shift ends at 7:00.

A cursor appears in the text field


The text field is blank

The text field displays the word "Poly Cron"

 A list appears with hours from 0:00 to 23:00



The list closes and the combo-box now displays "3:00"

A list appears with hours from 1:00 to 24:00



The list closes and the combo-box now displays "2:00"

A message appears stating that start time must be earlier than end time.

A list appears with hours from 1:00 to 24:00



The list closes and the combo-box now displays "24:00"

The preferences editor closes and the main window is displayed