ClickAppArmor

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2014-03-11 19:06:03 →
Size: 1759
Editor: jdstrand
Comment:
← Revision 3 as of 2014-03-11 19:06:40 → ⇥
Size: 1755
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
dd

Dependents/Clients

  • upstart-app-launch (uses apparmor kernel interface via upstart to load the AppArmor profile generated by click-apparmor)

  • ubuntu-sdk (eventually, once it uses the new aa-clickquery command)

Test Plan

This test plan is not supposed to be complete; use it to guide your manual testing so they dont miss big functional areas that are part in the component; also this should be used as guideline to inspire the exploratory testing which should be adapted smartly based on the real content of a MP

  • Install image on phone
  • Install freshly build MPs that are needed for landing and reboot

  • Verify the output of aa-status | grep 'com.ubuntu'. It should report many profiles are loaded for click packages

  • Verify apps launch
    • Launch an app (eg, start the weather app). Does it start?

    • Run sudo aa-status, is the process for the app running under confinement (in enforce mode)?

  • Ensure that webapps launch
    • launch a webapp (eg, start the facebook webapp). Does it start?

    • Run sudo aa-status, is the process for the webapp running under confinement (in enforce mode)?

  • Run image tests on Ubuntu Touch (emulator or touch image):

    $ bzr branch lp:qa-regression-testing
$ cd qa-regression-testing
$ adb push ./tests /tmp/tests
$ adb shell sudo -i -u phablet /tmp/tests/image/unprivileged/click-apparmor
$ adb shell sudo -i -u phablet /tmp/tests/image/unprivileged/apparmor-easyprof-ubuntu

Process/Merges/TestPlans/ClickAppArmor (last edited 2016-08-26 16:39:43 by jdstrand)