generic-poky

History

Michael Wood 83ebb89877 bitbake: toaster: tests builds Update buildtest Now that we're using fixtures for configuration just load these instead of trying to search for a toasterconf json file. Also for convenience add the ability for the tests to source the build environment script. To use this test make sure that directories are in the same layout as poky. (Bitbake rev: 448d1d9dc8989ef4c997a90c71cd7e1da0495c1c) Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2016-11-04 12:50:55 +00:00
..
README	bitbake: toaster: tests Rename test settings to python compliant name and fix import	2016-06-15 08:35:06 +01:00
__init__.py	bitbake: toaster: tests Add a BuildTest helper class	2016-05-20 10:09:03 +01:00
buildtest.py	bitbake: toaster: tests builds Update buildtest	2016-11-04 12:50:55 +00:00
test_core_image_min.py	bitbake: toaster: tests builds Add SSTATE_MISS as a valid condition for tc=833	2016-05-20 10:09:03 +01:00

README

# Running build tests

These tests are to test the running of builds and the data produced by the builds.
Your oe build environment must be sourced/initialised for these tests to run.

The simplest way to run the tests are the following commands:

$ . oe-init-build-env
$ cd bitbake/lib/toaster/ # path my vary but this is into toaster's directory
$ DJANGO_SETTINGS_MODULE='toastermain.settings_test' ./manage.py test tests.builds

Optional environment variables:
 - TOASTER_DIR (where toaster keeps it's artifacts)
 - TOASTER_CONF a path to the toasterconf.json file. This will need to be set if you don't execute the tests from toaster's own directory.