The source for this document can be gotten from Bazaar:

bzr cat lp:ubuntu-app-launch/tests/manual

The source is in the standard manual testing format for Ubuntu QA: Testing/TestCaseFormat

Test Case: ubuntu-app-launch/legacy-app


  • Ensure that the system-settings is installed: apt-cache policy ubuntu-system-settings

    • One of the versions in the version table should a *** next to it

  • Ensure the settings app is not currently running: ubuntu-app-list

    • Settings shouldn't be listed
  • Launch the settings application: ubuntu-app-launch ubuntu-system-settings

    • The settings application should be brought to focus and shown to the user

Test Case: ubuntu-app-launch/secondary-activation


  • Run test case: ubuntu-app-launch/legacy-app
    • Everything behaves as expected
  • Use the launcher to return to the home screen
    • The settings app is no longer shown
  • Send a URL to the service: ubuntu-app-launch ubuntu-system-settings settings:///system/battery

    • The settings application should come back into focus and be on the power settings pane

Test Case: ubuntu-app-launch/cgroup-containment


  • Install the Terminal app if not already installed
    • It can be found in the Application Store if not currently installed
  • Launch the Terminal app
    • A new application should open with a terminal prompt where you can type commands
  • Ensure the Terminal is in a terminal specific cgroup
    • Type the command cat /proc/self/cgroup

    • Under the "freeze" cgroup the end of the path should include the AppID of the terminal. An example would be (the version many change): 4:freezer:/user.slice/user-32011.slice/session-c2.scope/upstart/application-click-com.ubuntu.terminal_terminal_0.5.106

Process/Merges/TestPlan/ubuntu-app-launch (last edited 2017-02-16 13:56:01 by ken-vandine)