Changes

Jump to: navigation, search

QA/Fennec1.0/TestPlan:Awesome bar Search

2,321 bytes removed, 20:16, 24 October 2008
no edit summary
<small>[[QA/Firefox3.1/TestPlan|&laquo; QA/Firefox3.1/TestPlan]]</small>
;Private Browsing Test PlanFennec - Awesome-bar and Search test plan
*''First draft created 910-1524-08 by marcia jmaher - This is a work in progress''
= Overview =
Provide a way for users Awesome-bar integration into fennec is very similar 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 sessionsthe awesome-bar feature in firefox.
There will be some challenges with testing this feature since it Search 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 Storebit more limited as we don't have all the fields
= Test Strategy =
*Major areas of test coverageAwesome-bar**Entering Private Browsing ModeEnsure Awesome-bar compatible with firefox ***Confirm Pref Keep My Session Openlitmus test cases***Confirm Pref Save and Close my Sessionexisting automation*Exiting Private Browsing Mode*Ensure awesome-bar is mobile device friendly
*CookiesSearch**Unit tests should cover the various states that a cookie would be in when moving between normal->Private Browsing mode. We would want to have a few manual tests here. *HistoryUnit tests should cover the various states that history would be in when moving between normal->Private Browsing mode. We would want to have a few manual tests here.**Adding tags**Adding keywords**Confirm visited link coloring is turned off in private mode. *Cache**Memory cache**Offline cache *Content Prefs**Unit tests will cover retaining zoom setting, ensure existing automation for example. Need to figure out what other content prefs might be affected here.search runs and passes*Passwords**Unit tests will cover the UI piece (confirming the password prompt). *Autocomplete/Location Bar *DOM Storage *Authenticated Sessionsrun litmus search test cases*Download Manager *Session Store**[from ehsan] we currently do a little bit of work with the session restore at the start of the private mode and we need to special case it to just disable writing session data on disk if that pref ensure search is on, I guess... *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 session *Areas that will NOT be covered (by developer, third party, etc.)**Unit Tests***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.mobe device friendly
= Schedule Scoping =
Estimate amount of time it will take * what bugs do we have, and are they in or going to complete feature(Consider nightly builds, security reviews, bugs turnaround time)be ready when? what milestone?
= References =
*Relevant bugs:
**[https://bugzilla.mozilla.org/show_bug.cgi?id=411929 Private Browsing UI]**[https://bugzilla.mozilla.org/show_bug.cgi?id=248970 Private Browsing Mode]**[https://bugzilla.mozilla.org/show_bug.cgi?id=460346 Always on Private Browsing Mode] *ToDo List***[https://wiki.mozilla.org/User:Ehsan/PrivateBrowsingTodo Private Browsing To Do] *Specs**[https://wiki.mozilla.org/User:Mconnor/PrivateBrowsing Private Browsing Spec] *Unit Test Plans**[https://wiki.mozilla.org/Firefox3.1/PrivateBrowsing/TestPlan Unit Test Plan] *API for Extensions**[https://wiki.mozilla.org/User:Ehsan/PrivateBrowsingForExtensions API for Extensionsxyz test]
Jmaher
Confirm
3,376
edits
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/114016"

Navigation menu