= Associating Information with Tests = There are currently a few ways to associate information about a test with the test itself. 1. You can describe which tests are expected to pass or fail for which ports using the TestExpectations file. These files are in LayoutTests/platform/*/TestExpectations, and each line describes one expected test result. If there is no line in TestExpectations for a particular test, is is expected to pass. The syntax of each line is: webkit.org/b/?????? [ OS ] path/to/test.html [ ExpectedResult ] One (somewhat) real example is: webkit.org/b/148119 [ Mavericks Yosemite ] fast/text/trak-optimizeLegibility.html [ Pass Failure ] which means that on Mavericks and Yosemite, fast/text/trak-optimizeLegibility.html is expected to either pass or fail. Keep in mind that “Failure” means “text failure.” If the test is a reference test, and you expect it to fail, use the keyword ImageOnlyFailure. 2. Another way to associate information is using a non-declarative mechanism: the JavaScript “window.internals” object. For example, if you want to say that your test should be paginated, you can say the following in a