From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] nosleep 0.1.3-1 (needs GTG)
Date: Fri, 30 Sep 2011 19:57:00 -0000 [thread overview]
Message-ID: <hm6c87pqrior4g2f7ftb8rg6qla87c9d7u@4ax.com> (raw)
In-Reply-To: <CAHiT=DFE4XBj5cn+qgDwdinUkXSo2okxYD3gFnm4f=yKdR4sKw@mail.gmail.com>
> I would like to see a test with simple command lines without checking
> the nosleep behavior. Just to check if can correctly pass the command
> with options with proper quoting.
OK, this is a good idea. It's a first functional test. So I created a new
release upstream, 0.1.4, containing a new test directory and a 'make test'
target that runs all of the scripts there.
At present there's one test. It runs a helper script that just prints the
number and content of its command line arguments. The test runs the helper
with some command line arguments:
helper/args.sh arg1 --arg2 - "arg 4"
It runs that with and without nosleep, compares the results, and fails
noisily if they're different.
'cygport nosleep-0.1.4-1 test' now runs the functional tests from upstream,
specifically the argument check. It succeeds for me.
Thanks for the suggestion.
Andrew.
prev parent reply other threads:[~2011-09-30 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 10:15 [ITP] nosleep 0.1.3-1 Andrew Schulman
2011-09-27 18:33 ` Christopher Faylor
2011-09-27 19:05 ` Reini Urban
2011-09-27 19:18 ` Charles Wilson
2011-09-28 13:53 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-09-28 16:27 ` Andrew Schulman
2011-10-09 19:46 ` Reini Urban
2011-10-11 15:02 ` Andrew Schulman
2011-09-27 21:16 ` Chris Sutcliffe
2011-09-28 15:31 ` Christian Franke
2011-09-30 10:01 ` [ITP] nosleep 0.1.3-1 (needs GTG) Andrew Schulman
2011-09-30 14:00 ` Charles Wilson
2011-09-30 15:57 ` Andrew Schulman
2011-09-30 17:13 ` Reini Urban
2011-09-30 19:57 ` Andrew Schulman [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=hm6c87pqrior4g2f7ftb8rg6qla87c9d7u@4ax.com \
--to=schulman.andrew@epamail.epa.gov \
--cc=cygwin-apps@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).