Unity8

Differences between revisions 1 and 30 (spanning 29 versions)
⇤ ← Revision 1 as of 2013-12-18 14:54:39 →
Size: 339
Editor: port-19093
Comment:
← Revision 30 as of 2015-10-21 17:14:52 → ⇥
Size: 2192
Editor: saviq
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Test plan for: '''COMMON'''  * '''Test plan for component''': Unity8
 * '''Component Checklist''': https://wiki.ubuntu.com/Process/Merges/Checklists/Unity8
 * '''Trunk URL''': lp:unity8
 * '''Ubuntu Package URL (LP)''': http://launchpad.net/ubuntu/+source/unity8
Line 5: Line 9:
<list the hot components that are clients of this component and that are likely to see side-effect regressions from MP landings>  * Unity8 is the top-most component.
Line 9: Line 13:
 * Install image on phone
 * install freshly build MPs that are needed for landing
 * Test that X works
 * Test that Y works		  * In addition, install updated image on phone and tablet, load packages from PPA build silo per Release team's process
 * The following can be viewed as a 3 minute investigation test to ensure
  * on a locked phone, you can't unlock the phone during boot without entering the passcode ([[http://pad.lv/1395075|BUG #1395075]])
  * greeter can dismiss
  * indicator panel drop, connect to backends. Try launching settings from indicators, make sure all the indicators display meaningful data.
  * navigating/scrolling the dash works as expected, note whether performance did not suffer
  * previews in dash can be accessed (note: if change related to music and video, test those)
  * OSK reveals, takes input and dismisses as expected (note: cross check known OSK bugs for any oddity)
  * time out and power button blanks screen, and power button unblanks screen
  * apps can be installed, note that the whole preview journey is consistent
  * launcher can be accessed and launch an app (note: test a preinstalled and a click app)
  * right edge navigation between apps & dash is as expected, all apps can be closed
  * find ~ -name trust.db -exec rm {} \; reboot and then test some trust prompts (location, camera picture & video recording)
  * behavior associated with MPs is as expected with the relevant component, e.g. any special activity dash, indicator or launcher
 * Please run the ui unit tests tests, unless you know for certain that jenkins has run the ui tests on a silo
  * use adt
{{{$ adt-run unity8 -o vivid --setup-commands "apt install --yes software-properties-common; \
     apt-add-repository --yes --enable-source ppa:ci-train-ppa-service/landing-022; \
     apt update" --- schroot vivid-overlay-amd64-shm}}}
  * or run locally
   * grab source from the PPA
{{{$ ./build.sh
$ cd builddir
$ make test xvfbuitests}}}

Dependents/Clients

  • Unity8 is the top-most component.

Test Plan

  • In addition, install updated image on phone and tablet, load packages from PPA build silo per Release team's process
  • The following can be viewed as a 3 minute investigation test to ensure

    • on a locked phone, you can't unlock the phone during boot without entering the passcode (BUG #1395075)

    • greeter can dismiss
    • indicator panel drop, connect to backends. Try launching settings from indicators, make sure all the indicators display meaningful data.
    • navigating/scrolling the dash works as expected, note whether performance did not suffer
    • previews in dash can be accessed (note: if change related to music and video, test those)
    • OSK reveals, takes input and dismisses as expected (note: cross check known OSK bugs for any oddity)
    • time out and power button blanks screen, and power button unblanks screen
    • apps can be installed, note that the whole preview journey is consistent
    • launcher can be accessed and launch an app (note: test a preinstalled and a click app)

    • right edge navigation between apps & dash is as expected, all apps can be closed

    • find ~ -name trust.db -exec rm {} \; reboot and then test some trust prompts (location, camera picture & video recording)

    • behavior associated with MPs is as expected with the relevant component, e.g. any special activity dash, indicator or launcher
  • Please run the ui unit tests tests, unless you know for certain that jenkins has run the ui tests on a silo
    • use adt

{{{$ adt-run unity8 -o vivid --setup-commands "apt install --yes software-properties-common; \

  • apt-add-repository --yes --enable-source ppa:ci-train-ppa-service/landing-022; \ apt update" --- schroot vivid-overlay-amd64-shm}}}
  • or run locally
    • grab source from the PPA

{{{$ ./build.sh $ cd builddir $ make test xvfbuitests}}}

Process/Merges/TestPlans/Unity8 (last edited 2017-02-16 16:56:37 by localhost)