ade-commands automated

critical

Image Types:
basesdk-amd64 / sdk-amd64
Image Deployment:
APT
Type:
functional

Description

Test ade command and sub-command with default and custom options and arguments.


Pre Conditions

  1. Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):
  2. $ git clone --branch apertis/v2020dev0 https://gitlab.apertis.org/infrastructure/apertis-tests.git

  3. Copy the test directory apertis-tests to the target device:
  4. $ DUT_IP=<device-ip>

    $ scp -r apertis-tests user@$DUT_IP:

  5. Log into the target device:
  6. $ ssh user@$DUT_IP

  7. Network connectivity on the DUT as these tests fetch sysroot images over the network.

Execution Steps

  1. Enter test directory:
  2. $ cd apertis-tests

  3. Run the ade-tests-custom.sh and ade-tests-defaults.sh script from the ade/ directory
  4. $ common/run-test-in-systemd --timeout=60min ade/ade-tests-custom.sh

    $ common/run-test-in-systemd --timeout=60min ade/ade-tests-defaults.sh


Expected

The automated test should succeed and print some information about the built app-bundle:

>> + stat org.apertis.HelloWorld.SimpleAgent-0.1.0.bundle

>>> File: org.apertis.HelloWorld.SimpleAgent-0.1.0.bundle

Notes

  • Lots of ade messages will be logged on the standard output. Upon test fail, the script will abort with:
  • Job for generated-test-case-ade_ade-tests-defaults_sh.service failed because the control process exited with error code.

    >See "systemctl --user status generated-test-case-ade_ade-tests-defaults_sh.service" and "journalctl --user -xe" for details.

    >Command exited with non-zero status 1