ubuntu-app-launch

Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2014-01-29 16:54:42 →
Size: 917
Editor: cpe-76-182-235-222
Comment:
← Revision 4 as of 2014-01-29 19:52:30 → ⇥
Size: 974
Editor: cpe-76-182-235-222
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Process/Merges/Checklists/system-appsupstart-app-launch
## page was renamed from Process/Merges/TestPlan/upstart-app-launch
Line 21: Line 23:
   * Where you able to test starting a click app? (i.e. clock)
   * Where you able to test starting a legacy app? (i.e. system settings)
   * Where you able to test secondary activation? (i.e. system settings running, settings item from an indicator)		    * Run test case: upstart-app-launch/click-app
   * Run test case: upstart-app-launch/legacy-app
   * Run test case: upstart-app-launch/secondary-activation

The source for this document can be gotten from Bazaar: 

$ bzr cat lp:upstart-app-launch/MERGE-REVIEW

This documents the expections that the project has on what both submitters and reviewers should ensure that they've done for a merge into the project.

Submitter Responsibilities

  • Ensure the project compiles and the test suite executes without error
  • Ensure that non-obvious code has comments explaining it

Reviewer Responsibilities

  • Did the Jenkins build compile? Pass? Run unit tests successfully?
  • Are there appropriate tests to cover any new functionality?
  • If this MR effects application startup:
    • Run test case: upstart-app-launch/click-app
    • Run test case: upstart-app-launch/legacy-app
    • Run test case: upstart-app-launch/secondary-activation

Process/Merges/Checklists/ubuntu-app-launch (last edited 2014-05-27 10:39:36 by 194)