summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Bonnans <laurent.bonnans@here.com>2019-03-12 14:44:27 +0100
committerPatrick Vacek <patrickvacek@gmail.com>2019-04-29 09:22:54 +0200
commit6c73fd1caaea849c24ffb697a8f1d92e501551bf (patch)
tree607c2f7db8b691dfba5391503b4f7f0e91566f70
parent0da148c785a77e4f51fbf90078af12299f8480f2 (diff)
downloadmeta-updater-6c73fd1caaea849c24ffb697a8f1d92e501551bf.tar.gz
Document ptest for aktualizr
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
-rw-r--r--README.adoc13
1 files changed, 13 insertions, 0 deletions
diff --git a/README.adoc b/README.adoc
index d1469a8..434c04c 100644
--- a/README.adoc
+++ b/README.adoc
@@ -215,6 +215,19 @@ oe-selftest --run-tests updater
215 215
216For more information about oe-selftest, including details about how to run individual test modules or classes, please refer to the https://wiki.yoctoproject.org/wiki/Oe-selftest[Yocto Project wiki]. 216For more information about oe-selftest, including details about how to run individual test modules or classes, please refer to the https://wiki.yoctoproject.org/wiki/Oe-selftest[Yocto Project wiki].
217 217
218== Aktualizr test suite with ptest
219
220The meta-updater layer includes support for running parts of the aktualizr test suite on deployed devices through link:https://wiki.yoctoproject.org/wiki/Ptest[Yocto's ptest functionality]. Since it adds significant build time cost, it is currently disabled by default. To enable it, add the following to your `conf/local.conf`:
221
222```
223PTEST_ENABLED_pn-aktualizr = "1"
224IMAGE_INSTALL_append += " aktualizr-ptest ptest-runner "
225```
226
227Be aware that it will add several hundreds of MB to the generated file system.
228
229The aktualizr tests will now be part of the deployed ptest suite, which can be run by calling `ptest-runner`. Alternatively, the required files and run script can be found in `/usr/lib/aktualizr/ptest`.
230
218== Manual provisoning 231== Manual provisoning
219 232
220As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> section you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend. 233As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> section you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend.