Mir
Differences between revisions 32 and 87 (spanning 55 versions)
|
Size: 5072
Comment:
|
Size: 4366
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 * '''Test plan for component''': Mir and unity-system-compositor * '''Component Checklist''': https://wiki.ubuntu.com/Process/Merges/Checklists/Mir * '''Trunk URL''': lp:~mir-team/mir/utopic & lp:unity-system-compositor * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir & http://launchpad.net/ubuntu/+source/unity-system-compositor == Dependents/Clients == Clients of this component * '''Unity-Mir''' http://code.launchpad.net/unity-mir * '''Platform-api''' http://code.launchpad.net/platform-api * '''Xmir''' https://github.com/RAOF/xserver |
* '''Test plan for component''': Mir * '''Trunk URL''': [[https://github.com/MirServer/mir/|github:MirServer/mir]] * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir |
| Line 24: | Line 7: |
| '''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 "cancel power dialog" * select "power off" on dialog * 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 notepad * '''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 notepad, 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 * Notepad copy/paste to message app * '''note''' currently msg app has a bug where paste doesn't prompt/highlight properly * open notepad, 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 with the bottom bar make sure it reveals, hides as expected * 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). Note: same link as above, under "Running Deb tests" - look for 'webbrowser'. * If any oddities are witness, 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 82: | Line 10: |
| * Verify that the mir-tests-tools snap works | |
| Line 83: | Line 12: |
| * In addition update desktop from archive (assumes on utopic) * Install packages from build silo |
== Testing mir-test-tools == |
| Line 86: | Line 14: |
| * Install or enable XMir * boot to unity7 desktop and utilize applications such as browser, chat client * play a video in browser * suspend system and bring back * allow screen to blank, wake up |
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: |
| Line 92: | Line 16: |
| * 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: * '''beta: 1.2.0-snap45 2019-05-22 (415) 121MB -''' Where the version number matches the release being tested. * $ '''snap install --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 20.04LTS or later === ==== Test Matrix ==== ||'''Platform'''||23.10||23.04||22.04LTS||20.04LTS|| ||gbm-kms|| || || || || ||gbm-x11|| || || || || ||eglstream-kms|| || || || || ||'''Console'''||23.10||23.04||22.04LTS||20.04LTS|| ||minimal|| || || || || ||linux-VT|| || || || || ||logind|| || || || || ||'''WM'''||23.10||23.04||22.04LTS||20.04LTS|| ||floating|| || || || || ||tiling|| || || || || ||kiosk|| || || || || * 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''' * 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''' |
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:
beta: 1.2.0-snap45 2019-05-22 (415) 121MB -
Where the version number matches the release being tested.
$ snap install --beta mir-test-tools
There's a "handy script" to test the snap on the Wiki:
Copy this and run it.
Test Plan 20.04LTS or later
Test Matrix
Platform |
23.10 |
23.04 |
22.04LTS |
20.04LTS |
gbm-kms |
|
|
|
|
gbm-x11 |
|
|
|
|
eglstream-kms |
|
|
|
|
Console |
23.10 |
23.04 |
22.04LTS |
20.04LTS |
minimal |
|
|
|
|
linux-VT |
|
|
|
|
logind |
|
|
|
|
WM |
23.10 |
23.04 |
22.04LTS |
20.04LTS |
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-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
- 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
- Console provider
- 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
Process/Merges/TestPlans/Mir (last edited 2024-05-09 13:09:10 by alan-griffiths)