QA/Firefox3.5/CSS Transform Testplan: Difference between revisions
< QA | Firefox3.5
Jump to navigation
Jump to search
(New page: <small>« QA/Firefox3.1/TestPlan</small> ;CSS Transform Testplan = Overview = = Test Strategy = = Schedule Scoping = = References =) |
No edit summary |
||
Line 4: | Line 4: | ||
= Overview = | = Overview = | ||
We are implementing 2d transforms for content in web pages. I don't think we are doing 3d transforms yet. | |||
= Test Strategy = | = Test Strategy = | ||
== Things we should do == | |||
* There are quite a few reftests being applied with the patch. Need to talk with Keith to see if these are enough and if there are more sanity "does it work" reftest patches needed. | |||
* Test that multiple applied transforms equate to a sequentially applied transform | |||
* Test invalid measurements | |||
* Test invalid inputs | |||
* Test DOM interfaces that this exposes - it doesn't seem the reftests do that. | |||
* Test this with other embedded content and be sure the other content is (and is not) transformed as specified. | |||
* Test with various types of :fixed, :relative elements on the page | |||
== Things we'd like to do == | |||
* Test applying these tranforms to SVG elements, as per the spec, see if it works | |||
* Test how many of these transforms you can apply to one element | |||
* Test handing these transformations off to DOM Threads | |||
* Test with transparent images and backgrounds | |||
= Schedule Scoping = | = Schedule Scoping = | ||
* Writing these tests will take about 3 days, because verifying that the transform is correct and coming up with the proper reference image will be a bit of a pain. | |||
= References = | = References = | ||
* The webkit browsers have a good share of these implemented (Google Chrome & safari) | |||
* [https://wiki.mozilla.org/Firefox3.1/CSS_Transforms_Security_Review Security Review] |
Revision as of 03:27, 5 September 2008
- CSS Transform Testplan
Overview
We are implementing 2d transforms for content in web pages. I don't think we are doing 3d transforms yet.
Test Strategy
Things we should do
- There are quite a few reftests being applied with the patch. Need to talk with Keith to see if these are enough and if there are more sanity "does it work" reftest patches needed.
- Test that multiple applied transforms equate to a sequentially applied transform
- Test invalid measurements
- Test invalid inputs
- Test DOM interfaces that this exposes - it doesn't seem the reftests do that.
- Test this with other embedded content and be sure the other content is (and is not) transformed as specified.
- Test with various types of :fixed, :relative elements on the page
Things we'd like to do
- Test applying these tranforms to SVG elements, as per the spec, see if it works
- Test how many of these transforms you can apply to one element
- Test handing these transformations off to DOM Threads
- Test with transparent images and backgrounds
Schedule Scoping
- Writing these tests will take about 3 days, because verifying that the transform is correct and coming up with the proper reference image will be a bit of a pain.
References
- The webkit browsers have a good share of these implemented (Google Chrome & safari)
- Security Review