tests: Make $expected_mismatch skip the cardinality check, rather
than consider it an expected failure. With this change, if $expected_region_highlight and $region_highlight coincidentally have the same number of elements, the test won't be considered to fail. This is useful in conjunction with the next commit, q.v.. At this time, no tests set $expected_mismatch explicitly. However, the commit after next (this commit's grandchild) will add a test that will set $expected_mismatch implicitly, using the functionality in the next commit (this commit's child).
This commit is contained in:
@@ -23,8 +23,7 @@ need not match the order in `$region_highlight`.
|
||||
|
||||
Normally, tests fail if `$expected_region_highlight` and `$region_highlight`
|
||||
have different numbers of elements. Tests may set `$expected_mismatch` to an
|
||||
explanation string (like `$todo`) to avoid this and mark the cardinality check
|
||||
as todo.
|
||||
explanation string (like `$todo`) to avoid this and skip the cardinality check.
|
||||
|
||||
**Note**: `$region_highlight` uses the same `"$i $j $style"` syntax but
|
||||
interprets the indexes differently.
|
||||
|
||||
Reference in New Issue
Block a user