1f08c3bdfSopenharmony_ci 2f08c3bdfSopenharmony_ciQUICK-START 3f08c3bdfSopenharmony_ci*********** 4f08c3bdfSopenharmony_ci 5f08c3bdfSopenharmony_ciSo you're in a hurry and don't feel like reading all those docs in the Documentation section that we have worked so hard to write huh? 6f08c3bdfSopenharmony_ci 7f08c3bdfSopenharmony_ciNo worries! Here's a quick doc to help you around POSIX** Test Suite. 8f08c3bdfSopenharmony_ci 9f08c3bdfSopenharmony_ci======================== 10f08c3bdfSopenharmony_ciSetting up your machine 11f08c3bdfSopenharmony_ci======================== 12f08c3bdfSopenharmony_ci 13f08c3bdfSopenharmony_ci* See the "BUILD" file for info on how to set up the Makefile and your machine, 14f08c3bdfSopenharmony_ci depending on what specific area you are concentrating on. 15f08c3bdfSopenharmony_ci(Signals, Semaphores, Threads, Timers or Message Queues). 16f08c3bdfSopenharmony_ci 17f08c3bdfSopenharmony_ci=================== 18f08c3bdfSopenharmony_ciRunning the tests 19f08c3bdfSopenharmony_ci=================== 20f08c3bdfSopenharmony_ci 21f08c3bdfSopenharmony_ci* Easiest way to run all the tests is to do a "./configure && make all" 22f08c3bdfSopenharmony_ci in the top-level directory. 23f08c3bdfSopenharmony_ci 24f08c3bdfSopenharmony_ci* To run tests for a specific directory, do the following 25f08c3bdfSopenharmony_ci - make generate-makefiles # only required for the first shot. 26f08c3bdfSopenharmony_ci - cd <subdir> ; make all test 27f08c3bdfSopenharmony_ci 28f08c3bdfSopenharmony_ci Example: 29f08c3bdfSopenharmony_ci 30f08c3bdfSopenharmony_ci - make generate-makefiles 31f08c3bdfSopenharmony_ci - cd conformance/interfaces/pthread_create ; make all test 32f08c3bdfSopenharmony_ci 33f08c3bdfSopenharmony_ci* Running tests for a specific focus can be done like so: 34f08c3bdfSopenharmony_ci run-posix-option-group-test.sh [OPTION-GROUP] 35f08c3bdfSopenharmony_ci 36f08c3bdfSopenharmony_ci* For additional information on how to build and run the tests in this 37f08c3bdfSopenharmony_ci suite, see Documentation/HOWTO_RunTests. 38f08c3bdfSopenharmony_ci 39f08c3bdfSopenharmony_ci========================== 40f08c3bdfSopenharmony_ciDocumentation & Resources 41f08c3bdfSopenharmony_ci========================== 42f08c3bdfSopenharmony_ci 43f08c3bdfSopenharmony_ciPOSIX* Test Suite project page: http://posixtest.sf.net 44f08c3bdfSopenharmony_ci 45f08c3bdfSopenharmony_ciBUILD - describes how to set up your developer machine to build and test 46f08c3bdfSopenharmony_ci 47f08c3bdfSopenharmony_ciThe following files give developers information on how to write test 48f08c3bdfSopenharmony_cicases for the project (under Documentation): 49f08c3bdfSopenharmony_ci 50f08c3bdfSopenharmony_ciHOWTO_Assertions - describes format of the assertions files used to 51f08c3bdfSopenharmony_ci map test case descriptions to test cases 52f08c3bdfSopenharmony_ciHOWTO_BoundaryTest - information about testing boundary conditions 53f08c3bdfSopenharmony_ciHOWTO_CodingGuidelines - describes coding guidelines for this project 54f08c3bdfSopenharmony_ciHOWTO_Coverage - describes format of COVERAGE.<area> files 55f08c3bdfSopenharmony_ciHOWTO_DefinitionsTest - ideas behind testing POSIX header files 56f08c3bdfSopenharmony_ciHOWTO_ResultCodes - standardized return codes for tests 57f08c3bdfSopenharmony_ciHOWTO_Tagging - describes how to tag files for inclusion in a release 58f08c3bdfSopenharmony_ciHOWTO_RunTests - describes how to build and run the tests 59f08c3bdfSopenharmony_ci 60f08c3bdfSopenharmony_ci** POSIX (R) is a registered trademark of the IEEE 61f08c3bdfSopenharmony_ci 62f08c3bdfSopenharmony_ciMaintainer: Ling Yu (ling.l.yu@intel.com) 63