Home | History | Annotate | only in /external/ltp/testcases/open_posix_testsuite
Up to higher level directory
NameDateSize
AUTHORS21-Aug-2018366
bin/21-Aug-2018
BUILD21-Aug-20185.2K
CFLAGS21-Aug-201864
ChangeLog21-Aug-20186.6K
conformance/21-Aug-2018
COPYING21-Aug-201819.3K
Documentation/21-Aug-2018
functional/21-Aug-2018
include/21-Aug-2018
INSTALL21-Aug-2018229
LDFLAGS21-Aug-20180
LDLIBS21-Aug-20180
Makefile21-Aug-20183K
Makefile.linux21-Aug-2018530
NEWS21-Aug-20183.1K
QUICK-START21-Aug-20182.2K
README21-Aug-20184.4K
scripts/21-Aug-2018
stress/21-Aug-2018
tools/21-Aug-2018

README

      1 
      2 SECTIONS:
      3 1. Open POSIX* Test Suite Overview
      4 2. Design Goals
      5 3. Implementation
      6 4. Developer Docs & Resources
      7 5. How to Contribute
      8 6. Who are you?
      9 7. Disclaimer
     10 
     11 
     12 
     13 1. Open POSIX* Test Suite Overview
     14 -----------------------------------
     15 
     16 The POSIX Test Suite is an open source test suite with the goal of
     17 performing conformance, functional, and stress testing of the IEEE
     18 1003.1-2001 System Interfaces specification in a manner that is
     19 agnostic to any given implementation.
     20 
     21 While active development and testing is currently happening on Linux,
     22 our choice of portable tools should make this test suite usable on any
     23 POSIX operating system.
     24 
     25 All code is distributed under the GNU General Public License v2.  A
     26 copy of this license is contained in the COPYING file.
     27 
     28 This document gives a brief overview of the test suite, including its
     29 design goals, implementation, and how to contribute.  Within these
     30 sections, we describe where to find more detailed information.
     31 
     32 2. Design Goals
     33 ----------------
     34 This project was created with the following design goals:
     35 - Enable assertion based traceability for conformance testing of POSIX
     36   specifications.  We wanted to capture enough data to make deterministic
     37   statements about our coverage of the POSIX specification.
     38 
     39 - Give the ability to send test case source to bug reports to appropriate
     40   open source projects when our test cases revealed bugs in those projects.
     41   (Meaning we wanted fairly simple, self-contained test cases which
     42   illuminated a single failure.)
     43 
     44 - Make it easy for test cases to be contributed.
     45 
     46 3. Implementation
     47 ------------------
     48 
     49 This project will cover conformance, functional, stress, performance,
     50 and speculative testing.  Conformance, functional, and stress tests are
     51 the only tests formally documented and enabled by our framework, with our
     52 focus mainly on conformance; however, the other types of testing will be
     53 added as the need arises.
     54 
     55 For more information on these types of testing, under 'Documenation' see:
     56 HOWTO_ConformanceTest - info on creation and structure of conformance tests
     57 HOWTO_Functional-     - info on creation and structure of functional
     58   StressTest            and stress tests
     59 
     60 For additional information on how to build and run the tests in this
     61 suite, see Documentation/HOWTO_RunTests.
     62 
     63 
     64 4. Developer Docs & Resources
     65 ------------------------------
     66 
     67 The following files give developers information on how to write test
     68 cases for the project (under Documentation):
     69 HOWTO_Assertions      - describes format of the assertions files used to
     70                         map test case descriptions to test cases
     71 HOWTO_BoundaryTest    - information about testing boundary conditions
     72 HOWTO_CodingGuidelines- describes coding guidelines for this project
     73 HOWTO_Coverage        - describes format of COVERAGE.<area> files
     74 HOWTO_DefinitionsTest - ideas behind testing POSIX header files
     75 HOWTO_ResultCodes     - standardized return codes for tests
     76 HOWTO_Tagging         - describes how to tag files for inclusion in a release
     77 
     78 For additional information on how to build and run the tests in this
     79 suite, see HOWTO_RunTests.
     80 
     81 5. How to Contribute
     82 ---------------------
     83 
     84 * Patches welcome!
     85 
     86 * When you create a new test, please fill out an assertion description
     87   if none is available. Create a simple C [.c] or shell script [.sh]
     88   snippet that exploits the assertion and returns 0 or !0
     89   [passes/fails].
     90 
     91   Please name the file after the assertion it tests-dash-the number of
     92   the test [up to you, we can do the naming for you also].
     93 
     94   The code snippets need to be as simple as possible, for the sake of
     95   all. Please start them with a commentary briefly describing how
     96   you will test the assertion. The idea is that at the end, we can have
     97   automatic tools extracting the data from the XML and source files to
     98   generate reports.
     99 
    100 
    101 6. Who are you?
    102 ---------------
    103 
    104 We are the ones currently developing this:
    105 
    106 julie.n.fleischer REMOVE-THIS AT intel DOT com
    107 rusty.lynch REMOVE-THIS AT intel DOT com
    108 geoffrey.r.gustafson REMOVE-THIS AT intel DOT com
    109 inaky.perez-gonzalez REMOVE-THIS AT intel DOT com
    110 rolla.n.selbak REMOVE-THIS AT intel DOT com
    111 majid.awad REMOVE-THIS AT intel DOT com
    112 salwan.searty REMOVE-THIS AT intel DOT com
    113 sunyi REMOVE-THIS AT users DOT sourceforge DOT net
    114 
    115 Some like to say 'Nih!' from time to time ...
    116 
    117 
    118 7. Disclaimer
    119 --------------
    120 The Open POSIX Test Suite is not affiliated with the IEEE or The Open Group.
    121 
    122 * POSIX (R) is a registered trademark of the IEEE
    123