Personal tools

QA/Firefox 3.next/TestPlan:Direct2D

From MozillaWiki

< QA
Jump to: navigation, search

Contents

Direct2D

Area Details
Development Status: In progress, currently not enabled by default
Feature Testing: In progress (planning)
Team: Developer: jdrew, bas, QA: marcia
Tracking Bugs Bug bug 549116 - Enable Direct2D by default

Feature Description

Direct2D is designed as a replacement for GDI and functions as a vector graphics rendering engine, using GPU acceleration to give large performance boosts to transformations and blending operations.

How to Enable D2D

  1. Enter 'about:config'
  2. Click through the warning, if necessary
  3. Enter gfx.font in the 'Filter' box
  4. Double-click on 'gfx.font_rendering.directwrite.enabled' to set it to true
  5. Below this, right click and select New > Integer to add a pref setting
  6. Enter 'mozilla.widget.render-mode' for the preference name, 6 for the value
  7. Restart

Feature Release Readiness Assessment

The table below provides a top level go/no go assessment of whether the feature is release ready for the given milestone.

Milestone Assessment
#Beta1 N/A
#Beta2 N/A
#Beta3 N/A
#Beta4 N/A
#Beta5 On by default on Windows

top

Feature Documentation

Item Description Status
#Project_Wiki Wiki Links to all feature related entries
#Developer_Links (blogs) Developer links to feature related sites
#Other_Docs Web links to feature related sites
#Developer_QA_Review Details from developer and qa discussions regarding feature test strategies and issues.

top

Feature Bug Management

Item Description Status
#Bug_Tracking Top level bugs tracking feature
#Bug_Verification Feature bugs that need verification
#Bug_Triage Links triage bug tasks

top

Feature Test Items

The table below provides a breakdown of all feature items that should be covered and how they will be tested. Not all items will be covered by internal QA team members. It is important to list what should be covered. If it is not covered, list it as not covered.

Note: not all items listed below will apply for a given feature

Test Item Description Covered By Status
Item 1 Item 1 Description Developer Tests
Item 2 Item 2 Description Beta tester exposure
#Localization Feature localization
#Accessibility Feature accessibility
#Plugins Plugins compatibility
#Addons Addons compatibility
#Topsites Top internet sites compatibilities

top


Feature Tests

Automated Tests

Item Description Status
#Developer_Tests Links to automated developer tests
#Mozmill_Tests Links to automated mozmill feature test cases

Manual Tests

Item Description Status
#Smoke_Tests link to smoke tests
#Regression_Tests link to BFT and/or regression tests
#Functional_Tests link to FFT and/or complete functional tests

top

Community Test Events

Item Description Status
#Testdays Links to test day event results for feature
#Bugdays Links to bug day event results for feature
#Meetups Links to Meetup events for feature

top

Feature Documentation Details

Project Wiki

  • Provide link to all project related wikis

top

Developer Links

top

Other Docs

top

Developer QA Review

The QA person responsible for the feature should hold a formal interview with the lead developer or feature champion. Below are questions that should be asked in the interview:

  • Do we have automated tests for the feature?
  • What do they cover?
  • What do they not cover?
  • How well do they cover the feature?
  • What are the important areas we should focus on?
  • What are the dependencies?
  • What is our comfort level with this feature in its current state?
  • What feedback would you like from QA?

top

Feature Release Readiness Assessment Details

Beta1

Beta2

Beta3

Feature Bug Management Details

Bug Tracking

  • Top level bugs tracking feature. Include any relevant bug queries that are helpful for tracking feature status.
Query Name Description
bugzilla query url link query description

top

  • Tracking Bugs for Drivers
    • 605780 tracking bug of crashes with ATI cards
    • 605749 tracking bug of crashes with NVIDIA cards
    • 605779 tracking bug of crashes with Intel cards
    • 605781 tracking bug of crashes with S3 graphics cards

Bug Verification

  • Feature bugs that need verification

top

Bug Triage

  • Bug triage information

top

Feature Test Items Details

Localization

  • Details of feature localization test requirements

top

Accessibility

  • Details of feature accessibility test requirements

top

Plugins

  • Details of plugins compatibility test requirements

top

Addons

  • Details of addons compatibility

top

Topsites

  • Details of top internet sites test requirements

top

Feature Tests Details

Automated Tests Details

Developer Tests

  • Links to automated developer tests

top

Mozmill Tests

If a particular feature needs manual tests which should also be covered by Mozmill tests please add the "[mozmill-test-needed]" whiteboard entry to the feature implementation or regression bug.

List of Mozmill Tests:

  • Links to automated mozmill feature test cases

top

Manual Tests Details

  • Enabling the feature
    • Go to about:config
    • Click through the warning, if necessary
    • Enter 'render' in the 'Filter' box
    • Double-click on 'gfx.font_rendering.directwrite.enabled' to set it to true
    • Double click on 'mozilla.widget.render-mode', set the value to 6
    • Restart
  • Manual Tests
    • Flickering, shadowing, or graphic artifacts when doing things like scrolling, switching between multiple tabs, and playing videos. Like Grafx Bot, ideally these kinds of manual tests should be run on as many different hardware combinations as possible, so maybe they'd be good to combine with Grafx Bot in a testday.

Demoing Direct2D

Smoke_Tests

  • links to litmus smoke tests or description

top

Regression_Tests

  • links to litmus BFT and/or regression tests description

top

Functional_Tests

  • links to litmus FFT and/or complete functional tests description

top

Community Test Events Details

Testdays

Bugdays

  • Links to bug day event results for feature

Meetups

  • Links to Meetup events for feature