Mir

Differences between revisions 43 and 75 (spanning 32 versions)
⇤ ← Revision 43 as of 2015-08-28 08:51:05 →
Size: 5629
Editor: 1
Comment: added mir client dependencies, and change the link to Xmir and fixed the test plan for the new xmir
← Revision 75 as of 2019-08-09 16:22:47 → ⇥
Size: 5079
Editor: alan-griffiths
Comment: Updated fpr Mir 1.4
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from Process/Merges/TestPlans/Template
## page was renamed from Process/Merges/TestPlans/Common
## page was renamed from Process/TestPlans/Common

 * '''Test plan for component''': Mir and unity-system-compositor		  * '''Test plan for component''': Mir
Line 7: Line 3:
 * '''Trunk URL''': lp:mir/ubuntu
                    & lp:unity-system-compositor
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir                                    & http://launchpad.net/ubuntu/+source/unity-system-compositor
  * '''Trunk URL''': [[https://github.com/MirServer/mir/|github:MirServer/mir]]
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir
Line 17: Line 10:
 * '''QtMir''' http://code.launchpad.net/qtmir
 * '''qtubuntu''' https://launchpad.net/qtubuntu
 * '''Platform-api''' http://code.launchpad.net/platform-api
 * '''Xmir''' https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir
 * '''Unity-System-Compositor''' http://code.launchpad.net/unity-system-compositor
 * '''url-dispatcher'''
 * '''trust-store'''
 * '''pay-service'''
 * '''SDL'''
 * '''ubuntu-app-launch'''
 * '''GTK-3'''		  * '''Xmir''' https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir
 * '''SDL''' [''16.04LTS only'']
 * '''qtubuntu''' https://launchpad.net/qtubuntu [''16.04LTS only'']
Line 31: Line 16:
'''NOTE:''' Please consider all platforms and configurations. "Ubuntu Phone" includes Nexus4, Nexus10 and Nexus7. "Ubuntu Desktop" includes XMir and Unity8-desktop-preview. Note, substantive changes in unity-system-compositor should mandate testing of "Ubuntu Desktop".

=== Ubuntu Phone ===

 * Successful run of automated CI testing (already done by the CI autolander)
 * In addition, install updated image on phone and tablet
 * Install packages from build silo
  * note: even safer to install only the packages you've built (not dist-upgrade)
  * Ensure navigating/scrolling the ui/Dash works as expected (note: cross check known unity8 bugs for any oddities witnessed)
 * Ensure screen blanking & power down dialog works
  * '''time out''' screen goes off
   * Ensure time out sits for 5 minutes as to allow deep sleep
  * '''Power button blanks screen'''
  * '''Power button unblanks screen'''
  * Ensure '''wakeup phone call''' or text message wakes up phone from screen off
  * long power key press for power down dialog
   * select "power off" and ensure device powers off
   * select "restart" and ensure device restarts
   * select "cancel" to close the dialog box
  * during phone call make sure "proximity sensor blanks screen"
  * Ensure proximity sensor doesn't lock/crash the UI when stressed (bug 1359270 / 1359258)
 * Ensure '''app launches''' and can '''quit apps'''
  * make sure to launch multiple apps and swap them
  * when you launch the app, do not touch the screen and make sure it updates
  * when you quit the app, make sure a new app doesn't launch
 * Browser '''copy/paste''' to '''Notes''' application (need to be downloaded from the Ubuntu store)
  * '''note''' see bugs list, currently browser only allows selection of paragraph not a single word
  * open browser, go to cnn.com article with text
  * select text, long press for copy prompt, press copy
  * launch Notes, new note, long press to activate paste prompt, paste
  * select note to activate OSK, rotate a few times and ensure osk and notepad follow rotation
  * note copy/paste, OSK, rotation, moving between apps should function as expected
 * Notes copy/paste to message app
  * '''note''' currently msg app has a bug where paste doesn't prompt/highlight properly
  * open Notes, type some text
  * long press to prompt & select all text
  * long press again to prompt & copy text
  * dismiss keyboard
  * open message app, activate compose area, long press to prompt, paste
  * make sure OSK functions correctly, especially '''top row extended keys on OSK'''
  * make sure '''OSK rotates''' correctly
 * '''Download click app''' & launch (covers dash, click, osk, acct)
  * (without having setup accounts) Navigate to the Dash recommended applications
  * select app, select install
  * should be prompted to settings, enter U1 info with OSK
  * return to dash install app, open app
  * note the various screen switching and OSK prompting should function as expected
 * Open Gallery
  * play around in the app, make sure images captured by the Camera look correct.
 * run unity8 AP test per https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission
 * run browser AP test (ensure pass rate is similar to smoke results : http://ci.ubuntu.com/smokeng/vivid/). Note: same link as above, under "Running Deb tests" - look for 'webbrowser'.
 * If any oddities are witnessed, retest virgin image without mir changes
 * phablet-screenshot running from a desktop connected to the device shall work for all supported devices (manta, flo, mako).

=== Ubuntu Desktop ===

Desktop testing is recommended for XMir when Mir landing attempt involves client API changes and significant unity-system-compositor changes. Unity8-desktop-session-mir testing is also recommended for significant unity-system-compositor changes. 		'''This test plan is not supposed to be complete; use it to guide your manual testing so they don't 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 release'''
Line 90: Line 19:
 * Verify that the mir-tests-tools snap works
Line 91: Line 21:
 * In addition update desktop from archive (assumes on utopic)
  * Install packages from build silo		 == Testing mir-test-tools ==
Line 94: Line 23:
 * Install Xmir
  * go to a VT and launch mir_demo_server as root with the option --arw-file
  * launch Xmir in a another VT using: Xmir -mirSocket /tmp/mir_socket -damage :2
  * in another VT: DISPLAY=:2 gedit
  * Switch to the mir VT
  * Interact with gedit, write a text document, save it, load another.		 These tests should work on all supported series of Classic and on Ubuntu Core. First check that the `classic` channel has been updated with the release candidate:
Line 101: Line 25:
 * Install unity8-desktop-session-mir
  * login to unity8 desktop and utilize applications such as browser, play with dash
  * allow screen to blank, wake up		    * $ '''snap info mir-test-tools'''

This should show something like:

   * '''candidate: 1.2.0-snap45 2019-05-22 (415) 121MB -'''

Where the version number matches the release being tested.

   * $ '''snap install --candidate mir-test-tools'''

There's a "handy script" to test the snap on the Wiki:

   * https://github.com/MirServer/mir-test-tools/wiki/Notes

Copy this and run it.

== Testing Ubuntu Classic ==

Testing differs between 16.04LTS and 18.04LTS or later. Testing for 16.04LTS has its own section below.

=== Test Plan 18.04LTS or later ===

 * The following should be repeated for 18.04LTS and any later series:

 * In addition update desktop from archive
  * Install packages from the [[https://launchpad.net/~mir-team/+archive/ubuntu/rc|release candidate PPA]]:
   * $ '''sudo add-apt-repository --update ppa:mir-team/rc'''
   * $ '''sudo apt install mir-demos mir-graphics-drivers-desktop mir-test-tools'''
  * Install applications to test with:
   * Qt Wayland support, qterminal and kate to test with:
    * $ '''sudo apt install qtwayland5 kate qterminal'''
   * Install weston-terminal:
    * $ '''sudo apt install weston'''
   * Install glmark2:
    * $ '''sudo apt install glmark2-wayland'''

 * Mir-on-X11
  * Use an X11 based desktop (Unity, Gnome, etc.).
  * Start a terminal sessions to launch the tests.
  * Run the "smoke tests" to ensure the example clients work
   * $ '''mir-smoke-test-runner'''
   * Check the result is "I: Smoke testing complete with returncode 0"
  * Run a test session in a window
   * $ '''miral-app'''
  * [in the Mir-on-X11 session] Try running, resizing, moving and switching between the following:
   * $ '''mir_demo_client_multiwin'''
   * $ '''kate'''
   * $ '''gnome-terminal'''
   * $ '''weston-terminal'''
   * $ '''glmark2-es2-wayland'''

 * Mir-on-KMS
  * Switch to VT4 and sign in
  * Run a test "tiling desktop" session
   * $ '''miral-app --window-manager tiling'''
  * Try running, and switching between the following:
   * $ '''mir_demo_client_multiwin'''
   * $ '''kate'''
   * $ '''gnome-terminal'''
   * $ '''weston-terminal'''
   * $ '''glmark2-es2-wayland'''

=== Test Plan 16.04LTS ===

 * In addition update desktop from archive
  * Install packages from the [[https://launchpad.net/~mir-team/+archive/ubuntu/rc|release candidate PPA]]:
   * $ '''sudo add-apt-repository ppa:mir-team/release'''
   * $ '''sudo add-apt-repository --update ppa:mir-team/rc'''
   * $ '''sudo apt install mir-demos mir-graphics-drivers-desktop mir-test-tools'''
  * Install applications to test with:
   * Qt mirclient support, qterminal and kate to test with:
    * $ '''sudo apt install qtubuntu-desktop qtwayland5 kate qterminal'''
   * Install glmark2:
    * $ '''sudo apt install glmark2-wayland glmark2-mir'''

 * Mir-on-X11
  * Use an X11 based desktop (Unity, Gnome, etc.).
  * Start a terminal sessions to launch the tests.
  * Run the "smoke tests" to ensure the example clients work
   * $ '''mir-smoke-test-runner'''
   * Check the result is "I: Smoke testing complete with returncode 0"
  * Run a test session in a window
   * $ '''miral-app'''
  * [in the Mir-on-X11 session] Try running, resizing, moving and switching between the following:
   * $ '''mir_demo_client_multiwin'''
   * $ '''kate'''
   * $ '''glmark2-es2-wayland'''
   * $ '''glmark2-es2-mir'''

 * Mir-on-KMS
  * Switch to VT4 and sign in
   * $ '''miral-app --window-manager tiling'''
  * Try running, and switching between the following:
   * $ '''mir_demo_client_multiwin'''
   * $ '''kate'''
   * $ '''glmark2-es2-wayland'''
   * $ '''glmark2-es2-mir'''
  * Run the "smoke tests" to ensure the example clients work
   * $ '''mir-smoke-test-runner'''
   * Check the result is "I: Smoke testing complete with returncode 0"

 * Mir-on-KMS
  * Switch to VT4 and sign in
   * $ '''miral-app'''

Dependents/Clients

Clients of this component

Test Plan

This test plan is not supposed to be complete; use it to guide your manual testing so they don't 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 release

  • Successful run of automated CI testing
  • Verify that the mir-tests-tools snap works

Testing mir-test-tools

These tests should work on all supported series of Classic and on Ubuntu Core. First check that the classic channel has been updated with the release candidate:

  • $ snap info mir-test-tools

This should show something like:

  • candidate: 1.2.0-snap45 2019-05-22 (415) 121MB -

Where the version number matches the release being tested.

  • $ snap install --candidate mir-test-tools

There's a "handy script" to test the snap on the Wiki:

Copy this and run it.

Testing Ubuntu Classic

Testing differs between 16.04LTS and 18.04LTS or later. Testing for 16.04LTS has its own section below.

Test Plan 18.04LTS or later

  • The following should be repeated for 18.04LTS and any later series:
  • In addition update desktop from archive

    • Install packages from the release candidate PPA:

      • $ sudo add-apt-repository --update ppa:mir-team/rc

      • $ sudo apt install mir-demos mir-graphics-drivers-desktop mir-test-tools

    • Install applications to test with:
      • Qt Wayland support, qterminal and kate to test with:

        • $ sudo apt install qtwayland5 kate qterminal

      • Install weston-terminal:

        • $ sudo apt install weston

      • Install glmark2:

        • $ sudo apt install glmark2-wayland

  • Mir-on-X11
    • Use an X11 based desktop (Unity, Gnome, etc.).
    • Start a terminal sessions to launch the tests.
    • Run the "smoke tests" to ensure the example clients work

      • $ mir-smoke-test-runner

      • Check the result is "I: Smoke testing complete with returncode 0"
    • Run a test session in a window

      • $ miral-app

    • [in the Mir-on-X11 session] Try running, resizing, moving and switching between the following:

      • $ mir_demo_client_multiwin

      • $ kate

      • $ gnome-terminal

      • $ weston-terminal

      • $ glmark2-es2-wayland

  • Mir-on-KMS
    • Switch to VT4 and sign in
    • Run a test "tiling desktop" session

      • $ miral-app --window-manager tiling

    • Try running, and switching between the following:

      • $ mir_demo_client_multiwin

      • $ kate

      • $ gnome-terminal

      • $ weston-terminal

      • $ glmark2-es2-wayland

Test Plan 16.04LTS

  • In addition update desktop from archive

    • Install packages from the release candidate PPA:

      • $ sudo add-apt-repository ppa:mir-team/release

      • $ sudo add-apt-repository --update ppa:mir-team/rc

      • $ sudo apt install mir-demos mir-graphics-drivers-desktop mir-test-tools

    • Install applications to test with:
      • Qt mirclient support, qterminal and kate to test with:

        • $ sudo apt install qtubuntu-desktop qtwayland5 kate qterminal

      • Install glmark2:

        • $ sudo apt install glmark2-wayland glmark2-mir

  • Mir-on-X11
    • Use an X11 based desktop (Unity, Gnome, etc.).
    • Start a terminal sessions to launch the tests.
    • Run the "smoke tests" to ensure the example clients work

      • $ mir-smoke-test-runner

      • Check the result is "I: Smoke testing complete with returncode 0"
    • Run a test session in a window

      • $ miral-app

    • [in the Mir-on-X11 session] Try running, resizing, moving and switching between the following:

      • $ mir_demo_client_multiwin

      • $ kate

      • $ glmark2-es2-wayland

      • $ glmark2-es2-mir

  • Mir-on-KMS
    • Switch to VT4 and sign in

      • $ miral-app --window-manager tiling

    • Try running, and switching between the following:

      • $ mir_demo_client_multiwin

      • $ kate

      • $ glmark2-es2-wayland

      • $ glmark2-es2-mir

    • Run the "smoke tests" to ensure the example clients work

      • $ mir-smoke-test-runner

      • Check the result is "I: Smoke testing complete with returncode 0"
  • Mir-on-KMS
    • Switch to VT4 and sign in

      • $ miral-app

Process/Merges/TestPlans/Mir (last edited 2024-05-09 13:09:10 by alan-griffiths)