MFC r320443,r320444:

r320443:

Add kyua TAP test integration examples

The examples are patterned loosely after the ATF examples, similar
to the plain test examples.

r320444:

Commit the corresponding mtree file change for the TAP test examples

MFC with:	r320443

1 files changed, 36 insertions, 0 deletions

diff --git a/share/examples/tests/tests/tap/Makefile b/share/examples/tests/tests/tap/Makefile
new file mode 100644
index 0000000..6fa3948
--- /dev/null
+++ b/share/examples/tests/tests/tap/Makefile
@@ -0,0 +1,36 @@
+# $FreeBSD$
+
+# Directory into which the Kyuafile provided by this directory will be
+# installed.
+#
+# This is always a subdirectory of ${TESTSBASE}/.  The remainder of the
+# path has to match the relative path within the source tree in which
+# these files are found modulo the tests/ component at the end.
+#
+# For example: if this Makefile were in src/bin/cp/tests/, its TESTSDIR
+# would point at ${TESTSBASE}/bin/cp/.
+TESTSDIR=	${TESTSBASE}/share/examples/tests/tap
+
+# List of test programs to build.  Note that we can build more than one
+# test from a single directory, and this is expected.
+TAP_TESTS_C=	printf_test
+TAP_TESTS_SH=	cp_test
+
+# Tell bsd.test.mk that we are providing a hand-crafted Kyuafile in this
+# directory.  We do so because the file in this directory exists for
+# documentation purposes.
+#
+# In general, however, you should NOT define KYUAFILE at all to allow
+# bsd.test.mk auto-generate one for you based on the PLAIN_TESTS_*
+# definitions from above.
+KYUAFILE=	yes
+
+# Install file1 and file2 as files via bsd.prog.mk.
+FILES+=		file1
+FILESDIR=	${TESTSDIR}
+CLEANFILES+=	file1
+
+file1:
+	@echo "File 1" > ${.TARGET}
+
+.include <bsd.test.mk>