diff options
author | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> | 2010-08-22 06:32:39 +0200 |
---|---|---|
committer | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> | 2010-08-22 12:32:16 +0200 |
commit | b92d7e795871f8d22a13107b92427ae02bf32146 (patch) | |
tree | ec65695c95c5bfc07ba8737a54d4295d5bcb3ecc /doc | |
parent | 36bdc6089b33bcd7262bbb279ddf04b69768a6ac (diff) | |
download | libtool-b92d7e795871f8d22a13107b92427ae02bf32146.tar.gz |
check-interactive and check-noninteractive for both testsuites.
* Makefile.am (COMMON_TESTS, TESTS): Split into ...
(NONINTERACTIVE_TESTS, INTERACTIVE_TESTS): ... these new
variables.
(check-interactive-new): Rename from check-interactive.
(check-noninteractive-new): Rename from check-noninteractive.
(check-interactive-old, check-noninteractive-old): New targets.
(check-interactive, check-noninteractive): Depend on the
respective targets for the old and the new test suites.
* doc/libtool.texi (Test descriptions): Simplify description
about check-interactive and check-noninteractive. Add index
entries.
* NEWS: Update.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/libtool.texi | 28 |
1 files changed, 7 insertions, 21 deletions
diff --git a/doc/libtool.texi b/doc/libtool.texi index 26f9d9e8..f042a78a 100644 --- a/doc/libtool.texi +++ b/doc/libtool.texi @@ -5480,27 +5480,13 @@ recursive test groups themselves should never require user interaction, while the test groups they invoke may do so. @end table -For example, in order to avoid any interactive test groups, you could -use this: - -@smallexample -make check-local \ - TESTSUITEFLAGS='-k !interactive INNER_TESTSUITEFLAGS=",!interactive"' -@end smallexample - -@noindent -while to run only those test groups, you would use this: - -@smallexample -make check-local \ - TESTSUITEFLAGS='-k interactive -k recursive INNER_TESTSUITEFLAGS=,interactive' -@end smallexample - -@noindent -but the convenience targets @samp{check-interactive} and -@samp{check-noninteractive} avoid needing to remember these complex -commands, in addition to also disabling interactive tests in the old -test suite. +@cindex @samp{check-interactive} +@cindex @samp{check-noninteractive} +There is a convenience target @samp{check-noninteractive} that runs +all tests from both test suites that do not cause user interaction on +Windows. Conversely, the target @samp{check-interactive} runs the +complement of tests and might require closing popup windows about DLL +load errors on Windows. @node When tests fail |