Forked from
tests / apertis-test-cases
570 commits behind the upstream repository.
-
Frédéric Dalleau authored
Signed-off-by:
Frédéric Dalleau <frederic.dalleau@collabora.com>
Frédéric Dalleau authoredSigned-off-by:
Frédéric Dalleau <frederic.dalleau@collabora.com>
apertis-update-manager-automount.yaml 1.15 KiB
metadata:
name: apertis-update-manager-auto
format: "Apertis Test Definition 1.0"
image-type: any
image-arch: armhf
type: functional
exec-type: manual
priority: medium
maintainer: "Apertis Project"
description: "Test the apertis-update-manager automatic update via mass storage device."
resources:
- "A static update bundle file from https://images.apertis.org/updater-test/armhf-minimal/static-update.bundle"
- "A Fat32 USB flash drive, preloaded with the update bundle at the root of the disk"
- "The DUT u-boot environment must be clean: in u-boot, run: `env default -a` followed by `saveenv`"
- "A PC must be connected to DUT serial port"
expected:
- "The update was properly applied"
run:
steps:
- "Check the current deployment"
- $ sudo ostree admin status
- "Plug the USB flash drive in the device"
- "The update starts automatically"
- "After the update, the device will reboot automatically"
- "Remove the USB flash drive immediatly after reboot"
- "Check the current deployment has been updated and that the rollback entry points to the initial deployment"
- $ sudo ostree admin status