Mir

Differences between revisions 7 and 78 (spanning 71 versions)
⇤ ← Revision 7 as of 2014-01-17 11:49:50 →
Size: 976
Editor: 69
Comment:
← Revision 78 as of 2019-10-10 11:27:21 → ⇥
Size: 5327
Editor: alan-griffiths
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Process/Merges/TestPlans/Common
## page was renamed from Process/TestPlans/Common

 * '''Test plan for component''': <COMMON> (Replace this with your own compnent)
 * '''Component Checklist''': <backlink to your component checklist>
 * '''Trunk URL''': lp:trunkbranch
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/PACKAGENAME
  * '''Test plan for component''': Mir
 * '''Component Checklist''': https://wiki.ubuntu.com/Process/Merges/Checklists/Mir
 * '''Trunk URL''': [[https://github.com/MirServer/mir/|github:MirServer/mir]]
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir
Line 12: Line 8:
<list the hot clients of this component and that are likely to see side-effect regressions from MP landings> Clients of this component

 * '''Xmir''' https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir
 * '''SDL''' [''16.04LTS only'']
 * '''qtubuntu''' https://launchpad.net/qtubuntu [''16.04LTS only'']
Line 16: Line 16:
'''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''' '''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 18: Line 18:
 * Install image on phone
 * install freshly build MPs that are needed for landing
 * Test that X works
 * Test that Y works		  * 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 `candidate` 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:

   * 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:
   * $ '''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:
   * $ '''kate'''
   * $ '''gnome-terminal'''
   * $ '''weston-terminal'''
   * $ '''glmark2-es2-wayland'''

 * Mir-on-Nvidia
  * $ '''sudo apt install mir-graphics-drivers-nvidia'''
  * Switch to VT4 and sign in
  * Run a test session
   * $ '''miral-app'''
  * Try running, and switching between the following:
   * $ '''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 candidate 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:

      • $ 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:

      • $ kate

      • $ gnome-terminal

      • $ weston-terminal

      • $ glmark2-es2-wayland

  • Mir-on-Nvidia

    • $ sudo apt install mir-graphics-drivers-nvidia

    • Switch to VT4 and sign in
    • Run a test session

      • $ miral-app

    • Try running, and switching between the following:

      • $ 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)