Mir
Size: 1474
Comment:
|
Size: 4745
Comment:
|
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 |
|
Line 6: | Line 2: |
* '''Component Checklist''': https://wiki.ubuntu.com/Process/Merges/Checklists/Mir * '''Trunk URL''': lp:mir/ubuntu (note: mir has release branches example lp:mir/0.26) * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir == Dependents/Clients == Clients of this component * '''MirAL''' https://code.launchpad.net/miral * '''qtubuntu''' https://launchpad.net/qtubuntu * '''Xmir''' https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir * '''SDL''' * '''GTK-3''' |
* '''Trunk URL''': [[https://github.com/MirServer/mir/|github:MirServer/mir]] * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir |
Line 23: | Line 7: |
'''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 24: | Line 10: |
* Mir Test Plan (from ppa:mir-team/rc) * Mir Snaps Test Plan === Mir Test Plan === ==== Test Matrix ==== ||'''Platform'''||24.04LTS||22.04LTS||24.10|| ||gbm-kms|| || || || ||gbm-x11|| || || || ||gbm-wayland|| || || || ||eglstream-kms|| || || || ||virtual|| || || || ||'''Console'''||24.04LTS||22.04LTS||24.10|| ||minimal|| || || || ||linux-VT|| || || || ||logind|| || || || ||'''WM'''||24.04LTS||22.04LTS||24.10|| ||floating|| || || || ||tiling|| || || || ||kiosk|| || || || |
|
Line 26: | Line 34: |
* Install packages from build silo | * 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-platform-graphics-virtual 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''' |
Line 28: | Line 45: |
* 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. |
* Commands for testing specific features: * Console provider * `--console-provider=vt --vt=4` * 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` * Switch to VT4, sign in and `miral-app ...` * `--console-provider=minimal` * Used when all others fail. * Does not provide VT switching capabilities (Ctrl-Alt-F1, etc) * Used for the gbm-x11, gbm-wayland & virtual platforms * Window Manager * `--window-manager=tiling` * `--window-manager=floating` * `-kiosk` * Testing specific platforms * `--platform-display-libs=mir:$NAME --platform-rendering-libs=mir:$NAME` * Platform * X11: Use an X11 supporting desktop * virtual: `--platform-display-lib=mir:virtual --virtual-output=1280x1024` * Also add wayvnc support: `--add-wayland-extension=zwp_virtual_keyboard_manager_v1:zwlr_virtual_pointer_manager_v1:zwlr_screencopy_manager_v1` * In a separate terminal run: `WAYLAND_DISPLAY=wayland-1 ubuntu-frame-vnc` * In a separate terminal run: `gvncviewer localhost` * wayland: `--platform-display-lib=mir:wayland --wayland-host=$WAYLAND_DISPLAY` * Some tests * Run the "smoke tests" to ensure the example clients work * Start a terminal sessions to launch the tests. * $ '''mir-smoke-test-runner''' * Check the result is "I: Smoke testing complete with returncode 0" * try some apps * $ '''miral-app''' * [in the nested session] Try running, resizing, moving and switching between the following: * $ '''kate''' * $ '''gnome-terminal''' * $ '''weston-terminal''' * $ '''glmark2-es2-wayland''' |
Line 35: | Line 82: |
* Install MirAL * Follow [[https://wiki.ubuntu.com/Process/Merges/TestPlans/MirAL|MirAL test plan]]. |
* 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''' |
Line 38: | Line 90: |
* ''On zesty only'' Install unity8-desktop-session * login to unity8 desktop and utilize applications such as browser, play with dash * allow screen to blank, wake up |
=== Mir Snaps Test Plan === There are several snaps to consider * mir-test-tools * ubuntu-frame * confined-shell * miriway We give detailed instructions only for mir-test-tools as the pattern is obvious. * Verify that the snaps works These tests should work on all supported series of Classic and on Ubuntu Core. First check that the `beta` channel has been updated with the release candidate: * $ '''snap info mir-test-tools''' This should show something like: * '''24/beta: 2.17.0~rc5-snap165 2024-05-08 (15097) 105MB -''' Where the version (2.17.0~rc5-snap165) matches the release being tested. * $ '''snap install --channel=24/beta 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 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
- Mir Test Plan (from ppa:mir-team/rc)
- Mir Snaps Test Plan
Mir Test Plan
Test Matrix
Platform |
24.04LTS |
22.04LTS |
24.10 |
gbm-kms |
|
|
|
gbm-x11 |
|
|
|
gbm-wayland |
|
|
|
eglstream-kms |
|
|
|
virtual |
|
|
|
Console |
24.04LTS |
22.04LTS |
24.10 |
minimal |
|
|
|
linux-VT |
|
|
|
logind |
|
|
|
WM |
24.04LTS |
22.04LTS |
24.10 |
floating |
|
|
|
tiling |
|
|
|
kiosk |
|
|
|
- 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-platform-graphics-virtual 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
- Qt Wayland support, qterminal and kate to test with:
- Commands for testing specific features:
- Console provider
--console-provider=vt --vt=4
- 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
Switch to VT4, sign in and miral-app ...
--console-provider=minimal
- Used when all others fail.
- Does not provide VT switching capabilities (Ctrl-Alt-F1, etc)
Used for the gbm-x11, gbm-wayland & virtual platforms
- Window Manager
--window-manager=tiling
--window-manager=floating
-kiosk
- Testing specific platforms
--platform-display-libs=mir:$NAME --platform-rendering-libs=mir:$NAME
- Platform
- X11: Use an X11 supporting desktop
virtual: --platform-display-lib=mir:virtual --virtual-output=1280x1024
Also add wayvnc support: --add-wayland-extension=zwp_virtual_keyboard_manager_v1:zwlr_virtual_pointer_manager_v1:zwlr_screencopy_manager_v1
In a separate terminal run: WAYLAND_DISPLAY=wayland-1 ubuntu-frame-vnc
In a separate terminal run: gvncviewer localhost
wayland: --platform-display-lib=mir:wayland --wayland-host=$WAYLAND_DISPLAY
- Platform
- Some tests
- Run the "smoke tests" to ensure the example clients work
- Start a terminal sessions to launch the tests.
$ mir-smoke-test-runner
- Check the result is "I: Smoke testing complete with returncode 0"
- try some apps
$ miral-app
- [in the nested session] Try running, resizing, moving and switching between the following:
$ kate
$ gnome-terminal
$ weston-terminal
$ glmark2-es2-wayland
- 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
- Run the "smoke tests" to ensure the example clients work
- Console provider
Mir Snaps Test Plan
There are several snaps to consider * mir-test-tools * ubuntu-frame * confined-shell * miriway
We give detailed instructions only for mir-test-tools as the pattern is obvious.
- Verify that the snaps works
These tests should work on all supported series of Classic and on Ubuntu Core. First check that the beta channel has been updated with the release candidate:
$ snap info mir-test-tools
This should show something like:
24/beta: 2.17.0~rc5-snap165 2024-05-08 (15097) 105MB -
Where the version (2.17.0~rc5-snap165) matches the release being tested.
$ snap install --channel=24/beta mir-test-tools
There's a "handy script" to test the snap on the Wiki:
Copy this and run it.
Process/Merges/TestPlans/Mir (last edited 2024-05-09 13:09:10 by alan-griffiths)