History log of /dragonfly/usr.bin/dfregress/testcase.h (Results 1 – 4 of 4)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0
# 039caa27 27-Nov-2020 Antonio Huete Jimenez <tuxillo@quantumachine.net>

dfregress: Add 'rc' option

- Allows to specify which return code will be considered success for the
test case being run. In the example below, a return code of '1' will
make the test PASS.

dfregress: Add 'rc' option

- Allows to specify which return code will be considered success for the
test case being run. In the example below, a return code of '1' will
make the test PASS.

# Testcase type Options Args
builtins/alias.1 userland nobuild,rc=1 myarg1 myarg2

show more ...


# 0d575305 26-Nov-2020 Antonio Huete Jimenez <tuxillo@quantumachine.net>

dfregress: Add 'interpreter' option

- Allows to specify the interpreter that will run the testcase file.
Some test cases just provide a file without execution permissions or no
shebang, et

dfregress: Add 'interpreter' option

- Allows to specify the interpreter that will run the testcase file.
Some test cases just provide a file without execution permissions or no
shebang, etc. In some cases it is not desirable to modify the test case
files (i.e. contrib stuff).

Taking the example below, the previous behavior was to execvp() the file
'builtins/alias.0' but with 'interpreter' option, now you can specify
the shell you want to use to run it.

# Testcase type Options Args
builtins/alias.0 userland nobuild,interpreter=sh myarg1 myarg2

show more ...


Revision tags: v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


# a563ca70 16-Nov-2011 Alex Hornung <ahornung@gmail.com>

dfregress,tbridge - Move into usr.bin and sys/dev

* cleanup of the testcases, remove duplicates, consolidate in
test/testcases.