QA/Firefox3.5/Private Browsing Test Plan: Difference between revisions
< QA | Firefox3.5
Jump to navigation
Jump to search
No edit summary |
|||
Line 35: | Line 35: | ||
*Edge Cases | *Edge Cases | ||
**Visiting the same site in both Private and Normal Browsing Modes | **Visiting the same site in both Private and Normal Browsing Modes | ||
**Importing data during Private Browsing sessio | |||
*Areas that will NOT be covered (by developer, third party, etc.) | *Areas that will NOT be covered (by developer, third party, etc.) |
Revision as of 19:53, 16 September 2008
- Private Browsing Test Plan
- First draft created 9-15-08 by marcia - This is a work in progress
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
- Major areas of test coverage
- Entering Private Browsing Mode
- Confirm Pref Keep My Session Open
- Confirm Pref Save and Close my Session
- Entering Private Browsing Mode
- Exiting Private Browsing Mode
- Kill Process/Crash while in Private Browsing Mode
- With Session Restore
- Without Session Restore
- Edge Cases
- Visiting the same site in both Private and Normal Browsing Modes
- Importing data during Private Browsing sessio
- Areas that will NOT be covered (by developer, third party, etc.)
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
- Relevant bugs: