Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: A suggestion RE Xfail tests
- X-seq: zsh-workers 50173
- From: "Daniel Shahaf" <d.s@xxxxxxxxxxxxxxxxxx>
- To: "Zsh hackers list" <zsh-workers@xxxxxxx>
- Subject: Re: A suggestion RE Xfail tests
- Date: Wed, 04 May 2022 02:52:01 +0000
- Archived-at: <https://zsh.org/workers/50173>
- In-reply-to: <CAH+w=7YOn6fqxUVhCO_oi6pbCwr+o9t-90p_tzhSkCUvKdqggg@mail.gmail.com>
- List-id: <zsh-workers.zsh.org>
- References: <CAH+w=7YOn6fqxUVhCO_oi6pbCwr+o9t-90p_tzhSkCUvKdqggg@mail.gmail.com>
Bart Schaefer wrote on Wed, 04 May 2022 01:44 +00:00:
> It would be helpful if tests that are expected to fail could list both
> the expected "correct" result (that is, the result if the test were to
> succeed, which would cause the Xfail test to fail) and the expected
> "wrong" output ... so that if the way a test goes wrong changes, that
> too can be seen.
>
Fair request.
FWIW, I don't know of any other test harness that supports this.
> Yes, this can be done now by repeating the test twice, once as an
> xfail and once as a regular test but with the "broken" result ... but
> it might be easier to keep track of if it were all in one place.
>
How about if, for the time being, we use the "duplicate the test"
approach, with F: lines or comments as needed? Once we have some
experience with that, we may have a better idea of what test harness
functionality to implement.
> (No action on this expected pre-5.9-release, just musing.)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author