[lttng-dev] Running lttng-tools testsuite against an installed codebase

Stefan Seefeld stefan_seefeld at mentor.com
Fri Sep 13 16:02:15 EDT 2013

On 09/13/2013 03:56 PM, Christian Babeux wrote:
>> Of course, that would break the `make check` target as for in-development testing
>> the binaries would no longer be found. Is there any reason a simple
>> adjustment of the PATH variable would not be enough ?
> One of the issue I see with overriding the PATH _only_ in the make
> check target is that we will no longer be able to run each tests
> separately from the command line.

For avoidance of doubt, I'm not suggesting to modify PATH from within
the Makefile. I'd do that before invoking 'make'.

And thus, running tests individually should work just as fine, and pick
up executables according to your settings.

> Poking a bit around, I saw that the git project also use a TAP
> testsuite. They get around the issue of binary path resolving via a
> test-lib (similar to our tests/utils/utils.sh) which is sourced in
> each scripts and adjust the paths accordingly.

Setting up the environment with a convenience script sounds fine, but I
still don't understand why this would be called by the test harness,
rather than manually before the test harness is invoked. Keeping the two
separate sounds much simpler and less error-prone to me.


Stefan Seefeld
CodeSourcery / Mentor Graphics

More information about the lttng-dev mailing list