CS8 Development Library UI
Contents
1. r Handover UMTS 5 to LTE m Redirection w Redirection r Redirection h Redirection ma Redirection ga Redirection r Redirection r Redirection F a8 SuiteFile1 UMTS 2 to LT UMTS 5 to LT UMTS 2 to LT UMTS 5 to LT LTE 17 to UM LTE 4 to UMT LTE 17 to UM LTE 4 to UMT CS8 Developme CS8 Develo Redirection UMTS 5 to LTE 4 Blind UDP C58 Developme CS8 Develo Redirection LTE 1 7 to UMTS 2 Blind UDF CS8 Developme CS8 Develo Redirection LTE 4 to UMTS 2 Blind UDP CS8 Developme CS8 Develo Redirection LTE 17 to UMTS 5 Blind UDP CS8 Developme CS8 Develo Redirection LTE 4 to UMTS 5 Blind UDF Figure 4 9 Loading a Test Suite Description Specifies a short description of the test case IWalid values Any Chapter Four Running the Development Library Ul 33 2 In the Test Manager menu select Execute gt Start Session gt Run All Test Cases to start executing the entire Test Suite You also have the option of executing only the currently selected test case The Execute Session window displays 4 6 Selecting the Parameter Files for Session Execution After creating the custom test suite and configuring the test case parameters or selecting a pre defined test suite you must ensure the suite is compatible with the platform settings that is that the instrument and peripherals exist and are compatible with the functiona2. 8 Return This step shown in Figure 3 13 returns from the current section of the code with a Pass Fail ReturnValue Step Parameters ReturnValue e True False El Step 7 Description Type FlowControl Subtype Return Returni alue False Run Mode Normal Error Handling Fail Error Description Figure 3 13 Return Step 9 Trace This step posts a message to the TestManager executive The MessageText can be a literal text string enclosed in quotes or an expression that evaluates to a string In that case the message text expects a C C C style syntax If the Run Mode is set to Break the modal message displays instead and the test case is paused indefinitely until you close the window Step Parameters TestiMessans minus eighty five e Literal string Chapter Three Editing the Development Library UI 21 Step Parameters DLS SS LTE eNodeB 0 PHY ConfigurePowerLevel Expression value RSTP 85 HM Step Description Type FlowControl Subtype TRACE DL5 55 LTE eModeB 0 PHY ConfiguePowerlerel RSTP Run Mode Normal Error Handling Fail Error Description Figure 3 14 Trace Step 3 6 Sample Flow Control Scenario This sample provides a programmatic equivalent between Error Handling using Retry and performing the retries in an iterative fashion The CRRCStateQuery step is used which looks for the RRCState to become RRCState_Connected with a maximum wait time of thirty second
3. About Test Manager X Test Manager Version 2 7 0 Build 331 Copyright 2008 2011 Spirent Communications Ine SPIRENT Delete Password p Poer ASA Trial Expiration Date Feature Version Add New Password Password Hard Lack Serial ID Add Import 48789 OF Export OO Figure 1 2 About Test Manager Window Installed Features Chapter One Introduction 3 Password authentication is a prerequisite to running any tests supported by these Test Packs This password is tied to security information provided by the USB hard lock dongle that comes with the module installation If you have any questions or concerns contact Spirent Technical Support at support spirent com or by phone at 1 800 SPIRENT 1 5 Accessing Documentation There are two ways to access this document from the Controller PC 1 Windows Explorer 2 Test Manager 1 5 1 Accessing Documentation from Windows Explorer Access this manual offline by opening the CS8 Development Library U folder and clicking the User Manual pdf shortcut as shown in Figure 1 3 ee CSS Development Library UI O E TA cy A Doe gt Folders Es Es X l m Address C APrograrm Files Spirent Communications Test Manager Modules 58 Development Library UI fo l ser Manual pdf 1 840 KE Adobe Acrobat Doc 2 10 2012 2 44 PM m Figure 1 3 Accessing the Manual from Windows Explorer 1 5 2 Accessing Documen
4. DLS E Configuration gt DLS Main SS LTE i NAS E eNodeBl eModeB PHY ConfigureCellldentity ConfigureRFChannel ContiqurePhysicallhannel LonhaureLychoPref LonfigureCovyriLink T ransr ConfigurePowerLevel LContigureb andwidth Configure ULP ower Control z ConfigureFosktionngA eter ContigureCellT rr elay Lontigurelil Reporting LonfgurelF Configure IE Specifics ear E MAC ALC a ARC H eModeB z ContigureLombined ttachProcedure z ConfigureLS FE Procedure H Configure easurementControl E UMTS E Channel mulator iva i El Misc AM NE rable False CNA atio 0 MaxAS TP nd P 135 Figure 2 9 Interactive Editor Multiple Configurations of SS Step 2 7 Step Subtype Hierarchy Steps are hierarchically grouped by several criteria in the following order 1 Step Type Refer to Section Step Types2 5 Example Interactive Step shown in Figure 2 6 2 Step Assembly The assembly DLL the step resides in Example DLSMain or DLTestCaseSteps shown in Figure 2 9 3 Step Namespace The hierarchy derived by the functional grouping of the steps Example Grouping technologies topological elements and protocol layers as shown in Figure 2 8 Chapter Two Using the Development Library Ul 11 2 8 Characteristic Step Properties There are several properties commonly seen among many steps 1 SyncTimeOut Designates the maximum period of time in seconds
5. Array DLT estase Logging uen D atas eres DLT estase Logging uen D atas eres StepPropertyH ames Enter the step and property name in order to display values on the chart Example OL5 55 LTE eNodeB 0 PHY PowerLevel ASTP Examole OLS 55 UMTS COMA CEN PHY TA ePower PowerLeyvel Figure 3 18 Procedure Chart Definition To configure the data series to be tracked over time follow the instructions below L 2 Select Logging gt BaseDLTestCase gt LoggingOuery Select StepPropertyNames Click the Add button The window shown in Figure 3 19 displays Under Co or select the color for the line Under Label type text for the label associated with the data series Under Name select the data series source typically a readable numerical public property of an API step This field expects a C C C style syntax Repeat Steps 3 through 6 if additional data series are needed Click OK Chapter Three Editing the Development Library UI 25 DataSeries Collection Editor ajx Members DLS 55 LTE eNodeb O PHY ConfigurePowerLeyvel ASTP properties EEN 2 4 DevelopmentLibraryServices 55 L a 2 E Misc Color BE Blue LTE Cell 1 Power Name DLS 55 LTE eNodeb 0 PHY ConfigurePowerLevel RSTP Position Middle gt Add Remove Figure 3 19 Data Series Properties 9 Under the SamplingPeriod select the sampling period in seconds 10 Click OK Step Parameter SamplingPeriod e Sa
6. Under Position select the vertical placement of the annotations 7 Repeat Steps 2 through 6 if additional event annotations are needed 8 Click OK Chapter Three Editing the Development Library Ul 27 DataSeries Collection Editor 0 Power z set to Color Figure 3 21 Annotation Properties At run time the procedural chart displays as shown in Figure 3 22 Tm Test Manager D d l y Session ses 2012 01 18 1030 Pl fv LTE Cell 1 Power fv UMTS Cell 1 Power Iv lv Events IP Time Marks W Figure 3 22 Procedure Chart at Run time 4 Running the CS8 Development Library Ul 4 1 Overview This chapter provides information on using CS8 Development Library Ul from 7est Manager This includes the following steps 1 Locating the Test Cases 2 Creating a Custom Test Suite 3 Configuring Test Case Parameters 4 Selecting the Parameter Files for Session Execution 5 Running a Test Suite 4 2 Locating the Test Suites and Test Cases 4 2 1 Locating Module Test Cases 1 In Test Manager under the 7est Folders tab open the Test Folders folder 2 Open one of the CS8 Development Library UI Test Pack subfolders This folder contains CS8 Development Library Ul modules such as the LTE UMTS Mobility Test Cases as shown in Figure 4 1 E 9 Suites H CSB Development Library UI Fy Development Library Ee LTE UMTS Mobility M ELTE UMTS Mobility H E SuiteFilet Lh 1 mu T
7. CS8 Developer Tem O of 1 0 O of 1 0 1 of 1 100 O of 1 0 HH MM SS 00 00 36 Pending Other Elapsed Time Session Events z Type PC Timestamp Description E Inform 3 7 2012 1 01 25 PM Connecting to platform Inform 3 7 2012 1 01 48 PM Started lt CS8 Developer Template gt fi 3 7 2012 1 01 51 PM Initial Conditions Executing Configuration Steps o 3 7 2012 1 01 51 PM Init Step 1 Starting execution O of 1 Test Cases Executed Result File 2012 03 07 1301 Originating Suite File SuiteFile1 sui Execution In Progress Figure 4 11 Test Session in Progress Chapter Four Running the Development Library Ul 35 5 6 C Start Session gt Y Validate Suite Success Failure Connect to the Instruments Success Execute Tests Failure Disconnect from Instruments C End Session 9 Figure 4 12 Test Suite Execution Flowchart At any point in the Test Case execution you can pause or abort the test as shown in Figure 4 13 Note that some blocking steps might not check for the pause command this means that test pausing may be delayed until after the step is complete Also note that some steps do not periodically check if they are paused they may continue to operate their worker threads You can either abort the current test case or the entire suite Note that we recommen
8. Library UI test case 1 Double click the CS8 Development Library Ul icon on the desktop as shown in Figure 2 1 2 Navigate to StartAll Programs gt Spirent Communications gt CS8 gt CS8 Development Library UI as shown in Figure 2 2 Development Library UI Figure 2 1 CS8 Development Library Desktop Icon Chapter Two Using the Development Library Ul 5 CE Spirent Communications F Air ccess WCOMA HS T Test Manager Figure 2 2 CS8 Development Library Ul Menu Navigation After the Test Manager executive GUI is opened select the Test Folders tab double click the CS8 Developer Template and select the first test case in the Suite Editor as shown in Figure 2 3 File Cabinet SuiteFile1 sui a Test Folders Tesi Fit C58 roan Library Ul 8 Developme CS8 Develo E 1 General bse na CS8 Developer Template Description E z UMTS WCDMA E 2 Initial Conditions zy LTE UMTS Mobility E Initial Steps 1 a Step 1 F E 3 Test Conditions S E TestSteps 1 E Step 1 k Descr Tima hle Figure 2 3 Opening a CS8 DL UI Test Case 2 3 Test Case Structure A test case is divided into five sections as shown in Figure 2 4 El 1 General Description El 2 Initial Conditions Bf Initial Steps a El Step T Description Type Configuration Subtype 55 Run Mode Normal Error Handling Fail Error Description El 3 Test Conditions Test Steps M 4 Test Functions Fun
9. T LL 1 Pa k Figure 4 1 LTE UMTS Mobility test pack Test Cases Chapter Four Running the Development Library Ul 29 4 3 Creating a Custom Test Suite To set up a custom Development Library Ul test you must first create a Test Suite To create a Test Suite 1 In Test Manager select File gt xNew gt Suite File as shown in Figure 4 2 ti Test Manager r m Session File Platform File UE File Close All UE File Selection Session File Selection Platform File Selection Results Path Selection Options erization A Save Ctrl 5 gnal Strength Save AS Signal Strength Save All Ctrl 5hift 5 Model PEJ Exit Alt F4 ng letwork Call Setup Mobile Originated Figure 4 2 Creating a New Suite 2 Youcan also use the toolbar shortcuts available to create a new file as shown in Figure 4 3 L Test Manager Figure 4 3 Creating a Suite File using the Toolbar Shortcut 3 A new Zest Suite window opens with a default file name This window allows you to sequence and arrange the tests 4 To add atest from an existing opened suite right click the test case select Copy and then Paste into a new Suite To add a test from the CS8 Development Library Ul Module drag or double click the desired test from the 7est Folders tab of the File Cabinet on the left and move it to the Suite File on the right as shown in Figure 4 4 30 CS8 Development Lib
10. tab select the Post build Event Command Line and insert the CS Development Library Destination folder as shown in Figure 5 5 Post build Event Command Line i x copy l TargetPathy C Program FilesiSpirent Communications Test Manager Modules cs8 Development Library UI Figure 5 5 Adding the Destination Folder 40 CS8 Development Library Ul User Manual 8 Inthe Classi cs make sure the source code uses the using statements and the class derives in this case from CConfig For action steps this would be CAction and for queries CQuery The constructor can be left empty 9 The public properties need to have both read and write capability to display as modifiable in the CS8 Development Library editor There are two properties in this case 10 In this case the Override Commit method performs power assignments The correct code is shown below using System using System Collections Generic using System Ling using System Text using DevelopmentLibraryServices using DLTestCase namespace StepClassLibrary public class MyCustomStep CConfig protected MyCustomStep base public MyCustomStep BaseDLTestCase tc base tc double lte Power 75 double umts Power 75 public double LTEPower get return lte_Power set lte_Power value public double UMTSPower get return umts_Power set umts_Power value public override DLSResultEnum Commit DLSRef SS LTE
11. well If the step succeeds during the retry attempts the step outcome is considered a pass R un h ode Normal Error Handling A etry w Number of Retre 1 Delay T Figure 3 5 Retry Options Step Parameters Number of Retries e Number of retries while the step fails Delay e Delay in seconds between the retries 3 5 FlowControl Steps FlowControl steps provide test flow management capability and closely emulate the control structures from traditional procedural languages Some of these steps require matching an End step to enclose the block of steps because the FlowControl constructs can be nested Type FlowControl Subtype walk l Sync TimeOut CallFunction Run Mode Error Handling Error Description Shep El Step Description Type Subtype Run Mode Error Handling Error Description TRACE Fl Stent Figure 3 6 FlowControl Subtypes 1 CallFunction This step is used to invoke a function a named set of steps The FunctionName has to match the name of the function or it can be a numerical index starting from 1 of the function in the Functions section The option Blocking determines the mode of invocation True for blocking and False for non blocking in this case the test execution engine proceeds to the next step without waiting for a function to complete 16 CS8 Development Library Ul User Manual Step Parameter e Name or index of the Function to call FunctionName Blocking e True invok
12. 7 to UMTS Compressed Mode UDP Initial Steps 5 i slab l ee 7 CS8 Developme CS8 Develo Handover UMTS 2 to LTE 4 to UMTS Compressed Mode FTP gt n sr r Handover UMTS 5 to LTE CS8 Developme CS8 Develo Handover UMTS 2 to LTE 17 to UMTS Compressed Mode FTP a are g m Handover UMTS 5 to LTE CS8 Developme CS8 Develo Handover UMTS 5 to LTE 4 to UMTS Compressed Mode FTP pene je mns Handover UMTS 2 to LTE CS8 Developme C58 Develo Handover UMTS 5 to LTE 17 to UMTS Compressed Mode FTP E 5 Test Criteria r Handover UMTS 2 to LTE CS8 Developme CS8 Develo Handover UMTS 2 to LTE 4 Cell Not Available Compressed Mod E xecutionLi Iterations wa Handover UMTS 5 to LTE CS8 Developme CS8 Develo Handover UMTS 2 to LTE 1 Cell Not Available Compressed Mo iterations 11 r Handover UMTS 5 to LTE CS8 Developme CS8 Develo Handover UMTS 5 to LTE 4 Cell Not Available Compressed Mod MaxFailureF 10 r Handover UMTS 2 to LTE CS8 Developme CS8 Develo Handover UMTS 5 to LTE 1 Cell Not Available Compressed Mo EarlvTermin True ra Handover UMTS 2 to LTE CS8 Developme CS8 Develo Redirection UMTS 2 to LTE 1 Blind UDP l r Handover UMTS 5 to LTE CS8 Developme CS8 Develo Redirection UMTS 5 to LTE 1 Blind UDP C58 Developme CS8 Develo Redirection UMTS 2 to LTE 4 Blind UDP Test Folders REE RR RR M Result Files HB
13. S8 Development Library Ul User Manual M Stepi Descr Type Configuration Run h Normal Error t Fail Error File Figure 3 2 Step Subtypes 3 4 Step Execution Properties 3 4 1 Run Mode These step options determine the mode of execution of steps at run time 1 Normal The step is executed 2 Skip The step is skipped 3 Break This option is intended for debugging purposes The Step editor GUI displays and you can execute a step by clicking the Execute button The test case is effectively paused until you click Execute After closing the GUI the test resumes Mormal Run M ode Figure 3 3 Run Modes 3 4 2 Error Handling This option determines what type of error handling is applied if a step fails as shown in Figure 3 4 Error Handing F ail z Error Description aa 4 Test Functions Continue 5 Test Criteria Figure 3 4 Error Handling Modes 1 Fail Ifa step fails because of invalid parameters or functional reasons the test case will be stopped at that point and marked as failed 2 Continue Step failure is ignored and the test case proceeds to the next step Chapter Three Editing the Development Library Ul 15 3 Break This mode is used for debugging purposes The step editor GUI displays and you can view and change other system properties 4 Retry You are presented with two additional options shown in Figure 3 5 If the final retry fails the step and test case fail as
14. Scenario essesssesseseseeseseseoscsescoscseseseoecseseosesees 21 3 7 Charting and Annotation St p ssssessessssoseseosessoseseoseosesesecseoseseosesee 24 Running the CS8 Development Library Ul sscccsssccssccsssccssscoees 28 Al OW OIVICW erore AAEE AEAEE EOE ENG 28 ii CS8 Development Library Ul User Manual 4 2 Locating the Test Suites and Test CaSe S ccccsccecssecsscscescscesceese 28 42 LocatnoMoaul Fest COSCS seeen n E E RE ENE 28 Ao Creatina a Custom Test SUIE cause oa saunu ssebece 29 4 4 Configuring Test Case Parameters ccccscsscscsccscecsseecsccececeseecesees 31 Ld ROman a TeS UE a E EA ena 32 4 6 Selecting the Parameter Files for Session Execution 33 5 Creating Custom CS8 DL Ul Steps csccccssccssccssccsssccssccssccssceecs 36 Delis TOV GIVI CW oer EEI E E 36 5 2 Creating a Custom Step Interactively o0 o0eeores 36 5 3 Creating a Custom Step Project ccsccsccsscsccsscescsscescscesccecesceecens 37 1 Introduction ee 1 1 Overview This document provides information on the CS8 Development Library Ul module You will become familiar with using the CS8 Development Library UI by following step by step procedures 1 2 Intended Audience This manual is intended for those who have a working knowledge of wireless communication equipment and the automated testing of mobile dev
15. To create a new ncf file enter a desired file path for the new file and click the Subtype to input the settings After making the changes click OK and the settings are written to the file To use an existing file follow the instructions for creating a new file In this case the existing ncf file is overwritten after you click OK Initial Steps 5 El Stepi Configure Network Description Configure Network Type Contiguration Subtype 55 js Run Mode Morral Error Handling Fail Error Description File C Program Files Spirent Communications T est Manager Sutes4LTE UMTS Mobility_nct Figure 2 11 SS Network Configuration Parameter Initial Conditions 3 Editing the CS8 Development Library Ul 3 1 Step Editing These step options determine the mode of execution of steps at run time 1 Selecting the Step Type 2 Selecting the Subtype 3 Selecting the Execution Options 4 Selecting the Error Handling Options 3 2 Selecting the Step Type Select the Step Type from the ype field as shown in Figure 3 1 HM Step 7 Description Action Subtype Mor Run Mode Action Error Handling Configuration Error Description FlowlLontral 4 Test Functions fteractive 5 Test Criteria Logging Query Figure 3 1 API Step Types 3 3 Selecting the Step Subtype Select a specific step API from the Subtype field as shown in Figure 3 2 This initiates a wizard that allows you to set specific APIs and settings 14 C
16. a SPIRENT CS8 Development Library UI User Manual SS Spirent 541 Industrial Way West Eatontown NJ 07724 USA Email sales spirent com Web http www spirent com AMERICAS 1 800 SPIRENT 1 818 676 2683 sales spirent com EUROPE AND THE MIDDLE EAST 44 0 1293 767979 emeainfo spirent com ASIA AND THE PACIFIC 86 10 8518 2539 salesasia spirent com This manual applies to CS8 Development Library Version 1 30 or higher Page Part Number 71 006746 Version A1 Copyright 2012 Spirent All Rights Reserved All of the company names and or brand names and or product names referred to in this document in particular the name Spirent and its logo device are either registered trademarks or trademarks of Spirent plc and its subsidiaries pending registration in accordance with relevant national laws All other registered trademarks or trademarks are the property of their respective owners The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent The information in this document is believed to be accurate and reliable however Spirent assumes no responsibility or liability for any errors or inaccuracies that may appear in the document Table of Contents 1 Moda cOn eE E EEEE EEES 1 E OVC OW ee caus cusscaseasacequscesneasseccueancanssseueneecsanseces 1 T2 Merde d Aude sence sec secea E A S 1 1 3 Before VOU Gel Started osc csecusscee
17. a step is allowed to complete If the set time is exceeded the step fails Blocking Designates if test case execution proceeds with the next step while the current step is executing This property is only available in steps that support concurrent execution Done Property that indicates if a step has completed as a get It also forces premature completion of the step as a set Usually this is associated with non blocking steps Error Read only property of a Query step that indicates that a query has failed The error may be due to either the system state not being ready or the property being retrieved with a value that does not match requested criteria Note that an Error only applies after the Done parameter displays True nix DLS Query F OLSMain amp ss El Misc H LTE Blocking True H UMTS Done False H ChannelE mulato Error True o E oreMetwork RAN Mame Cell 1 F UE Utils RegistrationT ype Register E DLTestCaseSteps sync TimeOut 600 Transfery CRegister very Figure 2 10 Common Step Parameters 12 CS8 Development Library Ul User Manual 5 File Optional property of the first SS Configuration step in the Initial Conditions This property refers to the external network configuration file ncf that contains shared settings between different test cases and suites If left empty the step settings are stored locally in the suite as all the other steps This is the default setting
18. bly name is derived from the class name itself and should display in the editor tree view hierarchy in the next Test Manager session To create a custom step 1 Insert the interactive step in the suite 2 Run the suite 3 When the nteractive Step Editorwindow displays select the C tab 4 Make changes to the source code in the edit box and click on the Execute button If there are no compilation and runtime errors the effects should be observed in the status window on the bottom of the GUI and in the example below in the CS8 Interactive Tester Figure 5 7 Chapter Five Creating Custom Steps 37 HE CS8 Development Library UI Tester MainWindow O x ung System Windows Forms using Buster er using DevelopmentLibrans ervices using OLTestlase namespace DLT estlase public class ExternalStep CContig i protected ExternalStep basel i public ExternalStep BaseDLT estlase te base te i I public override OLSAResultE num Commit i DLSRefS5 LTE eNodeB 0 PHy PowerLevel AS TP 75 DLSRef S5 LTE eNodeB 0 PHY PowerLevel Corn DLSReh SS UMTS WCDMA Ce PH T From PowerLeyvel 75 DLSRet SS UMTS WCOMA Cel PHY TA sPower Commi return OLSAesultEnumOLS SUCCESS Save step Execute Figure 5 1 Interactive Step Generation Editor 5 3 Creating a Custom Step Project This section provides instructions on developing custom CS8 Development Library UI steps using Microsoft Visual Stud
19. ctions n Figure 2 4 Test Case Sections 1 General Contains a short description of the intended functionality of the test case 2 Initial Conditions Contains steps executed prior to call processing being enabled The first step is System Settings SS used to configure multiple network settings These configurations can then be shared among different test cases and suites through an external ncf file 6 CS8 Development Library Ul User Manual 3 Test Conditions Contains steps after the call processing has started and constitutes the main test flow of the case 4 Functions Contains the set of functions which are steps grouped by functionality These steps can be accessed from any point in the Initial Test or Function sections of the test case 5 Test Criteria Contains the settings for the pass fail criteria when test case is executed more than once for statistical confidence purposes 2 4 Step Structure APIs executed as steps have several common parameters and a number of proprietary parameters specific to each one of them given their respective functionalities Common step properties determine parameters shared among all the steps Step Parameter Description Description e Short description of what this specific instance of the step with its parameters is functionally intended to perform Type e The type of step per nomenclature described in 2 5 Subtype e The specific type class of t
20. d aborting the test case between step executions to ensure the coherency of the system If there is blocking step that does not periodically check for the abort command it is forcefully aborted after a short grace period Execute Report Help Validate SuiteFilel sui 201270309 12 je Start Session Pause Session Stop Session All Test Cases Current Test Case Figure 4 13 Pausing Aborting the Test 5 Creating Custom CS8 DL UI Steps Dl P Overview This chapter provides information on how to develop custom CS8 Development Library UI APIs that can be edited and executed by the CS8 Development Library Ul In general any assembly containing classes that inherit from Development Library Services or CS8 Development Library UI a certain set of interfaces can be recognized by the editor and the engine This chapter includes the following steps 1 Creating a C class library interactively 2 Creating a C class library project 3 Adding references to CS8 Development Library assembly 4 Deriving from one of the step type specific parent classes 5 Overriding some of the method and properties 6 Testing the step Creating a Custom Step Interactively This section provides information on developing a custom step during an interactive session It is intended for system debugging and rapid prototyping of light weight steps You can save the custom step by selecting the Save Step option The assem
21. device was used to generate the results Tm Test Manager File Edit 4 Click OK to begin execution If successful the test session begins as shown in Figure 4 11 Me x View Execute Report Help a A hb M B Z UEue 4 Session ses D ag File Cabinet FE La Suites ww 4 a x 7 4 CS8 Development Library UI FZ Development Library E i LTE UMTS Mobility E LTE UMTS Mobility LTE UMTS Mobility ma Handover md Handover ed Handover ha Handover hd Handover eed Handover gd Handover md Handover md Handover gd Handover md Handover md Handover md Redirection hd Redirection EG SuiteFilet ed CS8 Developer Template gd Redirection gd Redirection h Redirection ga Redirection gd Redirection i Redirection UMTS 2 to LTE UMTS 2 to LTE UMTS 5 to LTE UMTS 5 to LTE UMTS 2 to LTE UMTS 2 to LTE UMTS 5 to LTE UMTS 5 to LTE UMTS 2 to LTE UMTS 2 to LTE UMTS 5 to LTE UMTS 5 to LTE UMTS 2 to LT UMTS 5 to LT UMTS 2 to LT UMTS 5 to LT LTE 17 to UM LTE 4 to UMT LTE 17 to UM LTE 4 to UMT SuiteFile1 sui 720120307 1301 Active X Summary LTE UMTS Mobility sui Dashboard Test Folder C58 Development Libr Executing Indicator Test Description Test Case Test Status Fail Pass Percentage
22. e and wait for function to complete e False just invoke and proceed to the next step E Step 7 Description Type FlowControl Subtype CallFunction Function anne Func Blocking True Run Mode Morral Error Handling Fall Error Description 4 Test Functions Functions E Function 1 Furic Name Funct H Function Steps I Step Figure 3 7 Functions 2 Wait This step waits for SyncTimeOut number of seconds until proceeding to next step Any worker threads of already invoked steps are not affected Step Parameter SuncTimeOut e Delay in seconds can be a fractional number 3 If Then This step has the condition as an input parameter that can be an expression that evaluates to true or false The condition expects C C C style syntax Note that End step is mandatory to enclose the block of steps and Else step is optional The IfThen can be nested each enclosed having its own End statement Examples of Condition parameter are shown in Figure 3 8 a Else This is an optional step under IfThen and encloses the steps executed when a False result is recorded Chapter Three Editing the Development Library UI 17 Step 7 Description Type FlowControl Subtype IFT hen Condition true Run Mode Normal Error Handling Fail Error Description Step El Step 3 Description Type FlowControl Subtype Else Run Mode Normal Error Handling Fail Error Description El Step 4 Description Type FlowControl Subt
23. eNodeB 0 PHY PowerLevel RSTP lte Power DLSRef SS LTE eNodeB 0 PHY PowerLevel Commit DLSRef SS UMTS WCDMA Cell O PHY TxRxPower PowerLevel umts Power DLSRef SS UMTS WCDMA Cell 0 PHY TxRxPower Commit return DLSResultEnum DLS_ SUCCESS Chapter Five Creating Custom Steps 41 12 Build a solution 13 Make sure that the dll file is present in the C Program Files Spirent Communications Test Manager Modules CS8 Development Library UI folder 14 In Test Manager create a new suite from the CS8 Developer Template and insert the new configuration step in the Initial or Test Conditions section The nteractive Editor should display the information shown in Figure 5 6 15 Click OK nix DLS E Configuration H DLS Main F DLTestCaseSteps E StepllassLibrary a hp Custom tep TE O Misc LTEFower 75 UMTSPower Z5 LTEPower OF Cancel Figure 5 6 Custom Step Properties 16 Run the suite and ensure that the value of the RSTP parameter has changed in the CS8 Interactive Tester GUI as shown in Figure 5 7 El Downlink Configuration ae Cell Timing Delay Ts OU CFI 2 Cyclic Frefix normal Downlink EARFCN 5230 Frequency Band 13 Physical Cell IC 1 RSTF dB rl f5 0 Tranemission Mode Single Antenna UE Spectic Search Spac amp Figure 5 7 CS8 Interactive Tester GUI
24. ead only may show warning messages instead of values This is an indication that the values are not ready to be retrieved in edit mode nix DLS E Configuration DLSMain E 55 E LTE AW GNEnable False NAS CMRatio n E eModeB MaxASTP 74 O E eNodeB is TP Hm 1 v FH a ConfigureCelll dertity LContigureAF Channel LontiqurePhysicallhannell z LonfigureLychoFrefix z ConfigureD ownLink T ransn 7 ConfigurePowerLevel Figure 2 8 Interactive Editor Selecting API Parameters and Values e After one or more parameters of an API have been changed the OK button becomes enabled and the values are stored If the button is not enabled temporarily select any other property Note that only one API with multiple parameters can be stored for each step The exception is the first Configuration SS step in the Initial Conditions section The SS step can store multiple API settings at the same time and you can load or store them with an external file as shown in Figure 2 8 e Forthe configuration steps select the check box corresponding to the changed property to indicate that changes will be saved into the suite file The property value can always be explicitly saved even for the ones that have not changed by selecting the corresponding check box This is useful in the cases where the property values are changed indirectly by another step or as part of a later step 10 CS8 Development Library Ul User Manual alo x
25. elopment Library UI folder and click the Browse tab Add the following references a C Program Files Spirent Communications Test Manager Modules CS8 Development Library UN DLTestCase dll b C Program Files Spirent Communications Development Library Services bin DevelopmentLibraryServices dll c C Program Files Spirent Communications Test Manager Manager TestCaselnterface dll d System Windows Forms Chapter Five Creating Custom Steps 39 MET COM Projects Browse Recent Look in C58 Development Library Ul 5 CF i DevelopmentLibrary Services dll ki Instrumentintert DevLibbatalnterface dll Interop SECURIT DLSUtilities dll PropertyGridex d DLTCInstallUtils dll QueryResultPane O TestCase dl ResultsTableDetz DLTestCaseDependency dll Spirent beyeloprr S DLTestCaseSteps dl Spirent Deyeloprr DLTestCase Wizard exe Spirent Report Le File name Files of type Figure 5 3 Add Reference Window 4 Right click the Project Node and select Properties 5 Inthe Properties window select the Applications tab 6 Under Zarget Framework select NET Framework 3 5 as shown in Figure 5 4 This ensures that the assembly references the Net CLR that is already present on the target system Application Configuration W A hj Build Assembly name Build Events StepClassLibrary Debug Target Framework Beer eres Figure 5 4 Selecting Target Framework 7 Underthe Build Events
26. erived from the state of the system is met Queries do not alter the state of the system Logging These steps are used to log acquired data over time in memory and in some cases log to files as well Logging steps do not alter the state of the system FlowControl These steps are used to alter the flow of the test The common flow control steps are supported such as checking conditions looping calling functions error handling tracing etc Interactive This is general purpose step from which you can execute any API step Interactive steps are primarily used for debugging purposes The Interactive step type is shown in Figure 2 6 8 CS8 Development Library UI User Manual Configuration F Action Query Ee Logging BC Execute Figure 2 6 Main Window Interactive Step 2 6 Step Subtypes Within the step type categorization described in Section 2 5 you can select individual APIs through the Step Subtype field as shown in Figure 2 7 The GUI editor displays the subtypes You can select the types and parameter values which are replayed at run time M Stepi Descr Type Configuration Subty MT Run k Mormal Error t Fail Error File Figure 2 7 Step Subtypes The following list explains how to work with Subtypes e Steps shown in bold font have altered parameters relative to previous state of the system Chapter Two Using the Development Library UI 9 e Parameters that are r
27. eussubesecssoenuestcosvcassnesosoncoveesseuvineasanescess 1 1 4 Security INTOTMMGION 1 ccscasessnsaaneynosanveheouenatesesuteseuesdercecusssceaeenssaxtencates 1 1 5 ACCESSING Documental sascantessensnieesauceus ea nE S 3 1 5 1 Accessing Documentation from Windows Explorer ccceescesssceesceseees 3 1 5 2 Accessing Documentation from Test Manager ccsssccssccssccnescesscensceess 3 Using the CS8 Development Library Ul esseeseccseecsecseecseecseessecseecseesoe 4 Dida 61 p1 RP E E EE NA EEEE E E 4 ZF DEPU OI enner a E ES 4 2235 TESTCASE SCPC CUI G aerer E E E E T 5 DM STOP SUC errer irane E E a E a 6 Pe SLED IV E E P E E T E E A 6 2e D UDNES aa E N AE AE AE EEE OEE OE 8 2 7 Step Subtype Hierarchy sssssessessesesecsesecseeecseorcseoseseoseoseseseoseoreseeeese 10 2 8 Characteristic Step Properties ssisssssssisiscrrcssissssasinscsicssrsessacenccoiasssssis 11 Editing the CS8 Development Library Ul cccsssccssssccsssccessscoeees 13 Dede SUC CIM RST O P O A E 13 2 2 Selecting THE SLED FY DC veces sscctavoscwscsssescosceseutoesesaceensesadaswsnsseyntesensaeees 13 3 3 Selecting the Step Subtype e ssssssseeesssseseosessoseesoseseoseoscseseeseoseseosesee 13 ZA SlEDEXCCUUON PION GIES wicceceyesatccecoascaceraccsntescasssnteaeneea seseveesevacersss 14 eile TRU MOG eee E E 14 FAs 440 TION GHG PPOR O EE EE NEEE 14 35 FLOW GOI Ol SIEDS errori srren SETE E E EET TN 15 3 6 Sample Flow Control
28. he step as described in 2 6 Run Mode e Mode of execution of the step Error Handling e Mode of handling the step failures Error Description e Incase the step fails a custom message that gives additional info on context or possible probable cause 2 5 Step Types The APIs executed as steps shown in Figure 2 5 are classified into several categories based on their perceived usage and impact on the system They reflect the API hierarchy of the Development Library Services and other compatible API assemblies El Step Description Action Subtype Run Mode Error Handling Configuration Error Description FlowLontrol 4 Test Functions 5 Test Criteria Interactive Logging Query Figure 2 5 API Step Types Chapter Two Using the Development Library UI 7 None This is an empty step used as placeholder until you select a step type subtype and other parameters During run time it has no functional effect Configuration These steps allow you to configure the parameters of the system and its underlying components Actions These steps allow you to perform simple or complex procedures In some cases the procedures can take time to complete Actions can be executed while you are performing the consecutive steps Query These steps intended to retrieve the state of the system and are used with different capacities You can retrieve a specific property of the state of the system and check if a certain aspect or condition d
29. ices It is assumed that you are familiar with the Zest ManagerGUI environment Those who are unfamiliar with the Test Manager should refer to the Zest Manager User Manual before proceeding 1 3 Before You Get Started Before getting started with this guide install all software and power up the test system The controller PC should have Jest Manager Test Executive Development Library Services and their respective prerequisites installed For Development Library Services prerequisites such as the B series platform consult the Development Library Services User Manualand Platform User Manual These documents can be found under the Test Manager Help menu 1 4 Security Information The CS8 Development Library UI is shipped with the appropriate dongle and software hardware security passwords configured To verify the security information 1 Open Test Manager and select Help About The About Test Managerwindow displays as shown in Figure 1 1 2 CS8 Development Library Ul User Manual About Test Manager i x Test Manager Version 2 7 0 Build 331 Copyright 2008 2011 Spirent Communications Ine i Test Folders Building Blocks Platforms Passwords Test Folders Location C58 Development Library UI SPIRENT Versione Figure 1 1 Test Manager About Window 2 Select the Passwords tab 3 Under Installed Features confirm the CS8 Development Library Ul is installed as shown in Figure 1 2
30. iguration 55 Gi Normal Fail Mone Normal F all Iterations 1 10 EarlyT erminationE nable True Subtype Launches the editor to configure the current step selling corresponding to the step type Figure 4 7 Configuring Test Case Parameters 3 Select the appropriate parameters for the test 4 Save all changes to the Suite File The custom Suite File displays in the file cabinet as shown in Figure 4 8 32 CS8 Development Library Ul User Manual rm Test Manager File Edit wiew Execute Report H D G aal nnl File Cabinet E E Suites H C58 Development Library UI F E Development Library H E SuiteFilet Figure 4 8 Customized Suite Saved to the File Cabinet 4 5 Running a Test Suite To run the test suite 1 Inthe Test Manager open the desired test suite from the Suite Files tab of the File Cabinet as shown in Figure 4 9 l0lxl Fie Edit View Execute Report Help PM E MAM p 4 Session ses E ad Suites Description HL CS8 Development Library UI is t Developme Develo Handover UMTS 2 to LTE 4 to UMTS Compressed Mode UDP E 1 General H Development Library CS8 Developme CS8 Develo Handover UMTS 2 to LTE 17 to UMTS Compressed Mode UDP Description Redirection U H LTE UMTS Mobility CS8 Developme C58 Develo Handover UMTS 5 to LTE 4 to UMTS Compressed Mode UDP E 2 Initial Conditions ku sd i CS8 Developme CS8 Develo Handover UMTS 5 to LTE 1
31. io 2010 IDE This approach gives you greater control over the attributes of the project and better debugging capability To create a custom step project 1 Open Visual Studio DE and select FilexNew gt Project The New Project window displays as shown in Figure 5 2 2 Select a Visual C Class Library project 38 CS8 Development Library Ul User Manual New Project x Recent Templates J NET Framework 3 5 Sort by Default E Search Installed Templat O Installed Templates Type Visual C F Visual Basic zc Windows Forms Application Visual C A project For creating a C class library dll E Visual Ci Windows S WPF Application Visual C Web Office P Console Application Visual C Cloud Reporting 7 Class Library Visual C SharePoint e s 2 Silverlight c WPF Browser Application Visual C Test WCF c Empty Project Visual C Workflow Visual C E Windows Service Visual C F Visual Fi H Other Project Types c WPF Custom Control Librar Visual C Database Test Projects WPF User Control Library Visual C ech Online Templates ch Windows Forms Control Library Visual C Name StepClassLibrary Location C projects v Browse Solution name StepClassLibrary Create directory for solution T Add to Source Control pK cancel Figure 5 2 Creating a New Project 3 Inthe Add Reference window shown in Figure 5 3 select the CS8 Dev
32. l requirements of the steps in the test case As indicated in the 7est Manager User Manual the session execution cannot guarantee a successful run of the suite unless valid Platform Session and UE Parameter files are specified To specify Parameter Files for a Test Suite U In the Execute Session window select the Session File the UE File and the Platform File After selecting the Platform File select the Platform as shown in Figure 4 10 Execute Session Tester Hame Tester 1 UE Manulachwer Manufacturer A UE Modet Moda Rests Folder Selection C Resuts 7 Session Fle Selection C Program Files Sp Sessionsfilel oes C UE File Selection C Program Fies Spient C_AUEFiet ue Je Platiom Fle Selection C Program Fies Spi Platom det ohm Ca Flationm Selecion S100 8 Sense C Peron Validation C Test Connective Weny the settings ane caed for each Ted the zbran conmectons for bazi Cane each bast care Indicates Required Field Cancel Figure 4 10 Execute Session Window Selecting Parameter Files Select the appropriate parameter files and platform 34 CS8 Development Library Ul User Manual 3 The Tester Name UE Manufacturer and UE Model provide details about the testing performed These fields display on all reports you create based on the results of the session We strongly recommend that you utilize these fields If they are left blank it can be difficult to identify which
33. mpling period in seconds to read the values Color e Color of the line for the data series Label e Text of the label corresponding to the data series Name e The source step property for the data series e The substring of the text of the trace message for annotations Position e The placement of the vertical annotations Annotation settings shown in Figure 3 20 configure the occurrence of the events on the chart Shown in vertical green text You must associate text of certain trace messages and assign it a label 26 CS8 Development Library Ul User Manual El Spirent interactive Editor DLS El Logging DLSMain E BaseDLTestCase 1 LoggingQuery False F DLTestCaseSteps False DataSernes Array DL Test ase Loggingluern DataS eres Options SamplingFeriod StepFroperty ames DataSernes Array HessageAnnotations Enter unique substring of the step message in order to display annotations on the chart IE sample PowerLevel AST AlEsample TxA ePower PowerLe Figure 3 20 Annotation Settings To configure Annotation settings 1 Select MessageAnnotations 2 Click the Add button Under Co or select the color for the line Under Label type text for the label associated with the data series 5 Under Name select the unique substring text of the trace message The trace messages considered are the Development Library Services DLSLogging DLSFilter USR_EVENT type 6
34. n of For Loop Step Parameters Iterations e Max number of iterations Iteration e Read only the current iteration value Chapter Three Editing the Development Library Ul 19 HM Step Description Type FlowControl Subtype For Iterations 2 Run Mode Morral Error Handling Fail Error Description Steeple E Step 3 Description Type FlowControl Subtype End Run Mode Morral Error Handling Fail Error Description Figure 3 10 For Loop Step 6 AbortStep This step shown in Figure 3 11 is used to end the execution of any step by index in the current execution section of the test case Step HM Step Description Type FlowControl Subtype AbortStep Stepl rides Run Mode Morral Error Handling Fail Error Description Figure 3 11 Abort Step 7 Try This step shown in Figure 3 12 is used to enclose a block of steps capture the fails or exceptions on those steps and redirect the execution to the Catch End section of steps a Catch Associated with the Try step 20 CS8 Development Library Ul User Manual El Stepi Description Type FlowControl Subtype Try Run Mode Normal Eror Handling Fail Error Description Step 2 H Step Description Type FlowControl Subtype Catch Run Mode Normal Error Handling Fail Error Description Step 4 H Step 5 Description Type FlowControl Subtype End Run Mode Normal Error Handling Fail Error Description Figure 3 12 Try Catch Step
35. r Handling Error Description Step 15 Description Type Subtype Run Mode Error Handling Error Description Step 16 Description Type Subtype Condition Run Mode Error Handling Error Description Shep Description Type Subtype Return alue Run Mode Error Handling Error Description Step 18 Step 19 Description Type Subtype Sync T imel ut Run Mode Error Handling Error Description Shep 0 FlowControl For 2 Morral Fail FlowControl Try Morral Fail Quen LTE RAC State Query LTE RRC State Query CHRAStateQuery Normal Fail FlowControl Catch Normal Fail FlowControl IET hen ForjStep 12 _lteraton Morral F ail FlowControl Heturn False Normal Fail End IFT hen FlowControl Wat a 1 Morral Fail End TryCatch End For Figure 3 17 Error Handling Programmatic Retries 24 CS8 Development Library Ul User Manual 3 7 Charting and Annotation Step The LoggingQuery step provides logging settings for the procedural chart that can display any APIs numerical property value as a data series over time It also provides a way for you to of annotate certain events usually captured from the Development Library Service trace messages nix DLS E Logging H DLSMain BaseDLTestCase Misc ke LeggingQuery Blocking False F DLTestCaseSteps Done False Messagednnotatons DataSenes Array Options SamplingPerod StepProperty ames DataSenes
36. rary Ul User Manual File Cabinet 5 U C58 Development Library C58 Developer Templa ira JE 20 Des relo per T emplate E E UMTS WCDMA z LTE UMTS Mobility Test Folders Figure 4 4 Successfully Transferred Test Case de Cut CEF 3 Copy Ctrl C i Faste Ctrl Delete Ctrl D Select All Ctrl 4 Create Test Case Ctrl T Y Loop Test Case CEF Figure 4 5 Copy Paste Test Case 5 Configure the parameters for each Test Case based on your testing needs The steps can be Copied Pasted Moved and Deleted by right clicking on the Test Case name and selecting an option from the menu shown in Figure 4 6 Cut tr Copy CEF Faste Ctrl Move Up Move Down Insert Delete Expand Ctrl E Expand All Ctrl 4 Reset Property Figure 4 6 Copy Paste Menu Chapter Four Running the Development Library Ul 31 4 4 Configuring Test Case Parameters 1 In Test Manager under the Parameters tab select the desired Test Suite 2 Inthe Su te Editor select the Test Case to configure as shown in Figure 4 4 Tes M 1 General Description L 2 intial Conditions m Initial Steps E Step Description Type Subtype Run Mode Error Handling Error Description El 3 Test Conditions H Test Steps E Step Description Type Run Mode Error Handling Error Description El 4 Test Functions Functions El 5 Test Criteria E secutionLimit Iterations MaF allurePercentage 1 Conf
37. s After the condition is met the Done property displays a True value and depending on if the RRCState is Connected the Error becomes False or True In case the step fails because of a timeout or condition not being met the test case execution engine tries two more times with a three second delay The third try determines the final outcome of the step and the test case In x DLS E Query F DLSMain El DLTestlaseSteps CTransterQuery e CRegisteruery z True M CRRStateQuery setRACS tate RACState_Connected CActiveSetQuery syncT imeut 30 z QuenLavenshessagel Done QuenLTEResultQueu Indicates if the step has completed get or forces completion of m the step set OF Cancel Figure 3 15 Query Step Settings 22 CS8 Development Library UI User Manual HM Stepi Quen LTE RAC State Description Query LTE RRE Ste Type Query Subtype CHAStateQuery Aun Mode Morral Error Handling Retry Humber of Reties 2 Delay 3 Figure 3 16 Error Handling Two Retries and Three Second Delay The same scenario using explicit For loops Waits Try Catch IfThen Else and Return steps Chapter Three Editing the Development Library UI 23 UH Step 1 2 Description Type Subtype Iterations Run Mode Error Handling Error Description Step 1 3 Description Type Subtype Run Mode Error Handling Error Description Shep 4 Description Type Subtype Run Mode Ero
38. tation from Test Manager Access this Manual from the Test Manager menu by selecting Help gt Test Folders gt CS8 Development Library Ul User Manual as shown in Figure 1 4 mm Test Manager File Edit View Execute Report Help 07 GG I B EENE MRES Test Manager 4 Session ses k Test Folders Test Folders C58 Development Library UI FT User Manual Platforms Development Library ont i a r k k Report Engines r Cont About Figure 1 4 Accessing the Manual from Test Manager 2 Using the CS8 Development Library UI nn 2 1 Overview This chapter provides a high level overview of the key concepts involved in configuring the CS8 Development Library Ul and associated test packs This includes the following e Test Case Structure e Step Structure e Step Execution and Error Handling Options 2 2 Description The CS8 Development Library UI Module is an integrated software component that allows you to perform interactive and automated testing of an UE device The CS8 Development Library UI module test cases run with Test Manager software This provides an easy way to automate test sessions with analysis and reporting capabilities CS8 Development Library Ul provides a Graphic User Interface GUI and an automated Development Library Services API that abstracts the interfacing to the B Series platform instruments and UE oriented peripherals There are two ways to open a CS8 Development
39. ype End Run Mode Normal Error Handling Fail Error Description Figure 3 8 IfThen Step Condition Parameter DL2 Error e Outcome of the last step executed IQueryStep DL2 Step 1 Error e Outcome of the query at step 1 DLS SS LTE eNodeB 0 PHY ConfigurePowerLe Check for specific step parameter value vel RSTP 85 For DL2 Step 1 Iteration e Check for For Iteration parameter value at Step 1 4 End Enclosing step for each IfThen Else For and Try Catch constructs as shown in Figure 3 9 18 CS8 Development Library Ul User Manual O Step Description Type FlowControl Subtype IET hen Condition true Run Mode Morral Error Handling Fail Error Description O 5Stepl lt Description Type FlowControl Subtype IET hen Condition true Run Mode Morral Error Handling Fail Error Description Sheps Step 4 Description Type FlowControl Subtype End Run Mode Normal Error Handling Fail Error Description O Step Description Type FlowControl Subtype End Run Mode Normal Error Handling Fail Error Description Figure 3 9 Enclosing End Steps 5 For Performs the Loop Over step on the block of statements enclosed with the End step The For loops can be nested with each construct enclosed with its own End statement The Break and Continue steps described below are optional a Break This step is used to exit the For Loop b Continue This step is used to skip the rest of the steps in one iteratio
Download Pdf Manuals
Related Search