Test Plan

EEL 4884 Spring 2004

Modification history:

Killer Forwards

Team Members:

• Kristen Cannava Email Kristen's Webpage
• Kip Carr Email Kip's Webpage
• Robert Pescatore Email Rob's Webpage

Contents of this Document

1. Introduction:

Overall Objective for Software Test Activity

Reference Documents

2. Description of Test Environment
3. Overall Stopping Criteria
4. Description of Individual Test Cases

SECTION 1: Introduction

• Overall Objective for Software Test Activity:
  
  The underlying objective for the software test activity is to ensure that the basic functions required are intact. For this iteration of software development, the player is to be able to pass to team members, verify clear paths during passing and shooting, anticipate steals (either for their team or against their team) and obey all rules.


• Expected Results:
  
  The software test effort is expected to work and discover any initial problems that the program code may have. The previous test results were positive so through this iteration we expect all of the previous functionality to work properly unless it needs to be changed for the sake of functionality. For this set of added functionality, the player must be able to perform the activity, but not necessarily have the appropriate intelligence to know when. This will be done in later iteration.

Reference Documents:

• Concept of Operations
• Project Management Plan
• Software Requirement Specification
• Robocup Manual

SECTION 2: Description of Test Environment

The hardware and software that the program code will be tested on will be those provided in the lab. The hardware will be basic desktop PCs, the software environment will be the Linux/UNIX operating system. The testers will be the developers. The test environments are the same as those in which the software will run.

SECTION 3: Stopping Criteria

• Errors are going to be fixed when they are found. Testing length will be arbitrary. The code will be run in increments, fixing errors when they are encountered. The length of time that testing will take will be related to amount of errors as well as they amount of time required to fix them.
• If no errrors are found during initial testing, several different test cases will be tried. The player will be tested with only two players at first, then two and so on and so forth. This will ensure that functionality is working on a basic level at first then additionally complexity will be added as more players enter the field.

SECTION 4: Description of Individual Test Cases

• Test Objective: To test the ability to pass to another player
• Test Description: This will test the ability of a player within kicking distance of the ball to pass the ball to another player on the same team. Various players in various positions will be tested to ensure this ability.
• Test Conditions: See Test Environment
• Expected Results: The results will be that the player will properly calculate the necessary force and direction for the pass and the receiving player will be able to gain control of the ball.

• Test Objective: To test the ability of the player to verify a clear path when shooting or passing.
• Test Description: The player must be able to identify obstacles in the way of a clear shot or pass. Most likely these obstacles will be other players. We will check to make sure that before a shot or pass is made that the path between the target is clear.
• Test Conditions: See Test Environment
• Expected Results: The player should check and only pass or shoot under the appopriate conditions, in this case only when the path between he and his target is clear..

• Test Objective: To test the ability of the player to properly lead another player on with a pass.
• Test Description: When the decision has been made to pass to another player, the player must calculate the appropriate kick power and direction to ensure that when a pass is made to a running player he will not have to slowdown, the ball be on a intersection path with his current trajectory.
• Test Conditions: See Test Environment
• Expected Results: The expected results are that the player will have the ability to move around the field and that he will do so accordingly to our AI function.

• Test Objective: To test the ability of the player to anticipate steals from the other team.
• Test Description: During player, other players may approach towards our target player or goal. In this case, when it is obvious that the defending player may be able to perform a steal, an appropriate action be taken. For instance, instead of passing the player will continue to dribble the ball instead.
• Test Conditions: See Test Environment
• Expected Results: The expected results are that the player will make appropriate decisions depending on the position of defender.

• Test Objective: To test the ability of the player to intercept passes and shots.
• Test Description: During play, the player may be in a position to intercept a ball passes to a player on the opposite team or a shot towards either goal. The player should appropriately attempt to intercept the ball at these times.
• Test Conditions: See Test Environment
• Expected Results: The expected results are that the player will make appropriate decisions depending on the position of the ball and his position on the field.

• Test Objective: To test the ability of the player to move to a specific location on the field.
• Test Description: While running on the field, the player should have the ability to move a specific location. For instance, this would include being able to center field or to the goalie box via a specific command.
• Test Conditions: See Test Environment
• Expected Results: The expected results are that the player will be able to run to specific location on the field.

• Test Objective: To test the ability of the player to handle all fouls and game states.
• Test Description: At any time during play, the referee may change the game state. At this time, our players should move to the appropriate position on the field depending on the nature of the game state. Also, the player should openly break any of the rules of soccer as specified by the robocup server. This includes free kick faults, etc.
• Test Conditions: See Test Environment
• Expected Results: The expected results are that the player will not break any of the rules and that any game state called by the referee will handled in the appropriate fashion.

Template created by G. Walton (GWalton@mail.ucf.edu) on March 28, 1999 and last modified on August 15, 2000.

This page last modified by Rob Pescatore ( Email ) on March 23, 2004.