Difference between revisions of "Contribute to Private Browsing Tests"

From CDOT Wiki
Jump to: navigation, search
m (→‎September)
m (→‎What to expect for 0.1 release?)
Line 59: Line 59:
  
 
* 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.
 
* 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.
 +
** Places unit test reviewed by Ehsan
 +
** Blogged about it
 +
** Post unit test
 +
** Screenshots
 +
** Submit deliverables
  
 
== Project Notes ==
 
== Project Notes ==

Revision as of 23:50, 3 October 2008

Private Browsing Tests

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:
PbMenu.png StealthBarSmall.jpg

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 (QA)
      • E-Mail: (marcia at mozilla dot org)
    • Clint Talbert (QA Dev Engineer)
      • E-Mail: (ctalbert at mozilla dot com)
      • IRC: ctalbert

Project Description

Milestone 0.1 will contain the History component unit test. Note: Some areas already covered by Ehsan and others working on Bug #248970.

Private Browsing Test Plan

Private Browsing Unit Tests

Project Milestone Information

  • For the first iteration phase, I plan to have complete

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.
    • Places unit test reviewed by Ehsan
    • Blogged about it
    • Post unit test
    • Screenshots
    • Submit deliverables

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)

Project Contributor(s)

Area's where you could contribute to my project

  • (A) You have written an extension before
    • Testing is needed on the private browsing service. If you have written an extension in the past or are going to, it would sweet if you also test the new API found here - Let me know if API calls are working, nothing fancy has to be done, just has to work properly. Send me feedback and I can pass this on back to Mozilla Devs.
  • (B) You have not written an extension before
    • It would be very helpful if you could test out the new private browsing feature, specifically testing out the history component of it.

Should you select (B)

  • Make sure you have an updated trunk build of Mozilla Firefox.
  • Download the newest patch off Bug #248970
  • Install the patch, refer to week 4 lab.
  • Build Firefox.
  • Open Firefox.
  • Follow this test plan:
    • Visit a bunch of websites, ranging from anything in particular.
    • Create a bookmark from one of the sites.
    • Enter private browsing mode Tools -> Private Browsing Mode with a new session.
    • Open your history and visit the same sites, the visit count should not increase (this is visible in History -> Show All History, add the new column).
    • Check if your bookmark has been visited, it should not.
    • Visit new web sites, they should not be added to your history list.
    • Add a bookmark from a new website.
    • Exit private browsing mode.
    • Both bookmarks should still be accessible.
    • Visit the sites in your history again, the visit count should now increase (History -> Show All History).
  • If everything follows according to plan, let me know and I can add your name as a contributor.
  • If there is a problem let me know, I will add your name as a contributor and forward the problem to the Bug #248970.

Project Details

Bugs associated with Bug #248970

  • Depends On
    • Bug #456884 - Provide a way to open a link to Private Browsing Mode
    • Bug #457110 - Support in-memory DB for the downloads manager back-end
  • Blocker
    • Bug #454792 - Should safe browsing code react to private browsing mode?

History Unit Test Notes

  • AaronMT 00:41, 27 September 2008 (UTC)
    • Using a Mozilla function that checks to see if a URI exists in a database.
test_248970_history - uri_in_DB(URI) 
/**
 * Checks to see that a URI is in the database.
 *
 * @param aURI
 *        The URI to check.
 * @returns true if the URI is in the DB, false otherwise.
 */
function uri_in_db(aURI) {
  var options = histsvc.getNewQueryOptions();
  options.maxResults = 1;
  options.resultType = options.RESULTS_AS_URI
  var query = histsvc.getNewQuery();
  query.uri = aURI;
  var result = histsvc.executeQuery(query, options);
  var root = result.root;
  root.containerOpen = true;
  return (root.childCount == 1);
}
  • AaronMT 23:45, 26 September 2008 (UTC)
    • Wrote a new function that creates a handful of history items with various visit types.
test_248970_history - fill_history() 
var dayLabels = 
[ 
  "Today", 
  "Yesterday", 
  "2 days ago", 
  "3 days ago",
  "4 days ago",
  "5 days ago",
  "6 days ago",
  "Older than 6 days"
];
/**
 * 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

My Weekly TODO for September
  • Week of October 6th,
    • Goal is to have my places unit test reviewed by Ehsan, ready to go and onwards to the next area of testing
  • 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

September

  • AaronMT 04:44, 4 October 2008 (UTC)
    • Completed the places unit test.
      • Submitted to Ehsan @ Mozilla for review
  • AaronMT 21:06, 29 September 2008 (UTC)
    • Spoke with Ehsan over email about nsINavHistoryService object querying using higher level API over lower level SQL.
    • Wrote function that compares a bookmark's visit count during private browsing mode. Being analyzed by Ehsan.
  • 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
  • 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

Non-Related to project

Other

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Contribute_to_Private_Browsing_Tests&oldid=18737"