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.
So I disabled the three tests that create-fifo and everything else in
the test suite passes. Unix domain sockets don't work on Windows either,
but there isn't a test for those right now.
> 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.
So having experience with both java testing at work and perl's test
suites, I think it's important for the tests to continue until the end,
reporting pass/fail/skip/total statistics. right now it just dies on the
failure. I didn't expect to just not run the test, but to have it print
a message clearly stating why it was skipped, perhaps with a source
forge defect number included.
in any case, this isn't a 0.6.4 issue.