Test Management Extension User Guide
Contents
1. the column is not listed underthe Plugins Columns in the Requirement View If the tag is enabled value of 1 or if value is empty the column is listed Default value if tag not used 1 4 2 4 4 RunStatusLastColumn This section contains the tags used to set the name of the Run Status la st Column see section 3 3 3 and whether it is enabled or not 4 2 4 4 1 lt Name gt and Enabled The tag Name is used to set up the name of the Run Status las Colum This name is used as the column name in the Requirements View If the tag is empty the default name is used IRQA Test Management Extension December 2011 www visuresolutions com 30 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company Default value if tag not used Run Status last Plugins Columns Hun Status last The tag lt Enabled gt tells the module to enable the column ornot If the column is disabled value of 0 the column is not listed under the Plugins Columns in the Requirement View If the tag is enabled value of 1 or if value is empty the column is listed Default value if tag not used 1 4 2 4 5 lt RunStatusFullColumn gt This section containsthe tags used to set the name of the Run Status full Column see section 3 3 4 and whether it is enabled or not 4 2 4 5 1 lt Name gt and Enabled The tag Name is used to set up2. myArgument The second type of arguments is the test run object argument This argument is set via a test run TEXT attribute This argument isapplied to the individual scripts associated to the test run object Code Mame RQA Arguments lt l TS 0010 1 Locking connector usage L T5 0010 Runs 1 Locking connector usage Results myTesktRuna rgument 6 Ts_0070 1 Fiber cable protection L T5 0020 Runs 001 Fiber cable protection Results myTestRunArgumentz In this example the attribute IRQA Arguments is used as argument for each individual test run object applied to every scripts associated to the test run object Code Mame Associated Scri IRCA Arguments e T5 0010 Runs 001 Locking c TS 0010 Scrip mwvTeskRunArgumaent i 750020 Runs 001 Fiber cab T5 20 Scrip mwvTeskRunArgumentz The options Use test session arguments and Use test case arguments are used to enable or disable the use of the arguments when calling the scripts Users can see how the arguments will be used via the script call example shown on the dialog Iw Use best session arguments IRDA Arguments in scripts i Use best case arguments IRGA Arguments in scripts Example Script py TEST SESSION ARGUMENTS TEST RUNS ARGUMENTS 3 2 3 Test run results Test run results can be manually updated after the execution of the tests In this scenario a tester manually or automatically using test scripts execute the tests and then
3. IRQA Test Management Extension v0 6 the requirements company If multiple test scenanos are associated to the requirement all tests are colored in RED if at least one of the tests failed are colored in YELLOW if at least one test is pending and none of the tests failed are colored in GREEN if all tests were passed The column displays Test Scenario Code Test Scenario Name Test Result Code Mame Test Status FUNC 0015 COC System modes TST_O40 Self diagnostic test Failed FUNC 000 Fully computerised control TST 020 Correct appliance connection Passed T157_030 Incorrect appliance connection Pending FUNC 0030 Full dual control TST_010 Connect appliance Passed In this la st example the test scenarios and their test status were Code Marne Test Status TST 010 Connect appliance TST z Correct appliance connection TST 30 Incorrect appliance connection TST O40 Self diagnostic test 3 3 3 Run Status last Column The Run Status last column which name can be modified via the configuration file see section 4 2 4 4 displays traceability between the requirement their associated test scenarios and the last instance of a test run object associated to the test scenarios This helps users viewing the status of the last execution of a test case he column also adds the run status information appended to the test run object To retrieve the run status the column is usng the pred
4. Pending MechReg 0040 Air shipment T5_0110 Weight Test TS 0110 Runs_001 Weight Test Results Pass If a test scenario doesn t have any test run object it is displayed in BLACK Cade Mame Run Status last SysReg 0010 Maximum weights and dimensions SYS TS 0010 Modify preference settings Note Test run objects must be created as children from a hierarchical relationships point of view of the test scenarios for the column to display them see section 4 2 2 3 on how to enable parent children hierarchical relationships 3 3 4 Run Status full Column The Run Status full column which name can be modified via the configuration file see section 4 2 4 5 disolays traceability between the requirement their associated test scenanos all test run objects associated to the test scenanos and the run status This helps users viewing the full history of test execution based on the requirements The column displays Test Scenario Code Test Scenario Name Test Run Code 1 Last Test Run Name Run Status Test Run Code Z2 Last Test Run Name Run Status Test Run Code 3 Last Test Run Name Run Status Code Marne Run Status Full MechReg_0020 Enviromental conditions T5 0100 Humidity altering T5 0100 Runs DO Humidity altering Results Fail T5 0100 Runs 002 Humidity altering Results Fail T5 0100 Runs 003 Humidity altering Results Pending MechReg_0030 Weight T5 0110 We
5. manually update each test run object with the test results In another scenario the test scripts can populate a csv comma separated values file with the test results e g pass fail and the test session execution module can parse this file and automatically update the test run results To use the results import facility the test session execution module must be pointed to the csv file that will be populated by the test scripts as shown here IRQA Test Management Extension December 2011 WWW Visureso lutions c om 14 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company Cr Test Results Component Tests Runs 2011 11 28 1658 csv a The execution scripts are responsible to create the result file one per session The format of the csv file must be Test Run Code Test Result The Test Run Code isthe code of the test run that is being executed The Test Result is the result of the execution The format of the result needsto correspond to the test result attribute format used for the test run objects see section 4 2 1 4 on how to configure the module with the right test result attribute Each new test run entry with test run code and test result needsto be created on a new line in the csv file E g TS 0010 Runs 001 Pass TS 0020 Runs 001 Pass TS 0030_Runs 001 Faal After the execution of all the test scripts the test session execution m
6. 11 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 2 Test Session Execution The test session execution module lets users execute test scripts associated to test run objects part of a test session and update test results The update of the test result of a test run can be done manually by the users orautomatically by the module The test session execution module addsa new toolbar to the test scenarios view This toolbar contains one button that when clicked bringsa dialog to execute the scripts associated to test run objects that are part of a selected test sesson Execute a Test Session Select a Test Session Test Session Arguments IRA Arguments TA Use best session arguments ROA Arguments in scripts Use best case arguments IROA Arguments in scripts Script Files are called without any arguments Use Test Plan Scripts Select Ehe test cases to be executed in the test session Associated Scripts Select All Deselect All Import execution results From csv File ee ecu Cancel IRQA Test Management Extension December 2011 www visureso lutions com 11 Copyright 2011 OVisure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 2 1 Test scnpts execution To execute test scnpts users need to first select a Test session see section 3 1 on how to create a t
7. 7 4 2 2 7 xc eh ONAN A o M M m 28 4 2 2 8 a A e oo aaa 28 4 2 3 Test sion Execution settings sese sese sees 28 4 2 3 1 Teden EEC UON T aii 28 4 2 3 2 wide M 28 4 2 3 3 evel m e 29 124 EI uhr WS Columns iuda e OPI m 29 4 2 4 1 aps Bes T Re MS eee 30 4 2 4 2 lt le S ena nO 9 OIUmD P oie 30 4 2 4 3 dI Mq T N e 30 4 2 4 4 oc AA A O ae 30 4 2 4 5 equunsatusrulle c Ei rana 31 IRQA Test Management Extension December 2011 www visuresolutions com 3 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 1 introduction This document providesa description of the Test Management Extenson in IRQA The purpose of this extension is to add capabilities to IRQA to support Test Management These capabilities include Test Session Creation e e Test Session Execution via test scripts e Test Statusupdate e Test Scenarios View Columns IRQA Test Management Extension December 2011 www visuresolutions com 4 Copyright 2011 Visure Solutions S L All rights reserved ISure IRQA Test Management Extension v0 6 the requirements company 2 Install
8. Management Extension December 2011 www visuresolutions com 15 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company Depending on the usage it isup to the scnpt to ignore or make use of any of the arguments passed by the test session execution module If results need to be imported back by the test session execution module a csv file will need to be generated by the python scriptsto store the test results See section 3 2 3 for more details IRQA Test Management Extension December 2011 WWW Visureso lutions c om 16 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 3 Test Status Columns The test status columns module adds four columns to the requirement view to help users visualize traceability from requirements to test results These fourcolumnsare e Test Scenarios Display traceability to test scenarios e Test Status Display traceability to test scenarios with their test status e Run Status last Display traceability to test scenanos and their last associated test run with their run status e Run Status full Display traceability to test scenarios and all their associated test runs with their run status The test status columns can be added via the Grid View Configuration of any requirements view under the Plugins Columns section Plugins Columns Test Sce
9. U Runs DU TS UU2U Runs DU TS DU20 Runs DUI TS 40 Runs DU TS nus Runs DU TS Hed Runs UU TS DD Runs DT TS nS Runs DU TS n 30 Runs DU TS DITU Huns DUI 15_0120 Runs DU TS U UU Runs DU TR DT 20 Huns 001 T5 0010 Locking connector usage T5 0020 Fiber cable protection T5_0030 FAL Hardware Error T5_0040 Pull out power connector bp hand T5 0050 Transmission error T5_0060 System data error T5 B Invalid Key error T5_0080 Power cord availability T5_0090 Temperature altering 15 0110 Weight Test T5 020 Bump Test T5 0100 Humidity altering het ww P Locking connector usage Results Fiber cable protection Results FAL Hardware Error Results Pull aut power connector by hand Results Transmission error Results System data error Results Invalid Key error Results Power cord availability Results Temperature altering Results Weight Test Results Bump Test Results Humidity altering Results Image depth setting venficalton Results The test session creation module also creates a hierarchical link between the test session block and the predefined Runs block see section 4 2 1 2 on how to configure the module to find the predefined Runs block Test Status This allows test run objects to inherit attributes defined in the Runs block e g Component Tests Runs 2011 11 40 1558 IRQA Test Management Extension December 2011 Ts www visuresolutions com 10 Copynght 20
10. ario properties CO lUMMS occccoccconcccncnconcncnncnocononononncro nr nro rr enn nen nnn nnne n nari nnn annu nnns 20 3 4 2 Le Cla LEO files CO NIA ETE adi 21 SS SS ete Ta aT 22 4 TESTMANAGEMENT EXTENSION CONHGURATION HLUE ss ss ss sss ss sss ss sss nun nuu 23 41 XMLConfiguration file modifications eeeseeeeeeeennm mnn 24 4 2 XML Configuration Tags eesesseeeeeennnnn nennen nnn nnn nnn nn nina nnn nnne nnn nns 24 4 2 1 Tes Management Extension general settings seesssseesseeeeeeee nene nn nnn nnn nn nnn 24 4 2 1 1 A T c 24 4 2 1 2 o TP 24 4 2 1 3 Ka L e ehe Iz o RINT P E T eomm 24 IRQA Test Management Extension December 2011 www visuresolutions com 2 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 1 4 RUNSta USN Con a eee eee 25 A ios Ao lo eii ee EE 25 4 2 2 1 2I P X 25 4 2 2 2 MF eNO M RN 25 4 2 2 3 R e re NIC SIUNE EC 26 4 2 2 4 eius c 26 4 2 2 5 boo ao ode enne RETE TET TOTIS 26 4 2 2 6 COLS Froma OUM ERE OO TD D TO DOE 2
11. ation The Test Management Extension is made up of five files TME TestSession im a TME TestSessionExecution irqa TME TestSatus irqa TME TestScenariosColumns irqa TM EC onfig xml All files need to be copied to the Plugins folder insde the IRQA Installation folder usually HDD Program files IRQA 41 or the project s Corporate Plugin Folder The files need to be directly copied to the Plugins folder no subfolder Open the IRQA 4 Client then open a project and navigate to the menu Project Plugins to open the Plugin Manager Make sure the TME plugins are activated If they are notactivated check them press OK and restart the IRQA 4 Client m Plugin Manager Plugin Loading Order Available Plugins Status TME 1A044 Test Session Creation Loaded TME IRGA4 Test Session Execution Loaded TME lAGA4 Test Status Loaded THE IRGA4 Test Scenarios Columns Loaded Plugin Infermatian 2 1 IRQA Support The test management extension can be used with IRQA 4 3 and up 2 2 MFC Secunty Update In order to use the extension the Microsoft Visual C 2005 Service Pack 1 Redistributable Package update KB2538242 from the Microsoft Security Bulletin MS11 025 must be installed You can get it from this website http technet mic ro soft c om en us security bulletin ms11 025 IRQA Test Management Extension December 2011 www visuresolutions com 5 Copyright 2011 Visure Solutions S L All rights reserved v su
12. by the user Attribute are not automatically created by the module and ignored if not found Default value if tag not used IRQA Arguments 4 2 3 3 1 Effecton module The Test Session Execution module usesthis setting when calling the python scripts with arguments The attribute name specified in the dRQAArgument gt tag is used asa test run argument Test Scenario attribute AND the test session argument block property See section 3 2 2 on how arguments are used If the tag isempty the default value isused 4 2 4 Test Status Columns settings The Test Status Columns settings are used to configure the Test Status Columns module lt TestStatusColumns gt lt TestScenariosColumn gt lt Name gt Test Scenarios lt Name gt lt Enabled gt 1 lt Enabled gt lt TestScenariosColumn gt lt TestStatusColumn gt lt Name gt Test Status lt Name gt lt Enabled gt 1 lt Enabled gt lt TestStatusColumn gt lt RunStatusLastColumn gt lt Name gt Run Status last lt Name gt lt Enabled gt 1 lt Enabled gt lt RunStatusLastColumn gt RunstatusFullcolumau lt Name gt Run Status full lt Name gt lt Enabled gt 1 lt Enabled gt lt RunStatusFullColumn gt lt TestStatusColumns gt IRQA Test Management Extension December 2011 www visuresolutions com 29 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 4 1 lt TestStatusColum
13. ction T5 30 FRL Hardware Error T5 0040 Pull out power connector by hand TS 0050 Transmission error 3 T5 0060 System data error T5 0070 Invalid Kev error T5 0080 Power cord availability T5 0090 Temperature altering T5 0110 Weight Test ITS 0120 Bump Test gt Users can select any test casesto be included in the Test Session If the suspect links are enabled in the project the suspects button is enabled and when clicked selects all test cases that have a suspect link to a requirement When the button OK is clicked it creates one test run object that will be used to store execution results for every selected test case Code Mame Test Status Locking connector usage IE I T5 0010 Runs O01 Locking connector usage Results Pending e T5_0020 1 Fiber cable protection L T5 0020 Runs DO01 Fiber cable protection Results Pending T5_0030 1 FRL Hardware Error L T5_0030_Runs_001 FRL Hardware Error Results Pending lt l T5 n40 1 Pull out power connector by hand L T5 0040 Runs_001 Pull out power connector by hand Results Pending lt l T5 n050 1 Transmission error L T5_0050_Runs_001 Transmission error Results Pending e T5_0060 1 System data error L T5_0060_Runs_001 System data error Results Pending T5_0070 1 Invalid key error L T5_0070_Runs_001 Invalid Key error Results Pending gt T5_0080 1 Power cord availability L T5 0080 Runs_001 Power cord availability Resul
14. efined run status attribute see section 4 2 1 4 to configure which run status attribute to use that is associated to the test run Furthermore if the run status uses one of the predefined values the text displayed in the column is colored The predefined values and their associated color are PassorPassed colored in GREEN Fail or Failed colored in RED Pending colored in YELLOW Any other statuses are colored in BLACK If multiple test scenarios with test runs are associated to the requirement all tests are colored in RED if at least one of the test runs failed are colored in YELLOW if at least one test run is pending and none of the test runs failed are colored in G REEN if all test runs were passed The column is colored in BLACK if none of the test scenarioshave atleast one associated test run The column displays Test Scenario Code Test Scenario Name Last Test Run Code Last Test Run Name Run Status IRQA Test Management Extension December 2011 www visuresolutions com 18 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company Code Name Run Status last MechReg 0070 Enviromental conditions T5 0100 Humidity altering T5 0100 Runs 002 Humidity altering Results Fail MechReg 0030 Weight T5 0110 Weight Test TS 0110 Runs 001 Weight Test Results Pass T3 120 Bump Test T5 0120 Runs_001 Bump Test Results
15. escription If the tag isset to 1 the description is copied If the tag isempty or set to 0 the description is NOT copied 4 2 3 Test Session Execution settings The Test Session Execution settings are used to configure the Test Session Execution module lt TestSessionExecution gt lt PythonPath gt c Python27 Python exe lt PythonPath gt lt IRQAArgument gt IRQA Arguments lt IRQAArgument gt lt TestSessionExecution gt 4 2 3 1 lt TestSessionExecution gt This isthe entry tag of the Test Session Execution settings All settings must be added below 4 2 3 2 lt PythonPath gt This tag defines the path AND the python executable that isused to execute the scnipts Default value if tag not used cA Python27 Python exe IRQA Test Management Extension December 2011 www visuresolutions com 28 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 3 2 1 Elect on module The Test Session Execution module uses this setting when calling the python scripts See section 3 2 4 on how python scripts are called If the tag isempty the default value isused Note The module doesn t check if the path is valid and if the executable exists Users need to make sure they are valid 4 2 3 3 IRQA Argument This tag defines the IRQA attribute that can be used asa script argument The IRQA attribute needs to be a TEXT attribute and defined
16. est session The Select Test Session drop down menu givesa list of all test session in the project Select a Test Session wm Component Tests Runs 2011 11 02 1248 Component Tests Runs 2011 11 28 1658 The selection of the test session populates the list of test run objects that are part of the test session Users can select which test runs willbe executed Select the test cases to be executed in Ehe test session Associated Scripts TS 0010 Runs 001 Locking connector usage Res TS 0010 Script py TS 0020 Runs DU Fiber cable protection Results TS 0020 Script py T5 0030 Runs_001 FRL Hardware Error Results T5 0030 _ Script py T5 0040 Runs 001 Pullout power connector by h T5 0040 Script py T5 0050 Runs 001 Transmission error Results T5 0050 Script py T5 0060 Runs O01 System data error Results T5 0060 Script py T5 D 70 Runs 001 Invalid Kev error Results T5 70 Script py T5 OO80 Runs 001 Power cord availability Results TS 0050 Script py T5 0090 Runs_001 Temperature altering Results T5 _0090_Script py T5 0110 Runs 001 Weight Test Results T5 0110 Script py T5 0120 Runs 001 Bump Test Results T5 0120 Script py TS 0100 Runs DO01 Humidity altering Results TS_O100_Script py gt The list displa ys up to four columns The code and name of the test run object the associated scripts and any attribute that will be used as argument to the scripts see section 3 2 2 The associated scri
17. he default test scenario code format 4 2 2 5 1 Effecton module The Test Session Creation module uses this setting when assigning a code to the test run object If it is set to 1 the code of the test plan stest case isused to which the sting XXX isappended XXX are digits that are incremented for each test run For example Test Case TS 0010 Test Run TS 0010 001 If the tag isset to 0 the default test scenario code format is used set via the Configuration gt Code gt Test Scenarios menu in IRQA For example Test Case TS 0010 Test Run 00010 4 2 2 6 lt CodeFormatSuffix gt Thistag defines whethera suffix is appended to the test run code The test run code format is defined via the lt UseSameCodeFomat gt tag see 4 2 2 5 Default value if tag not used i e empty value the suffix value isignored 4 2 2 6 1 Effecton module The Test Session Creation module uses this setting in collaboration with the lt UseSameCodeFomat gt tag If the lt CodeFormatSuffix gt is set to a value and lt UseSameCodeFomnat gt is enabled then the test run code format is Test Scenario Code CodeFormatsSuffix XXX For example CodeFormatSuffbc is set to Runs UseSa meCodeFormat is set to 1 The Test Case TS 0010 generatesthis test run code TS 0010 Runs 001 If the lt CodeFormatSuffix gt is set to a value and lt UseSameCodeFomat gt is disabled then the test run code for
18. ibute gt lt RunStatusAttribute gt Run Status lt RunStatusAttribute gt lt TME gt 4 2 1 1 lt TME gt This isthe entry tag of the general settings All general settings must be added below 4 2 1 2 lt RunBlock gt This tag defines the name of the predefined Run block used in the project Default value if tag not used Runs 4 2 1 2 1 Effecton modules The Test Session Creation module uses this setting when creating the hierarchical link between the test session block and the run block This allows users to define attributes that all test session blocks inherit from the run block The run block name is also used to filter the Select Test Plan drop down menu removing any runsortest session blocks see section 3 1 The Test Session Execution module uses this setting to filter the Select Test Session drop down menu removing any block that are not runs see section 3 2 The Test Status Columns module uses this setting to retrieve the run statusof only the test run objects 4 2 1 3 lt TestStatusAttribute gt Thistag defines the name ofthe predefined Test Status attribute used in the project Default value if tag not used Test Status IRQA Test Management Extension December 2011 www visuresolutions com 24 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 1 3 1 Elect on modules The Test Status Columns module uses this set
19. ic verson of the test object The test session creation module addsa new toolbarto the test scenarios view This toolbar contains one button that when clicked brings a dialog to create a test session based on a test plan Create a Test 5ession Select Test Plan r Test Session Name e Select Ehe test cases En be included in the test session Select All Deselect All Suspects oma IRQA Test Management Extension December 2011 www visuresolutions com 7 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company To create a Test Session users need to first select a Test plan Test plans are based on test scenano blocks The Select Test Plan drop down menu gives a list of all test scenario blocks in the project The list of test scenariosblocks does not include the test scenarios blocks used to store the test run objects For example from this list of project bloc ks Mame Acceptance Tests Component Requirements Component Tests Component Tests Runs 2011 11 02 1237 Customer Requirements Defects Electrical Requirements Marketing Requirements Mechanical Requirements Runs Software Requirements Stakeholder Requirements Standards System Requirements Type of elements Test Scenarios Requirements Test Scenarios Test Scenarios Requirements Requirements Requirements Requirements Requirements Test Scena
20. ight Test T5 0110 Runs 001 Weight Test Results Pass T5 0110 Runs 002 Weight Test Results Pending TS 0120 Bump Test T5 0120 Runs_001 Bump Test Results Pass T5 0120 Runs 002 Bump Test Results Pass MechReg 0040 Air shipment T5 0110 Weight Test T5 0110 Runs 001 Weight Test Results Pass T5 0110 Runs 002 Weight Test Results Fail Note Test run objects must be created as children from a hierarchical relationships point of view of the test scenanos for the column to display them see section 4 2 2 3 on how to enable parent children hierarchical relationships IRQA Test Management Extension December 2011 www visuresolutions com 19 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 4 Test Scenanos View Columns The test scenarios view columns modules add ten columnsto the test scenarios view to help users see test scenarios properties These columnsare Precondition Display the precondition property Post condition Display the post condition property Logical Environment Display the logical environment property Physical Environment Display the physical environment property Responsible Display the responsible property Location Display the location property Date Display the date property Associated Files Display the list of all associated files only name of the file Associated Files full
21. jects are created Default value if tag not used default 4 2 2 2 1 Effecton module The Test Session Creation module uses this setting as the partition in which the test run objects are created The partition used here needs to be predefined in the project and it must be able to contain Test Scenarios object Furthermore the user needsto have write access to it If these conditions are not met test run objects will not be created IRQA Test Management Extension December 2011 WWW Visureso lutions c om 25 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 2 3 lt HierarchicalLink gt This tag defines whether the test run objects are created aschildren of the test plan stest cases Default value if tag not used 1 i e created as children 4 2 2 3 1 Effecton module When the tag isset to 1 the test creation module creates the test run objectasa child of the test case Code Mame lt l TS 0010 r1 Locking connector usage E T5 0010 Runs DU Locking connector usage Results When the tag is set to 0 the test creation module does not create the test run object asa child of the test case Code Mame TS 0010 Locking connector usage TS 0010 Runs_001 Locking connector usage Results Note If the hierarchical links are not used tag set to 0 it prevents the Run Status last and Run Status full of the Test Statu
22. mat is Next default Test Scenario Code CodeFomatSuffix For example CodeFormatSuffb is set to Runs lt Use Sa meCodeFormat is set to 0 The Test Case TS 0010 generatesthis test run code when default format isto use of 5 digits 00010 Runs If the CodeFormatSuffbc tag is empty the suffix is ignored IRQA Test Management Extension December 2011 www visuresolutions com 27 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 2 2 7 lt NameFormat gt This tag defines the format of the test run object name Default value if tag not used s Runs 4 2 2 7 1 Effecton module The Test Session Creation module uses this setting when assgning a name to the test run object To reuse the same name asthe test plan stest case object the symbol s can be used For example lt Nameformat gt is set to s Results Test Case Name Locking connector usage Test Run Name Locking connector usage Results If the tag isempty or not used the default value 9es Runs is used 4 2 2 8 IncludeDescription This tag indicates the module if the test plan s test case description is copied insde the test run description Default value if tag not used I 4 2 2 8 1 Effecton module The Test Session Creation module uses this setting to determine if the test plan s test case description is Copied in test run d
23. narios Test Status Hun Status last Hun Status Full 3 3 1 Test Scenario Column The Test Scenario column which name can be modified via the configuration file see section 4 2 4 2 displa ys tra ceability between the requirement and any test scenario The column displays Test Scenario Code Test Scenario Name Code Mame Test Scenarios MechReg_0110 Fiber connector robustness T5 0010 Locking connector usage MechReg_0120 Mechanical cladding on Fiber TS_0020 Fiber cable protection T5 25 Fiber cable cladding 3 3 2 Test Status Column The Test Status column which name can be modified via the configuration file see section 4 2 4 3 displays traceability between the requirement and any test scenario The column also adds the tes status information appended to each test scenario To retrieve the test status the column is using the predefined test status attribute see section 4 2 1 3 to configure which test status attribute to use that is associated to the test scenario Furthermore if the test status uses one of the predefined values the text displayed in the column is colored The predefined values and their associated color are e PassorPassed colored in GREEN e FailorFailed colored in RED e Pending colored in YELLOW e Any other statuses are colored in BLACK IRQA Test Management Extension December 2011 www visuresolutions com 17 Copyright 2011 Visure Solutions S L All rights reserved vis ure
24. ns 001 Locking connector usage Res TS 0010 Script py When the option is unchecked the scripts associated to the test run object here TS 0010 Runs 001 are used Use Test Plan Scripts Select the test cases to be executed in Ehe test session Associated Scripts fe TS 0010 Runs 001 Locking connector T5 0010 Runs 004 Script py When clicking on OK the test execution module executes all valid scnpts of any of the selected test run objects 3 2 2 Atinbutes as script arguments A dedicated attribute can be used to specify arguments for the test scripts There are two types of attributes arguments The first type is a test session argument The test session argument is used in every script cal The test session argument is a predefined block property see section 4 2 3 3 on how to configure the extension to retrieve the right block property of type TEXT Mame TRA arguments Component Tests Runs 2011 11 02 1248 myArgument Component Tests Runs 2011 11 28 1658 myArgument In this example the block property IRQA Arguments is used as the test session argument applied to every scripts IRQA Test Management Extension December 2011 WWW Visureso lutions c om 13 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company Select a Test Session Component Tests Runs 2011 11 28 15658 Test Session Arguments IRQA Arguments
25. ns gt This isthe entry tag of the Test Status Columns settings All settings must be added below 4 2 4 2 lt TestScenariosColumn gt This section contains the tags used to set the name of the Test Scenano Column see section 3 3 1 and whether it isenabled ornot 4 2 4 2 1 lt Name gt and lt Enabled gt The tag lt Name gt is used to set up the name of the Test Scenano Colum Thisname isused asthe column name in the Requirements View If the tag is empty the default name is used Default value if tag not used Test Scenarios Plugins Columns Test Scenarios The tag Enabled tells the module to enable the column ornot If the column is disabled value of 0 the column is not listed under the Plugins Columns in the Requirement View If the tag is enabled value of 1 or if value is empty the column is listed Default value if tag not used 1 4 2 4 3 TestStatusColumn This section contains the tags used to set the name of the Test Status Column see section 3 3 2 and whether it is enabled or not 4 2 4 3 1 lt Name gt and Enabled The tag Name is used to set up the name of the Test Status Colum This name is used asthe column name in the Requirements View If the tag isempty the default name isused Default value if tag not used Test Status Plugins Columns Test Status The tag lt Enabled gt tells the module to enable the column ornot If the column is disabled value of 0
26. odule will parse the csv execution results file and update the test results attribute of all the test run objects that were executed accordingly 3 2 4 Python sc ripts The test session execution module can execute any python script Python script are detected as being valid i e can be executed if their extenson is py In orderto run the script properly python must be installed Python can be found here http www python org downloa d The test session execution callsthe python scripts on the command line using this syntax PythonPathAndExe DPsthonserapt SelectedSession TestCode TestName ParentCode SessionArg TestArg where e PythonPathAndExe Python path python exe as specified in the configuration file see section 4 2 3 2 PythonScript the name of the python script file that is being executed SelectedSession the name of the test session that isbeing executed TestCode The code of the test run object that isbeing executed TestNa me The name of the test run object that isbeing executed ParentCode The code of the parent of the test run object that is being executed SessionArg The test session argument if included TestArg The test run argument if included E g Cz Python27 python exe TS 0010 Script py Component Tests Runs 2011 11 28 1659 TS 0010 Runs 001 Locking connector usage result TS 0010 mySessionArgument myTestArgument IRQA Test
27. path Display the list of all associated files with theirfull path Steps Display the list of all steps The test status columns can be added via the Gnd View Configuration of any test scenarios view under the Plugins Columns section Plugins Columns Precondition Post condition Logical Environment Physical Environment Responsible Location Date Associated Files Associated Files Full path Sheps All columns are in read only mode All columnsare exportable to Excel 3 4 1 Test Scenano properties columns The columns Precondition Post condition Logical Environment Physical Environment Responsible Location and Date Code Mame Precondition Post condition Logical Environment Physical Environment Responsible Location Date T5T_020 Correct appliance connection System is loaded and working Appliance is correctly Configuration Y Hardware X John Smith Madrid Spain 2011 12 06 User is lagged in connected and installed Directly correspond to the associated test scenario property Precondition from the Precondition and Post condition property tab Frecanditian System is loaded and working User i logged in Post condition from the Precondition and Post condition property tab IRQA Test Management Extension December 2011 www visuresolutions com 20 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company Post condition Appliance is cor
28. pts are any associated files to the test run that are detected as being scripts Currently any python script file with the py extenson is detected asa valid script to be executed see section 3 2 4 on python scripts Properties EJES Blocks and Attributes Test case Precondition and Post Condition Details Related Elements Associated files Versions Related Test Scenarios Discussion File Statue Projecte Suspect T5 0010 Script py L Multiple scripts can be attached to one tes These are executed in sequence in the order of appearance in the Associated Filestab IRQA Test Management Extension December 2011 WWW Visureso lutions c om 12 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company The test session execution module can execute scripts associated to the test run object or scripts associated to the parent test cases The option Use test plan scripts allows the users configuring this behavior Iw Use Test Plan Scripts For example Code Mame Associated Files G TS D010 1 Locking connector usage TS_0010_ Script py L T5 0010 Runs 001 Locking connector usage Results T5 0010 Runs 001 Script py When the option is checked the scnpts associated to the parent test case here TS 0010 are used v Use Test Plan Scripts Select the test cases to be executed in Ehe test session Associated Scripts T5 0010 Ru
29. re the requirements company IROA B Test Ma nagement Extension vO 6 3 Test Management Extension Description The Tes Management Extension is made of four main modules IRQA Test Management Extension December 2011 Test Session Creation Module that lets users instantiate a test sesson from a test plan Test Session Execution Module that lets users execute test scripts associated to a test session and update test results Test Status Columns Module that addstest status columnsto the Requirement view Test Scenarios Columns Module that adds test scenario properties columns to the test scenarios view www visuresolutions com 6 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 1 Test Session Creation The test session creation module lets users instantiate test cases part of a test plan into test run objects part of a test session As stated in the Standard glossary of terms used in Software Testing from the Intemational Software Testing Qualifications Board ISTQB a test session can be defined by An unintemupted period of time spent in executing tests In exploratory testing each test session is focused on a charter but testers can also explore new opportunities or issues during a sesson The tester creates and executes test cases on the fly and recordstheir progress A test run can be defined by Execution of a test on a specif
30. rectly connected and installed Logical Environment from the Test Case property tab Logical environment Configuration T Physical Environment from the Test Case property tab Physical environment Hardware A Responsable from the Test Case property tab Responsible John Smith Location from the Test Case property tab Location Madrid Spain Date from the Test Case property tab Date 2011 12 06 3 4 2 Associated files columns The columns Associated Files and Associated Files full path displays the list of all files associated to a test scenano Code Mame Associated Files Associated Files Full path TST 20 Correct appliance connection TST O20 Script py C 1YTest Scripts TST 20 Script py TST 050 Incorrect appliance connection T5ST_O30 Scripk py Test Scripts TST 020 Script py Test Image bmp CU Test Scripts Test Image bmp The associated files are set via the Associated files property tab Properties G Details Related Elements Blocks and Attributes est case Precondition and Post Condition Associated files Versions Related Test Scenarios Discussion File Status Projects Suspect T5T 020 Script py R Test Image bmp IRQA Test Management Extension December 2011 www visuresolutions com 2T Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 3 4 3 Steps col
31. rios Requirements Requirements Requirements Requirements System Tests Test Scenarios Use Cases Services The available test plansare Select Test Plan O Y Acceptance Tests Component Tests System Tests The Runs and Component Tests Runs 2011 11 02 1237 blocks are test runs blocks that contains test run objects that track the results of the execution of a test scenario defined in a test plan see section 4 2 1 2 on how to configure the module to recognize Runs block Once the user selects a test plan the module automatically generates a test session name This test session name can be modified if needed However be aware to keep the string used to recognize Runs blocksaspart of the name see section 4 2 1 2 on how to configure the module to recognize Runs block Select Test Plan Component Tests Test Session Mame Component Tests Runs 2011 11 26 1650 IRQA Test Management Extension December 2011 www visuresolutions com 8 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company The selection of the test plan also populates the list of test cases that will be included in the test session The list contains all test cases associated to the test plan i e test scenarios associated to the selected block Select the test cases to be included in the test session T5 0010 Locking connector usage T5 0020 Fiber cable prote
32. s Columns module see section 3 3 3 and 3 3 4 from working since they are using these hierarchical relationships 4 2 2 4 Motive This tag defines which motive is used to create the traceability relationship between the test run objects and the test plan stest cases Default value if tag not used Execute 4 2 2 4 1 Elect on module The Test Session Creation module uses this setting when creating the traceability relationship between the test run object and the test plan stest case TIS Level Relationships by motive Execute nd Level Filter First Level Direction Outgoing Code Marne J 8 TS no1in 1 Locking connector usage E 15_0010_Runs_004 Locking connector usage Results If the motive doesn t exist it is created automatically If the motive already exists and traceability restrictions are enabled users needs to make sure that it is possble to create a traceability relationship between the test run object and the test plan stest case If itis not the case then no traceability links are created 4 2 2 5 UseSameCodeFormat Thistag defines whether the test run code isbased on the test plan stest case code format orthe default test scenario code format IRQA Test Management Extension December 2011 www visuresolutions com 26 Copynght 2011 Visure Solutions S L All nghts reserved vis ure IRQA Test Management Extension v0 6 the requirements company Default value if tag not used O i e using t
33. ser presses the Accept button IRQA Test Management Extension December 2011 www visuresolutions com 22 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 Test Management Extension Configuration File The Test Management Extension is configured via the TMEConfig cfg xml file The configuration options are used by the individual TME module Below isan example of the configuration file lt xml version 1 0 encoding UTF 8 gt lt Config gt lt TME gt lt RunBlock gt Runs lt RunBlock gt lt TestStatusAttribute gt Test Status lt TestStatusAttribute gt lt RunStatusAttribute gt Run Status lt RunStatusAttribute gt lt TME gt lt TestSession gt lt Partition gt default lt Partition gt lt HierarchicalLink gt 1 lt HierarchicalLink gt lt Motive gt Execute lt Motive gt lt UseSameCodeFormat gt 1 lt UseSameCodeFormat gt lt CodeFormatSuffix gt _Runs_ lt CodeFormatSuffix gt NameFormat s Results lt NameFormat gt lt IncludeDescription gt 1 lt IncludeDescription gt lt TestSession gt lt TestSessionExecution gt lt PythonPath gt c Python27 Python exe lt PythonPath gt lt IRQAArgument gt IRQA Arguments lt IRQAArgument gt lt TestSessionExecution gt lt TestStatusColumns gt lt TestScenariosColumn gt lt Name gt Test Scenarios lt Name gt lt Enabled gt 1 lt Enabled gt lt TestScenariosColumn gt lt TestStat
34. the name of the Run Status full Colum This name is used as the column na me in the Requirements View If the tag isempty the default name is used Default value if tag not used Run Status full Plugins Columns Hun Status Full The tag Enabled tells the module to enable the column ornot If the column is disabled value of 0 the column is not be listed under the Plugins Columns in the Requirement View If the tag is enabled value of 1 orif value is empty the column is listed Default value if tag not used I IRQA Test Management Extension December 2011 WWW Visureso lutions c om 31 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company Visure the requirements company Avda de los Labradores 1 4th Floor 28760 Tres Cantos Madrid Spain Tel 34 91 806 17 13 Fax 34 91 804 39 50 info visuresolutions com www visuresolutions com aa t cument may not be reproduced or including photocopying recording or IS S L All of the material contained in isthe property of VISURE SOLUTIONS S L EE Ep uw Q
35. ting to retrieve the test status of the test scenanos object that are directly link to the requirement This value isused by the Test Status column see section 3 3 2 4 2 1 4 lt RunStatusAttribute gt This tag defines the name of the predefined Run Status attribute i e the test status of the runs used in the project Default value if tag not used Run Status 4 2 1 4 1 Effecton modules The Test Status Columns module uses this setting to retneve the run status of the test run objects This value is used by the Run Status last column see section 3 3 3 and the Run Status full column see section 3 3 4 The Test Session Execution module uses this setting when importing results from the csv file see section 3 2 3 4 2 2 Test Session Creation settings The Test Session Creation settings are used to configure the Test Session Creation module lt TestSession gt lt Partition gt default lt Partition gt lt HierarchicalLink gt 1 lt HierarchicalLink gt lt Motive gt Execute lt Motive gt lt UseSameCodeFormat gt 1 lt UseSameCodeFormat gt CodeFormatSuffix Runs CodeFormatSuffix NameFormat s Results lt NameFormat gt lt IncludeDescription gt 1 lt IncludeDescription gt lt TestSession gt 4 2 2 1 lt TestSession gt This isthe entry tag of the Test Session Creation settings All settings must be added below 4 2 2 2 lt Partition gt Thistag defines in which partition the test run ob
36. ts Pending lt l T5_0090 1 Temperature altering L T5 0090 Runs 001 Temperature altering Results Pending leTS_0100 1 Humidity altering L T5 0100 Runs 001 Humidity altering Results Pending EsTS D110 13 Weight Test L T5 0110 Runs 001 Weight Test Results Pending lt l TS 0120 1 Bump Test L T5 0120 Runs D 1 Bump Test Results Pending lt l TS 0130 1 Image depth setting verification L T5 i30 Runs 001 Image depth setting verificaiton Results Pending IRQA Test Management Extension December 2011 www visuresolutions com 9 Copynght 2011 Visure Solutions S L All nghts reserved Visure the requirements company IRQA Test Management Extension v0 6 The format of the test run object Code Name traceability to tests partition etc is configured via Test Management Extenson configuration file See section 4 2 2 formore details These test run object are associated to the test session block as specified by the test session name that is created by the extension IROA 4 Project Edit Engineering process Tools 3 Current e cae Mame Globa 1st Level Lidl Acceptance Tests Component Requirements Component Tests Component Tests Runs 2011 11 26 1658 Properties Element Type Details Block Properties Element Attributes Included Elements Relationships Versions Mot Included Elements Included Elements TS n
37. umns The steps column displays the test scenarios steps in a textual format The format used is Step X Actor Y Direction lt OR gt OR lt gt Event Z Description For example the steps ld Actor Event Direction 1 User The user presses the Connect appliance option in the screen 7 User The system provides the possibility to select the initial working mode of the appliance 3 User The user selects the working mode for the appliance being connected 4 System lt The system checks that the appliance ts ready to be connected n User The system enables the Accept button b User The user presses the Accept button Are displayed as Code Mame Steps TST 020 Correct appliance connection Step 1 Actor User Direction Destination System gt The user presses the Connect appliance option in the screen Step 2 Actor User Direction Destination System gt The system provides the possibility to select the initial working mode of the appliance Step 3 Actor User Direction Source System The user selects the working mode For the appliance being connected Step 4 Actor System Direction Reflexive lt gt The system checks that the appliance is ready to be connected Step 5 Actor User Direction Destination System gt The system enables the Accept button Step 6 Actor User Direction Source System lt The u
38. usColumn gt lt Name gt Test Status lt Name gt lt Enabled gt 1 lt Enabled gt lt TestStatusColumn gt RunsSstatusLasutColumn lt Name gt Run Status last lt Name gt lt Enabled gt 1 lt Enabled gt lt RunStatusLastColumn gt lt RunStatusFullColumn gt lt Name gt Run Status full lt Name gt lt Enabled gt 1 lt Enabled gt lt RunStatusFullColumn gt lt TestStatusColumns gt SLOTS Note XML is a case sensitive language make sure to use tags with their conect case IRQA Test Management Extension December 2011 WWW Visureso lutions c om 23 Copyright 2011 Visure Solutions S L All rights reserved vis ure IRQA Test Management Extension v0 6 the requirements company 4 1 XML Configuration file modifications If the TMEConfig cfg xml configuration file is modified IRQA needs to be restarted in order to reconfigure the Test Management Extenson 4 2 XML Configuration Tags This section describes the XML configuration tags that are used to configure the Test Management Extension and their effect on the individual modules All configuration tags must be added within the lt Config gt tags lt xml version 1 0 encoding UTF 8 gt lt Config gt SL i gt 4 2 1 Test Management Extension general settings The Tes Management Extension general settings are used across the individual modules lt TME gt lt RunBlock gt Runs lt RunBlock gt lt TestStatusAttribute gt Test Status lt TestStatusAttr
39. www visuresolutions com Visure the requirements company Test Management Extension User Guide December 2011 P d Requirements Definition and Management a j 7 SAU U BI A N NETT y SU e T A w IM C HD Y JESS z E EF S PA Z f NY 2 00 H li Ly gt M 260 11201111 her 7 240 Uan Z Uy yyy S N vis ure IRQA Test Management Extension v0 6 the requirements company TABLE OF CONTENTS E INIA e aaa a 4 2 INSTALLATION ooo uuu uuu rr 5 2 1 TRO PUD sle P E 5 2 2 MFC Sec uny UDA uu 5 3 TEST MANAG EMENT EXTENSION DESC RIPTION ss sss ss sss ss sss ss s ss ss ssa asas uuu nuu nu 6 3 1 Test Session C eao 7 3 2 Test Session ecu Nissan did cia dr iiem dada 11 3 2 1 TEX SENMPES execution iia via 12 23 2 2 AUIDUtes as nt GO UMMC IS sees eee eee eee 13 3 23 Teg O CA 14 S PORNS P EE TTE 15 3 3 Test Status Columns 2 cccccccccececcccccececucececceauacaeauseesuauaeaeseceeguaneeauaeaeaeneceenuaenenensnaeauansuauaeaenenes 17 3 3 1 Test Scenario Column iii rnn norn ranno rn DAR AREADEAPEDEREARRAREAREEOEADAREAEEEDER RARER EAEn na 17 3 3 2 15 TTU a g e A ea marc E PE E E EEA EE PE A AEE A E E E E A E PE 17 3 3 3 Run Satus as C OM eroittaa enai a e a a iiaa da 18 3 3 4 RUM atus ATUN ed ON Emm 19 3 4 Test SenanosView EOL Sanet ws Pane 20 3 4 1 Test Scen
Download Pdf Manuals
Related Search