Changes between Version 6 and Version 7 of GCI/Coding/POSIXTimingTest


Ignore:
Timestamp:
Nov 15, 2018, 1:48:41 PM (7 months ago)
Author:
shashvat jain
Comment:

Made changes to some the instructions

Legend:

Unmodified
Added
Removed
Modified
  • GCI/Coding/POSIXTimingTest

    v6 v7  
    66
    77**Pre-Requisite**: You '''must''' have completed the "Getting Started: Hello World" task or equivalently done the [wiki:GSoC/GettingStarted GSoC Getting Started Guide] before attempting this task.
     8This task consists of adding a benchmark test to the RTEMS POSIX Timing Test Suite.  There are templates for each benchmark pattern we have identified.  The task consists of identifying the correct pattern, instantiating it using the "mktest" script, and then filling that in with the appropriate calls.
    89
    910===  Invoking rtems-testing/rtems-test-template/mktest  ===
    1011
    11 To create a test, you'll need to be in the rtems/testsuite/your_pattern directory.
    12 This task consists of adding a benchmark test to the RTEMS POSIX Timing Test Suite.  There are templates for each benchmark pattern we have identified.  The task consists of identifying the correct pattern, instantiating it using the "mktest" script, and then filling that in with the appropriate calls.
    13 For example:
     12First of all you will need the [https://git.rtems.org/rtems-testing/ rtems-testing] repository .
     13
    1414{{{
    15  ~/rtems/testsuites/psxtmtests>
     15 cd development
     16 git git://git.rtems.org/rtems-testing.git
    1617}}}
    17 You'll need to specify the source (-s), the destination (-d), and the test number (-n). Change the location to match where you put rtems-testing. For example:
     18
     19**NOTE** : Which contains different **templates** for tests ,**Templates**  are generalized benchmark skeleton tests given for making the work of making specific test cases easier . You will have to follow the same format as of the template while calling functions in the test.
     20
     21Second ,instantiating the mktest script ,
     22for this you must be in rtems tree and inside the rtems/testsuites/psxtmtests , here is where you will find all the benchmark tests for POSIX API.
     23This folder also contains the [https://git.rtems.org/rtems/tree/testsuites/psxtmtests/psxtmtests_plan.csv psxtmtests_plan.csv] file which is the plan for making all tests,
     24you will identify the name of template , test case ,test name and status of test ('Yes' means it exists).
     25Search for the test case name of which you have to generate the benchmark test. Identify the name of the corresponding template .
     26Take the test psxtmcond04 , so you will give the following attributes to the script.   
     27
     28
    1829{{{
    19  ~/rtems/testsuites/psxtmtests> ~/rtems-testing/rtems-test-template/mktest \
    20  -s ~/rtems-testing/rtems-test-template/psxtmtest_unblocking_preempt \
     30 ~development/rtems-testing/rtems-test-template/mktest \
     31 -t ~/rtems-testing/rtems-test-template/psxtmtest_unblocking_preempt \
     32 -s ~/rtems-testing/rtems-test-template \
    2133 -d psxtmcond04 \
    2234 -n 4
    2335}}}
     36
     37You'll need to specify the source (-s),location/path of template (-t), the destination directory (-d),(-D)Discription, and the test number (-n). Change the location to match where you put rtems-testing.
     38
     39This step will generate the required test , here (psxtmcond04)
     40
     41
    2442===  Adding the Test to the Build System  ===
    2543