Ubuntu Wiki

• Test plan for component: Mir

• Trunk URL: github:MirServer/mir

• Ubuntu Package URL (LP): http://launchpad.net/ubuntu/+source/mir

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:

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

Copy this and run it.

Test Plan 20.04LTS or later

Test Matrix

• 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

• Commands for testing specific features:
  • Console provider

    • --console-provider=vt

      • This requires running with root privileges

      • Need to ensure that XDG_RUNTIME_DIR is set in the environment. If using sudo, it might strip this out; running something like sudo env XDG_RUNTIME_DIR=/run/user/1000 miral-shell … will ensure this is set.

    • --console-provider=logind

      • This will be used by default
      • Requires an active login session

    • --console-provider=minimal

      • Used when all others fail.
      • Does not provide VT switching capabilities (Ctrl-Alt-F1, etc)
      • Used for the mir-on-x11 platform (as neither VT nor logind will work there)
  • Window Manager

    • --window-manager=tiling

    • --window-manager=floating

    • -kiosk

  • Testing specific platforms

    • --platform-display-libs=mir:$NAME --platform-rendering-libs=mir:$NAME

• 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