Files
allwpilib/test-scripts
Thad House 5e3755493d Linking and maven publish location rewrite (#298)
* Links HAL shared instead of static, and doesn't include library in jar

* Strips shared object files, and includes debug in releases

* Zips the HAL libraries into a separate maven artifact

* Switches to shared wpiutil

* Switches wpilibc to shared

* Moves maven artifacts

wpilibc now in edu.wpi.first.wpilibc:athena
wpilibj now in edu.wpi.first.wpilibj:athena
wpilibj jni not in edu.wpi.first.wpilibj:athena-jni
hal now in edu.wpi.first.wpilib:hal
athena runtime added (hal, ntcore, wpiutil) edu.wpi.first.wpilib:athena-runtime

Changes made where wpilibc does NOT include all required artifacts anymore. Dependent on hal, wpiutil and ntcore packages to work correctly.
JNI does NOT include all required artifacts anymore. Dependent on hal and wpiutil packages to work correctly.
2016-10-25 20:46:09 -07:00
..
2015-11-21 18:26:49 -05:00

WPILIB TEST SCRIPTS

Overview

These test scripts are designed to allow the user of the WPILib test framework to quickly and easily deploy and run their tests on the WPI roboRIO.

In order for the automated test system to work there is a driverstation onboard the roboRIO that handles a queue of users waiting to use the driver station. All of the interaction with this queue is handled internally by test scripts contained within this folder.

If you deploy code to the test stand using the Eclipse plugins, you must remove the build artifacts in /home/lvuser, or you will break tests.

roboRIO Setup

The roboRIO on the test bench must be updated everytime NI releases a new image.

  1. Use the roboRIO Imaging Tool to format the roboRIO with the lastest image.
  2. Install Java on the roboRIO.
  3. SFTP the teststand, netconsole, and libstdc++ ipk files on to the roboRIO.
  4. ssh on to the roboRIO as the admin user (ex: ssh admin@roboRIO-190-FRC.local)
  5. Use opkg to install the ipk files (ex: opkg install teststand_1.2-1_armv7a-vfp.ipk)
  6. Reboot the roboRIO