QA/Firefox3.5/FontFace TestPlan
Notes
- A possible crash vector: http://cg.scs.carleton.ca/~luc/opentypecrash.html
Feature <abc> Test Plan
Overview
(Provide an abstract of the feature and the test strategy. Are there particular challenges with testing this feature?)
Current Test Status: QA/Firefox3.1/FontFace TestStatus
Scope of planned testing
Tests are executed to check the properties of @font-face. In summary, @font-face download fonts from the designated sources and assigns it to a font-family name. These fonts can be accessed by using the font-family name written above. Note that the downloaded fonts are available from the document they are referenced. They are not available from other applications or other documents.
Platform and Configurations
- Tests are executed on following operating systems
- Mac OS X
- Windows XP Professional SP 3
- Ubuntu 8.04
Major Test Areas
Combination Tests
| Font Face | serif, sans-serif, cursive, Asian, Arabic |
| Font Format | TrueType, OpenType, TrueType-AAT(Apple Advanced Typography), EOT(Microsoft Embedded OpenType) |
| Source | url, local |
| File Encoding | Western, UTF-8, Shift_JIS, and other language-specific encodings |
Syntax of font name. We need to check:
- if it can handle malicious multi-byte code
- how it works on font with multiple names (ex. MS Mincho & MS 明朝)
Font Source(src). We need to check:
- Fallback function when font is not available
- when designated src was invalid
- when designated src was valid, but the font format was unacceptable
- when the string assigned to format descriptor does not correspond to the actual format
Rules. We need to check the behavior:
- when multiple @font-face rules was in a single file
- when multiple font face was assigned to a single font-family by @font-face
- font matching algorithm (font-weight, font-style, font-stretch)
- how CSS marksups and HTML tags affect
Other things to be checked are:
- Make sure downloaded fonts cannnot be used from other documents
- Handling of 'crashing' fonts
- if those fonts exist
- Copy & Paste test
- Printing Test
Debug builds are used to:
- Testing of new patches or regression if needed.
Testcases will be mainly created in reftest
Schedule/milestones
( Provide some breakdown of the major areas of the feature, how long it will take to develop or run the tests, and an approximate time this will be done.
References
(List useful links to the bug containing design info, feature meeting notes, wiki info, standards info, litmus group or subgroup, etc)