You are currently viewing a snapshot of taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to, please file a bug.

Embedding High Level Test Plan

Embedding Project

Written by: Michael Dunn




    2001-02-13 mdunn Draft
    2001-02-28 mdunn Abstracted Out API test detail
    2001-03-07 mdunn Incorporated team feedback
    2001-05-02 mdunn Moved to Mozilla

Product Overview:

    The purpose of the Embedding project is to provide a realistically embeddable GECKO layout engine. The embedding engine can be used to render, display, and manipulate web content. 

    Third Party Applications are expected to embed the GECKO engine and interact with the layout engine via a public set of APIís. 

    The net result of the QA effort will produce a set of deliverables available on and by definition available for external use and expansion.

QA Suite Definition
    The QA burden is to insure that the embeddable layout engine built is fully functional and compliant to browser standards for layout and rendering. 

    We need to insure i18n compliance. 

    We need to insure compatibility with plug-ins. 

    We expect to use a combination of Black Box testing and direct API testing to insure full API test coverage.

QA Deliverables
  • High Level Test Plan
  • Lower Level Component Test Plans (Feature Test Plans)
  • Test Suites for the various functional test areas
  • Documentation of how to execute the test suites and evaluate the results
  • Documentation of how to modify the test suites for regression
  • Documentation of how to add test cases to the test suites to account for new functionality

Value Proposition
    When assembled these test suites will provide any developer with the means to verify that their application that embeds GECKO meets the requisite baseline functional requirements. 

    Developers will be able to qualify their code changes prior to checking-in new source. Developers will have a template and test harness that they can add new functional tests to match any code modification or addition of new functionality.

Test Areas

Test Area Ownership