QA/Firefox3.5/DOMWorkerThreads TestPlan: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.5
Jump to navigation Jump to search
(DOM Worker Threads Test Plan)
 
 
(5 intermediate revisions by 2 users not shown)
Line 17: Line 17:
* Running the [http://mxr.mozilla.org/mozilla-central/source/dom/src/threads/test/ Mochikit tests]
* Running the [http://mxr.mozilla.org/mozilla-central/source/dom/src/threads/test/ Mochikit tests]
* Example code
* Example code
* Performance comparisons
* Performance comparisons, Matthew Russel's Vector Graph Code
* Automated test cases
* Automated test cases


Line 26: Line 26:
= References =
= References =


[https://wiki.mozilla.org/DOMWorkerThreads Original Proposal]
* [https://wiki.mozilla.org/DOMWorkerThreads_current Current Wiki Page]
[http://ejohn.org/apps/threads/ John Resigs Working Example]
* [https://wiki.mozilla.org/DOMWorkerThreads Original Proposal]
* [http://ejohn.org/apps/threads/ John Resigs Working Example]
* [http://www.whatwg.org/specs/web-workers/current-work/ Web Workers Spec]
* [http://developer.mozilla.org/web-tech/2008/09/04/web-workers-part-1/ Draft Docs on MDC]

Latest revision as of 03:57, 24 March 2009

Feature DOM Worker Threads Test Plan

Overview

Currently, everything is on one UI thread and this affects performance of the browser. DOM Worker Threads allows the developer to break up processing into multiple threads in order to increase this performance and take strain off of the UI thread.

We need to test message passing, error passing, timeouts/intervals, security, scoping, interaction with the platform are all bug free.

Bugs:

Test Strategy

Test coverage consists of:

  • Verifying the above bugs and regression-testing affected areas
  • Running the Mochikit tests
  • Example code
  • Performance comparisons, Matthew Russel's Vector Graph Code
  • Automated test cases

Schedule Scoping

Running all of the above should take the better part of a day to thoroughly ensure validation.

References