| Y |
Yes |
All parts of the test passed completely. |
+20 |
| Yb |
Yes, but with minor bugs |
Same as Y but with some small, probably unrelated, bug(s). For example, a rendering error that disappears when the window is invalidated (causing a reflow). |
+15 |
| U |
Untestable |
The test is irrelevant (untestable) because no effort at supporting the relevant specification is made. For example, Lynx is marked U for any CSS tests, since it does not have CSS support. Note that this is rewarded, rather than penalised. This is because it is considerably better to not implement a specification at all, rather than implementing it wrongly. |
+10 |
| P |
Partial |
Minor errors mean that the test did not pass completely, but it is very close otherwise. Think of this as a "Y-". Only some minor tweaks to the code would be enough to change this into a Y. |
+5 |
| M |
Maybe |
The correct behaviour was exhibited, but this may be because of a fundamental failure rather than correct standards support. For example, stylesheet linked with media=tty should be skipped, but it might also be skipped because the link method used is not supported at all. Tests that can result in M are always related to other ones, if all related tests are Y or Yb then an M result is switched to a Y. |
+3 |
| A |
Arguable |
The result is arguably correct, but only if the person arguing is the devil's advocate. The behaviour is technically correct, but it isn't what I would suggest. This is usually due to vagueness in the specifications. |
0 |
| N |
No |
Test failed, indicating lack of support for specifications. This means that the browser does nothing at all. This is not possible for mandatory features, such as collapsing P elements in HTML (in those cases, lack of support is a bug). This is not penalised, since as there is no bug, the feature can still be used, without fear that it will break in the browser. |
0 |
| B |
Buggy |
Test failed indicating non-conformance to the specifications. This means that the browser does something wrong. Note that the weighting of the scores are based on the principle that it is much better to not support a specification, rather that supporting it only half heartedly (failing half the relevant tests). |
-30 |
| D |
Destroys |
The browser is sooo buggy that it destroys pages that use that feature. This is heavily penalised as it would be better to have not shipped the browser with 'support' for the relevant specification at all, rather than shipped with bugs as serious as this. |
-60 |
| C |
Crash |
The browser either crashes completely, or freezes, or does some other equally horrendous thing. |
-90 |
