Mir
Differences between revisions 23 and 66 (spanning 43 versions)
|
Size: 4209
Comment:
|
Size: 2940
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 |
* '''Test plan for component''': Mir |
| Line 7: | Line 3: |
| * '''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 |
* '''Trunk URL''': [[https://launchpad.net/mir/ubuntu|lp:mir/ubuntu]] (note: mir has release branches, for example [[https://launchpad.net/mir/0.26|lp:mir/0.26]]) * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/mir |
| Line 17: | Line 11: |
| * '''Unity-Mir''' http://code.launchpad.net/unity-mir * '''Platform-api''' http://code.launchpad.net/platform-api * '''Xmir''' https://github.com/RAOF/xserver |
* '''qtubuntu''' https://launchpad.net/qtubuntu * '''Xmir''' https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir * '''SDL''' * '''GTK-3''' |
| Line 24: | Line 18: |
| '''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 * 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 time out and power button blanks screen, and power button unblanks screen * Ensure time out sits for 5 minutes as to allow deep sleep * Ensure app launches and can quit * 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 * 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 * 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 * Download click & 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) * If mirclient API break, test Xmir on desktop * 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 MP''' |
| Line 71: | Line 22: |
| * In addition update desktop from archive (assumes on utopic) * Install packages from build silo |
* The following should be repeated for each of the supported series: 16.04LTS, 18.04LTS and (at the time of writing) 17.10. |
| Line 74: | Line 24: |
| * 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 |
* 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/rc''' * $ '''sudo apt update''' * $ '''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''' * ''On 16.04 Xenial ONLY'' also install qt support for Mir * $ '''sudo apt install qtubuntu-desktop''' * Install weston-terminal: * $ '''sudo apt install weston''' * Install glmark2: * $ '''sudo apt install glmark2-wayland''' |
| Line 80: | Line 39: |
| * Install unity8-desktop-session-mir * login to unity8 desktop and utilize applications such as browser, play with dash * allow screen to blank, wake up |
* 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''' [''On 16.04 Xenial ONLY'' add '''-qt-mirclient -gtk-mirclient'''] * [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, switch back to the desktop * Run a test "desktop" session * $ '''miral-desktop''' [''On 16.04 Xenial ONLY'' add '''-qt-mirclient -gtk-mirclient'''] '''--window-manager tiling''' * [in the Mir session] Try running, and switching between the following: * $ '''mir_demo_client_multiwin''' * $ '''kate''' * $ '''gnome-terminal''' * $ '''weston-terminal''' * $ '''glmark2-es2-wayland''' |
Test plan for component: Mir
Component Checklist: https://wiki.ubuntu.com/Process/Merges/Checklists/Mir
Trunk URL: lp:mir/ubuntu (note: mir has release branches, for example lp:mir/0.26)
Ubuntu Package URL (LP): http://launchpad.net/ubuntu/+source/mir
Dependents/Clients
Clients of this component
qtubuntu https://launchpad.net/qtubuntu
Xmir https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir
SDL
GTK-3
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 MP
- Successful run of automated CI testing
- The following should be repeated for each of the supported series: 16.04LTS, 18.04LTS and (at the time of writing) 17.10.
- In addition update desktop from archive
Install packages from the release candidate PPA:
$ sudo add-apt-repository ppa:mir-team/rc
$ sudo apt update
$ 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
On 16.04 Xenial ONLY also install qt support for Mir
$ sudo apt install qtubuntu-desktop
- Install weston-terminal:
$ sudo apt install weston
- Install glmark2:
$ sudo apt install glmark2-wayland
- Qt Wayland support, qterminal and kate to test with:
- 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 [On 16.04 Xenial ONLY add -qt-mirclient -gtk-mirclient]
- [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, switch back to the desktop
- Run a test "desktop" session
$ miral-desktop [On 16.04 Xenial ONLY add -qt-mirclient -gtk-mirclient] --window-manager tiling
- [in the Mir session] Try running, and switching between the following:
$ mir_demo_client_multiwin
$ kate
$ gnome-terminal
$ weston-terminal
$ glmark2-es2-wayland
Process/Merges/TestPlans/Mir (last edited 2024-05-09 13:09:10 by alan-griffiths)