Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Anyone wants to join Zsh-Suite project, tools with integrations for Zsh software development
- X-seq: zsh-users 23518
- From: Marc Chantreux <eiro@xxxxxxxxx>
- To: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- Subject: Re: Anyone wants to join Zsh-Suite project, tools with integrations for Zsh software development
- Date: Fri, 29 Jun 2018 08:15:24 +0200
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-filter: OpenDKIM Filter v2.10.3 aurora-borealis.phear.org 9F9B310AB9
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=phear.org; s=20180217; t=1530252926; bh=QFIIkdkv9hh8HDcyFyvyyv9g+/W+l+0b2tsNA6uAWMQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=T/HgaT/6+QUyWsKkleNCS8NQ6ui5QJRiOBeFtPakPc/buhmbql3sdZ1M4R0XC7Qfl PQNtL4jPu6oBTjeX1HhKiUqu8hj5n9UWr07j43DNnbS5nyeqkKrkGTTQqiM2fnhT7U hf/LlQy2wL9lg/h495l06dT8q0O+WtySU8RzPtzaDfF1jO7cwCWGbyLLHIfhZnJNew I+rBmk9kXiMW1+d5aSAMcK6j5Zw9Bt2nbOw5QSUuDaqsPozVj0qDilMUnNAhblW5Rv Ok2eyTaALYCA5vSzFlEg0oyYzBzXRNavizpVZQpBWcBcntCsy2M2FXeyLfYvE/Sa0h puCUclcFKG2Dg==
- In-reply-to: <CAKc7PVA9a3MQk7AxFnXH6cDVL3xdX4fCeKMP4Qf6Sppb5hgW6Q@mail.gmail.com>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- List-unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVA9a3MQk7AxFnXH6cDVL3xdX4fCeKMP4Qf6Sppb5hgW6Q@mail.gmail.com>
hello Sebastian,
> Has anyone a testing framework or other project that could
> be part of a "zsh-suite"
i don't know what are the crietia to be a part of zsh-suite.
for the uze project, i wrote a TAP (https://testanything.org/)
emiter inspired by Test::More ().
but everything is written using the uze convention and helpers.
i would be pleased to be part of a larger project but i'm really
bound to some "good practices" i developped over years. for example
uze use those options and i'm not open to discussion about
it (because reliability and readability).
braceccl extendedglob globstarshort
rcquotes promptbang promptsubst
nohashdirs pathdirs
nounset warncreateglobal
pipefail shinstdin
also: i use "alternative syntax" as a first choice and really encourage
it
Back to TAP.zsh
the idea behind that is to have a simple implemetation to
give me the ability to reuse all the tooling already written
for TAP and JUnit (because there is a converter).
here is an exemple of test suite
https://github.com/zsh-uze/http-tools/blob/master/t/100_json.t
if you clone the repo and zsh is already installed, you
can have a test report using
prove -ezsh -r t
prove comes with perl, it has a lot of plugin
(html reports for example)
at some point, i also would like to hack on ztst.zsh to give
it a TAP output.
> I have Zshelldoc
for the moment, i use inline pod strings
: <<=cut
=head1 why?
this is cool because i can just run
perldoc my/zsh/lib.zsh
to have a manpage
=cut
but i'm not bound to this.
regards
Messages sorted by:
Reverse Date,
Date,
Thread,
Author