bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] maint: mention how to run a single test in HACKING docs


From: Jim Meyering
Subject: Re: [PATCH] maint: mention how to run a single test in HACKING docs
Date: Fri, 13 Feb 2009 07:46:08 +0100

Pádraig Brady <address@hidden> wrote:
>> The name after TESTS= should be the name of the file relative to
>> the tests/ directory:
>>
>>      make check -C tests TESTS=misc/newtest VERBOSE=yes
>
> Oops right :)
> I noticed that the original README said:
>
>   make check -C tests/misc TESTS=newtest VERBOSE=yes
>
> This doesn't work I think because there are no Makefile.am
> files in the test subdirectories (there was related info
> in tests/README that I didn't follow).
>
> Anyway the attached patch should contain info that currently works.
>
> cheers,
> Pádraig.
>>From 11dab666a195fa14d4bcb32ad8daef90a85c52a3 Mon Sep 17 00:00:00 2001
...
> -as possible.
> +as possible. Note to run tests/misc/newtest in isolation you can do:
> +
> +  make check -C tests TESTS=misc/newtest VERBOSE=yes
>
>  There are hundreds of tests in the tests/ directories.  You can use
>  tests/sample-test as a template, or one of the various Perl-based ones
> diff --git a/README b/README
> index 157432e..2770faf 100644
> --- a/README
> +++ b/README
> @@ -164,12 +164,12 @@ in verbose mode for each failing test.  For example,
>  if the test that fails is tests/mv/hard-link-1, then you
>  would run this command:
>
> -  env VERBOSE=yes make check -C tests/mv TESTS=hard-link-1 >> log 2>&1
> +  env VERBOSE=yes make check -C tests TESTS=mv/hard-link-1 >> log 2>&1
>
>  For some tests, you can get even more detail by including
>  DEBUG=yes in the environment:
>
> -  env DEBUG=yes VERBOSE=yes make check -C tests/mv TESTS=hard-link-1 >> log 
> 2>&1
> +  env DEBUG=yes VERBOSE=yes make check -C tests TESTS=mv/hard-link-1 >> log 
> 2>&1

Looks fine, now.
Thanks for the clean-up.

BTW, you can shorten those latter two commands by removing the leading
"env " and putting the VERBOSE/DEBUG variable settings at the end,




reply via email to

[Prev in Thread] Current Thread [Next in Thread]