Created a separate test page for gpu rasterization.

Created a separate test page for gpu rasterization.

The new test page uses the viewport tag which makes it easy to sample
pixels from the screenshot. Adding the viewport tag to pixel_css3d page
which is also used for pixel tests because it starts to fail due to
unknown reasons on random bots.

BUG=368495
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274469

[Ken Russell (switch to Gerrit), 2014-06-02 23:20:14]

lgtm

https://codereview.chromium.org/302003015/diff/1/content/test/gpu/page_sets/g...
File content/test/gpu/page_sets/gpu_rasterization_tests.py (right):

https://codereview.chromium.org/302003015/diff/1/content/test/gpu/page_sets/g...
content/test/gpu/page_sets/gpu_rasterization_tests.py:14:
url='file://../../data/gpu/pixel_background.html',
I'd suggest "pixel_blue_box.html" as a more descriptive name of this page.

[alokp, 2014-06-02 23:44:03]

https://codereview.chromium.org/302003015/diff/1/content/test/gpu/page_sets/g...
File content/test/gpu/page_sets/gpu_rasterization_tests.py (right):

https://codereview.chromium.org/302003015/diff/1/content/test/gpu/page_sets/g...
content/test/gpu/page_sets/gpu_rasterization_tests.py:14:
url='file://../../data/gpu/pixel_background.html',
On 2014/06/02 23:20:14, Ken Russell wrote:
> I'd suggest "pixel_blue_box.html" as a more descriptive name of this page.

The naming convention used in data/gpu directory seem to use html features
rather than the content.

[alokp, 2014-06-02 23:45:54]

The CQ bit was checked by alokp@chromium.org

[commit-bot: I haz the power, 2014-06-02 23:47:34]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/alokp@chromium.org/302003015/1

[commit-bot: I haz the power, 2014-06-03 11:54:22]

Change committed as 274469