Symbian3/PDK/Source/GUID-72F3CFD2-DDE4-56F1-907A-7C455BEDF674.dita
author Dominic Pinkman <Dominic.Pinkman@Nokia.com>
Fri, 22 Jan 2010 18:26:19 +0000
changeset 1 25a17d01db0c
child 3 46218c8b8afa
permissions -rw-r--r--
Addition of the PDK content and example code for Documentation_content according to Feature bug 1607 and bug 1608

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
<!-- This component and the accompanying materials are made available under the terms of the License 
"Eclipse Public License v1.0" which accompanies this distribution, 
and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
<!-- Initial Contributors:
    Nokia Corporation - initial contribution.
Contributors: 
-->
<!DOCTYPE task
  PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
<task xml:lang="en" id="GUID-72F3CFD2-DDE4-56F1-907A-7C455BEDF674"><title>Running the NetPerf Test Suite Tutorial</title><shortdesc>This topic describes how to run the NetPerf test suite. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody><prereq><p>Before you start, you must: </p> <ul><li id="GUID-18564683-F714-5993-A394-B99D45AC9C0A"><p>Understand the NetPerf configuration, Test Controller PC, and Device Under Test (DUT). </p> </li> <li id="GUID-4A6C6A76-C1F9-5EC3-8A38-E43FF5EAA1FA"><p>Understand the <xref href="GUID-B7A40638-BA80-5175-B23D-2F3964C274A0.dita">Communications Framework</xref>. </p> </li> </ul> </prereq> <context><p>The <i>NetPerf</i> master script controls the complete test process from the <i>Test Controller PC</i>. The master script and other related files are created in <codeph>%EPOCROOT%epoc32\tools\netperf\bin</codeph>. The Master script is designed to automate the test progress. When the master script is run for the first time, it assists with building and configuring the necessary software for the DUT. By using the run parameter, the subsequent tests can be run without rebuilding the script. </p> <p>When the test is run for the first time, use the <codeph>interactive</codeph> option. In interactive mode the master script generates the configuration files for the target system and the tools. The script informs the users that all the test script files are generated. This information enables the user to prepare for <i>DUT</i>. The test can be continued only if <i>DUT</i> is ready. </p> <p>The command line for the master script has the following structure: </p> <codeblock id="GUID-1963C11C-143F-586F-926B-91AA54644A14" xml:space="preserve">
netperf.pl [&lt;inifile&gt;] &lt;target&gt; [run] [interactive]
</codeblock> <p>Where: </p> <ul><li id="GUID-9BC064BB-50F8-5063-87E5-2AAC3658B6B6"><p> <codeph>inifile</codeph> – is the configuration file created by the Test Script Configuration. The default script file name is <codeph>netperf.ini</codeph>. </p> </li> <li id="GUID-100B54D7-6260-5254-83B6-311CB440A8B2"><p> <codeph>target</codeph> – specifies the type of <i>DUT</i>: <i>emulator</i>, <i>development board</i> H2 or H4 hardware reference board or <i>device</i> a mobile device. </p> </li> <li id="GUID-94EEC18C-3808-52D3-882C-42AF0674E6BB"><p> <codeph>run</codeph> – If specified, runs the test script without building test files. </p> </li> <li id="GUID-C3973CFB-04D4-5757-B95B-7E1B5B6E7388"><p> <codeph>interactive</codeph> – If specified, prompts the user to prepare the target with the generated files, before running the tests. </p> </li> </ul> <p> </p> </context> <steps id="GUID-EC459C83-DF44-5EB7-B673-09EB3DF85230"><step id="GUID-B982863B-580A-58E5-986B-D6A407D094CB"><cmd>The test can be run in two modes. </cmd> <substeps id="GUID-A5649822-F6D9-5D69-A137-782A16B8614C"><substep id="GUID-AB26EC17-3C40-5B3A-B1EF-BE807AB0DC27"><cmd>Automatic or Supervised Test - the Test Controller PC connects to the DUT, transfers the test to be run over to the DUT and starts each stage of the test. </cmd> </substep> <substep id="GUID-B33F37C2-F3AD-52E4-AD57-1BC1D765AD07"><cmd/><info>Semi-Automatic or Unsupervised Test - the Test Controller PC builds a test script for the DUT to use, and then pauses while the user copies the script across the DUT. The user uses a memory card to transfer the data than FTP and other methods. The tests are run on the DUT, and the results are copied back to the Test Controller PC, on a memory card or other medium. The Test Controller PC master script then resumes and processes the results. </info> </substep> </substeps> </step> <step id="GUID-2EAC5696-8322-54A7-8095-49CE1D352141"><cmd/><info>If the master script runs in interactive mode, it waits for the user confirmation. After confirmation, it builds the necessary software and configures the devices. </info> </step> </steps> </taskbody><related-links><link href="GUID-D1B54263-1637-5D4E-8FE1-92612AB2851C.dita"><linktext>Network Performance Test</linktext> </link> <link href="GUID-5CDD2D09-33B2-501B-A060-784C401CA373.dita"><linktext>Building a ROM for Development
                Board</linktext> </link> <link href="GUID-C2125B4A-A945-529C-AA2F-BDD00EADF489.dita"><linktext>Configuring the
                Communications Database for the DUT</linktext> </link> </related-links></task>