summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEd Bartosh <ed.bartosh@linux.intel.com>2016-10-31 16:40:40 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-11-04 12:50:29 +0000
commit0e675547166acc8650498e153bd3482420342c32 (patch)
treee0c0eefb7da32360e099565a0715f60d272608fb
parentc922f4904301174cc72ba35e76870fbf964082cf (diff)
downloadbitbake-contrib-0e675547166acc8650498e153bd3482420342c32.tar.gz
toaster: add tests/eventreplay/README
Put instructions on how to prepare event log files and run eventreplay tests. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--lib/toaster/tests/eventreplay/README22
1 files changed, 22 insertions, 0 deletions
diff --git a/lib/toaster/tests/eventreplay/README b/lib/toaster/tests/eventreplay/README
new file mode 100644
index 000000000..8c5bb6432
--- /dev/null
+++ b/lib/toaster/tests/eventreplay/README
@@ -0,0 +1,22 @@
+# Running eventreplay tests
+
+These tests use event log files produced by bitbake <target> -w <event log file>
+You need to have event log files produced before running this tests.
+
+At the moment of writing this document tests use 2 event log files: zlib.events
+and core-image-minimal.events. They're not provided with the tests due to their
+significant size.
+
+Here is how to produce them:
+
+$ . oe-init-build-env
+$ rm -r tmp sstate-cache
+$ bitbake core-image-minimal -w core-image-minimal.events
+$ rm -rf tmp sstate-cache
+$ bitbake zlib -w zlib.events
+
+After that it should be possible to run eventreplay tests this way:
+
+$ EVENTREPLAY_DIR=./ DJANGO_SETTINGS_MODULE=toastermain.settings_test ../bitbake/lib/toaster/manage.py test -v2 tests.eventreplay
+
+Note that environment variable EVENTREPLAY_DIR should point to the directory with event log files.