DevTools/Features/ConsoleObjectCompletion/Test Plan

From MozillaWiki
Jump to navigation Jump to search

Feature/subfeature to test

General info/Overview

This feature tracks work that was originally blended into the WebConsole7 feature, but not completed for Firefox 7.

When the Web Console shipped with Firefox 4, it provided the first console object to be always available to content in Firefox. It provided enough of the console object to be useful (console.log being by far the most popular method on the object). However, it was still lacking in features that developers commonly use. |Feature users and use cases=You can open up the Web Console and type console.dir(window) and see a set of properties and values from the window object in the console object.

In a JavaScript program, you can use console.group and console.groupEnd to visually group together related log messages. |Feature requirements=* The console object implements the portion of the API that is implemented by both Firebug and WebKit. Notably, this includes time, timeEnd, dir, group and groupEnd.

Feature page

Link and details about the feature page

Tracking bug

Should contain the bugzilla link of the feature tracking bug

Feature status

Please use "Edit with form" above to edit this page.

Status

Console Object Completion
Stage Landed
Status Complete
Release target Firefox 10
Health OK
Status note `

{{#set:Feature name=Console Object Completion

|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 10 |Feature health=OK |Feature status note=` }}

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)
Retrieved from "https://wiki.allizom.org/index.php?title=DevTools/Features/ConsoleObjectCompletion/Test_Plan&oldid=368548"