The Platform Qualification Tools (PQT) project provides the tools required to validate each component of a MicroEJ Platform. After porting or adding a feature to a MicroEJ Platform, it is necessary to validate its integration.

Clone this repository with git clone --recursive https://github.com/MicroEJ/PlatformQualificationTools.

The CORE Test Suite contains a C Test Suite and a Java Test Suite. It is the most basic Test Suite to run. It ensures MicroEJ Application will run correctly.

All other Test Suites assume the CORE Test Suite is validated.

See CORE Readme

The UI Test Suite is a C Test Suite. It checks the integration of the LLDisplay API and the tearing signal usage. It also provides indication about the minimum draw time allowed to display animations at a given framerate.

See UI Readme

The FS Test Suite is a Java Test Suite. It checks the integration of the LLFS* APIs over a C File System library.

See FS Readme

The Platform Qualification Tools (PQT) contains:

• a framework/ folder with scripts and frameworks used by the tests
• a tests/ folder with one sub-folder per Test Suite (e.g. tests/core/ for the CORE Test Suite, etc.)

Each Test Suite sub-folder contains a README.rst that explain how to use the Test Suite in details.

The following sections give an overview of the Platform Qualification Tools (PQT).

The framework/ folder contains the infrastructure required to build and run the tests.

The framework/c/ folders contains the following:

• Embedded Unit (embUnit) is a unit testing framework used for C tests.
• CoreMark is a processor benchmark used by the CORE Test Suite.
• utils provides several utilities used by various C tests

The framework/platform/ folder contains the MicroEJ Platform Configuration Additions. See the Platform Configuration Additions README for more information. For licenses management, please refer to License .

The Platform Qualification Tools (PQT) provides two kinds of Test Suite:

• C Test Suite that must be added to the BSP
• Java Test Suite that are launched as standard MicroEJ Application

A Test Suite validates a particular component of a MicroEJ Platform. The CORE Test Suite is applicable to every MicroEJ Platform. The other Test Suites depends on the capabilities provided by the MicroEJ Platform to validate.

A detailed explanation how to use each Test Suite is provided in the README.rst present in each sub-folder. For example, for the CORE Test Suite, refer to the CORE Readme.

The C Test Suites validate that the hardware and RTOS (if applicable) are properly integrated in the BSP.

The C Test Suites uses Embunit framework. They have to be launched just before MicroEJ Application (just before the call to microjvm_main()). At this moment, the BSP is fully initialized and the OS is started.

The C Test Suites perform some basic checks which ensures MicroEJ Application will run. Unless specified otherwise, C Test Suites are linked with a MicroEJ Application (microejapp.o) and a MicroEJ runtime library (microejruntime.a).

The C Test Suites often require some additional data (some specific functions have to be implemented in addition of LLAPI implementation functions).

The Java Test Suites validate the Foundation Libraries integration.

The Java Test Suites verify the integration of the MicroEJ Platform over the BSP. No specific unit test framework is used, each test describes how it works.