Home | History | Annotate | Line # | Download | only in dist
README revision 1.1.1.2
      1    Basic information
      2 
      3    By Julio Merino, The NetBSD Foundation
      4 
      5                                     Contents
      6 
      7     1. Introduction
      8 
      9     2. Other documents
     10 
     11     3. Contributing
     12 
     13                                   Introduction
     14 
     15    The Automated Testing Framework (ATF) is a collection of libraries and
     16    utilities designed to ease unattended application testing in the hands of
     17    developers and end users of a specific piece of software.
     18 
     19    As regards developers, ATF provides the necessary means to easily create
     20    test suites composed of multiple test programs, which in turn are a
     21    collection of test cases. It also attempts to simplify the debugging of
     22    problems when these test cases detect an error by providing as much
     23    information as possible about the failure.
     24 
     25    As regards users, it simplifies the process of running the test suites
     26    and, in special, encourages end users to run them often: they do not need
     27    to have source trees around nor any other development tools installed to
     28    be able to certify that a given piece of software works on their machine
     29    as advertised.
     30 
     31                                 Other documents
     32 
     33      * AUTHORS: List of authors and contributors for this project.
     34 
     35      * COPYING: License information.
     36 
     37      * INSTALL: Compilation and installation instructions. These is not the
     38        standard document shipped with many packages, so be sure to read it
     39        for things that are specific to ATF's build.
     40 
     41      * NEWS: List of major changes between formal, published releases.
     42 
     43                                   Contributing
     44 
     45    If you are planning to contribute code to the project, be absolutely sure
     46    to read doc/hacking.txt first.
     47