Changes between Version 5 and Version 6 of AutomatedTesting
- Timestamp:
- Aug 18, 2010 5:58:55 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AutomatedTesting
v5 v6 16 16 == Introduction == 17 17 18 The automated testing framework automatically and continuously updates, configures, builds, and performs various unit tests , and submit the result to [http://my.cdash.org/index.php?project=PJSIP PJSIP's CDash] test dashboard. The scenario uses [http://trac2.pjsip.org/ccdash CCDash] (client for CDash; note the extra "c") framework to automate the tasks.18 The automated testing framework automatically and continuously updates, configures, builds, and performs various unit tests on PJSIP distribution, and submit the result to [http://my.cdash.org/index.php?project=PJSIP PJSIP's CDash] test dashboard. The scenario uses [http://trac2.pjsip.org/ccdash CCDash] (client for CDash; note the extra "c") framework to automate the tasks. 19 19 20 20 Supported targets: … … 24 24 - [wiki:Getting-Started/iPhone iPhone/iPad] 25 25 26 [[BR]] 27 26 28 == Installation == 27 29 1. Checkout PJSIP source code from SVN … … 29 31 1. Download and install any features to be used/tested, e.g. Intel IPP, Symbian APS/VAS plugin, etc. 30 32 33 [[BR]] 34 31 35 == Configuring and Running Test Scenarios == 32 36 33 The general steps to configure automated test script on a platform :37 The general steps to configure automated test script on a platform are as follows: 34 38 35 39 0. Go to directory '''{{{tests/automated}}}''' inside pjsip distribution. 36 1. Choose the appropriate scenario ''template'' for your target/test objective. A template is an XML file containing c ommand to perform automated tests for a particular target. The templates are listed below:40 1. Choose the appropriate scenario ''template'' for your target/test objective. A template is an XML file containing ccdash commands to perform automated tests for a particular target. The PJSIP distribution have been equipped with the following templates: 37 41 38 42 || '''Target platform ''' || '''Template file name ''' || '''Description ''' || '''Requirements ''' || 39 43 || Makefile based (Linux, Mac OS X) || {{{gnu.xml.template}}} || Default settings || - || 40 || Linux, Mac OS X || {{{gnu-ipp.xml.template}}} || Intel IPP || [wiki:Intel_IPP_Codecs Intel IPP and samples] ||41 || MSVC/Win32 || {{{msvc.xml.template}}} || Default settings || - ||44 || Linux, Mac OS X with IPP || {{{gnu-ipp.xml.template}}} || Intel IPP || [wiki:Intel_IPP_Codecs Intel IPP and samples] || 45 || MSVC/Win32 inc. WM || {{{msvc.xml.template}}} || Default settings || - || 42 46 || Symbian/S60 3rd Ed|| {{{symbian.xml.template}}} || Default settings || - || 43 47 || Symbian/S60 3rd Ed || {{{symbian-aps.xml.template}}} || Nokia APS and APS-Direct || [wiki:APS Nokia APS plugin] || … … 49 53 $ ./configure.py scenario.xml.template -o scenario.xml 50 54 }}} 55 The above command will produce '''{{{scenario.xml}}}''' scenario file. 51 56 3. For testing, run the scenario by running: 52 57 {{{ 53 58 $ ./run_scenario.py scenario.xml 54 59 }}} 55 This will perform the automated tests and submit the result under "Experimental" group . Depending on which test is being run, it may take between two minutes to two hours to complete. You may press Ctrl-C to stop the execution.56 4. Once you're satisfied that the scenario(s) will work correctly, run thisto perform both "Continuous" and "Nightly" builds on the specified scenario(s):60 This will perform the automated tests and submit the result under "Experimental" group on CDash. Depending on which test is being run, it may take between two minutes to two hours to complete. You may press Ctrl-C to stop the execution. 61 4. Once you're satisfied that the scenario(s) will work correctly, run '''{{{run_continuous.py}}}''' to perform both "Continuous" and "Nightly" builds on the specified scenario(s): 57 62 {{{ 58 63 $ ./run_continuous.py scenario1.xml [scenario2.xml ...] 59 64 }}} 60 The script will run the automated tests everytime changes occur in the repository, or at every 00:00:00 GMT for the "Nightly" build.61 5. Go to [http://my.cdash.org/index.php?project=PJSIP PJSIP's CDash] test dashboard to check the test results. Note that test results are only submitted once all tests are completed.65 The script will run the automated tests in the scenario(s) everytime changes occur in the repository, or at every 00:00:00 GMT for the "Nightly" build. 66 5. Go to [http://my.cdash.org/index.php?project=PJSIP PJSIP's CDash] test dashboard to check the test results. Note that test results are only submitted once all tests in a scenario are completed. 62 67 6. Now the automated test will run everytime there is a new checkin in the repository, or at every 00:00:00 GMT for the "Nightly" build. 63 68 64 69 65 The detailed steps for each template will be explained below. 70 [[BR]] 71 72 == The Templates == 73 74 The detailed steps to configure each template will be explained below. 75 76 [[BR]] 66 77 67 78 === gnu.xml.template === … … 72 83 $ ./run_scenario.py gnu.xml 73 84 }}} 85 86 [[BR]] 74 87 75 88 === gnu-ipp.xml.template === … … 96 109 97 110 111 [[BR]] 112 98 113 === iphone.xml.template === 99 114 … … 114 129 115 130 131 [[BR]] 132 116 133 === msvc.xml.template === 117 134 … … 121 138 122 139 140 [[BR]] 141 123 142 === symbian.xml.template === 124 143 … … 126 145 127 146 TBD. 147 148 [[BR]] 128 149 129 150 === symbian-aps.xml.template === … … 133 154 TBD. 134 155 156 157 [[BR]] 135 158 136 159 === symbian-vas.xml.template ===