DevTools/Features/ConsoleObjectCompletion/Test Plan

From MozillaWiki
< DevTools‎ | Features‎ | ConsoleObjectCompletion
Revision as of 15:01, 11 November 2011 by Unchiu maniac (talk | contribs) (Created page with "= Feature/subfeature to test = == General info/Overview == ; What is the feature intended for? Some brief details about purpose and basic functionality == Feature page == ; Li...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Feature/subfeature to test

General info/Overview

What is the feature intended for? Some brief details about purpose and basic functionality

Feature page

Link and details about the feature page

Tracking bug

Should contain the bugzilla link of the feature tracking bug

Feature status

Can be extracted from the feature page - it is best to have it in the testplan as well

Testing status

Current testing status for the feature - to be provided every week or when it is necessary (highlight any outstanding issue or blocker if it's the case/testing is ongoing as planned)
  • E.g.: week 46 updates:
  • E.g.: week 45 updates:

Team

Team members
  • Development
  • Security
  • QA
  • Contributors
  • Other members

Builds

Available builds for testing the feature with prioritization order clearly noted
Mochitests available (link to mochitests and what has been covered by mochitests)

Testing

Prerequisites

Environment needed
Settings
Preparations for test
Areas planned to be covered by testing
Areas that will not be covered by testing (not in scope)

Use cases

List the use cases for this feature and how are these assessed.

Focus on

Prioritization

Bug queries

Bugzilla queries for
  • unconfirmed bugs
  • new bugs
  • closed bugs
    • resolved fixed
    • resolved wontfix
    • resolved invalid
    • resolved incomplete
General work on bugs
  • fixed bugs verifications
  • bug confirmations

Manual testing

List of testcases and scenarios
Corner cases (optional)
Exploratory testing

Automation

Planning
Coverage information
Guidance to run automation
Guidance to create tests

Results

Platform
Results
  • PASS/FAIL
Comments/Unreproducible issues

Sign-off

sign-off criteria
  • Sign off criteria for merge (Aurora -> Beta)
    • E.g: All planned tests have been executed. No outstanding issues/regressions have been found.
  • Sign off criteria for release (Beta -> Released)
    • E.g: All planned tests have been executed. No outstanding issues/regressions have been found.
  • (Otilia please add your details)