System Test Cases

System Requirements:
(For testing purposes only)

• Windows ME or Windows NT 4.0
• JDK 1.3

Directions:

1. Download the source jar for the current build.
2. Unjar the jar file
   • jar -xf currentbuildsource.jar (replace 'currentbuildsource.jar' with the real file name)
3. Create a new folder named "ETA".
4. Place the 2 folders that the source jar unpacked inside "ETA".
5. Inside "ETA", create 3 folders named "actual", "oracle", and "results".
6. Download the following zip files:
   • bats.ZIP
   • needed.ZIP
   • oracle.ZIP
   • scripts.ZIP
7. Unzip each of those files.
8. Place the unzipped contents of needed.ZIP into "ETA".
9. Place the unzipped contents of scripts.ZIP into "ETA".
10. Place the unzipped contents of oracle.ZIP into "oracle".
11. Place the unzipped contents of bats.ZIP into "src" - which is located at
    • ETA\edu\calpoly\cpe205\fetter\src
12. Edit "compile.bat" inside "src" and remove the 'target 1.2' tag.
13. Launch "compile.bat".
14. Launch "linkbyte.bat".
15. Launch "stage3.bat" that is located inside of "src".

    Warning: Do not click the mouse while the scripts are running. This may cause the scripts to produce incorrect results.

    • This should start the automated scripts for each test case in stage 3.
    • There is a 25 second pause after each script finishes (nothing is happening in ETA). This is to let you quickly examine the status pane. After the 25 seconds is up, ETA will quit and the next script will run.
    • The results of the diff between the oracle files and actual files are placed in the folder named "results".
    • A simple program named "Check" goes through this directory when all of the scripts are finished and produces a file named "regression.txt". This file contains a brief overview of each test log file - whether or not it agreed with the oracle file (pass or fail).


Hints on why a test might fail:

1. You may have performed extra actions while the ETA program was idle for those last 25 seconds. Those actions are still recorded (and not part of the oracle).
2. On slow systems, some actions might perform too fast - causing buttons to be clicked before they redraw.
3. Newer code may make changes to the default screen size of the application and its dialogs. Some script commands rely on absolute pixel coorindates. You will have to edit those coordinates or convert those mouse clicks to keyboard commands.
4. The oracle files may be wrong. The current (3/13/01) oracle files were created using the stage 3 release. You may have to recreate the oracle files for later builds.

Results of previous regression tests

• stage3.txt - run on 3/13/01

Stage 3 Features

• Feature 1 - Get the Value of a Field
• Feature 2 - Set the Value of a Field
• Feature 3 - Inspect Parameter Value
• Feature 4 - Invoke a method
• Feature 5 - Inspect Returned Value
• Feature 6 - Removing a Returned Data Item
• Feature 7 - Save Status Logs

Stage 2 Features
(Not scripted)

• Feature 1 - Change the value of a Primitive
• Feature 2 - Create Object
• Feature 3 - Create Primitive
• Feature 4 - Instantiate Class
• Feature 5 - Open Class
  An example of a script and corresponding dos batch file.
  
  • robot script
  • openclass.bat
• Feature 6 - Remove a Test Data Item