d8b51c8ab7
utilities. That is, not the low level ones that look like syntax, but aren't: break/continue/return; not those which are really just external programs that are built in for efficiency (printf, test, and kill - though kill really needs to be built in) - those should all have separate test programs (there is a test here for the built-in echo, as that is an entirely different thing to /bin/echo); and also not those for which there are other tests because of the nature of the built-in (like exit, wait, shift, ...). Lastly not "times" either as that just seems to be too hard to test rationally. There is a test (well, framework) for ulimit and there's also t_ulimit.sh one of those should go, but I am not yet sure which is the best way to reconcile things. Note: many (in fact) most of the test cases added here are either entirely empty (no tests at all, beyond testing that the built-in is in fact a shell built-in) or only very rudimentary tests - assistance in fleshing those out would be welcome (the boilerplate is all here, all that is needed is some actual tests to run...)
31 lines
550 B
Makefile
31 lines
550 B
Makefile
# $NetBSD: Makefile,v 1.14 2018/12/05 02:45:06 kre Exp $
|
|
#
|
|
|
|
.include <bsd.own.mk>
|
|
|
|
TESTSDIR = ${TESTSBASE}/bin/sh
|
|
|
|
TESTS_SUBDIRS += dotcmd
|
|
|
|
TESTS_SH+= t_arith
|
|
TESTS_SH+= t_builtins
|
|
TESTS_SH+= t_cmdsub
|
|
TESTS_SH+= t_evaltested
|
|
TESTS_SH+= t_exit
|
|
TESTS_SH+= t_expand
|
|
TESTS_SH+= t_fsplit
|
|
TESTS_SH+= t_here
|
|
TESTS_SH+= t_option
|
|
TESTS_SH+= t_patterns
|
|
TESTS_SH+= t_redir
|
|
TESTS_SH+= t_redircloexec
|
|
TESTS_SH+= t_set_e
|
|
TESTS_SH+= t_shift
|
|
TESTS_SH+= t_syntax
|
|
TESTS_SH+= t_ulimit
|
|
TESTS_SH+= t_varquote
|
|
TESTS_SH+= t_varval
|
|
TESTS_SH+= t_wait
|
|
|
|
.include <bsd.test.mk>
|