The test filename is significant in determining the type of test it contains, and enabling specific optional features. This page documents the various flags available 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
- Indicates that a file is a visual test.
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 multiple scopes.
- Indicates that a test makes assertions about optional behavior in a specification, typically marked by the RFC 2119 “MAY” or “OPTIONAL” keywords. This flag should not be used for “SHOULD”; such requirements can be tested with regular tests, like “MUST”.
- Indicates that a test makes assertions not yet required by any specification, or in contradiction to some specification. This is useful when implementation experience is needed to inform the specification. It should be apparent in context why the test is tentative and what needs to be resolved to make it non-tentative.