The  Automated  Testing Framework is a to implement test programs
in a variety of languages.  These  libraries  all  offer  similar
functionality  and  any  test program written with them exposes a
consistent user interface.  Test  programs  using  the  libraries
rely  on a separate runtime engine to execute them in a determin‐
istic fashion.  The runtime engine  isolates  the  test  programs
from  the rest of the system and ensures some common side‐effects
are cleaned up.  The runtime engine is also responsible for gath‐
ering the results of all tests and composing reports.   The  cur‐
rent  runtime  of  choice is Kyua, described in If your operating
systems distributes it should also provide an introductory manual
page.  You are encouraged to read it now.  The rest of this  man‐
ual  page serves as a cross‐reference to all the other documenta‐
tion shipped with C programming interface.  C++  programming  in‐
terface.   programming  interface.   Generic  description of test
cases, independent of the language they are implemented in.  Com‐
mon interface provided by the test programs written using the li‐
braries.  started as a Google Summer of Code  2007  project  men‐
tored by The NetBSD Foundation.  Its original goal was to provide
a  testing  framework for the operating system, but it grew as an
independent project because the framework itself did not need  to
be  tied to a specific operating system.  Originally, shipped the
collection of libraries described in this manual page as well  as
a  runtime engine.  The runtime engine has since been replaced by
Kyua and the old tools were removed in  which  shipped  in  early
2014.   As  of late 2014, both and ship in their base systems and
provide extensive test suites based on it.  For more  details  on
historical changes, refer to: For more details on the people that
made possible, refer to: