Contribute to Private Browsing Tests

Private Browsing Tests

• Project assigned to AaronMT

An Introduction

Background history

"The purpose of private browsing is to put Firefox into a temporary state where no information about the user's browsing session is stored locally. Firefox currently handles the user's privacy with a feature in preferences to clear all private data. This feature forces the user to choose between having privacy (even if only momentary), and other useful features like browsing history, and saved passwords. Users should be able to go "off the record", they shouldn't have to shoot the reporter. " wiki.mozilla.org/PrivateBrowsing

Preliminary Mockup:

The Project Offered

The new Private Browsing feature (see bug 248970 and the test plan) needs thorough tests written in order to insure its proper functionality. This will involve collaborating with those writing the patch and tests in order to develop a full suite of tests. Resources: ehsan, discussion of Private Browsing

• Helpful Contacts:
  • Ehsan Akhgari
    • E-Mail: (ehsan dot akhgari at gmail dot com)
  • Marcia Knous
    • E-Mail: (marcia at mozilla dot org)
  • Clint Talbert
    • E-Mail: (ctalbert at mozilla dot com)
    • IRC: ctalbert

Project Description

• Private Browsing Test Plan (Outlined by Marcia Knous)
• Private Browsing - Unit Tests
• Possible Project Release Iteration
  • Unit Tests
    • Possible Testing Areas
      • Cookies -> Cookie Service
      • History -> History Service and Bookmark Service
      • Cache
      • DOM Storage
      • Content Prefs
      • Passwords
      • AutoComplete
      • Authenticated Sessions
      • Downloads
      • Session Store

Divided up into some kind of iteration group (0.1/0.2/0.3) of a testing suite. Some areas already covered by Ehsan and others working on Bug #248970.

Private Browsing Test Plan

• Private Browsing Test Plan (Outlined by Marcia Knous)

Private Browsing Unit Tests

• Private Browsing - Unit Tests

Project Milestone Information

• For the first iteration phase, I plan to have complete
  • Testing Areas
    • Unit Tests
      • Places/History Outline Plan

What to expect for 0.1 release?

• I plan to have a unit test complete for the testing area involved with places and history. This will be submitted to Ehsan as well.

Project Notes

• To run a single unit-test use check-one SOLO_FILE
  • Example

make SOLO_FILE=test_bug248970.js -C objdir/netwerk/test check-one

Project Leader(s)

• AaronMT

Project Details

• Private Browsing Test Plan

History Unit Test

• AaronMT 23:45, 26 September 2008 (UTC)
  • Wrote a new function that creates a handful of history items with various visit types.

/**
 * Function fills history and checks if date labels
 * are correct for partially filled history
 *
 * @returns nothing
 */

function fill_history() {
  const checkOlderOffset = 4;

  // add visits for the older days
  for (var i=checkOlderOffset; i<dayLabels.length; i++)
  {
    var testURI = uri("http://mirror"+i+".mozilla.com/b");
    add_visit(testURI, -i);
    var testURI = uri("https://mirror"+i+".mozilla.com/a");
    add_visit(testURI, -i);
    var testURI = uri("ftp://mirror"+i+".google.com/b");
    add_visit(testURI, -i);
    var testURI = uri("http://mirror"+i+".google.com/a");
    add_visit(testURI, -i);
  }
}

Project Weekly TODO

• Week of Sept 29th
  • Goal is to have a unit test available for History Testing Area by the end of the week
    • The testing plan criteria may be found here: click here
• Week of Sept 22nd - (Script available here: test_historySimple.js)
  • Goal is to write a simple XPCShell unit test that taps into an XPCOM service that
    • (a) Creates a history entry.
    • (b) Checks to see if history entry exists.
• Week of Sept 15th
  • What the scope of the project is?
  • What tools/environment will be needed (Windows/Ubuntu)?
  • What scope limitations can be handled for first iteration (0.1)?
  • IRC Channels related to project and or other involved members?

Project News

September

• AaronMT 23:35, 25 September 2008 (UTC)
  • New patch released, downloaded and spoke with Ehsan on IRC over properly installing new patch as well as what test plans I can write
    • Patch 2.10
• AaronMT 03:43, 24 September 2008 (UTC)
  • Wrote a simple unit test script that integrates the nsiBrowserHistory service from XPConnect that creates a history manager, inserts an entry, and checks if it was properly inserted. In essence, this acts as a simple example of writing a unit test.
• AaronMT 16:52, 21 September 2008 (UTC)
  • Researching how the directory structure of unit tests are inside a Mozilla Build / E-Mailed Ehsan
• AaronMT 00:19, 21 September 2008 (UTC)
  • Conversed with Ehsan through E-Mail, asked some questions regarding XPCShell tests and 'How tests are submitted'.
• AaronMT 02:08, 19 September 2008 (UTC)
  • Introduced myself to Bug 248970, hope I get some feedback.
  • Found an excellent example of a unit test written by Ehsan (Mozilla)
• AaronMT 02:09, 18 September 2008 (UTC)
  • Met Mardeg, was introduced to Build:TryServer, and the MozillaTry tree of Tinderbox
• AaronMT 23:50, 16 September 2008 (UTC)
  • Met and talked briefly with Clint Talbert (ctalbert) (QA Dev Engineer)
• AaronMT 18:30, 15 September 2008 (UTC)
  • Selected a project & created project profile page.

External Links

• Detailed Private Browsing Spec (Mozilla)
• Private Browsing (Mozilla)
• Build:TryServer (Mozilla)
• Tinderbox:Tree(MozillaTry) (Mozilla)
• XPCShell Based Unit Tests

Non-Related to project

• AaronMT
• Aaron on Software