Zsh Mailing List Archive
Messages sorted by:
Re: "make check" suggestion
- X-seq: zsh-workers 47692
- From: Felipe Contreras <felipe.contreras@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: "make check" suggestion
- Date: Sat, 28 Nov 2020 04:31:46 -0600
- Archived-at: <https://zsh.org/workers/47692>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2020-11/CAMP44s0UDMz%3DkSgpUVJ5HtU8d2_Mmnb%3D%3D%3DdMUgqAJ%2BmE%2B%2BGfHg%40mail.gmail.com>
- Authentication-results: zsh.org; iprev=pass (mail-wr1-f54.google.com) smtp.remote-ip=220.127.116.11; dkim=pass header.d=gmail.com header.s=20161025 header.a=rsa-sha256; dmarc=pass header.from=gmail.com; arc=none
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LRiCb97DnA+eBMlSdtTR414tmlvOWjjV7Pr8uUN3kTE=; b=uCSbr0+1HK2RqESfyuZUV5XaRTqM0uYR55yfHiCr7RU+cO1uThm+r3uCE/nL4O3wTJ ury8VeAxNxGc44LZjr7kRMWjiYuBSsDPxhZRIaPRBJbO1sC7rk3feWxA7S0jZc1m5toy HesDwYFYTGdS819Pw54zMsRrpbxMv92vxzDvEJafoJSeQ96bpCN3N3ZhGVQqkUSVZmZL yQCs/jHv6HEYUueGwMPXav1eAsJKS5xta9zOM/5BN1425pyrTHxyNjmLrbCo+TECPkWz I5VAYRU5pYO4JF5JPbknQ6aWIbORtPkgdAsi8CkJ4G+Cw/1tsrOS20y1isho9NKCupnS IqAg==
- In-reply-to: <CAH+w=7YxWQY+WCX+SMC-R-n0u+JE1Ty9iCmEp6oyz9Ba_Xewqw@mail.gmail.com>
- List-archive: <http://www.zsh.org/sympa/arc/zsh-workers>
- List-help: <mailto:email@example.com?subject=help>
- List-id: <zsh-workers.zsh.org>
- List-owner: <mailto:firstname.lastname@example.org>
- List-post: <mailto:email@example.com>
- List-subscribe: <mailto:firstname.lastname@example.org?subject=subscribe%20zsh-workers>
- List-unsubscribe: <mailto:email@example.com?subject=unsubscribe%20zsh-workers>
- References: <CAH+w=7YxWQY+WCX+SMC-R-n0u+JE1Ty9iCmEp6oyz9Ba_Xewqw@mail.gmail.com>
- Sender: zsh-workers-request@xxxxxxx
On Sat, Nov 28, 2020 at 12:53 AM Bart Schaefer
> I haven't messed around with ztst.zsh for some years, so I'm not
> familiar with how the newer features like intentionally failed tests
> are handled. A suggestion perhaps for someone who has worked on it
> more recently:
> It might be nice to have a mode in which ALL the tests in each file
> are run, rather than abort the whole test file when one of them fails
> (or unexpectedly succeeds).
Coming from Git, I have to say their testing framework is the best
I've ever seen.
It is developed in shell. There may be some bashisms, but they try to
avoid them. Last time I tried it in zsh, it didn't work correctly, but
shouldn't be too hard to fix (and maybe it was a problem in zsh), and
I'm sure they would accept the patches.
The project that tried to extirpate the test system from git.git is
called sharness . I've used it in all my projects, and it works
like a charm.
In this test system all you have to do is pass -i to the test, to stop
at a failure.
Additionally, the system supports Perl's Test Anything Protocol (TAP) .
So you can do:
prove completion-zsh.t :: -i
That's how I developed the git-completion zsh specific tests, which
work great, and are integrated into Travis-CI .
If anyone is interested, I could give it a try to port some zsh test
In my personal opinion the testing system of zsh is far from ideal.
But that's just my opinion.
Messages sorted by: