documentation about running tests could be more obvious

[Jonathan Lange]

$ PYTHONPATH=python ./runtests.py
test_close_after_finished_stream_safe (subunit.tests.test_chunked.TestDecode) ... ok

test_stats_smoke_everything (subunit.tests.test_subunit_stats.TestTestResultStats) ... ok
/home/jml/src/subunit/trunk/./shell/tests/test_source_library.sh: line 37: subunit.sh: No such file or directory
shell bindings can be sourced ... FAIL
subunit_start_test exists ... FAIL
subunit_pass_test exists ... FAIL
subunit_fail_test exists ... FAIL
subunit_error_test exists ... FAIL
subunit_skip_test exists ... FAIL
/home/jml/src/subunit/trunk/./shell/tests/test_function_output.sh: line 27: subunit.sh: No such file or directory
...
FAILED (failures=7)

runtests.py isn't enough on its own to run the tests, make check is needed: and this is only documented in INSTALL.

[Robert Collins (lifeless)]

Looks like you haven't run ./configure - can you confirm that?

[Jonathan Lange (jml)]

On Thu, Mar 11, 2010 at 8:58 PM, Robert Collins
<email address hidden> wrote:
> Looks like you haven't run ./configure - can you confirm that?
>
> ** Changed in: subunit
>   Importance: Undecided => Critical
>
> ** Changed in: subunit
>       Status: New => Incomplete

Ah. If I run "autoreconf -vi; ./configure; make" and then runtests, I
still get the failure. They pass with 'make check' though, so it's
probably pebkac. Or documentation or something (I wasn't expecting to
look in INSTALL to find the instructions for running the tests).

jml

[Robert Collins (lifeless)]

TESTS_ENVIRONMENT = SHELL_SHARE='$(top_srcdir)/shell/share/' PYTHONPATH='$(abs_top_srcdir)/python':${PYTHONPATH}

is the line in Makefile.am that makes the tests pass.

I agree that INSTALL is perhaps unobvious a place to write docs. I should add a .testr.conf, so you can 'testr run' - but I don't have full support for getting subunit out of the subunit test suite atm. Bit of a bootstrap problem.