You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ These two characters should precede each test line, so that Asar sees them as co
39
39
* 2 hex digits - a byte for it to check for
40
40
* You can specify more than one, like in the examples below, and it will automatically increment the offset.
41
41
* A line starting with `+` tells the testing app to patch the SMW ROM instead of creating a new ROM
42
-
*`errEXXXX` and `warnWXXXX` (where `XXXX` is an ID number) means that the test is expected to throw that specific error or warning while patching. The test will succeed only if the number and order of errors and warnings thrown exactly matches what's specified here. Be wary that Asar uses multiple passes and throws errors and warnings across multiple of them. This can make the actual order in which errors and warnings are thrown a bit unintuitive.
42
+
*`errE{name}` and `warnW{name}` (where `{name}` is the name of an error or warning) means that the test is expected to throw that specific error or warning while patching. The test will succeed only if the number and order of errors and warnings thrown exactly matches what's specified here. Be wary that Asar uses multiple passes and throws errors and warnings across multiple of them. This can make the actual order in which errors and warnings are thrown a bit unintuitive.
43
43
44
44
In addition to the format mentioned above, it's also possible to check for user prints a patch is expected to output (by `print`, `error`, `warn` or `assert` commands). This is done by starting the line with one of the following sequences:
45
45
```
@@ -61,17 +61,17 @@ This line tests that `22`, `20`, `80` and `90` were written to the ROM offset `0
61
61
;`007606 22 20 80 90
62
62
```
63
63
64
-
This line tests that assembling the patch throws error `5117` twice and warning `1030` once.
64
+
This line tests that assembling the patch throws error `Eunknown_command` twice and warning `Wfeature_deprecated` once.
65
65
```
66
-
;`errE5117
67
-
;`errE5117
68
-
;`warnW1030
66
+
;`errEunknown_command
67
+
;`errEunknown_command
68
+
;`warnWfeature_deprecated
69
69
```
70
70
71
-
This line tests that the byte `FF` was written to the start of the ROM, that the string `This is a print.` was printed and that the string `This is a user error.` was output via the error command (which itself also causes error `E5159`to be thrown once).
71
+
This line tests that the byte `FF` was written to the start of the ROM, that the string `This is a print.` was printed and that the string `This is a user error.` was output via the error command (which itself also causes error `Eerror_command`to be thrown once).
0 commit comments