Robot Controller
Test Results
Senior Design, Summer, 2001
Modification history:
Version |
Date |
Who |
Comment |
v0.0 |
08/15/00 |
G. H. Walton |
Template |
v1.0 |
07/18/01 |
Jeff Goodman |
Test Results |
Test Objective | Test if the system does actually control a robot. |
Test Description | Start the programs, on their respective machines. Attempt to move the robot using the two interfaces. |
Test Conditions | We will perform this test preferably twice, the first time will be on a regular Ethernet network using two Linux machines. The second test will be performed on wireless Ethernet using two Linux machines. |
Expected Results | The system will control the robot in either of the two given tests. |
Pass | The system controlled the robot in either of the two given tests. |
Test Objective | Test surrogate to see if it responds like an actual robot |
Test Description | Start the programs, on their respective machines. Attempt to control the robot using one of the two interfaces (probably the human control), and compare results of the surrogate to that of an actual robot. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | We expect that the surrogate will perform its actions exactly as a real robot would. |
Pass | The surrogate acted exactly as the real robot did. |
Test Objective | Test communication between API and surrogate. |
Test Description | Monitor where there is two way communications between the surrogate and API. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | Two way communications will take place. |
Pass | Two way communication was accomplished. |
Test Objective | Test the GUI to see if it properly displays the motion of the robot. |
Test Description | Move the robot using the human interface, and monitor the motion of the robot, and compare this with the on screen value. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | The GUI will properly display the motion of the robot. |
Pass | GUI did display the motion of the robot. |
Test Objective | Test the commands of the system (forward, backward, turn left, turn right, increase speed, decrease speed, stop). |
Test Description | Using the human interface test each of the commands given. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | The surrogate or actual robot will respond to the commands and take the appropriate actions to carry them out. |
Pass | The surrogate and the robot responded to all commands from the controller. |
Test Objective | Test to see if the API has a standard interface that both the human interface and OTB are communicating with. |
Test Description | We will review our code and test it against our detailed design to make sure we are following our design. |
Test Conditions | Code review meeting. |
Expected Results | Our design will match our planned design. |
Pass | Our design did match the planned design |
Test Objective | Test that only the API is controlling the robot through its common interface. |
Test Description | Start the programs on their respective machines. Input no commands to the API, and make sure the robot does nothing except send regular status reports. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | The robot will not move, but send regular status updates. |
Pass | The robot sends status updates. |
Test Objective | Test to see if our human interface is acceptable (comfortable to use and understand what is going on with the robot). |
Test Description | Show our interface to our client and get it approved. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | Our client will approve of the interface, which we have constructed. |
Pass | All users have approved of the interface. |
Test Objective | Test documentation is meeting our set coding standards. |
Test Description | Code Review, we will have a meeting and examine each others code to make sure we coding to the standards we have established. |
Test Conditions | Meeting |
Expected Results | Our code will meet our standards. |
Pass | We met our coding standards. |
Test Objective | Test responsiveness of the system. |
Test Description | We will issues commands to the robot rapidly. |
Test Conditions | We will perform this test on an Ethernet network using two Linux machines. |
Expected Results | The system should respond rapidly to the input commands. |
Pass | The machine responds quickly to commands. |
Test Objective | Test for robustness. |
Test Description | Each programmer will test their code for exceptional circumstances. After the program is completely integrated we will also test for robustness |
Test Conditions | While coding, or shortly after completion. Also we will test for robustness when the entire system is built. |
Expected Results | Our program should be stable and handle all exceptional events. |
Pass | The program is stable. |
Template created by G. Walton (GWalton@mail.ucf.edu) on August 15, 2000.
This page last modified by Jeff Goodman (goodmanj@orl.saic.com) 07/18/01