On 25 April 2015 at 00:04, Arthur Schwarz <aschwarz1...@att.net> wrote: > > In 15.3.3.1 Command-line arguments for test drivers > > --log-file=PATH.log > > The .log file the test driver must create (see Basics of test metadata). > If it has a directory component (as in e.g., sub/foo.log), the test harness > will ensure that such directory exists before the test driver is called. > > Q: Does this mean that custom, dejagnu, and TAP test drivers must generate a > log file? When I run a test it seems that the output of scripts or programs > (TEST = some_script_or_program) is captured in a log file by the test > harness, as in some_script_or_program.log.
>From my reading, it means that a custom driver must recognize this option, but it could do what it likes with it. See 15.3.1. Overview of Custom Test Drivers Support. > > --trs-file=PATH.trs > > The .trs file the test driver must create (see Basics of test metadata). > If it has a directory component (as in e.g., sub/foo.trs), the test harness > will ensure that such directory exists before the test driver is called. > > Q: The command line input is given without qualification. Does this mean > that it applies to all of the serial and parallel test harness, the custom, > dejagnu and TAP test drivers, and test scripts? Or should there be some > qualification This is in a section of the manual that is specifically about custom test drivers.
