From: Marc Chantreux <eiro@phear.org>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
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 [thread overview]
Message-ID: <20180629061524.GA17197@prometheus.u-strasbg.fr> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2018-06-29 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 12:51 Sebastian Gniazdowski
2018-06-29 6:15 ` Marc Chantreux [this message]
2018-06-29 17:22 ` Daniel Shahaf
2018-06-29 17:52 ` Marc Chantreux
2018-06-29 18:04 ` Jérémie Roquet
2018-06-29 18:04 ` Daniel Shahaf
2018-06-29 18:57 ` Marc Chantreux
2018-06-29 18:39 ` Sebastian Gniazdowski
2018-06-29 18:58 ` Bart Schaefer
2018-06-29 20:38 ` Sebastian Gniazdowski
2018-07-13 12:02 ` Sebastian Gniazdowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180629061524.GA17197@prometheus.u-strasbg.fr \
--to=eiro@phear.org \
--cc=sgniazdowski@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).