The test filename is significant in determining the type of test it contains, and enabling specific optional features. This page documents the various flags avaiable and their meaning.
These flags must be the last element in the filename before the
foo-manual.html will indicate a manual test, but
foo-manual-other.html will not. Unlike test features, test types
are mutually exclusive.
Indicates that a test is a non-automated test.
Indicates that a file is not a test but a support file. Not required for files in a directory called `resources`, `tools` or `support`.
Indicates that a file is a visual test. </dl> ### Test Features These flags are preceded by a `.` in the filename, and must themselves precede any test type flag, but are otherwise unordered.
Indicates that a test is loaded over HTTPS.
Indicates that a test uses the server-side substitution feature.
(js files only) Indicates that the file generates a test in which it is run in a Window environment.
(js files only) Indicates that the file generates a test in which it is run in a dedicated worker environment.
(js files only) Indicates that the file generates tests in which it is run in Window and dedicated worker environments. </dl>