Changes between Version 36 and Version 37 of Writing Layout Tests for DumpRenderTree

Timestamp:

May 31, 2012 1:55:58 PM (11 years ago)

Author:

jchaffraix@webkit.org

Comment:

Added a section on ref-tests and added more tips on portable text

Writing Layout Tests for DumpRenderTree

@@ -143 +143 @@
 As you can see, we did not need the pixels to get the information. The idea is that in this case, we were testing CSS and not the painting part of WebKit so querying the property directly would give us the result we need without having to dump the pixels.
 
+=== Couldn't you do a ref-test? ===
+
+Most test cases can be easily transformed into ref-tests and it is the preferred way to add new tests. See the dedicated page: [wiki:"Writing Reftests" Layout Tests: Writing Reftests]
+
 === How to write portable pixel tests ===
 
@@ -163 +167 @@
 '''Important note:''' For the 2 last points, the text will still be in the text render tree dump! You can however disable the text dump if you don't need it to achieve maximum portability, see below.
 
-If you test '''really needs to use some fonts''', make sure you use the ''Ahem'' font as it is a very portable font. Make sure to specify the font-height too not to depend on the platform for that (FIXME: not sure if the font-size is really needed but better safe than sorry).
+If you '''really need visible text in your pixel output''', there is a neat trick to make the output pretty cross-platform:
+
+{{{
+html {
+    font: Ahem 10px;
+    -webkit-font-smoothing: none;
+}
+}}}
+
+(It may be possible to not set the font-size but it's better to do it to ensure consistent behavior across platforms)
+
+This ensures that all text in your page uses the Ahem font which renders the same on all platforms. Ahem has other nice properties so make sure you read up about it! Also note that your text will be unreadable so any instructions in the pixel output will be useless.
 
 ==== Native controls ====