Get rid of static Atffiles and let bsd.test.mk generate them on the fly.

branches: 1.4.2;
Re-add the NetBSD CVS Id tag to the header. It just had to be quoted to
be accepted by the parser; i.e. no bug in the code :-)

Note to self: do not try to "fix" stuff the last minute before going to
sleep.

Back out the change to introduce the X-NetBSD-Id header entry. For some
reason the parser does not accept its contents... You know, one should
always test even trivial changes!

Will review this in more depth tomorrow to find the real root cause of the
problem and rule out a fix for ATF.

Add the NetBSD Id tag to the Atffiles. Issue raised by pooka@ a while ago.

Convert the regress/games tests to the atf

This change converts all the existing regression tests in regress/games
to the new framework provided by atf. As a side effect, this also moves
all the tests programs in regress/games to tests/games.

tests/morse: add basic tests

branches: 1.2.4;
Explicitly define TESTSDIR, because the automatic deduction of its value
breaks the build if some component of NETBSDSRCDIR is a symlink. Reported
by drochner@.

Convert the regress/games tests to the atf

This change converts all the existing regression tests in regress/games
to the new framework provided by atf. As a side effect, this also moves
all the tests programs in regress/games to tests/games.

tests: replace deprecated '-s eq:...' with '-s exit:...'

simplify: use two arguments again, suggested by kre@

Add tests for h and x flags

Do this more cleanly - put the do-we-have-crypto check inside the actual
do-the-test code rather than in a test's head() code. This way, if we
ever add more tests, we simply need to invoke the common do-the-test code
with an appropriate flag argument rather than duplicating the test.

Split each test into its own test case.

For test case loop2, where there are multiple prime factors greater
than 65535, skip the test if the program was not built with crypto
support. We need crypto/openssl for large factors.

Should address PR bin/23663

Since /usr/games is rarely in one's $PATH, provide an absolute path to the
test-program. This lets automated testing reach and execute a couple more
tests rather than skipping them.

Discussed privately with pooka@

Adjusts tests after import of atf-0.12:

- The use.fs property is gone.
- Mark the tests/fs/t_create:attrs test as broken when using the default
unprivileged-user:_atf setting. This probably deserves a fix somehow
but I'm not sure at this point.

atf-0.9 introduces an use.fs test-case property to allow tests to write to
their work directory. The purpose is to be able to know which tests intend
to touch the file system and to allow a minor optimization in atf-run.

Define use.fs=true for all those tests requiring it. (This highlights that
some tests currently require modifying the file system but conceptually
they shouldn't be... which leaves room for further improvements/cleanups
later :-)

Adjust tests to work with the new API in ATF 0.6.

Convert TNF licenses to new 2 clause variant

branches: 1.2.4;
Remove a warning that said that the test could loop forever because ATF
will now automatically terminate it after 5 minutes of run time.

branches: 1.1.4;
Convert the regress/games tests to the atf

This change converts all the existing regression tests in regress/games
to the new framework provided by atf. As a side effect, this also moves
all the tests programs in regress/games to tests/games.

tests/morse: test decoding of dot-dash morse output

branches: 1.2.2;
tests/morse: only run the tests if morse is installed

Not sure why the releng/i386 tests don't install the games.

tests/morse: add basic tests