subunit

documentation about running tests could be more obvious

Bug #537614 reported by Jonathan Lange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subunit
Triaged
Wishlist
Unassigned

Bug Description

$ 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.

See original description
Revision history for this message
Robert Collins (lifeless) wrote :

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

Changed in subunit:
importance: Undecided → Critical
status: New → Incomplete
Revision history for this message
Jonathan Lange (jml) wrote : Re: [Bug 537614] Re: subunit tests fail in trunk

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

Revision history for this message
Robert Collins (lifeless) wrote : Re: subunit tests fail in trunk

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.

description: updated
summary: - subunit tests fail in trunk
+ documentation about running tests could be more obvious
Changed in subunit:
importance: Critical → Wishlist
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.