Your message dated Sat, 1 Nov 2014 17:02:07 +0200
with message-id <[email protected]>
and subject line Re: Bug#759035: cmdtest: better error messages
has caused the Debian Bug report #759035,
regarding cmdtest: better error messages
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
759035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759035
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cmdtest
Version: 0.12-1
Severity: wishlist

Thank you for writing/packaging cmdtest.

If you follow the echo test example from the cmdtest manpage, but
forget to make echo-tests/hello.script executable, you get the
following error message:

$ cmdtest echo-tests
test 1/1: ERROR: Permission denied

The message isn't very helpful, it doesn't you what cmdtest was trying
to do when the error occured, or the name of the test involved.

It's important to be able to distinguish between the case were cmdtest
wasn't able to run a test, and a test failure.

--- End Message ---
--- Begin Message ---
On Sat, Aug 23, 2014 at 08:51:49AM -0400, Daniel Murphy wrote:
> Package: cmdtest
> Version: 0.12-1
> Severity: wishlist
> 
> Thank you for writing/packaging cmdtest.
> 
> If you follow the echo test example from the cmdtest manpage, but
> forget to make echo-tests/hello.script executable, you get the
> following error message:
> 
> $ cmdtest echo-tests
> test 1/1: ERROR: Permission denied
> 
> The message isn't very helpful, it doesn't you what cmdtest was trying
> to do when the error occured, or the name of the test involved.
> 
> It's important to be able to distinguish between the case were cmdtest
> wasn't able to run a test, and a test failure.

Hi, Daniel,

thank you for the suggestion. You're right, cmdtest should show better
error messages. However, I recommend that you don't use cmdtest
anymore. I've found that its design results in test suites that are
hard to understand and maintain. The yarn tool, part of the cmdtest
package, is a better tool for developing this type of test suites.

Thus, I close this wishlist bug.

-- 
http://gtdfh.branchable.com/ -- GTD for hackers
http://obnam.org/ -- HAVE YOU BACKED UP TODAY?

--- End Message ---

Reply via email to