From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: MicoJade <micojade@hotmail.com>, <zsh-workers@sunsite.dk>
Subject: Re: Please help: How to test/hack Zsh and find bugs?
Date: Wed, 23 Jul 2008 22:57:05 +0100 [thread overview]
Message-ID: <20080723225705.2179783c@pws-pc> (raw)
In-Reply-To: <BAY131-W493592054B330DA3488FF3CD840@phx.gbl>
On Wed, 23 Jul 2008 16:50:08 +0000
MicoJade <micojade@hotmail.com> wrote:
> I want to know how does a developer(say a Zsh application developer
> who actually works on Zsh or port Zsh) do testing for Zsh either by
> unit design testing, or hack testing for a Zsh release before it
> finally is released?
>
> Are there any classical test cases that we can use to do the testing
> for the Zsh and find bugs for Zsh or the ported Zsh on specific OS
> platform?
You should find that the test suite in the Test subdirectory of the
zsh distribution is a good starting point. If those are passing, there
can't be much wrong. There main gap in the coverage is purely
interactive features such as job control.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
prev parent reply other threads:[~2008-07-23 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 16:50 MicoJade
2008-07-23 21:57 ` Peter Stephenson [this message]
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=20080723225705.2179783c@pws-pc \
--to=p.w.stephenson@ntlworld.com \
--cc=micojade@hotmail.com \
--cc=zsh-workers@sunsite.dk \
/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).