ClickAppArmor

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2014-03-11 19:07:31 →
Size: 1451
Editor: jdstrand
Comment:
← Revision 5 as of 2014-03-14 08:04:33 → ⇥
Size: 1617
Editor: jdstrand
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
  * '''Note:''' if testing a new framework, be sure to declare the new framework in /usr/share/click/frameworks/<framework>.framework before running the image tests

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

  • 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

    • Note: if testing a new framework, be sure to declare the new framework in /usr/share/click/frameworks/<framework>.framework before running the image tests

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