expected ouput is used as a regexp pattern. If an ouput specification
contains characters (e.g, ()), tests fail even if the spec matches
the output character by character.
multiline output make the TSV files very hard to work with, because a
record expands more than one row. Excel does not read it, and using an
editor is unintuitive because the columns are missaligned.
AFTER:
the expected output is run through re.escape() before searching. This
behaviour is avoided if the specification is enclosed by forward slashes.
This can break backward compatibility for users that rely on the
undocumented fact that the the output specification was treated as a regexp
pattern instead of as a string
multiline output specifications can use <br> instead of line breaks.
Output specifications with line breaks are still properly processed.
The test reports use <br> use instead of line breaks.
BEFORE:
()), tests fail even if the spec matches the output character by character.AFTER:
<br>instead of line breaks. Output specifications with line breaks are still properly processed. The test reports use<br>use instead of line breaks.DCO 1.1 Signed-off-by: Xavier Vergés xverges@gmail.com