User:Mevans/FeatureTemplateB: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(82 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= Feature (example: add-ons preferes UI)  =
= Feature (example: add-ons preference UI)  =


*'''Development Status:''' - In progress (date)  
*'''Development Status:''' - In progress (date)  
Line 6: Line 6:
*'''Tracking Bugs''':
*'''Tracking Bugs''':


= Feature Overview =
=== Feature Description ===


Brief description of the feature
Brief description of the feature listed here.


= Feature Description =
 
= [[#Feature Release Readiness Assessment_Details|Feature Release Readiness Assessment]] =
 
The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone. Each milestone link references a section below that discusses the criteria and evaluation that went into the QA go/no-go decision.
 
{| class="fullwidth-table"
|-
! Milestone
! Assessment
|-
| [[#Beta1]]
| N/A
|-
| [[#Beta2]]
| N/A
|-
| [[#Beta3]]
| N/A
|}
 
[[#Feature_Description|top]]
 
= [[#Feature_Documentation_Details|Feature Documentation]] =


{| class="fullwidth-table"
{| class="fullwidth-table"
Line 16: Line 38:
! Item
! Item
! Description
! Description
! Notes
! Status
|-
|-
| [[#Project_Wiki]]
| [[#Project_Wiki]]
Line 22: Line 44:
|
|
|-
|-
| [[#Developer Links (blogs)]]
| [[#Developer_Links|#Developer_Links (blogs)]]
| Developer links to feature related sites
| Developer links to feature related sites
|  
|  
|-
|-
| [[#Other Docs]]
| [[#Other_Docs]]
| Web links to feature related sites  
| Web links to feature related sites  
|
|-
| [[#Developer_QA_Review]]
| Details from developer and qa discussions regarding feature test strategies and issues.
|
|}
[[#Feature_Description|top]]
= [[#Feature_Bug_Management_Details|Feature Bug Management]] =
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Bug_Tracking]]
| Top level bugs tracking feature 
|
|-
| [[#Bug_Verification]]
| Feature bugs that need verification 
|
|-
| [[#Bug_Triage]]
| Links triage bug tasks 
|
|}
[[#Feature_Description|top]]
= [[#Feature_Test_Items_Details|Feature Test Items]] =
The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what '''should''' be covered. If it is not covered, list it as not covered.
'''Note: not all items listed below will apply for a given feature'''
{| class="fullwidth-table"
|-
! Test Item
! Description
! Covered By
! Status
|-
| Item 1
| Item 1 Description
| Developer Tests
|
|-
| Item 2
| Item 2 Description
| Beta tester exposure
|
|-
| [[#Localization]]
| Feature localization
|
|
|-
| [[#Accessibility]] 
| Feature accessibility
|
|
|-
| [[#Plugins]]
| Plugins compatibility 
|
|
|-
| [[#Addons]]
| Addons compatibility 
|
|
|-
| [[#Topsites]]
| Top internet sites compatibilities 
|
|
|}
[[#Feature_Description|top]]
= [[#Feature_Tests_Details|Feature Tests]] =
== [[#Automated_Tests_Details|Automated Tests]] ==
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Developer_Tests]]
| Links to automated developer tests
|
|-
| [[#Mozmill_Tests]]
| Links to automated mozmill feature test cases 
|  
|  
|}
|}
== [[#Manual_Tests_Details|Manual Tests]] ==
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Smoke_Tests]]
| link to smoke tests
|
|-
| [[#Regression_Tests]]
| link to BFT and/or regression tests
|
|-
| [[#Functional_Tests]]
| link to FFT and/or complete functional tests
|
|}
[[#Feature_Description|top]]
= [[#Community_Test_Events_Details|Community Test Events]] =
{| class="fullwidth-table"
|-
! Item
! Description
! Status
|-
| [[#Testdays]]
| Links to test day event results for feature
|
|-
| [[#Bugdays]]
| Links to bug day event results for feature
|
|-
| [[#Meetups]]
| Links to Meetup events for feature
|
|}
[[#Feature_Description|top]]
= [[#Feature_Documentation|Feature Documentation Details]] =
== Project Wiki ==
* Provide link to all project related wikis
[[#Feature_Documentation|top]]
== Developer Links ==
* Provide links to all feature related developer links to blogs and other internet sites
[[#Feature_Documentation|top]]
== Other Docs ==
* Provide links to all feature related developer links to blogs and other internet sites
[[#Feature_Documentation|top]]
== Developer QA Review ==
The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:
* Do we have automated tests for the feature?
* What do they cover?
* What do they not cover?
* How well do they cover the feature?
* What are the important areas we should focus on?
* What are the dependencies?
* What is our comfort level with this feature in its current state?
* What feedback would you like from QA?
[[#Feature_Documentation|top]]
= [[#Feature_Release_Readiness_Assessment|Feature Release Readiness Assessment Details]] =
== Beta1 ==
== Beta2 ==
== Beta3 ==
= [[#Feature_Bug_Management|Feature Bug Management Details]] =
== Bug Tracking ==
* Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
{| class="fullwidth-table"
|-
! Query Name
! Description
|-
|bugzilla query url link
|query description
|}
 
[[#Feature_Bug_Management|top]]
== Bug Verification ==
* Feature bugs that need verification 
[[#Feature_Bug_Management|top]]
== Bug Triage ==
* Bug triage information
[[#Feature_Bug_Management|top]]
= [[#Feature_Test_Items|Feature Test Items Details]] =
== Localization ==
* Details of feature localization test requirements
[[#Feature_Test_Items|top]]
== Accessibility == 
* Details of feature accessibility test requirements
[[#Feature_Test_Items|top]]
== Plugins ==
* Details of plugins compatibility test requirements
[[#Feature_Test_Items|top]]
== Addons ==
* Details of addons compatibility 
[[#Feature_Test_Items|top]]
== Topsites ==
* Details of top internet sites test requirements
[[#Feature_Test_Items|top]]
= [[#Feature_Tests|Feature Tests Details]] =
== [[#Automated_Tests|Automated Tests Details]] ==
=== Developer Tests ===
* Links to automated developer tests
[[#Feature_Tests|top]]
=== Mozmill Tests ===
If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "''[mozmill-test-needed]''" whiteboard entry to the feature implementation or regression bug.
List of Mozmill Tests:
* Links to automated mozmill feature test cases 
[[#Feature_Tests|top]]
== [[#Manual_Tests|Manual Tests Details]] ==
=== Smoke_Tests ===
* links to litmus smoke tests or description
[[#Feature_Tests|top]]
=== Regression_Tests ===
* links to litmus BFT and/or regression tests description
[[#Feature_Tests|top]]
=== Functional_Tests ===
* links to litmus FFT and/or complete functional tests description
[[#Feature_Tests|top]]
= [[#Community_Test_Events|Community Test Events Details]] =
== Testdays ==
* Links to test day event results for feature
== Bugdays ==
* Links to bug day event results for feature
== Meetups ==
* Links to Meetup events for feature

Latest revision as of 21:30, 8 June 2010

Feature (example: add-ons preference UI)

  • Development Status: - In progress (date)
  • Feature Testing: - In progress (date)
  • Team: Developer, QA contact 1, QA contact 2, Community Volunteer...
  • Tracking Bugs:

Feature Description

Brief description of the feature listed here.


Feature Release Readiness Assessment

The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone. Each milestone link references a section below that discusses the criteria and evaluation that went into the QA go/no-go decision.

Milestone Assessment
#Beta1 N/A
#Beta2 N/A
#Beta3 N/A

top

Feature Documentation

Item Description Status
#Project_Wiki Wiki Links to all feature related entries
#Developer_Links (blogs) Developer links to feature related sites
#Other_Docs Web links to feature related sites
#Developer_QA_Review Details from developer and qa discussions regarding feature test strategies and issues.

top

Feature Bug Management

Item Description Status
#Bug_Tracking Top level bugs tracking feature
#Bug_Verification Feature bugs that need verification
#Bug_Triage Links triage bug tasks

top

Feature Test Items

The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.

Note: not all items listed below will apply for a given feature

Test Item Description Covered By Status
Item 1 Item 1 Description Developer Tests
Item 2 Item 2 Description Beta tester exposure
#Localization Feature localization
#Accessibility Feature accessibility
#Plugins Plugins compatibility
#Addons Addons compatibility
#Topsites Top internet sites compatibilities

top


Feature Tests

Automated Tests

Item Description Status
#Developer_Tests Links to automated developer tests
#Mozmill_Tests Links to automated mozmill feature test cases

Manual Tests

Item Description Status
#Smoke_Tests link to smoke tests
#Regression_Tests link to BFT and/or regression tests
#Functional_Tests link to FFT and/or complete functional tests

top

Community Test Events

Item Description Status
#Testdays Links to test day event results for feature
#Bugdays Links to bug day event results for feature
#Meetups Links to Meetup events for feature

top

Feature Documentation Details

Project Wiki

  • Provide link to all project related wikis

top

Developer Links

  • Provide links to all feature related developer links to blogs and other internet sites

top

Other Docs

  • Provide links to all feature related developer links to blogs and other internet sites

top

Developer QA Review

The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:

  • Do we have automated tests for the feature?
  • What do they cover?
  • What do they not cover?
  • How well do they cover the feature?
  • What are the important areas we should focus on?
  • What are the dependencies?
  • What is our comfort level with this feature in its current state?
  • What feedback would you like from QA?

top

Feature Release Readiness Assessment Details

Beta1

Beta2

Beta3

Feature Bug Management Details

Bug Tracking

  • Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
Query Name Description
bugzilla query url link query description

top

Bug Verification

  • Feature bugs that need verification

top

Bug Triage

  • Bug triage information

top

Feature Test Items Details

Localization

  • Details of feature localization test requirements

top

Accessibility

  • Details of feature accessibility test requirements

top

Plugins

  • Details of plugins compatibility test requirements

top

Addons

  • Details of addons compatibility

top

Topsites

  • Details of top internet sites test requirements

top

Feature Tests Details

Automated Tests Details

Developer Tests

  • Links to automated developer tests

top

Mozmill Tests

If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.

List of Mozmill Tests:

  • Links to automated mozmill feature test cases

top

Manual Tests Details

Smoke_Tests

  • links to litmus smoke tests or description

top

Regression_Tests

  • links to litmus BFT and/or regression tests description

top

Functional_Tests

  • links to litmus FFT and/or complete functional tests description

top

Community Test Events Details

Testdays

  • Links to test day event results for feature

Bugdays

  • Links to bug day event results for feature

Meetups

  • Links to Meetup events for feature