NetBSD

History

kamil 8a7b75cec0 Import new C and C++ ATF tests for ASan Add new tests: - tests/usr.bin/cc/t_asan_poison.sh - tests/usr.bin/c++/t_asan_poison.sh These tests verify the following build options: - regular - profile - pic - pie - compat32 - (static unsupported) These tests verify whether ASan code can include compiler and sanitizer specific header: <sanitizer/asan_interface.h>. The testing code checks the ASAN_POISON_MEMORY_REGION() functionality, poisoning valid memory and asserting that it triggers expected failure. Patch submitted by <Siddharth Muralee>		2018-04-11 03:25:25 +00:00
..
bin	Add a test case for "set -X".	2017-11-16 19:41:41 +00:00
crypto	PR lib/53044: remove tests not provided by OpenSSL 1.1.x	2018-02-22 14:24:03 +00:00
dev	implement 32-bit compat support for raidframe.	2018-01-18 00:32:48 +00:00
fs	Use sysctl -n rather than parse the output.	2018-01-17 00:23:17 +00:00
games
include	Update recently-added test to adapt to new signature of LIST_MOVE()	2017-10-02 05:14:29 +00:00
ipf
kernel	Add new ATF tests: kernel/t_zombie	2018-03-14 02:13:47 +00:00
lib	Cover more fork/vfork/vforkdone scenarios in ATF ptrace(2) tests	2018-04-11 01:52:59 +00:00
libexec	Avoid casting fun by switching ifunc helper functions to return	2018-03-09 20:15:03 +00:00
modules	Skip the test on non-modular kernels	2018-01-09 15:16:02 +00:00
net	Add a test case for bridge_rtdelete	2018-04-10 07:09:00 +00:00
rump	Fix build	2017-12-28 07:46:34 +00:00
sbin	Make most of the resize_ffs tests skip if PUFFS is not configured	2017-10-08 21:12:27 +00:00
share
sys	Typos.	2018-02-08 09:05:16 +00:00
usr.bin	Import new C and C++ ATF tests for ASan	2018-04-11 03:25:25 +00:00
usr.sbin	Add test mtree -O with same hash value in directory and leaf.	2017-09-07 04:05:21 +00:00
h_macros.h
Makefile	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
Makefile.inc
README

README

$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $

When adding new tests, please try to follow the following conventions.

1. For library routines, including system calls, the directory structure of
   the tests should follow the directory structure of the real source tree.
   For instance, interfaces available via the C library should follow:

	src/lib/libc/gen -> src/tests/lib/libc/gen
	src/lib/libc/sys -> src/tests/lib/libc/sys
	...

2. Equivalently, all tests for userland utilities should try to follow their
   location in the source tree. If this can not be satisfied, the tests for
   a utility should be located under the directory to which the utility is
   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
   even though the source code for the program is located under src/external.

3. Otherwise use your own discretion.