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

Test that agl-compositor is able to run, it can show popups and gnome-menus is able to show and launch installed applications.

Test the apertis-update-manager API for updates over the air when the network is diconnected and reconnected.

Test the apertis-update-manager API for updates over the air when the network is changed from a phone hotspot to wifi.

Test the automatic rollback and blacklist mechanism of apertis-update-manager with network updates.

Test the automatic rollback and blacklist mechanism of apertis-update-manager. The automated version of this test: https://qa.apertis.org/aum-rollback-blacklist.html

Test the apertis-update-manager automatic update interrupted by mass storage removing.

Test basic apparmor profiles. Only parsing and syntax of profiles are tested for now. Security infrastructure: parsing and syntax of basic Apparmor profiles is part of strategic application and services confinement.

Test AppArmor profile for Bluez AVRCP volume up and down commands.

Test AppArmor profiles for setting up of Bluetooth stack by running basic tests using hciconfig. Check if the interface can be brought up/down, can be changed of mode and can discover devices.

Test AppArmor profile for support for SPP profile (bluez-spp) and core functionalities (bluez-core).

Test that AppArmor's system wide rules works according to Apertis security goals (Chaiwala was an older codename for Apertis).

Security infrastructure: AppArmor D-Bus mediation is part of strategic application and service confinement.

Show some main AppArmor functionalities, like transitions, net access or resource permissions, under the form of tests.

Test that geoclue apparmor profiles are working properly.

Test that AppArmor profiles provided in GStreamer 1.0 works without Auditd complaining.

Test that AppArmor profiles provided in ofono package work without unexpected auditd log entries.

Test that AppArmor profiles provided in PipeWire work without apparmor complaining.

Test that the session lockdown profile is not blocking more than it should.

Test apparmor_parser and other tools in apparmor package can be executed

Security infrastructure: checking that AppArmor is available in the kernel and active is part of strategic application and services confinement.

Apertis update manager: API test This test ensures that the update manager API behaves as expected.

Apertis update manager: offline upgrade test between branches. This test ensures that Apertis is capable to upgrade the previos version to the recent. And update manager is able to fix all refs after successful update.

Apertis update manager: test of update failure with invalid update file. This test ensures that the update manager refuses to install an update with improper Collection ID, refs or timestamps.

Apertis update manager: check signed offline upgrade test This test ensures that the update manager uses static bundle with signed commit only.

Apertis update manager: Offline upgrade test This test ensures that the update manager is able to install an update provided offline.

Apertis update manager: OTA API test This test ensures that the update manager API behaves as expected.

Apertis update manager: automatic OTA updates test This test ensures that the update manager is able to work in unattended mode.

Apertis update manager: Out of space update test during OTA upgrade This test ensures that the update manager behaves appropriately in low disk space conditions.

Apertis update manager: blacklist and rollback for OTA updates. This test ensures that the update manager is able to rollback and blacklist an invalid update.

Apertis update manager: check signed OTA upgrade test This test ensures that the update manager uses commit signed with known key during OTA upgrades.

Apertis update manager: Out of space update test This test ensures that the update manager behaves appropriately in low disk space conditions.

Apertis update manager: Power cut resiliency test This test ensures that the update manager resists a power cut.

Apertis update manager: Blacklist and rollback This test ensures that the update manager is able to rollback and blacklist an invalid update.

Test the AVRCP volume up and down commands.

Test all BlueZ features needing interaction with a phone like file transfer of images or audio/video files

Test Hands Free Profile (HFP) BlueZ feature call and hold.

Test Hands Free Profile (HFP) BlueZ feature for incoming call.

Test Hands Free Profile (HFP) BlueZ feature.

Test all BlueZ features needing interaction with a phone (Pairing, OBEX, PBAP, AVRCP, A2DP, HSP, HFP, PAN). Strategic component: Bluetooth phone calls is part of smartphone interaction functionality.

Test setup of Bluetooth stack by running basic tests using hciconfig. Check if the interface can be brought up/down, can be changed of mode and can discover devices. Strategic component: Bluetooth setup and basic functionality is part of smartphone interaction functionality.

Check that nothing crashed when booting.

Test boot performance. This test checks boot performance using systemd-analyze statistics.

Test the wpa_supplicant interface.

Test ConnMan support for bluetooth PAN Network Access Profile. This test will test that after restarting the Bluetooth tethering from the phone side the internet access from Apertis to a bluetooth device sharing its internet connection is maintained.

Test ConnMan support for bluetooth PAN Network Access Profile. This test will test internet access from Apertis to a bluetooth device sharing its internet connection. The underlying connection makes use of Bluetooth Network Access Profile with connman. First the two devices will be paired, then connection will be established. It will then be possible to verify that internet is usable from Apertis.

Test Connman-pan-tethering support for PAN connectivity after reboot.

Test ConnMan support for PAN connectivity.

Tests Network connection management: ensuring that ConnMan can connect to actual networks even after the device under test is rebooted

Tests Network connection management: ensuring that ConnMan can connect to actual networks even after the device under test is rebooted

Tests Network connection management: ensuring that ConnMan can connect to actual networks is part of strategic network management functionality.

Test ConnMan support for USB tethering (connection side).

Runs some automated tests using the ConnMan D-Bus API. It guarantees most of the basic features are working. Network connection management: ensuring that ConnMan's APIs are accessible is part of strategic network management functionality.

Regression tests for D-Bus.

Test cross-compilation support for ARM64 architecture using devroot utility

Ensure that the root file system check is enabled on boot

Fixed function Web server.

Test a headless Flatpak demo application

Test a graphical Flatpak demo application

Check that gettext internationalization works.

Run the GLib gio tests that do I/O on the local filesystem.

Check grilo metadata notifications, and filesystem browsing.

Test video and audio decoders and demuxers on a list of media. Audio/video decoding through GStreamer is important but not required by any of the currently strategic functionalities.

Run a few tests related to service browsing, introspection, etc.

Test that the songs present play and can be paused, skipped, volume can be changed up/down and audio policy works correctly

Test that the songs present play and can be paused

Test that audio policy to mute song application when switching to video application

Test that the songs can be rewind or fast-forwarded

Test that the volume controls work as expected

Test that the Rhythmbox app can be launched from the agl-compositor

Test that the Rhytmbox app can be successfully uninstalled

Switching between two graphical applications is smooth and glitch free

Tests that the video files are present

Test that the video files play without any glitches

Test whether the image is bootable. Basic functionality: booting up.

Test whether the image starts a graphical environment. Basic functionality: ensuring that the GUI boots up.

Network connection management: ensuring that iptables is available and usable is part of strategic networking management functionality.

Test the availability of the licensing summary.

Run the Newport test suite

This test checks that an image that was flashed using the nfsroot properly booted.

Test receiving SMS messages with oFono.

Test sending of SMS with oFono.

OSTree: Collection ID test This test ensures that the system is booted with proper Collection ID.

Parse polkit policy files

Test the pstore functionality usage

Test that rfkill is functional.

Rhosydd module test.

This test checks the Robot Framework functionality on SDK by running the testcases on connected target using SSH.

This test checks that the system bus is up, that a user session is created and that a graphical interface is successfully running in the system, as well as other similar basic services so that a stable and reliable environment can be confirmed before futher tests are executed. Basic functionality: services.

This test checks that the system bus is up, that a user session is created and that a graphical interface is successfully running in the system, as well as other similar basic services so that a stable and reliable environment can be confirmed before futher tests are executed. Basic functionality: services.

Checks basic gcov functionality by running a sample program a few different ways and ensuring that a sufficient portion of its code paths are executed.

Checks basic splint functionality by checking its output when run on a simple source file.

Attempt building bash package in the devroot SDK images ship.

Test that bustle-dbus-monitor shows services on the session bus.

Test that D-Feet both shows services on the session bus and that new services appear automatically.

Ensure that the sample image recipes can be built on the SDK and that the commands in the documentation work.

Checks basic gdb functionality by stopping a program at a set point and checking its backtrace matches expectations.

Checks basic strace functionality by checking its output when run on a simple command line program.

Checks basic valgrind functionality by running a program with and without memory leaks, ensuring expected results from valgrind.

Install and run hello-world docker container.

Checks basic import-debian-package functionality.

Checks basic gprof functionality by ensuring a CPU-intensive program shows up in its log as consuming the vast majority of the CPU cycles.

Checks basic sysprof functionality by ensuring a CPU-intensive program shows up in its log as consuming the vast majority of the CPU cycles.

Tests that persistent disk can be used when upgrading the SDK.

Tests that the SDK VM can be fullscreened in VirtualBox. Development environment: ensuring that the VirtualBox SDK provides a seamless experience. Check that when fullscreened the output is not stretched, even for accelerated contents.

Test that Secure Boot via HAB on the SabreLite board works for bootloader and initial OS image in FIT format.

Test that the AppArmor profile for dbus-daemon is loaded in system-wide privileged container

Test of Tiny system-wide privileged container using shared networking with the host

Test of AppArmor profile for Tiny system-wide privileged container

Test of device sharing between host and Tiny system-wide privileged container

Test of folder sharing between host and Tiny system-wide privileged container started as user

Test that the custom seccomp profile could be applied for system-wide privileged container

Test that the AppArmor profile for dbus-daemon is loaded in unprivileged container started as user

Test of Tiny unprivileged container without any networking started as user

Test of AppArmor profile for Tiny unprivileged container started as user

Test of device sharing between host and Tiny unprivileged container started as user

Test of folder sharing between host and Tiny unprivileged container started as user

Test that the custom seccomp profile could be applied for unprivileged container started as user

Traprain library test.

Check that all thumbnailing features of tumbler are working properly (large, small, videos, documents, images).

Test whether Plymouth is able to display a graphical theme.

Test that 3D transforms are applied correctly.

Tests html5 video playback with GStreamer 1.0 in WebKit2GTK. This test opens an URL to stream video and audio using MiniBrowser.

Test implementation of W3C touch events API in WebKit2GTK.

Test WiFi WPA2-PSK access point (AP mode) is working in Apertis. Also check connection is re-established after rebooting the AP.

Test WiFi WPA3-SAE access point (AP mode) is working in Apertis. Also check connection is re-established after rebooting the AP.

Test WiFi WPA3-Transition-Mode access point (AP mode) is working in Apertis. Also check connection is re-established after rebooting the AP.

Test whether the correct GLES2 render is used.