1SECTIONS: 21. Overview 32. Framework Functionality 43. Building and Running the Tests 5 61. Overview 7------------ 8This document describes how to run the tests in the POSIX Test Suite. 9 10Our framework currently has the ability to build and run conformance, 11functional, and stress tests. All tests are built with make all, but 12certain care should be used when running the stress test suite as the 13tests may leave the system in an indeterminate state. 14 152. Framework Functionality 16---------------------------------------------------- 17 18 * Conformance Tests 19The build and execution process varies for conformance tests. 20 21For definitions tests, the build and execution process is the same since 22the pass/fail criterion is determine by whether or not the test compiles. 23A definitions test will be compiled, not linked, by the toolchain. 24 25For all other tests, they will have one test for the compile, one for the 26link, and one for the execution of the test. Successful tests return 27PTS_PASS, which the interprets as success. All other return values are 28considered failures [For more info, see HOWTO_ResultCodes]. 29 30 * Functional/Stress Tests 31Functional and stress tests have their own Makefile and method for running, 32and the framework merely calls these mechanisms. To build functional and 33stress tests, the framework calls the main Makefile for each functional 34area. To run these tests, the framework calls the run.sh file for each 35functional area. 36 373. Building and Running the Tests 38---------------------------------- 39 40** See the BUILD file for info on how to set up the build for the specific 41area you are testing (threads, mqs, semaphores, etc.), as well as setup the 42build specific to your environment. 43 44To build and run the tests, you should be in the main posix test suite 45directory. 46 47From there, execute: 48 # ./configure 49 # make all 50 51This will build all of the conformance, functional, and stress tests. 52 53To disable known failures on Linux do make filter-known-fails. 54 55* Conformance-specific items * 56 57To run conformance tests for a specific directory, just cd to the directory 58and run make all test. 59 60Example: 61 # cd conformance/definitions/time_h ; make all test 62 63To just build conformance tests, run: 64 # make conformance-all 65 66To just run conformance tests, run: 67 # make conformance-test 68 69* Functional/Stress-specific items * 70 71To run only functional tests, run: 72 # make functional-test 73 74To run only stress tests, run: 75 # make stress-test 76 77To make only functional tests, run: 78 # make functional-all 79 80To make only stress tests, run: 81 # make stress-all 82 83To skip known failures on Linux, run: 84 # make filter-known-fails 85 # make test 86 874. Running POSIX Option Group Feature Tests 88----------------------------------------------------- 89 90There are several POSIX option groups available that can be tested with this 91test suite. The available groups are: 92 93 AIO | Asynchonous I/O 94 MEM | Memory 95 MSG | IPC 96 SEM | Semaphores 97 SIG | Signals 98 THR | Threading 99 TMR | Timers 100 TPS | Thread Execution Scheduling 101 102You can run the tests by executing: 103 104 bin/run-posix-option-group-test.sh [OPTION-GROUP] 105 106or run all of the tests by executing: 107 108 bin/run-all-posix-option-group-tests.sh 109 110More details about these features can be found on the OpenGroup site 111(http://www.opengroup.org). 112 113Contributors: rusty.lynch REMOVE-THIS AT intel DOT com 114 julie.n.fleischer REMOVE-THIS AT intel DOT com 115 rolla.n.selbak REMOVE-THIS AT intel DOT com 116 yaneurabeya REMOVE-THIS AT gmail DOT com 117