scsh-hackers
[Top] [All Lists]

Re: [Scsh-hackers] 0.6.4 Beta 1

To: "Brian D. Carlstrom" <bdc@ai.mit.edu>
Subject: Re: [Scsh-hackers] 0.6.4 Beta 1
From: Martin Gasbichler <gasbichl@informatik.uni-tuebingen.de>
Date: Fri Mar 14 00:11:23 2003
Cc: Eric Marsden <emarsden@laas.fr>, scsh-hackers <scsh-hackers@lists.sourceforge.net>
List-id: Discussion among the implementors <scsh-hackers.lists.sourceforge.net>
Sender: scsh-hackers-admin@lists.sourceforge.net
>>>>> "Brian" == Brian D Carlstrom <bdc@zurich.ai.mit.edu> writes:

Brian> Martin Gasbichler writes:
>> There is no methodology for skipping tests yet. However, your fifo
>> example is there only case I'm aware of where a feature of scsh
>> doesn't work on all systems. 

Brian> So I disabled the three tests that create-fifo and everything else in
Brian> the test suite passes. Unix domain sockets don't work on Windows either,
Brian> but there isn't a test for those right now.

Ah, good to know. Do the cygwin people intend to fix this?

>> I would rather declare this a bug in scsh (which of course we cannot
>> fix) than changing the test suite to skip the test. We could add some
>> output to test-all saying which tests are known to fail due to bug in
>> scsh or add an optional argument to add-test! which indicates whether
>> the test is known to fail.

Brian> So having experience with both java testing at work and perl's test
Brian> suites, I think it's important for the tests to continue until the end,
Brian> reporting pass/fail/skip/total statistics. right now it just dies on the
Brian> failure.

Right, it definitly should catch errors and report them. I'll change
this.

-- 
Martin


<Prev in Thread] Current Thread [Next in Thread>