@@ -192,7 +192,7 @@ They have several forms, but generally are a comment with the diagnostic level
192
192
to write out the entire message, just make sure to include the important part of
193
193
the message to make it self-documenting.
194
194
195
- The error annotation needs to match with the line of the diagnostic. There are
195
+ Most error annotations need to match with the line of the diagnostic. There are
196
196
several ways to match the message with the line (see the examples below):
197
197
198
198
* ` ~ ` : Associates the error level and message with the * current* line
@@ -205,9 +205,6 @@ several ways to match the message with the line (see the examples below):
205
205
* ` ~v ` : Associates the error level and message with the * next* error
206
206
annotation line. Each symbol (` v ` ) that you add adds a line to this, so ` ~vvv `
207
207
is three lines below the error annotation line.
208
- * ` ~? ` : Used to match error levels and messages with errors not having line
209
- information. These can be placed on any line in the test file, but are
210
- conventionally placed at the end.
211
208
212
209
Example:
213
210
@@ -222,6 +219,10 @@ The space character between `//~` (or other variants) and the subsequent text is
222
219
negligible (i.e. there is no semantic difference between ` //~ ERROR ` and
223
220
` //~ERROR ` although the former is more common in the codebase).
224
221
222
+ ` ~? ` is used to match error levels and messages with errors not having line
223
+ information. These can be placed on any line in the test file, but are
224
+ conventionally placed at the end.
225
+
225
226
### Error annotation examples
226
227
227
228
Here are examples of error annotations on different lines of UI test source.
0 commit comments