Test Results

Killer Forwards

Test Results

EEL 4884 Spring 2004

Modification history:

Version	Date	Who	Comment
v0.0	08/15/00	G. H. Walton	Template
v1.0	03/04/2004	Kristen Cannava, Rob Pescatore, Kip Carr	Initial Test Results information added
v1.1	03/28/2004	Kristen Cannava, Rob Pescatore, Kip Carr	Second Test Results added for implementation of Passing and rule understanding.

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

Introduction:

Overall Objective for Software Test Activity

Reference Documents

Description of Test Environment
Overall Stopping Criteria
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 higher level of functions work, such as passing and following the rules. For this iteration of software development, assuming the previous basic functional requirements were met, the software was to understand rules as well as be able to pass to a player. This involved properly recognizing all rule cases such as:

Kick off
Free kicks
Fouls
Corner kicks
Off sides
Goals
and Half time

It will also be able to pass the ball to another player given a lead for the player and calculating his position. In doing these things we will also calculate our absolute position on the field.

Expected Results:

The software test effort is expected to work and discover any initial problems that the program code may have. This could include not passing correctly to another player or wrong player, or any rule errors that we don’t follow. Further optimization may be done at a later date to improve the high level functions.

Reference Documents:

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 but should not exceed 3 hour per error. The code will be run in increments, fixing errors when they are encountered, several errors might be done at one time if they are small changes. 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. Testing will be run till all are working or the 3 hour limits have been meet.
If no errors are found during testing, several different test cases will be tried. The player will be initialized to several different positions to ensure that the player can locate the ball and handle any rules or exceptions that are being addressed. The player will also be tested to pass to a player in many different locations with varying angle and distance to ensure the code is working properly. The code will be "good enough to deliver" when all of the functional requirements are met for this iteration

SECTION 4: Description of Individual Test Cases

Requirement Test 106:

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.

Actual Results:

This test was performed March 28th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "marginal PASS". The player can locate a receiver on the same team and pass but some cases where the players are not facing the correct goal will cause errors in the calculation. Also, our player does not currently understand not to pass far backwards (away from the goal). The player does correctly pass in most cases and will pass to a moving target and a stationary one given that their trajectory stays the same from the last information received by the player. More testing will be done to correct the problem with the incorrect passing and should be done a day or so after these results are looked at.

Requirement Test 107:

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 targets is clear.
Test Conditions: See Test Environment
Expected Results: The player should check and only pass or shoot under the appropriate conditions, in this case only when the path between he and his target is clear.

Actual Results:

This test was performed March 25th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "PASS". The player can locate a receiver on the same team and attempt to pass given a clear shot. A clear shot for our program is specified as when an opposing team member is not within reachable distance to the line the ball will be traveling. This is done assuming that the opposing team member is traveling at maximum speed and is traveling toward the balls path line already. This was done to assume worse case considering the player would not have to turn and was already moving.

Requirement Test 108:

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.

Actual Results:

This test was performed March 28th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "marginal PASS". The player can lead a player but as was mentioned in the results for 106 the calculations some times have a problem and he will kick the ball at the wrong angle or power. More testing will be done to correct the problem with the incorrect passing and should be done a day or so after these results are looked at.

Requirement Test 109:

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.

Actual Results:

This test was performed March 24th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "PASS". Our player will anticipate steals by not letting them occur. We will not attempt to pass if there is any possibility of a steal from the other team. This does limit our passing abilities a bit more than necessary but will remove stealing all together.

Requirement Test 110:

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.

Actual Results:

This test was performed March 25th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "partial PASS". The reason for the partial pass is currently the code forces all forwards to run towards the ball so they will be running towards the ball trying to intercept it if an opponent has possession of the ball.

Requirement Test 111:

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.

Actual Results:

This test was performed March 28th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "PASS". The player can be told to move to an absolute position on the field and the player will run to that location unless another play is called for in the code. This was shown when certain play modes, such as free kick right, needed the player to move to a given location.

Requirement Test 112:

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.

Actual Results:

This test was performed March 25^th and 28^th, 2004. This test case was performed in the Linux environment, specifically the PC Linux 5. This test was performed with the entire group present. This test was a "PASS". The player can handle all rules mentioned in the introduction. Depending on which teams fault the foul or status was will determine if the player should go interact with the ball or move to an appropriate location on the field. This was shown by going through each foul in the game and verify the players move into correct position.

Comments:

Testing was overall a success. All of the higher functions worked enough to progress to the next phase. Further optimization was easy to do once certain issues became apparent during testing.

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 Kip Carr ( Email ) on March 28, 2004.