QA/Firefox3.5/Private Browsing Test Plan: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.5
Jump to navigation Jump to search
(New page: <small>« QA/Firefox3.1/TestPlan</small> ;Feature <abc> Test Plan = Overview = Provide an abstract of the feature and the test strategy. Are there ...)
 
No edit summary
Line 1: Line 1:
<small>[[QA/Firefox3.1/TestPlan|&laquo; QA/Firefox3.1/TestPlan]]</small>
<small>[[QA/Firefox3.1/TestPlan|&laquo; QA/Firefox3.1/TestPlan]]</small>


;Feature <abc> Test Plan
;Private Browsing Test Plan


= Overview =
= Overview =


  Provide an abstract of the feature and the test strategy.
Provide a way for users to not be tracked when doing private browsing. According to mconnor's document, there should be a clear delineation between your "public" and "private" browsing sessions.
  Are there particular challenges with testing this feature?
 
There will be some challenges with testing this feature since it is a complex area and many areas of stored data will need to be tested including:
**Cookies
**History
**Cache
**Content Prefs
**User Passwords
**Autocomplete
**DOM storage
**Authenicated Sessions
**Downloads
**Session Store


= Test Strategy =
= Test Strategy =


  List major areas of test coverage
*Major areas of test coverage
  List areas that will NOT be covered (by developer, third party, etc.)
**See list above
  Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)
*Areas that will NOT be covered (by developer, third party, etc.)
*Unit Tests
**Unit Tests
**https://wiki.mozilla.org/User:Ehsan/PrivateBrowsingTests
***https://wiki.mozilla.org/User:Ehsan/PrivateBrowsingTests
 
There will be a set of manual test cases that will be added to Litmus to cover this feature area.


= Schedule Scoping =
= Schedule Scoping =
    
    
  Estimate amount of time it will take to complete feature
Estimate amount of time it will take to complete feature
  (Consider nightly builds, security reviews, bugs turnaround time)
(Consider nightly builds, security reviews, bugs turnaround time)


= References =
= References =
Line 26: Line 39:
**[https://bugzilla.mozilla.org/show_bug.cgi?id=248970 Private Browsing Mode]
**[https://bugzilla.mozilla.org/show_bug.cgi?id=248970 Private Browsing Mode]
**[https://wiki.mozilla.org/User:Mconnor/PrivateBrowsing Private Browsing Spec]
**[https://wiki.mozilla.org/User:Mconnor/PrivateBrowsing Private Browsing Spec]
  Include notes, links, specs, relevant bugs

Revision as of 00:07, 16 September 2008

« QA/Firefox3.1/TestPlan

Private Browsing Test Plan

Overview

Provide a way for users to not be tracked when doing private browsing. According to mconnor's document, there should be a clear delineation between your "public" and "private" browsing sessions.

There will be some challenges with testing this feature since it is a complex area and many areas of stored data will need to be tested including:

    • Cookies
    • History
    • Cache
    • Content Prefs
    • User Passwords
    • Autocomplete
    • DOM storage
    • Authenicated Sessions
    • Downloads
    • Session Store

Test Strategy

There will be a set of manual test cases that will be added to Litmus to cover this feature area.

Schedule Scoping

Estimate amount of time it will take to complete feature (Consider nightly builds, security reviews, bugs turnaround time)

References

Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox3.5/Private_Browsing_Test_Plan&oldid=108920"