As mentioned previously, all new test files need to be in the
proper place for the build system to find them.
New tests for additional functionality outside of the core
should be added to the layer that adds the functionality, in
(as long as
layer
/lib/oeqa/runtimeBBPATH
is extended in the layer's
layer.conf
file as normal).
Just remember the following:
Filenames need to map directly to test (module) names.
Do not use module names that collide with existing core tests.
Minimally, an empty
__init__.py
file must exist
in the runtime directory.
To create a new test, start by copying an existing module
(e.g. syslog.py
or
gcc.py
are good ones to use).
Test modules can use code from
meta/lib/oeqa/utils
, which are helper
classes.
df.py
and
date.py
modules for examples.
You will notice that all test classes inherit
oeRuntimeTest
, which is found in
meta/lib/oetest.py
.
This base class offers some helper attributes, which are
described in the following sections: