11. Testing

RTEMS developers run test executables when adding new features or testing a bug fix. All tests are run to make sure changes do not introduce regressions. Users can run the RTEMS tests to be certain the build of the kernel they have is functioning.

The section describes using and configuring the RTEMS Tester and RTEMS Run tools, the types of laboratory set ups supported and how to add your BSP to the framework. The tools command line interfaces are detailed in RTEMS Tester and Run.

An RTEMS Test is an RTEMS executable where the application code is a test. Tests in RTEMS print banners to the console to indicate the configuration of the test and if it has start and finished.

The RTEMS Tools Project provides the RTEMS Tester and RTEMS Run tools. The RTEMS Tester command is rtems-test and the RTEMS Run command is rtems-run. These commands manage the complexity of running embedded executables. The commands provide a consistent command line interface to a testing framework that supports the various run time and testing scenarios we encounter such as simulators, GDB and executing directly on target hardware.

The RTEMS kernel code contains an extensive set of tests to exercise and test the RTEMS kernel. The tests check functionality, provide coverage testing and make sure the kernel is operating as intended on your target system. The testsuite has support to make creating a test simple and uniform.

The tests are built by adding BUILD_TESTS = True to a BSP section in config.ini. There are over 600 tests and building them does extend the RTEMS kernel’s build time and use more disk space but it worth building and running them. The RTEMS test executables have the .exe file extension.

• 11.1. Test Banners
• 11.2. Test Controls
  • 11.2.1. Expected Test States
  • 11.2.2. Test Configuration
• 11.3. Test Builds
• 11.4. Tester Configuration
  • 11.4.1. Defaults
  • 11.4.2. BSP and User Configuration
  • 11.4.3. Configuration Scripts
    • 11.4.3.1. Console
    • 11.4.3.2. Execute
    • 11.4.3.3. GDB
    • 11.4.3.4. TFTP
    • 11.4.3.5. Wait
• 11.5. Coverage Analysis
• 11.6. Consoles
• 11.7. Simulation
• 11.8. GDB and JTAG
• 11.9. TFTP and U-Boot
  • 11.9.1. Target Hardware
    • 11.9.1.1. U-Boot Set Up
  • 11.9.2. BSP Configuration
  • 11.9.3. TFTP Sequences