Oe-selftest: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Introduction= | |||
Oe-selftest is a test framework used for testing the poky build system. Following are some key points in describing oe-selftest: | Oe-selftest is a test framework used for testing the poky build system. Following are some key points in describing oe-selftest: | ||
- based on Python Unit Testing | - based on Python Unit Testing | ||
| Line 6: | Line 6: | ||
- implements a new layer that contains generic/specific metadata used only by tests | - implements a new layer that contains generic/specific metadata used only by tests | ||
=How to use= | |||
In order to use oe-selftest, you need the following(in this specific order): | In order to use oe-selftest, you need the following(in this specific order): | ||
| Line 21: | Line 21: | ||
- running all tests can take a long time! | - running all tests can take a long time! | ||
=Related source files and locations= | |||
=How to contribute= | |||
Revision as of 16:54, 22 January 2014
Introduction
Oe-selftest is a test framework used for testing the poky build system. Following are some key points in describing oe-selftest: - based on Python Unit Testing - designed to simulate poky external usage patterns - does not cover image run-time testing - implements a new layer that contains generic/specific metadata used only by tests
How to use
In order to use oe-selftest, you need the following(in this specific order): - the poky source (1.5 M2 or better) - a sourced build environment - the meta-selftest layer added in conf/bblayers.conf
How to run specific tests
'Hidden' tests
You should be aware of the following: - oe-selftest uses the settings in conf/local.conf as a base for all test configurations. Any modifications made(like DISTRO) or not made here(like BB_NUMBER_THREADS) will impact all tests if the modifications are not overwritten s specifically by a test - running all tests can take a long time!
