On Sun, 9 Jan 2005, _brian_d_foy wrote: > [[ This message was both posted and mailed: see > the "To," "Cc," and "Newsgroups" headers for details. ]] > > In article <[EMAIL PROTECTED]>, > Randy Kobes <[EMAIL PROTECTED]> wrote: > > > The loop is there so that if a user gives a non-existent > > location, the dialogue informs the user that no such program > > exists, and asks again - this is for convenience, > > how about breaking out of the loop if it repeats a certain > number of times?
That's something that we might consider. It would help in the motivation to do so if we knew that putting this in would prevent a FAIL from the automated testing script; I'd suspect, as things stand, that a FAIL would still result if the loop was ended after N tries, as the tests wouldn't run (note that this dialogue occurs at the 'make test' stage, which is deliberate, so as to be configureable and changeable). > you might also ensure you have an interactive session, and > bail out with a nice message if you don't. :) That might get a bit complicated ... Apache-Test can be used in a non-interactive setting, and is done, for example, by the mod_perl developers in testing svn builds. For this, a number of options are available to avoid having to answer interactive prompts: - specifying the relevant httpd location in an Apache::TestConfigData in a specified location; - setting certain environment variables (eg, APACHE_TEST_HTTPD) that Apache-Test will use; - adjusting the PATH in a way such that Apache-Test can guess the desired httpd location; However, none of these will help the automated testing, as they must be known and configured beforehand. -- best regards, randy
