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
A little more syntax test besides Unit Test, like:
- malicious multi-byte characters
- especially the ones involving quotes, colons, etc
Needs some check on downloading.
- when the specified fonts were not available.
- when no fonts were installed on the machine (the downloaded fonts should be the only ones you can use in this case)
- font matching algorithm (specified in Section 5 of the spec)
- especially font-weight matching algorithm (specified in Section 5.3.d)
Make sure the downloaded fonts cannot be used from other documents.
- Not from HTML files in other windows
- When two HTML files share same .css files by LINK tag (what'll happen?)
Checks on the rendering
- diacritic marks
- ligature
on various fonts like
- Times, Corsiva
- Multi-byte fonts: MS Mincho, and some other Chinese/Korean fonts
- some Arabic fonts
and make sure to check them on various types like
- OpenType
- TrueType
- SVG (if possible)
Other things to check (not categorized yet)
- Handling 'crashing' fonts
- if those fonts exist
Debug builds are used to:
- Testing of new patches or regression if needed.
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)