Bug 13739 - Enable OE runtime testing infrastructure for non-Linux systems
Summary: Enable OE runtime testing infrastructure for non-Linux systems
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: oeqa/runtime (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 3.1
Assignee: Alejandro
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-01-20 01:37 UTC by Alejandro
Modified: 2020-04-30 08:30 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro 2020-01-20 01:37:15 UTC 
The build system now has the capability to build non-Linux systems whether that means an RTOS system such as FreeRTOS or a baremetal application, when using either TCLIBC=newlib or TCLIBC=baremetal.

The automated runtime testing infrastructure that already exists on OpenEmbedded and is used to test individual components of the Linux system can also be used to test baremetal applications such as the ones mentioned above.

In the case of multiarchitecture embedded devices, using the same testing infrastructure for all the software applications/OS's running on different hardware components of the same device would prove to be really useful for users of the project.


An example of this would be running the following:

$ bitbake freertos-demo -c testimage

or

$ bitbake mc:baremetal-config:baremetal-helloworld -c testimage


Returning the usual summary results depending on the runtime testsuite chosen:

RESULTS:
RESULTS - freertos.FreeRTOSTest.test_freertos: PASSED (29.0 s)