summaryrefslogtreecommitdiffstats
path: root/usr.bin/indent/tests/label.pro
diff options
context:
space:
mode:
authoreadler <eadler@FreeBSD.org>2018-03-08 07:05:19 +0000
committereadler <eadler@FreeBSD.org>2018-03-08 07:05:19 +0000
commitc5a232e4e456f8db4a1f853a05f900e561253195 (patch)
treec68bb1c63ff7ad7b32bd80b311a3161aefdb6460 /usr.bin/indent/tests/label.pro
parent126864de7120b99391210ae581dc5e61ee5dd88c (diff)
downloadFreeBSD-src-c5a232e4e456f8db4a1f853a05f900e561253195.zip
FreeBSD-src-c5a232e4e456f8db4a1f853a05f900e561253195.tar.gz
MFC r313544:
indent(1): add regression test cases These examples show expected behavior of indent(1). They are meant to be used together with a regression test mechanism, either Kyua, a Makefile or perhaps something else. The mechanism should in essence do this: indent -P${test}.pro < ${test}.0 > ${test}.0.run and compare ${test}.0.stdout to ${test}.0.run. If the files differ or the exit status isn't 0, the test failed. * ${test}.pro is an indent(1) profile: a list of options passed through a file. The program doesn't complain if the file doesn't exist. * ${test}.0 is a C source file which acts as input for indent(1). It doesn't have to have any particular formatting, since it's the output that matters. * ${test}.0.stdout contains expected output. It doesn't have to be formatted in Kernel Normal Form as the point of the tests is to check for regressions in the program and not to check that it always produces KNF.
Diffstat (limited to 'usr.bin/indent/tests/label.pro')
-rw-r--r--usr.bin/indent/tests/label.pro2
1 files changed, 2 insertions, 0 deletions
diff --git a/usr.bin/indent/tests/label.pro b/usr.bin/indent/tests/label.pro
new file mode 100644
index 0000000..b5afc20
--- /dev/null
+++ b/usr.bin/indent/tests/label.pro
@@ -0,0 +1,2 @@
+/* $FreeBSD$ */
+-nut
OpenPOWER on IntegriCloud