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

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

Test the apertis-update-manager automatic update via mass storage device.

Ensure that failures due to disk full errors during updates have no effect on the system The automated version of this test: https://qa.apertis.org/aum-out-of-space.html

Test the apertis-update-manager API for updates over the air.

Test the apertis-update-manager automatic updates over the air.

Ensure that failures due to disk full errors during network updates have no effect on the system

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

Test the apertis-update-manager uses only signed updates over the air.

Ensure that failures due to power losses during updates have no effect on the system The automated version of this test: https://qa.apertis.org/aum-power-cut.html

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 the manual update with apertis-update-manager. The automated version of this test: https://qa.apertis.org/aum-offline-upgrade.html

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 PulseAudio work without apparmor complaining.

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

Tests that the tracker abstraction and tracker profiles don't cause false negatives and that it does not allow arbitrary reading of files in the home directory.

Tests that the tumbler AppArmor profile doesn't cause false negatives and that it does not allow arbitrary reading of files in the home directory.

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: 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: 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 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 for Canterbury library.

Run cgroup resource control tests

Test the wpa_supplicant interface.

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 support for PAN connectivity.

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.

Check the reply time of a few D-Bus method calls while dbus-daemon is loaded by D-Bus traffic. Different patterns of D-Bus loads are tested: 1) A connection calling a D-Bus method repetitively. 2) A process calling a D-Bus method repetitively using a different connection each time to generate traffic related to connections joining and leaving the bus (NameOwnerChanged signals). 3) The same with 100 threads generating traffic. 4) Tens of threads registering hundreds of D-Bus match rules DoS resistance is part of strategic basic services functionality.

Regression tests for D-Bus.

Test the content hand-over feature by launching an application. Didcot service is responsible for the content hand-over by launching an application which supports the mime type or uri schemes . The script launches a browser application which supports http uri schemes

Ensure that the root file system check is enabled on boot

Test copying files to the remote device from within Eclipse. It will create a dummy project and then create a configuration to copy the binary file to a remote device.

Test remote debugging within Eclipse. It will create a dummy project and then create a configuration to copy the binary file to a remote device and debug it remotely using Eclipse.

Test sysroot management and update within Eclipse. It will go through configuring an existing sysroot in Eclipse, and then updating it from the web with the latest version.

Synchronizing Bluetooth-paired phone contacts to Evolution.

Reading contacts from 3G modem SIM card.

Frome library test.

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 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 firewall using nmap from another computer.

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 that rfkill is functional.

Rhosydd module test.

Ribchester library test.

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.

Test remote debugging with ADE. Cross-build an example HelloWorld agent, deploy it to the target device and debug it with proper backtraces.

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.

Creates a simple test project and confirms that compiling and executing work.

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 persistent disk can be used when upgrading the SDK.

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.

Support making and receiving phone calls in Telepathy manually, with a bluetooth-paired phone.

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

Check tracker indexing of local storage and journal behaviour.

Check tracker indexes mass storage devices on insertion.

Test basic traffic control support. This test does not use tcmmd but it could catch missing support in the kernel or misbehaving traffic control.

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.

Test that compositing layers are created for animating properly.

Test that actors created for representing layers scroll properly.

Test HTML5 drag-and-drop support in WebKit2GTK.

Test WebKit2Gtk ability to scroll by touch with inertial behaviour after the touch ended.

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 whether the correct GLES2 render is used.