Home

User Manual

1. T m Test Suites Select Test Suites New Test Suite V6 1 1 New Test Suite V8 1 1 Requirement Structures Select Structures Components Notepad Requirement attributes Y Chart EE pata E Detailed Data y Requirement Requirement Structu failed passed not executed not on Chart Horizontal Bar Chart b Func_req2 e an m a Sort Func_req21 Je g Fo F alphabetical Func_req22 __ Notepad V1_ E _ tc536 New Test Suite V6 1 1 A oe TO ascending F Not V2 itc536 New Test Suite unc_req22 otepad ew Test Suite pa ing Func_req23 Notepad V 1 l tc742_1 New Test Suite V6 B Pe l Func_req23__ Notepad V2 aia Ris _ tc742_1 New Test Sut l FF Values Func_req24 E a is m 6 Al Only zero values Func_req26 Notepad V1 tc537 New Test Suite V6 1 1 aa ee T T or 2 1 i No zero values Func_req26 Notepad V2 tc537 New Test Suite Func_req27 Notepad V 1 tc536 New Test Suite V6 1 1 Func_req27_ Notepad V2 i a __ tc536 New Test Suite Func_req28 Notepad 1 tc703 Ne tc702 New Test Suite V6 1 A J L a es ee ee An FIN tT the A lin Figure 137 Requirement analysis over several test suites Detailed Data 3 1 5 6 Reporting TEMPPO Test Manager offers a reporting feature which allows you to create flexible textual and graphical
2. 00 91 3 1 4 3 2 Adding and changing test packages during test case execution91 SLAA Pinging BUG IDS soriire intel seusaaiaak Mirae eben e ein 92 54 425 FINISHING TeSt EXECUtiIOM iverna a 92 3 1 4 6 Creating M re Test SUIRGS russi niaan a a e ede a i 92 3 1 4 7 Test case execution with an exported test suite 0088 93 SAC4 Fo EXPOrG a LeSt SUILG ica te ass a OA rO 93 3 1 4 7 2 Test case execution with an exported test suite 05 95 DLA IMPONG TESE TESUNTS pacon aaae E E AEA 95 3 1 4 7 4 Unlocking the test suite ssesssssssssnsnsnsnnnunsnrsnrnrsnrnrenens 97 Seo EVIAN araeir eea N AAEE 97 halL ANalySIS eieaa E NT E A 97 3 1 5 1 1 Analysis with previous test SUITES s ssssssessnsrnnrsnrerrrennns 99 3 1 5 2 Requirement analysis cccccecccccssscccccsseeneceereeeeeesssseeegunengs 100 3 1 5 3 Analysis by Bug ID project ccccseseceesseeeeeeeeeeeeeessseeeeeueenns 104 3 1 5 4 Analysis by Bug ID test Suite ceeeeeeeeeeeeeeesseeeeeurenes 105 Sdxso PROGRESS Challo iienaa esata ana Gameeee es eiaks 105 Seize Creaton Progr asvci cor starsaestauni oes eae a torneo casereees 105 SLA EXCCULION Progres S orreina EEE a A 107 Selk O REDOING rererere A aA aa 116 SAOL NCW Edeier E 117 3 1 5 6 2 Report of several test suiteS sssessssesurersnnnnnrensnsrerrns 127 Isko Chart SCINS ieioea EEE 131 3 1 5 6 4 Previewing and Saving cccccceeeccccssceecccueenneennreeeeeenssegs 13
3. Figure 208 Copy Meta Data There you can choose from three possibilities to paste e Copy without Meta Data Only the selected part of the structure is copied but not the metadata e Copy with Meta Data o Only those assigned to opened project The selected part are copied only with those metadata which are already assigned to the target project o All used in selected sub tree The selected part with all assigned metadata is pasted to the project B Metadata which is not yet assigned to the target project are implicitly assigned to it The third possibility is disabled if the user has not the right Copy All After opening the window the metadata types checkboxes are selected which are used in the copied sub tree You can also un select each metadata which should be pasted By clicking OK the items are added to the test structure 3 3 5 Find and Replace TEMPPO offers a find and replace mechanism By pressing F3 or activating the menu item Edit gt Find and Replace Figure 209 is shown Page 170 User Manual TEMPPO V6 0 Edition March 2014 Description of Use irina o x Test case Test package search in user defined ID for Replace with Direction Up E Case sensitive i Bown Find Next Find Mext Test Case Replace Replace Allin Test Case Replace All List Occurrences Figure 209 Find and Replace The find replace dialog includes two tabs wherea
4. Figure 49 Test Case Test Step Editor With cut copy paste you copy or move one or more test steps via multi select either within a test case or to other test cases in the test structure By selecting a test step and pressing the corresponding button you apply these functions Even the short cuts lt Ctrl gt X lt Ctrl gt C and lt Ctrl gt V are supported If the mouse cursor is located over the column headings a menu for hiding and displaying the columns is popped up when pressing the right mouse button w Input w Expected Figure 50 Context menu for column hiding displaying 3 1 3 1 3 Test Creation Assistant When pressing t or double clicking a test step Figure 51 is displayed The Test Creation Assistant can especially be used to edit text fields with a long description and navigate up and down between the test steps If the last step is opened and you press Navigate down test step a new step is inserted Page 52 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Test creation assistant X Navigation main mend Instruction Haut st data Ment points Destination memory Destination entry Last destination POls are offered Sk TMC sk4 Mode SKS Settings Bale Expected ores Figure 51 Test Creation Assistant 3 1 3 1 4Keyboard edit mode Quick editing and navigation in the test step table is supported by lt F2 gt start st
5. Test Suites Oblocked M failed Bnotimplemented M passed aee Figure 117 Analysis with previous test suites There is also the possibility to save the chart as jpg or png file by pressing the button Save As 3 1 5 2 Requirement analysis You create a special analysis chart by selecting the node to analyze and activating Evaluation gt Analyse selected gt Requirements only At first you have to select the requirement structure which you want to analyze If the requirement structure is imported from an RM tool only the selectable requirements are analyzed If you want to analyze the requirement attributes you should select an attribute Then the analysis is calculated with the values of attribute see example Figure 123 Figure 118 shows a requirement analysis if the plan value for the coverage is greater than 1 test case The requirement GEN FN 0030 is covered by 2 test cases but the plan value was 3 Therefore the requirement is displayed red means Coverage false The following chart types for displaying the data are possible e Horizontal bar chart e Horizontal bar chart 3D e Stacked horizontal bar chart e Stacked horizontal bar chart 3D There is also the possibility to save the chart as jpg or png file by pressing the button Save As Figure 119 Figure 122 and Figure 121 show an analysis from a requirement structure displaying the number of assignments from a requirement to test cas
6. Figure 219 New branch confirmation Pressing No will abort the action Pressing Yes will create a new V2 2 branch a branch latest version of the test structure and the test package in this branch latest version The latest version in the branch will automatically be activated and can be edited like the latest version in the main line usually Page 177 User Manual TEMPPO V6 0 Edition March 2014 Description of Use called main latest One version can have several branches which can be created in the same manner Motepad RTF Import with Tos oN Edit ERI Test Suites for W1 1 2012 02 16 Cy Check In Wl 44 editable version Eales Activate O A Test Suites for W21 2012 02 16 iF Merce i FE Menge O ke W2 44 editable version eae i B23 gt Tree style ie VE Versions only WT eciteable varsi Labels only if versions and Labels ClearCase style m Order tf ascending descending Close Figure 220 CM Branch After working on a branch it is necessary sometimes to merge the results of a branch version e g V2 2 1 Branch to the latest version of the main line e g V3 latest There are 2 possibilities of merge support in TEMPPO On one hand you can merge a whole test structure to the latest version of the main line whereas the latest version will be checked in before copying the branch The additional version of the main line is necessary in order to keep the pos
7. TEMPPO Test Suite Generator Cancel Figure 76 Name and comment Bj Test Suite Wizard x Steps Determine the test suite 1 Introduction Select and apply fiter or attributes values and logical operators 2 Choose creation mode 3 Select an existing Test Suite Filter E No filter v Apply 4 Select nodes or subtrees Attribut Val 5 Enter testsuite name meee one 6 Determine the logical ie Regressiontest expression 7 Remove test cases manually I O ax Regressiontest yes TEMPPO Test Suite Generator lt lt Prey Next gt gt Figure 77 Logical Expression Cancel When pressing Next the user can remove test cases that should not be executed Figure 78 The test cases are also pre selected like the predecessor was set The de selection can be realized with the lt CTRL gt and lt Shift gt keys Page 73 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard 4 x Steps Rework Test suite Introduction Select obsolete test cases hold lt STRG gt and lt Shift gt for muti select Choose creation mode Select an existing Test Suite Test object Version XYZ RCO2 16 02 2012 Detailed description of the required product features Z Required functions of the product J File Administration B a New Fl New ile opened no changes not executed L Search Functions Find a Find up
8. TEMPPO Test Suite Generator lt lt Prey Next gt gt Finish Cancel Figure 80 Copy Select a test suite In the final step test suite name and comment are to be specified Additionally you can configure if you want to get Actual Result and Bug ID of source test Suite You can retest bug fix more efficiently Page 75 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard E Steps Determine the test suite Introduction Enter test suite name T 2 3 4 Select nodes or subtrees 5 6 Test object Version XYZ RCOS COPY 7 Remove test cases manually Created 16 02 2012 14 52 33 Owner Testmanager Type Test Suite Description Assume the actual result field Assume the bug Id field f TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 81 Copy Enter name and comment 3 1 4 1 4Special Based on an existing test suite with restrictions to test results This mode is a special one that solves a problem that arises in many projects Normally after test case execution you ll have a test suite with passed and failed test cases and therefore bugs in the SUT that have to be fixed in future versions For testing such a new version it can be decided to test only the test cases that failed in the previous test execution In TEMPPO you are supported by the special mode that provides you t
9. af Test Execution fagina Planning and rePorting Organizer j User Manual Edition March 2014 Copyright Atos IT Solutions and Services GmbH Microsoft MS MS DOS and Windows are trademarks of Microsoft Corporation The reproduction transmission translation or exploitation of this document or its content is not permitted without express written authority Offenders will be liable for damages All rights reserved including rights created by patent grant or registration of a utility model or design Right of technical modification reserved Contents L OVGRVICW ciicianspanrsivatarscenscsnnstnnpadssanssansseessbestiannnnarieniadasacenanetinesinananeane 8 Z ENEFOGUCEION sirarsa Ea 9 ENE TeSt PrOCESS scsinnnts iiic aaa N 10 3 Description of US ssss 22 2522u2202u2u2050u2uununuunnnnnnnnnnnnnn 13 3 1 The Test Process Phases ssssssssssnsersnrnrnnrunnnrsnrnrnernrnneunnnrsnsnrenns 13 Sea TeSt Pan sennen A EEA A 13 3 1 1 1 Writing the Test Plan sssnssssnssnsssnnsnnnnsennnnnnnnnnrnnsnrnnrnrnnnns 13 Ilk Witing the Project PIAN siceririnariceni dert TANEN 13 3 1 1 3 Defining Test Case AttributeS ssssesssssssnrnnrursnrsnrnrsnrnrenens 14 3 1 1 4 Baseline Import RequirementsS sessssssssrnnnnrsnrsnrrrnnrurenens 14 DA TESCDE SIOM N 14 3k21 Working With PFOJECES sicsGavissncaataaieitensaeacaaaidina a aaea 15 AAi Creanga ProjeCteir erior eor E r 15 3 422 4 2 OPENING an EX
10. Not all combinations display valid values Test Suite Execution Time Tester Execution Time Page 110 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 5 5 2 2 Filtered If a test suite is opened and menu item Execution Progress gt Filtered is activated Figure 131 is shown By pressing the button Select Test Suites Figure 130 is displayed where you can set a filter and select from the test suite tree with the mouse together with lt CTRL gt pressed the suites to be displayed Value IN v 683 req684 req635 Components IN req633 req684 req635 Tree style Notepad RTF Import with TCs V4 Versions oniy V1 1 Test Suites for V1 1 2012 02 16 V7 1 7 editable version Test object Version XYZ RCO1 16 02 2012 Versions and Labels Test object Version XYZ RCO2 16 02 2012 YJ Test object Version XYZ RCO3 16 02 2012 g gt Test object Version XYZ RC03 COPY 16 02 2012 Labels oniy ClearCase style Order V2 V2 1 Test Suites for V2 1 2012 02 16 ascending V2 1 1 editable version d ji Version 2 of Test object RC01 16 02 2012 V2 2 W227 V3 editable version Figure 130 Select Test Suites If you want to display several consecutive versions you have to select the first one keep holding the lt SHIFT gt key and select the last one in the tree normal selecting behavior The following chart types are available e H
11. Od Save O Gl Save as 27 01 2004 13 27 25 Exit O A Ext file open no changes O Gd Ext cancel file open changes O Gd exit No file open changes Gd Exit Yes file open changes lt 4 Open Open E Open normal 27 01 2004 13 27 14 Fuchs Clemens Open file opened changes 27 01 2004 13 27 18 Fuchs Clemens JEN Save aM Save ME Save as 27 01 2004 13 27 25 Fuchs Clemens Cred Exit fi Exit file open no changes fi Exit Cancel file open changes fi Exit No file open changes fil Exit Yes file open changes Figure 242 Manual import of test results Rules for importing If test results differ from test step results e g test case result passed test step 1 result failed test step 2 result passed the new test case result will be failed If a test case has already a result result output and it is set to not executed tester and tested will be deleted empty and result output is kept or updated 3 3 13 2 1 Import characters of other fonts If you want to import Chinese or Arabic characters the xml header has to be lt xml version 1 0 encoding UTF 8 gt For more information see 8 com 3 3 14Export Test Suite to DOORS This feature allows exporting Test Suite Results of test cases where requirements from DOORS Requirement Structures are linked to DOORS http de wikipedia or wiki UTF 8 and http www utf Page 192 User Manual
12. Selecting test results to be considered Enter test suite name TEMPPO Test Suite Generator Figure 62 Test Suite wizard Introduction When pressing Next Figure 63 is shown where you can select one mode Page 64 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard g x Steps Choose creation mode 1 Introduction 2 Choose creation mode New based on current test structure C New based on a predecessor Copy based on an existing test suite Special based on an existing test suite with restrictions to test results TEMPPO Test Suite Generator lt lt Prey Figure 63 Creation mode selection 3 1 4 1 1 New Based on current test structure This mode is the usual way to create a test suite The following steps are necessary e Test structure pre selection e Test suite name e Logical expression e Remove test cases manually Page 65 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard a xj Steps Test structure pre selection Introduction Select test packages hold lt STRG gt and lt Shift gt for multi select Choose creation mode 4 2 3 Select nodes or subtrees 4 Enter test suite name 5 TR Notepad RTF Import with TCs ga Introduction ga General description of the product E 5 Detailed description of the required product features Scope of delivery fe Sequences scena
13. e Server Port IP address or server name where Telelogic Change is running e Context If your Telelogic Change is located at context you have to add it here e Database only the name of the database e File of list box entries path to the config file of list boxes with its dependencies Page 219 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e User Password User name who will post a bug and password of the user e Role Role of the user in Telelogic Change Example If the web address of your Telelogic Change is located at http 158 92 135 211 change it has to be separated like in the following screen shot Telelogic Change User Interface Tree Telelogic Change gt Test Step Cells gt Analysis gt Newsboard Port 86644 gt Test Package Test Suite Context Database Database Test Automation gt Sik Test File of list box entries WinRunner Universal Fie Universal Socket File of default values gt QuickTest Pro Test Partner gt TEMPPO Designer IDATG Ranorex Commands Password SHOSSSSSSSSESSSSSSSSSSSSSSSSSSSSSSSSSSSSSESSSSESESSEEES Office Change Management Role User Bugzilla Server 158 92 135 211 User atw10905 gt ClearQuest Test fae clelogic Change Test JIRA Figure 280 Telelogic Change Page 220 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Manager 4 TEMPPO Manager The following TEMPPO configurations are
14. 3 3 14 1 Effects in DOORS Following steps will be processed during export 1 Creation of folder for test execution data if not already existing according to following naming convention Test Results lt Version gt lt Name of Test Suite gt 2 Copy of affected DOORS modules corresponding baseline or latest version to test execution folder if copies do not already exist The module is constructed by lt subfolder 1 gt lt subfolder 2 gt lt subfolder n gt lt module name gt lt baseline name gt Page 195 User Manual TEMPPO V6 0 Edition March 2014 Description of Use DOORS Database Test Results 3 1 1 A Sample DOORS Sel File Edit View Favorites Tools Help Ema a amp E E pr DEW Copy Formal SITEMPPO Sy Test J Results E3 3 1 1 A Sample s Usemame Administrator User type Administrator Figure 250 Copy of DEV module 3 Creation of module attribute test result in each module copy e Write test result into attribute test result of affected requirements If a requirement is covered by more than one test case a unique result will be built according to rules described above The attribute test result of not affected requirements will remain empty Formal module Test Results 3 1 1 4 Sample DEV1_Copy SRE File Edit view Insert Link Analysis Table Tools User Help HSe sme y DEV Copy 1 Regi 2 Aege 3 Reqs F failed 4 Regd P failed Username Administrato
15. Figure 334 Step 2 A JUnit test class can be selected by which a JUnit test suite is defined Hert z After clicking next the test collector specified in the Administrator see 6 2 starts searching for JUnit test classes JUnit allows having nested test suites one test suite containing others and it also allows naming two or more test suites having the same parent test suite identically e g All Junit Tests jJunit samples VectorTest Junit samples money MoneyTest Framework Tests Framework Tests Framework Tests Framework Tests Since TEMPPO will create a Test Package for each JUnit test suite and TEMPPO does not allow identical names of items with the same parent a warning message will be raised if the test collector finds test suites named like described above for further details see 6 3 2 Whit Import Warning B xj duplicate names in the same hierarchical level The import of these elements will cause an automatic renaming in TEMPPO and the references to their JUnit counterpart will be last G There are elements in the selected JUnit Suite with Figure 335 Warning of duplicate test suite names The related test suites are marked accordingly and can t be selected for importing Page 260 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fi Import JUnit Tests x Steps Test Case Selection Introduction Select all the JUnit test cases to be imported z Select a JUnit test class Select a set of
16. User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 5 6 2Report of several test suites When selecting the menu item Evaluation gt Report selected gt Several Test Suites Figure 145 is displayed Reports for several test suites are test structure wide Therefore such a personal report setting can only be provided to other test structure users Fi TEMPPO reporting settings Test Structure Settings Created E Several test suites with attribute filter 5 charts Testmanager 25 06 2013 12 5 This report setti Figure 145 Report setting test structure wide When creating or editing a report setting Figure 146 is displayed where you can e Select the test suites of a test structure e Seta filter for these test suites and e Specify the report itself Limitations It is only possible e to specify tabular reports as Excel or HTML e to select Result current and Result current and history for a test case Page 127 TEMPPO V6 0 User Manual Edition March 2014 Description of Use Hevonen enone eg Name NewReportSetting singa Owner Testmanager Fiter Created 25 06 2013 12 53 22 Ta _ Updator Testmanager Updated 25 06 2013 12 56 14 Description This report setting is used for evaluating more test suites za Figure 146 Report of several test suites Settings A TENerO mpor seira paea Deron E O Notepad RTF
17. With the change of predecessors the settings of the current test suite can t be changed in common Now all results of one test case are displayed in the new tab Previous Results see 3 1 4 1 8 All results can be analyzed see 3 1 5 1 1 and written to report see Figure 153 so that all results of a test case in a sequence of test suites can be shown Page 74 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 4 1 3Copy Based on an existing test suite This mode is used to copy a test suite and repeat a test run with exactly the same test cases The copied test suite will be created on a branch of the current selected test structure version Therefore it is possible to copy test suites from prior version to later ones and vice versa The following steps are necessary to do e Select an existing test suite e Test suite name In the first step the test suite tree is shown Figure 80 where you can select an existing test suite that will be copied to a new branch Bj Test Suite Wizard f Steps Select Test Suite x 1 Introduction Select an existing Test Suite 2 Choose creation mode 3 Select an existing Test Suite Notepad RTF Import with TCs V4 F W1 1 Test Suites for V1 1 2012 02 16 Ef V1 1 1 editable version Test object Version XYZ RCO1 16 02 2012 Test obje K est objec ct Version XYZ RCO2 16 02 2012 est ct Versio 1CO3 16 02 2012 V2 editable version
18. X A rested i sti i s SOSOSOSC CSY Yeas Testcases amp Goby Ewe S Chart Stacked Vertical Bar Chart 309 Orientation horizontal bertical Representation a jal jal la T si Cases Sug sbaolute onl oo rebative 355 i533 3 I Accumulate da a R gig Time Settings i s g gg a 8 8 8 Stort 09 12 2001 El Created End 09 12 2004 Ey Ura is ornis 200 Janu ory _ rs a i i 2501 Gecamben State BOeigned Bin Wok E Ready BB Ready foi Review Figure 154 Test case creation progress Test case creation overview test structure Graphical settings Y axis Sum of test cases X axis Test packages of first level Value subdivision State Display data absolute Chart Selection 3D Stacked Bar Chart Page 134 User Manual TEMPPO V6 0 Edition March 2014 Description of Use MS Betigned BinWok BReady MB Ready toi Review Figure 155 Test case creation overview Test execution progress graph test suite Graphical settings Y axis Sum of test cases X axis Tested Value subdivision Result Date Unit 1 Day Accumulate Data no Display data absolute Chart Selection Line Chart Page 135 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Gl chart E bata H Acme Tested Ya Axis Test Cases al Fi Grupby Ret ff Chart Lins Chart 36 Orientation horizontal a2 vertical Represer
19. reordered it keeps the new order but neither Updated nor Updator is written Changed TCs Detected changes Name test goal attributes planning attributes fields for automated TCs new attribute assignments deleted attribute assignments new requirement assignments and deleted requirement assignments If a change in test steps is detected all steps of XML file are applied Changed TPs Detected changes Name description test category change new delete change document path document name document chapter new attribute assignments deleted attribute assignments new requirement assignments and deleted requirement assignments Page 189 User Manual TEMPPO V6 0 Edition March 2014 Description of Use New TPs If a new TP is detected whose ID doesn t exist in test structure the TP is created No history entry is created like a create on the GUI New TCs If a TC is detected whose ID doesn t exist in test structure the TC is created No history entry is created like a create on the GUI 3 3 13Test Suite XML Export Import This feature allows exporting the entire or a part of a test suite into an XML document fill in some test execution data and import that information to TEMPPO E g some users may have complicated test automation tools scenarios whose test cases can t be started and executed from TEMPPO but are managed in TEMPPO Therefore those test cases are administrated in T
20. Device type 4 Device type Device type car G oo4 aE Device type Figure 39 Attribute value selection The test case design and the test design phase as a whole are finished when the test cases are designed and obsolete test packages are removed do not forget to do that The tasks of designing and developing implementation phase test cases are sometimes overlapping especially if designer and implementer is the same person or you import a complete test structure see 3 1 2 2 4 2 Page 45 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Requirement Optionally you can use the feature requirement tracking As described in chapter 3 1 2 3 4 requirements can be associated to test packages and inherited Of course it is possible to inherit requirements from test packages and or relate requirements to test cases Figure 40 shows the test case 3 4 1 1 1 New file opened no changes which inherits from the test package 3 4 Required functions of the product the requirements ComponentA R3 inherits from the test package 3 4 1 1 New the requirement ComponentA R2 has a link to the requirement ComponentC R3 Fi TEMPPO Testmanager Demo Notepad l loj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help z Test Structure Notepad RTF Import with TCs System Test v1 M a gt N GP EE No fiter M 243 4 Required functions of the product 3 4 1
21. General Attributes Test steps Ei utometion Requirements History Plan Execution History ee instruction Actionimage EERE l i A Unbenannt Editor Editor Pane cleared Bearbeiten Format Ansicht 7 Stro h Strg o peichern Strg 5 Speichern unter E 3 4 1 1 2 Mew file o pen n 3 4 1 2 Open a 3 4 1 3 Save 3 4 1 4 Exit 3 4 2 Edt Functions cae 33 4 3 Print Functions E a 3 4 4 Search Functions EMG 3 4 4 1 Find o gt EF 3 4 4 11 Find up fi 344111 Case fl 344141 2 Quicl 7 3 4 4 41 2 Find down _ ol 3 4 4 2 Replace aE Pe bn 345 Help System i I 4 3 6 External interfaces of the pre a 351 User interfaces z lock Apply Discard Seite einrichten Drucken Strg P Beenden Untitled Notepad in tithe bar Figure 52 New Columns in test steps There are 2 possibilities to add columns 1 TEMPPO Administrator Tab Metadata User Fields See chapter 5 4 7 You can create new Uploads directly in the database You have the possibility to define text or image columns 2 Import XML On the other hand you may have an XML file created by TEMPPO Designer IDATG or yourself that you want to import to TEMPPO If you follow the DTD can be found in your XML directory you can import test cases with additional columns The definitions in tab MetaData User Fields TEMPPO Administrator application are automatica
22. O x e Test Structure Notepad RTF Import with TCs System Test WA WM a amp HW No fitter ALA Notepad RTF Import with TCs EFLA 1 Introduction ft aa 4 parietal Geecinien of the procie Requirements History Flarn Execution History Sim 3 Detailed description of the required prod General Attributes Test Steps E Automation ee 3 1 Scope of delivery as 3 2 Sequences scenarios of interactir Inherit attributes E IA 3 3 User goals Sie 3 4 Required functions of the product Ea 3 44 File Administration e Medium a O T om Regular E validation Priority Mediun Z o B3411 New i a mA 344 1 1 1 Mew file opened D Error f Verification State in Tene ee 442 d LB 3 4 1 1 3 New Test Packac La 3 4 1 2 Open Additional Test Levels Attribute values d a saue ma Acceptance Test E Milestone Mit ool 3 44 4 Exit bai 54 3 4 2 Edit Functions amp Platform Windows 7 64 bit a TA 3 4 21 Undo E Regressiontest yes fae 42 2 E Test location Offshore La 3 4 2 3 Copy La 3 4 24 Paste DA 3 4 25 Delete ee ee ee ee fo Merge Lock Apply Discard os Figure 109 Locked test structure 3 1 4 7 2Test case execution with an exported test suite Let s continue the example of offline test case execution You ll close TEMPPO and unplug your notebook from the central database LAN Unplugged from the central database you first start the TEM
23. Program FilesiSiTEMFPO S 3ijretbinijava exe E Arguments Jar OStempimeinjar jar args argi Additional Arguments Cancel Figure 202 Hyperlink command Hyperlink to test case is defined if a test case or test steps are reused in another test case E g if you create a test case Login with some steps that is used other test cases it can be referenced by hyperlinks from other test cases First of all you create a step and select the text that becomes a hyperlink Page 165 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad E joj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help e Test Structure Notepad RTF Import with TCs System Test 13 H da b W GP E No iter d Notepad RTF Import with TCs EH 1 Introduction E E 2 General description of the product General tributes Test Steps Al Automation Requirements History Plan Execution History zi rS 3 Detailed description of the required product aE oe Expected 3 2 Sequences scenarios of interactions i 3 3 User goals E a 3 4 Required functions of the product E a 3 4 1 File Administration E 3 4 14 windows Login 32 File Mew pick Editar Pane cleared fi 34111 Login PE 3 Untitled Notepad in title bar EY ra 3 4 1 2 Nem EE 34122 Wew a TERE E sf 541 23 New Test Package c 3 4 1 3 Open 3 4 1 4 Save 0b bef 341 5 Ex
24. User Manual Edition March 2014 Import users from LDAP x i User cancelled importing users From LDAP Figure 297 Cancel the import from LDAP 5 3 1 3 Synchronizing users with LDAP A LDAP search for all TEMPPO users is performed and if they were found the first name and the last name are updated The synchronization will be performed for each user from the current LDAP server or for manually created users If a manually created user was found the column LDAP server is set The synchronization can be cancelled at any time by clicking the button Cancel Synchronize with LDAP X Laj i 1 User cancelled the synchronization Figure 298 Cancel the synchronization with LDAP If there are TEMPPO users with the current LDAP server as origin that could not be found in the LDAP server a dialog shows these users You can delete users by clicking the button Delete Fi Synchronize with LDAP X The Following users could not be Found in the LOAF server Thomas Andreas Andreas Michael Roland Holzlechner Manfred kKronegger Martin Mayrbaeurl Max Moritsch Karin Moritsch Karin xyz 10by1 xyzl0cl6 xyz9f769 xyZz11av4 xyzll4c5 y2lZbs2 xyz1l2903 xyzl sf xyzgf ci xyzgf4z atlnzpl0pa atlnzp10pa atlnzp10pa atinzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atInzp10pa atlnzp10pa atlnzp10pa Figure 299 Result of the synchronization with LDAP 5 4 Metadata You can customize Metada
25. Version XYZ RC02 Press Select Test Suites for choosing test suites Test object Version XYZ RC03 Select Test Suites is Test Suites is Test Cases Z Result Show 0 values wn a wn m ee m wn a Test Suites O planned O executed M failed passed Mnotexecuted O blocked E notcompleted M not implemented O on hold Figure 128 Execution progress of several test suites chart example 1 In the following example Test Suites is selected for x axis and Execution Time You can see that the Planned execution time is much higher than the actual one sum of passed and failed A test manager can also observe a large amount of remaining test time not executed ones Page 109 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Test Suite Selection Test object Version XYZ RCO1 Test object Overall test suite analysis Version XYZ RC02 Press Select Test Suites for choosing test suites Test object Version XYZ RC03 11h0 min 3 h 54 min 7 h4 min 6 h36 min Ime 5 h 30 min E a 2e LU 4 h 24 min 3 h18 min 2 h12 min 1h6 min Test Suites E planned execution time O actual execution time M failed M passed Bnotexecuted O blocked Mnotcompleted Mnotimplemented E on hold Figure 129 Execution progress of several test suites chart example 2 3 1 5 5 2 1 1 Detailed data Tab Detailed data shows the data table which can be exported to csv
26. oe 2497 Tire iMate Figure 173 Selection with lt Shift gt With pressing lt Shift gt and lt Alt gt the not visible items are selected too The tree is expanded and the items are selected see and Figure 174 Page 146 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Evaluat Test Suite Test abject Version Ye REOS COPY VA M4 W GP EE No nter i Test object Version sYa RCOS COPY Si 3 Detailed description of the reguired g 3 4 Required functions of the prod FI 4 3 4 1 File Administration 3 4 44 New 333 3 4 4 Search Functions Fy 3 4 4 1 Find bcs 34 444 Find up Figure 174 Tree after selection with lt Shift gt lt Alt gt in Test Suite There are two ways for deselecting e Deselect all Click on any item and the right side changes to the detailed view of this item e Deselect single item Press lt Ctrl gt and click on a selected test package or test case If the user has finished his selection he activates the context menu item Show Details see Figure 175 and the tabs with the content of the selected items is shown on the right side see Figure 176 and 3 3 1 2 The TEMPPO Designer Task Package and test cases generated by TEMPPO Designer IDATG cannot be changed and therefore also not in multi selection mode If such an artifact is selected the menu i
27. Bug ID test suite 105 Previous test suites 99 Requirement analysis based on several test Suites 113 several test suites 108 Several test suites 107 Apply 173 Attribute 14 customize See Metadata Attributes B Baseline 14 C Command Line 281 D Database connection See Administration Database Connection See Administration Database Connection Discard 173 E Evaluation 12 97 Excel import Test Cases 26 37 Execution progress Standard 108 Export test suite to DOORS 192 F Filter 181 change 184 criterion 185 delete 184 Edit filter criterion 187 export 187 import 188 Predefined 182 Find and Replace 170 Freeze unfreeze 251 TEMPPO V6 0 Index H Hyperlink Download an upload 168 Edit 168 existing upload 163 File 162 new upload 163 Remove 168 to description 161 to fields of test case in test suite 161 to instruction expected input 161 to precondition 161 to test goal 161 to to postcondition 161 Web 162 Hyperlinks and Uploads 161 Implementation Phase 12 Import Characters from other fonts 192 from Excel 26 37 J JUnit 256 Test execution 270 Update 265 K Keyboard Quick navigation 53 L LDAP 230 License Server See Administration License Server Connection Locks 252 Find 138 Login with password 224 Main Window 17 Metadata 233 Attributes 237 copy 169 Requirement Structure 241 Test Categories See Metadata Test Categories Test Levels 235 Uploads 240 Page 300
28. Meilenstein 11 Bi Ni wos Bie none cs Figure 114 Test Structure Analysis x Test Results X AXIS Resutt z Group by Resul a 70 hart vertical Bar Chart T 60 a0 50 30 20 10 blocked failed not nat not on hold passed completed executed implement ed Result Result blocked Ml failed not completed not executed E not implemented Son hold passed ce Figure 115 Test Suite Analysis A special analysis is the result coverage The following analysis compares or displays the planned tests and executed not executed tests Page 98 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bi analysis SS lt CO i Result Coverage kd Tecs Stacked vertical Bar chat GD E Figure 116 Test Suite Analysis Coverage 3 1 5 1 1 Analysis with previous test suites Now there is an analysis through a sequence of test suites predecessors Activate Evaluation gt Analyse selected gt with current opened explorer gt All and Figure 117 opens In the Analysis dialog you can set group values on the Y Axis and chart type Page 99 User Manual TEMPPO V6 0 x charti E vata Group by kes Test Results J z Chart vertical Bar Chart 3D Orientation horizontal C vertical Representation f absolute C relative Accurnulat 9 ae A a oa es New Te Dias ist jet wy W127 New Te
29. Of course you can upload files that exceed that limit and or change this value in admin properties TEMPPO Note X You are about to upload a file which exceeds the limit of 466 25 kByte v Do you want to continue Figure 200 File size exceeds the upload limit The fourth possibility is that you create hyperlinks with parameters e by atest automation tool e oracommand defined in settings see 3 3 16 2 11 which is selected in the first combo box Hyperlink with a test automation tool are defined like automated test cases You have to define a file and optional additional arguments for more details see 3 1 3 1 6 Pressing on the hyperlink defined with a test automation tool executes the link and then a message box is shown with the result Page 164 User Manual TEMPPO V6 0 Edition March 2014 Description of Use x web Si Fie E Database E Command EA manual Test Case Command Universalle Fie MTemp Testcase Ooml O00000 l Additional Arguments Command Line Previewy DaTempitest Case O cmd gt lt lt ResutFile gt gt 2 gt lt lt ErrorFile gt gt Figure 201 Hyperlink test automation tool Hyperlink with a command can be defined with additional arguments Pressing on the hyperlink defined with a command then the command is executed and then a message box shows the output of the process iieb File Database EJ Command EJ manual Test Case Command Fath e
30. Requirement Mame Requirement Structure Func_reqe4 Required Motepad WH All functions of the product implemented requirements Func_rege New Motepad W Al implemented ie requirements Func_reqzg Save Notepad V1 All 2 Pas Delete requirement implemented requirements El Lock Apply Discard tad off 3 5 4 2 Search Diak i 35 2 System aiil 4 F Figure 33 Test Package Delete requirement s 3 1 2 3 4 3 Inherit from parent test packages If you associate requirements to test packages we assume that the sub test package or children nodes may also refer to the same requirement It would be very time consuming to relate always the same requirements as many times as Page 40 User Manual TEMPPO V6 0 Edition March 2014 Description of Use you have children test packages Therefore TEMPPO offers you to inherit requirements from parent test packages O x Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test 41 H d gt H o Eor AL Notepad RTF Import with TCs Fe 1 Introduction HL 2 General description of the pre General attributes Details Requirements History Plan os 3 Detailed description of the rec ca 3 1 Scope of delivery I Inherit J 3 2 Sequences scenarios Ea 3 3 User goals Ea 3 4 Required f
31. Requirement name 14 No zero values Requirement name 17 Requirement name 18 Coverage Kenulinroank name wil Average number of TC s per requirement 8 00 TC s Requirement name 2 Percentage of requirements covered by TC s 100 00 Requirement name 20 Requirement name 21 coe Figure 119 Test Structure Requirement Analysis Page 102 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Requirement Analysis Demo Requirement structure 7 Stacked Horizontal Bar Chart v Requirement name 1 Requirement name 10 Requirement name 11 Requirement name 12 Requirement name 13 Requirement name 14 Requirement name 17 Requirement name 18 Requirement name 19 Requirement name 2 Requirement name 20 Requirement name 21 Requirement name 22 Requirement name 23 Requirement name 24 Requirement name 29 Requirement name 3 a tis ian a tis H Requirement name 31 Donitiramant mama 27 r z Stacked Horizontal Bar Chart v Requirement name 1 tc13442 tc13443 tc13444 Al Requirement name 10 tc13543 tc13544 tc13545 tc13546 tc13548 tc13550 tc13552 Requirement name 11 tc13574 tc13575 tc13576 Requirement name 12 _ tc13578 tc13868 tc13869 Requirement name 13 tc13581 tc13582 tc13583 Requirement name 14 tc13586 Requirement name 17 tc13611 tc13612 tc135992 tc13593 tc13596 tc13598 tc13600 Requirement
32. Sample code public class MyTestPkgWithStatSuite extends TestCase public MyTestPkgWithStatSuite String name super name public static Test suite TestSuite suite new TestSuite MyTestPkgWithStatSuite suite addTest new MyTestPkgWithStatSuite testSomethingRight protected void runTest testSomethingRight FE tet rn SuLte public void testSomethingRight assertTrue true Page 274 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Designer IDATG 7 TEMPPO Designer IDATG TEMPPO Designer IDATG is your gateway to professional and cost efficient test automation While up to now test teams had to spend a huge effort for the implementation and maintenance of automated test cases TEMPPO Designer IDATG aims at generating test cases based on a simple model of the application The advantage is obvious Instead of having to write test scripts from scratch and manually adapt each of them whenever there is a change in the tested application all that is needed now is keeping the model up to date The costs for test maintenance are reduced dramatically thus leading to shorter test cycles and better product quality The unique TEMPPO Designer IDATG tool combines user friendly test specification editors with a patented test case generator that employs a wide range of systematic test methods TEMPPO Designer IDATG supports a number of popular GUI testing tools but can also generate scripts for o
33. Special padlock icon green locked by the current user yellow locked by another user or due to an exported test suite Tool Tip Locked by lt user gt Page 139 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad 3 Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x Test Structure Notepad RTF Import with TCs System Test W 3 AL Notepad RTF Import with TCs Fb 1 Introduction et al 4 General description of the product General Attributes Details Requirements History Plan 3 Detailed description of the required prod 2 a 3 1 Scope of delivery ID S85 _ 3 2 Sequences scenarios of interacti 3 33 3 User goals d 3 4 Required functions of the product Heme Lew O ERJ 3 4 1 File Administration TEREE 4 1 1 Men O E 341141 New file opened Created 16 02 2012 16 45 50 Updated 16 02 2042 17 08 21 3 4 1 1 2 New file opened f 3411 3 New Test Packar LI 3 41 2 Open Number of TCs 2 3 4413 Save 3 44 4 Exit Test Category 3 4 2 Edt Functions 3 4 3 Print Functions Description om 3 4 4 Search Functions few 3 4 5 Help System H E 3 5 External interfaces of the product o H 3 6 ot her product features required a S E F eet a Lock Apply Discard Owner Testmanager Updator Testmanager Type Test Package Figure 162 Lock button 3 2 1 3 Creating a versi
34. amp amp i S amp amp amp Figure 179 Set Filter Page 154 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 3 Setting new assignments The user can set or remove attributes values or requirements to from the selected items If any changes are made the buttons Apply and Discard get enabled Values of radio buttons and combo boxes If a value is set and the button Apply is pressed all selected items get that value If no value is set nothing changes Values in lists Common values can be set and removed The assignment of additional test levels attribute values and requirements to the selected items is done analogue to the assignment of these values to a single item with the assignment dialog see Figure 180 Anew common value is written in red with a white background color see Figure 181 Fi Attribute value selection Attribute atrote vae E Color yellow Figure 180 Assignment dialog Page 155 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad E oj Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test w5 H db WH no fter Notepad RTF Import with TCs i 21 Introduction 5 1 1 Purpose of the document General Test Packages Test Case cE 1 2 Validity of the document 2E 1 3 Definitions of terms
35. considered If the items of the multi selection are still shown they are selected again see Figure 178 and Figure 179 The Show Details menu item has to be activated again because the selection has changed Page 153 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad ol x Project Test Structure Edt Test Execution Evaluation Tools Windows Help EE v4 1 1 Li Notepad RTF Import with Tos L 1 Introduction i z 1 1 Purpose of the document General Test Packages Test Caze 211 2 Validity of the document A 1 3 Definitions of terms and abbreviati 1 4 Relationship with other documente Total number of selected TPE 26 215 Overview of the document Total number of selected TCs 7 Relationship with existing projects Relationship with earlier and follow Purpose of the product Delimitation and embedding of the Overview of the required function General restrictions Hardware and software specificat 6 Product users M 3 Detailed description of the required prac Ea 3 1 Scope of delivery Sequences scenarios of interac D 3 4 1 1 1 Mew file opener 3 4 1 1 2 New file openec 3 41 12 at Packs Merge Apply Discard Figure 178 No filter Project Test Structure Edt Test Execution Evaluation Tools Windows Help 5 x a Test Structure Notepad RTF Import with TCs System Test 01 1 1 Menge Apply Discard
36. e g passed failed failed Test Suite results can be exported if a test suite is open and active and the menu item Export test suite gt to DOORS is activated TEMPPO first verifies whether the test suite contains any test cases linked to requirements imported from DOORS If no linked requirements can be found the user is informed via a message and the process is aborted x 1 Export to Doors not possible because no test cases with links to LD Doors requirements could be found in the active test suite Figure 244 Information Message If there are linked requirements the user is guided through the wizard Page 193 User Manual TEMPPO V6 0 Edition March 2014 Description of Use A Export of Testsuite Sheps Export requirement data to a RM tool 1 Introduction This Wizard assists you to export requirement data to a provided RM tool 2 Export of Testsuite affected modules baselines Figure 245 Export Wizard step 1 TEMPPO starts the communication with DOORS and searches for the affected module s baseline s in the DOORS database Before starting the export TEMPPO gives an overview Export of Testsuite Steps Export of Testsuite 1 Introduction The Following DOORS modules will be copied and updated 2 Export of Testsuite affected with test results modules b aselines DEY 3 0 TEMPPO 5 2 Requirements The Following DOORS mudules could not be located the results of the corresp
37. external Figure 1 Test Process with TEMPPO Execute Automated TC external e Offline Test SS execution Page 10 User Manual TEMPPO V6 0 Edition March 2014 Introduction Test Planning This phase covers mainly writing the test plan and a project plan typically in a planning tool like MS project A test plan template can be found in the TEMPPO installation directory under doc and it takes into account the following issues test requirements baselined requirements in TEMPPO Requirement Manager test management responsibilities planning and organization CM etc preparations for the test e g setting up the test infrastructure creating test aids conventions etc tests to be performed including test goals end of test criteria test procedures sequences etc test cases test documentation error reporting procedure TEMPPO supports the issues test cases planning design implementation execution and test documentation evaluation i e you can refer to TEMPPO in your test plan for these topics Although your testing activities just started in the phase of test planning you might already anticipate the situation as it will be at the beginning of the test case execution or evaluation phase by that time you will have a lot of test cases However you have to consider now how test cases should be designed to make it easy to 1 select a speci
38. i Iii pO DRD 4 1 1 e 4 240pe 41 d45ave 3 4 1 44Exit 3 4 24Edit Functions 4 4 2 14Undo 34 2 22 Uti 34 2 3 2Copyi 3 4 2 44Paste 3 4 2 64D elete 3 4027 8 aSelect Al 3 4 2 7 lime Daten 34 2 84VVord Wrapt 3 4 2 945et Font 3 4 34Print Functions 34 5 14Page Setup So 34 35 24Print 3 4 44Search Functions o 344 1 FReplace oe 344 24Find FP AE Lale Oe ee OT Figure 12 Sample Software Requirements Specification for MS Notepad Sih J J J j 4 Mooo00 Y k 4 mm mm m mm mm SA SmwANe SS Ta Before starting the import process an empty test structure see 3 1 2 2 1 has to be created Then the menu item Test Structure gt Import Document Structure has to be activated which will cause the Import Settings dialog to be displayed Page 21 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Import Settings X Document C tempiPiichtenhet_Motepad rtf M Generate document path Heading Mask Heading Limit test structure depth to fa Generate numbers and start with f V Generate test packages ca Import description a Generate test cases m Import test goal Fixed test step columns Atest case is identified by a table with following headers M Instruction Instruction M Inget Input M Expected Expected m Ignore empty table rows ido not create empty test steps User defined test step colu
39. lif 3 4 441 1 5 QuickTestPro Test case 3 4 4 1 1 4 Test Partner Test case 3 44115 UA x General Attributes Test Steps EY Automation Recuirements History Plari Execution History UniversalFile Tool UniversalFie File fevni TEMFPONTEMP P Otsources lspriv bat S Additional Arguments Ai Command Line Previews OsvniTEMPPOMEMPPONsourcesispriv bat 0 i lt lt ResutFiles gt 2 gt lt lt Error File gt gt Lock Apply Discard Figure 60 Test case settings for Universal Automation Interface Results of test cases Page 60 User Manual TEMPPO V6 0 Edition March 2014 Description of Use All executables must create an output that contains at least this line result passed failed blocked not implemented on hold not completed Additionally TEMPPO can store an execution summary stored to the text field Result Output if the following block is written by the test executable to the output summary_begin summary_end After execution of each test case TEMPPO Test Manager will read the corresponding result file If the whole file is missing or if the result line is missing e g due to a crash of the test script the result of the corresponding test case will be set to blocked Otherwise the result of the test cases execution will be set to the value found in the result file If the summary block is present TEMPPO Test Manager will store the information found between
40. 1 412 WinRunner Check Ste 3 4 4 1 1 3 Quick TestPro Test ca E 34 44 14 Test Partner Test ca B Al 3 4 4 1 1 5 UAI not executed Figure 90 Test Case Result Attributes 3 1 4 1 8 Previous Results With predecessors there is also the possibility to get known about the results in the predecessor test suites The table isn t changeable Page 82 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad e F oj xj Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RC03 v1 1 1 M d b AGS E No fitter ALJ Test object Version XYZ RCO3 5j oh 3 Detailed description of the required g 3 4 Required functions of the prodi General attributes Test Steps BI outonction Requirements History attributes TR Previous Results plan Execution History LM 3 4 1 File Administration B E E ma Test Suite version Res Bwm 4 1 1 1 New file ope E 3 4112 New ffile ope Test object Version lt Z RCO1 1 1 1 editable version failed Testmanager 16 02 2012 1 E 2 3 4 4 Search Functions Test object Version XYZ RCO2 1 1 1 editable version not executed ve Test object Version XYZ RCOS 1 1 1 editable version passed Lock Apply Discard Figure 91 Previous Results 3 1 4 1 9 Enter new bug entry An actual behavior and in case of errors a bug ID can be recorded for eac
41. 153 3 3 1 2 3 Filter in multi selection mode ssssesnssssssnnsnsnrnssnesnrnrnnns 153 3 93 13 Setting NEW aSSIGNIMGNUS erence nceerad cocursrtstusinde raai 155 33 14 Move Ownership savas swede yriiwsiawnas aaa tes eeavans EA ceeds 158 Sebi Cleve scaeapancnatsnersetses pr uuuiitaon rr 159 3 3 1 6 Set test results i cerccnsccasenasiearathiodestaarteenthsicaneniamestenderhinl 160 J2 AHyperinKS and UPIOAGS seis ie neern E TEE Nani 161 I2 Creating PYDEFINKS wcsssevandvanacadnantranesenas sine sinranavawaesdiaiawene 161 aAA EdIENYDErINKS trinnin saree a N N 168 332 Remove NY DERN KS asrini a a 168 3 73 24 Download an UDlOA Gs rocii a taesiadesaate 168 3 MOVE OWMElSIND ierra AE 169 3 3 4 Map of Meta Data project wide COPY s ssssssssserssrensrrsrrnrrreense 169 3 3 9 Fi diand IR COVA CS soreinoaena i ai oana a E A aesalanty 170 3 3 5 1 1 Find Test Case Test Package sssssssssssnnrnnrnrrnrsnrrrenns 172 3 3 5 1 2 Replace Test Case Test Package cc cece cece eee eeeeeeeees 172 S350 APPA DISCE anea A eee mannan munnsaet euadeaayaaas 173 Soul NEWSDO ANG arere dada E A A Y 173 32520 WEFSIONING scescorntenscssaiccteosnivesdarbacdecoanavnccstanuceeeansuesdaroaceedoanaene 175 52929 COMPA O sarrerari a a cade orcsathe E A E a code aaa iei 179 3 3 10 ICC EAE E EE A E EE A A A A E E A E E E E 181 IALL Predefined MTE S caiene aa a a 182 RIOZ Croate NICSE asie A EE aa G eee esas 182 310 Change Tl Ce i awhacinaetcin dave
42. 188 XML update 188 Test Structure 11 17 create 17 generate test cases 23 generate test packages 20 import RTF document 20 28 open 19 properties 17 19 reopen 20 Test suite based on a predescessor 71 Based on previous results 76 copy 75 delete 249 Export 190 Freeze unfreeze 251 Import 95 191 tab Attributes 70 tab Details 70 Test Suite 12 82 create 63 Tools TEMPPO Designer IDATG 275 U User Management See Administration User Management See Administration User Management V Versioning 175 Page 302
43. 4 2 Edit Functions EH E 3 4 3 Print Functions i E 3 4 4 Search Functions bw 34 5 Help System Figure 205 Referenced Test case ID If you click on the hyperlink the destination test cases is selected automatically Additionally a Back button see Figure 206 is shown to return to the source test case Page 167 User Manual TEMPPO V6 0 F TEMPPO Testmanager Demo Notepad E joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test W5 ajx Ho d b WM E No fitter T El tll Notepad RTF Import with TCs a M H1 troduction E 2 General description of the product General Attributes Test Steps Ei Automation Requirements History Plan Execution History Eim 3 Detailed description of the required product e I Bo aa Expected p m 3 2 Sequences scenarios of interactions De 13 3 User goals PE Enter account in test domain Login successtul EL 3 4 Required functions of the product and password EG 3411 Windows Login EN 3 4 1 2 New o fill 3 4 1 2 1 New ffile opened no E 3 4 1 2 2 New file opened ch Sf 5 4 1 2 3 New Test Package c m 3 41 3 Open m 3 4 1 4 Save f e 3 4 1 5 Exit 3 4 2 Edit Functions 3 4 3 Print Functions namn 3 4 4 Search Functions be 3 4 5 Help System m 3 5 External interfaces of the product J 3 6 Other product features r
44. 6 Other product features required ni Ea 4 Specifications for project management O5 Obligations of the client E 6 Literature ET ANNEX Merge Lock Apply Discard Owner Testmanager Updator Testmanager Type Test Package Description Figure 104 Creating new test package on branch After pressing the Apply button the user automatically asked if he wants to apply the new test package or changes on it to the latest version x The test package was modified in this branch version Would you like to apply the changes alsa in the main latest version 3 1 4 4 Finding Bug IDs If you have the problem of finding bug IDs and do not remember the test cases you activate the menu item Find and Replace For more details see 3 3 5 3 1 4 5 Finishing Test Execution After all of the test cases in your test suite have their results recorded you have two choices check in the current version leave it checked out in this case TEMPPO Test Manager will prohibit editing test cases because they have results 3 1 4 6 Creating More Test Suites Here is an example with more test suites for more than one application release Page 92 User Manual Edition March 2014 TEMPPO V6 0 Description of Use F Open Test Suites X Motepad RTF Import with TES EH 4 EM Test Suites for W1 1 2012 02 16 Fl editable version A Test object Version XvZ RCO 16 02 2012 oA Test object Version XYZ RCO2 16 02
45. Designer IDATG F Connection status E X Locking structures OK Prepare data ating for TEMPPO Designer IDATGI to connect Figure 358 Connection Status TEMPPO Designer IDATG offers a huge number of features for test design test generation and applying several test design methods For detailed information see the TEMPPO Designer IDATG User s Guide The following screen shots illustrate a simple example of designing a task flow with several steps When TEMPPO Designer IDATG is opened it displays the task packages defined in TEMPPO and automatically creates a use case for each leaf in the task package hierarchy The user has now the possibility of creating task flows consisting of several steps The following figure shows a modeled task flow consisting of some steps A task step consists of several attributes like name description expected result commands for test script conditions etc All this information will be used in the generated test cases Figure 360 displays a sample step FR IDATG Task SubusecaseNewalreadyopened i loj x Project Edit Draw View Window Generate Help ceH2 i2e 9e 4 S S 8 a 4 a Oo ia x oy amp ee ot So SX x F Task SubusecaseNewalreadyopened E l Project Notepad Elf System amp Acceptance Test Ele IDATG Tasks e Use case File Mew Sub use case New already opened Press OK Window _closed ny H E Sub use case New
46. Discard amp 8 S amp amp amp Figure 176 After Show Details content is shown 3 3 1 2 Display of assigned attributes and requirements 3 3 1 2 1 Test Structure After activating the menu item Edit gt Show Details two tabs Test Package and Test Case are displayed Tab Test Package with the sub tabs General and Requirements and tab Test Case with the sub tabs Attributes and Requirements that contain 3 sub tabs for own attributes requirements inherited attributes requirements and the inheritance state If at least two test packages and no test case are selected the tab Test Case is disabled If at least two test cases and no test package are selected the tab Test Package is disabled Page 148 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 2 1 1 Test Case tab Attributes The tab Attributes contains 3 tabs Direct linked Attributes Inherited Attributes and Inheritance Tab Direct linked Attributes displays the attributes Requirements Plan attributes which are directly linked to a test Ged iied Airea Te case n Type and Situation radio buttons aa a ee Error 0 Verification State r If all selected test cases have set the same value the value is selected otherwise there is no selection Priority and State combo boxes If all selected test cases have set the same value the value is displayed otherwise the sele
47. Downloads io hy Podcasts 4P Eigene Datenquellen oo My Received Files ca rrorReport20d 21 3021 30732 Eigene Widens gt error Report201 214021 44458 9 Nerovision C error Report201 215021 33105 O Obsorge geglo o Ranorex E HF D SAP 3 I MO RA AT Schlosser Home MENS working B SharePoint Dras vernendete Eigene Dateien Arbeitsplatz File name Open n Poed Files of type emt Document File xml Cancel TEMPPO Reporting Progerty File troi Figure 158 Import report settings In the file dialog you can set the type of file to trp or xml After selecting a file and pressing open report setting is imported to TEMPPO 3 2 Multi user ability Multi user ability establishes an environment for working with several users in a parallel way on the same test structure or suite It prevents unintentional overriding of changes manages the synchronization between viewed and stored data and avoids inconsistency if multiple users work on the same database Moreover it provides features to facilitate the collaboration in a team working on the same TEMPPO Project Chapter 3 2 1 describes the behavior when locking and editing an item On the other hand chapter 3 2 2 illustrates the 2 possibilities of refreshing manual automatic Multi user ability is not supported for MS Access databases 3 2 1 Lock modes TEMPPO provides 2 possibilities of locking items test packages test cases e
48. E 3 2 Sequences scenarios of interactions with the environmen EJ automation Requirements History Plan Execution History D33 User goals a 3 4 Required functions of the product wi Ru Et 43 4 1 File Administration ee nunner S Er a oe File C Program Files Mercury Interactive win Runner samples dighttests chbxstat o D 3 4 1 1 1 New file opened no changes aM 3 4 1 1 2 New file opened changes or 3 4 1 2 Open oo 3 4 1 3 Save ob bl 3414 Exit 3 4 2 Edit Functions 3 4 3 Print Functions fe 3 4 4 Search Functions ERAN 34 4 1 Find 2 dee a 3 4444 Find up E i dii 4 L eee Script Data 3 4 4 1 1 4 Hew Test Case FP 344 145 New Test Case 1 z lock Apply Discard Figure 56 Automated WinRunner test case The paths to the WinRunner QuickTest Professional SilkTest TestPartner executables are specified in TEMPPO settings see Figure 57 Page 57 User Manual TEMPPO V6 0 Edition March 2014 Description of Use settings x WinRunner fl User Interface p Tree Application Path CaProgram Files Mercury Interactive win RunnenarchWwirun exe S Test Step Cells Analysis Temporary Path c AProgram Files Mercury Interactive Win Runner tmp S p Newshoard aTi st Suit Baran oon Result Path CAProgram FilesiMercury Interactiven Runnertmg I Test Automation Silk Test Result viewer CAProgram Files Utra Editwedits2 exe niwersal File H Universal Sock
49. F TEMPPO Testmanager 5 x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Li Mer BS Duplicate i Open Reopen gt 1 Notepad System amp Acceptance Test Demo Notepad l a lose gt 2 Notepad Demo Notepad generated v4 o Te 3 Notepad Demo Notepad generated w1 1 1 we 4 Notepad System amp Acceptance Test Demo Notepad v4 El Import Structure Update 7 Export Structure Apply reguiremernt updates Task lists Hewshoard T Versions amp Find locks Figure 11 Reopen a test structure 3 1 2 2 4Importing an RTF formatted document TEMPPO is able to generate test packages and test cases from headings within RTF formatted documents You can either generate a basic test structure containing just test packages and no test cases or even a complete test structure with test cases 3 1 2 2 4 1 Generating a basic test structure If requirements are specified in Software Requirement Specification SRS documents they can be used to generate a basic test structure The obvious advantage of creating a test structure according to the structure of a base document is that the test case to requirement relation is evident every time This enables the test responsible to easily verify which requirements are covered by test cases Page 20 User Manual TEMPPO V6 0 Edition March 2014 Description of Use i II inl tk E s gt La ry W il
50. File Administration aa rate 1 New General Attributes Test Steps IE outonstion Requirements History Plan Execution History fe 8 403 4 1 1 1 New file opened no 2 E 3 4 1 1 2 New file opened ch V Inherit 1 3 4 1 2 Open gh M OO Ph OE Requirement ID Requirement Name Requirement Structure 4 1 4 CX d 3 4 2 Edit Functions ma req685 ComponentA R2 Components v1 H E 3 4 3 Print Functions v1 3 4 4 Search Functions __ Required functions of the product req683 ComponentA R3 V1 1 3 4 5 Help System ll New file opened no changes req6s Componente R3 Components 24 3 5 External interfaces of the product 5 5 3 5 1 User interfaces 8 3 5 1 1 Editor Pane A 2 51 2 Search Dialog 0 3 5 2 System interfaces oe pees Figure 40 Requirement Test case You might ask for reason of the requirement tracking On one hand you can analyze the test structure and on the other hand such a requirement analysis can be applied to the test suite For test structures you can create an analysis about the quality of your test coverage For test suites the quality of requirements can be visualized For detailed description of requirement analysis see chapter 3 1 5 2 e History History entries are generated for test packages and test cases The entries are Shown in an own tab History Only the entries until the last check in are shown If an item is merged the history is del
51. File exists S LY The file already exists Do you want to overwrite it Figure 107 Overwrite file After successful export the test suite with activated root node looks as follows Fi TEMPPO Testmanager Demo Notepad a _ ojx Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Version 2 of Test obeject ROOI V211 ey x MH d b H GP EE No mter eee obeject RCO i 3 Detailed description of the required g General Details Expor Into Attributes Predecessor Plan Mame version 2 of Test obeject Rci Owner Testmanager Updator Testmanager Created 16 02 2012 15 53 31 Updated 16 02 2012 15 53 31 Type IncludedTPs Whole test structure ExcludedT Cs Lock Apply Discard Figure 108 Locked test suite In the tab Export Info all exports of course more than one are possible of this locked test suite are listed Even the test packages are marked locked which means that the item is read only Test cases also cannot be changed but can be executed on workstations connected to the central database The corresponding test structure will also be locked Figure 109 shows that also test cases are marked read only The only possible change is to add test results Page 94 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help
52. Fort tp550 export dat 20 02 201 E41 Test Suites for V2 1 20124 Demo Not Notepad W214 editable w Test Pac Print tp553 export dat 20 02 201 El editable version Demo Not Notepad W214 editable v Test Pac Page Setup tp552 export dat 20 02 201 Version 2 of T Demo Not Notepad W244 editable v Test Pac Select All tp547 export dat 20 02 201 N Demo Not Notepad w2 1 1 editable v Test Pac Delete tp546 export dat 20 02 201 Notepad System amp Acceptance T Demo Not Notepad W211 editable w Test Pac Word Wrap tp549 export dat 20 02 201 Fi User documentation x Demo Not Notepad W211 editable v Test Pac Time Date tp546 export dat 20 02 201 a Demo Not Notepad W211 editable w Test Pac Cut tn643 export dat 20 02 201 E Figure 327 TEMPPO Administrator Large lock table Additionally you have the possibility to start a more concrete find by activating the checkboxes Exclude test suites and Suppress export locks e Exclude test suites If you want to see the locks of a project without test suites activate that checkbox e Suppress export locks If a test suite is exported to XML or DB each item is locked This may cause an large amount of locked item You hide those items by activating that checkbox Locked items can be unlocked by selecting any them and pressing the button Unlock selected items Page 253 User
53. Import with TCs ag El V1 1 Test Suites for V1 1 2012 02 16 v2 _ E V2 14 Test Suites for V2 1 2012 02 16 O B J v2 1 1 editable version i AQ Version 2 of Test object RCO1 16 J gt ok canos Figure 147 Report of several test suites suite selection Page 128 User Manual Edition March 2014 TEMPPO V6 0 Description of Use doia Test Result IN failed passed not implemented blocked C AND v General Q Req_ Type Header AND Sososo Ti itie Page oa GSI LW WD SiCOCTTa sy Priority v Hih a has X Test Result IN faled passed not implemented blocked AND Req_Type Header AND Priority High ox Figure 148 Report of several test suites Filter Page 129 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Additionally to standard reports you select General Information of Report which displays the selected e test suites e selected filter General Information of Report Filter attributevalue 63_ M1 Selected TestSuites Test object Version XYZ RCO3 V1 1 1 Version 2 of Test object RCO1 V2 1 1 Figure 149 Reported information LA TEMPPO report setting in proj Name NewReportSetting El Settings E Text General Information of Report _ Tabular Report General Information of Test Suites Charts Char 4 Text Charts Layout Continuous Tabular Fo
54. JUnit test ae Details Cafes 4 Set package default values Document 5 Settest case default values amp Summary Mame Chapter Precondition Page 261 User Manual TEMPPO V6 0 Edition March 2014 JUnit Figure 337 Step 4 Test package default values can be entered In the next step default values for JUnit test methods i e TEMPPO test cases can be entered Note that the same tabs as for TEMPPO test cases are presented in the wizard However it is not possible to enter values in the General tab The reason is that the only possible input field would be Test Goal and there is no meaningful text that could be entered there Since the test goal must be specific for each individual test case it does not make sense to define one common and therefore abstract goal for all test cases Fi Import JUnit Tests X Steps Test Case Default Values 1 Introduction Enter default values for the new test cases in TEMPPO z Select a JUnit test class 3 Select a set of JUnit test General attributes SE ditions Cares 4 Set package default values cs Regular Priority To 5 Settes case default values 4 x 6 Summary Error Designed i 7 adhe ce lens attribute Values TIE TEMPPFO Extension JUnit F Import JUnit Tests x Steps Summary 1 Introduction Review your settings z Select a JUnit test class 3 Select a set of JUnit test You choose to import
55. Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Bj TEMPPO Administrator Testmanager D 10 x B Database e Roles Users a Metadata DH Projects By Locks Ea License A a D Exclude test suites J Suppress export locks Unlock selected elements Example for versioning Demo Not Notepad v2 44 editable v Test Pac Performa tp562 export dat 20 02 201 T Link test t i rit HP eni p oesie Demo Not Notepad v2 44 editable v Test Pac Resource tp563 export dat 20 02 201 S Notepad RTF Import Demo Not Notepad W211 editable w Test Pac Systemin tp560 export dat 20 02 201 1 editable version Demo Not Notepad W214 editable vw Test Pac Other pro tp561 export dat 20 02 201 EH Notepad RTF Import with TCs Demo Not Notepad v2 44 editable v Test Pac Externali tp558 export dat 20 02 201 i Demo Not Notepad W214 editable w Test Pac User inter tp559 export dat 20 02 201 4 Test Suites for V2 1 2012 4 Demo Not Notepad W244 editable v Test Case Test Part tc702 export dat 20 02 201 4 editable version Demo Not Notepad Version 2 V2 1 1 editable v Test Suite Version 2 export dat 20 02 201 Version 2 of T Demo Not Notepad v2 44 editable v Test Case UAI tc703 export dat 20 02 201 Siera lt De
56. Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Figure 291 Role properties General Details The functions are predefined and cover the whole functionality of TEMPPO Administrator and TEMPPO Level of access of the function e New or execute e Edit e Delete e Read e Move Ownership e Consider User objects can only be deleted if the user is the owner of the object In the dialog only the possible checkboxes are shown E g report It only makes sense and is only possible to execute a report Therefore only the checkbox New or execute can be selected By this way roles can be created and adapted due to user demands 5 3 User management Fi TEMPPO Administrator Testmanager _ Oo x Database Roes Users a Metadata LA Projects Locke E License C Fas LDAP OOOO o oaee Firstname fon OOOO E k Testeri testerz testers tester4 tester5 testerB tester Testmanager hanhan ee Be es temppo_um Figure 292 Administration User management This tab is only active if the connected user is allowed to by his assigned roles Users are created changed and deleted here The list shows all currently existing users By clicking the New or Properties button the user properties dialog pops up where you can change the user name Clicking the Delete button will delete the selected user after you confirmed the verification message By selecting the checkbox LDAP yo
57. Metadata is defined project spanning The assignment is made per project Fi Meta Data Editor x Test Levels Test Categories _ Attributes E Uploads ia Requirement Structures E User Fields Find S ui Layoukt Test S Maintenance Test Performance Test Portability Test Reliability Test s Resource Test Z 4 7 Stabe Based Test a Task Based Test Usability Test Figure 323 Metadata Editor Example On the left side all available test categories are listed By clicking the buttons gt gt gt lt lt lt the test categories can be moved to right list box The assignments on the right are saved by pressing the button Apply 5 5 8 Move Ownership In the TEMPPO Administrator there is the possibility to move the ownership of the whole project or of parts of it A part of a project is a test structure or a test Suite Page 250 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator The button Move Ownership in the project tab see Figure 317 is enabled if a project or a test structure or a test suite is selected After pressing the button Move Ownership the following dialog comes up x tastname Frame ton le atwl 12h9 E Tester E tester E Testmanager ores Figure 324 Move Ownership The new owner of the project or part of it can be chosen By clicking ok and a project was selected the owner of all items of the
58. Test structure dtd is the DTD file See 13 1 Otherwise the import will fail In your TEMPPO installation directory there is a subdirectory XML where you ll find the DTD Test structure dtd together with an XML example Before the importing process can start you have to decide if the requirement assignments should be imported too ML Importer x i j Do you want bo import the reguirment assignments too Figure 21 Import with requirement assignments Before you can import a test structure with requirement assignments correctly the requirement structure already has to exist in the database Import the requirement structure before Stages of Import Page 28 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 1 Parsing and validation of XML file checking of semantics and creation of new objects 2 Saving new or modified objects to the database 3 Reloading of the whole test structure from database Each stage has its own progress bar When the import is finished the following information dialog comes up SITEMPPO x 2 Test structure successfully imported The imported test packages and cases are placed below the selected node 3 1 2 2 7 1 Possible errors during the import eros Reaction XML file doesn t match DTD schema Nothing is written to the database a message is shown and the project status before the import is loaded from database Required attribute exists but is ze
59. Test Automation Ranorex 59 Universal Automation Interface UAI 60 WinRunner Quicktest Professional SilkTest TestPartner 57 Test Automation settings 207 Test case Additional test levels 45 Attributes TR 82 Execution History 49 Link Requirements 39 Set test results 160 Tab History 46 Tab Plan 48 Unlink requirement 40 Test Case 9 81 82 Adding more columns 53 attribute 9 Compare 179 design 42 Import from Word 23 Merge 90 Postconditions 50 Preconditions 50 results 78 tab Attributes 43 tab Automated 56 tab General 43 Tab Requirement 46 tab Test Steps 51 Test Case Execution 12 62 Test Case Implementation 50 Test case template 247 Page 301 User Manual Edition March 2014 Filter 249 Test Categories See Test Package categorize customize See Metadata Test Categories Test Creation Assistant 52 Test Design 11 14 Test execution add test package 91 Test Execution 79 add test case 91 automated 86 continue 88 92 finish 93 manual 77 start 63 Test Level 11 customize See Metadata Test Levels Test Package 11 categorize 34 create 31 Test Plan 11 Test Planning 11 13 Test Result template 249 Test step Copy Upload 55 Delete Upload 55 Paste Upload 55 Pictures in columns 55 Reference to Upload 55 Upload 55 Uploads 55 Test Step See Test Case tab Test Steps results 77 Test structure delete 249 Extend 31 Freeze unfreeze 251 Transfer 30 TEMPPO V6 0 Index Transfer to other database 30 Version 19 XML export
60. Test object Ver Test object Ver Test Suite Selection Test suite analysis depending on fiter settings Press Select Test Suites for choosing test suites and setting filter a k itt EE 3 d Attribute Value Components req634 req635 Components IN req683 req634 req635 Figure 132 Test Execution Progress Filtered Data 3 1 5 5 2 3 Requirements only You create a requirement analysis chart of several test suites by activating Evaluation gt Progress charts gt Execution gt Requirements only if at least a test structure is opened It is only possible to create a test suites chart of a single test structure When opening that analysis the chart is empty and you can select the test suites in a window that opens if you press the button Select Test Suites A Select Test Suites E Notepad RTF Import with TCs p Besse Eb V9 Versions only EbV4141 Test Suites for V1 1 2012 02 16 VT 1 1 editable version Test object Version XYZ RCO1 16 02 2012 Versions and Labels Test object Version XYZ RCO 16 02 2012 Test object Version XYZ RCOS 16 02 2012 P pearen 16 02 2012 Oni EF V2 a WZ 1 Test Suites for V2 1 2012 02 16 ascending PE Eb V2 1 1 editable version i H descending Version 2 of Test object RCO1 16 02 2012 L eee Page 113 User Manual TEMPPO V6 0 Edition Marc
61. Therefore 2 sub test packages are necessary that refer to these requirements Fi TEMPPO Testmanager Demo Notepad Ioj x Project Test Structure Edit Test Execution Evaluation Toole Windows Help Test Structure Motepe Test Package Ctrl Alt T a Test Package before Dl Test Case Ctrl Alt C Sri Util fi Test Case before Find and Replace LI Notepad RTF Irr E 1 Introductior i E Select All Ctrl A 2 General de es Details Requirements History Plan 3 Detailed de DE E Tree o ag i WE Compare db Cut Crx E Search Functions i B Ez 2341 Copy Cirle Testmanager Updator Testmanager o 342 A paste Ctrl H 343 a 15 02 2012 16 28 59 Updated 16 02 2012 08 12 20 bE mm GL Paste before a ELET B 3 5 Exter s0 ce 38 Other S Delete H 4 Specificatio i x 0 5 Obligations l 6 Literature 7 Annex i Edit Fitter e Test Package i Order Test automated test case ii Refresh recursively fa Mowe Ownership gt Lock Apply Discard 1 Figure 24 Create new test package In Figure 25 such a test package Search Functions was identified and split up into Search Up and Search Down A reference to the document containing the Page 31 User Manual TEMPPO V6 0 Edition March 2014 Description of Use description e g a use case document of the respective requirement was applied to the new test packages which made them be displayed c
62. User Manual Edition March 2014 User Field 244 Migration See Administration Database Migration Move ownership 169 Multi selection Delete 159 Move ownership 158 Multi selection mode 142 Multi user ability 137 N Newsboard 173 P Plug ins 283 Progress charts 105 Creation 105 Execution 107 Requirement analysis based on several test suites 113 Project 15 copy 246 create 15 245 open 16 properties 16 Test case template 247 Projects 245 Assign metadata 250 delete 249 Freeze unfreeze 251 Move ownership 250 Test Result template 249 R Refresh 141 recursively 141 Reload whole tree 141 Report Export to XML 136 Import from XML trp file 137 Import Templates 136 New 117 Several test suites 127 Templates 136 Reports 116 Chart Settings 131 General Settings 118 preview 132 samples 134 save 132 Textual Settings 120 Requirement Analysis 100 delete 40 Test package 39 41 Requirements Import 14 Roles 227 Predefined 292 TEMPPO V6 0 Index S Settings 198 Bugzilla 217 Change 219 Change Management 216 Clearquest 218 Global 198 JUnit 213 QuickTestPro 211 Ranorex 214 TEMPPO Designer 214 TEMPPO Test Manager 199 Test Automation settings 207 TestPartner 212 UAI 209 T Task lists 196 TEMPPO Administrator 226 LDAP 230 License Server Connection 254 Locks 252 Metadata 233 Projects 245 Requirement structures 241 Roles 227 Uploads 240 TEMPPO Designer Restore designed test cases 280 TEMPPO Manager 221
63. V6 0 Edition March 2014 Description of Use Should be configured On the right side all single settings can be edited see Figure 256 User Interface Tree Test Step Cells Analysis gt Newsboard Test Package Test Suite Database Test Automation Silk Test WinRunner 7 Universal Fie Universal Socket gt QuickTest Pro Test Partner JUnit TEMPPO Designer IDATG Ranorex Commands Change Management gt Bugzilla ClearQuest Telelogic Change JIRA Expand the tree to edit settings Figure 256 Settings Via button Restore Defaults all settings of the selected setting group are restored to the default values Following settings can be configured in TEMPPO e User Interface o Tree Test Step Cells Analysis Newsboard Test Package o Test Suite e Database settings e Test automation o Silk Test WinRunner Universal File Universal Socket QuickTest Pro Test Partner JUnit TEMPPO Designer IDATG o Ranorex e Commands e Change Management Bugzilla IBM Telelogic Change IBM Rational Clearquest JIRA O O O O OOO O O O O O O Page 200 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 16 2 1 Tree Tree settings which can be changed are see Figure 257 Property Default Description value Display automatic deactivated Switches on off to display the internal numbering order of items in the tree Recursive activated Switches on off to show the order recurs
64. aa aaa 184 3 5 10 04 Delete Or iaiaaeaia eenrieesacisainawniataeeen teins 184 3 3 10 5 Defining the filter CriteriOn ccccssseeeeeeeeeeeeneeeeeeeesseeeeuunenns 185 IANO ZEGIE TILE CRCCHOM autern a e 187 LLO EXPO TILED riaren e a e A AE N 187 210S IMPDO MTO tasnmasseentasesnaveustsaensaiesvamiact eanetaaaanevse veaesaaes vanes 188 J2 LL TESTS SrUCtUreE XM LAEX DOPE pisiri eriep test desneveasiaeressigeees 188 3 3 12 Test structure XML Update ccc cccccsssccceesseneeecceeeeeeeesseseceurengs 188 SS Zed Update DPOCESS sc sccsccciateusnnrdinreraistarssesaserciousawaiwieinrcedt 189 3 3 13 Test Suite XML Export Import cece eeeeeeeeeeeeeees 190 FRAL VEX DOME sernir n ETE examen N ews e ese e ees 190 3 956 De2 IMDO T errin iE TE S sees E E O 191 3 3 13 2 1 Import characters of other fONtS ccccceeeeeeeeeeeeeeeeees 192 3 3 14 EXDOrM Test Suite to DOORS necare niae EAE 192 JAL EMects MN DOORS rria a a eae eats 195 3a MASKIS ea canieaeaneusicamianueu arene aanionieains 196 3 3 16 S CUUING S aaaea aa rr 198 3e LOL GlODali SCE GS Sirion arainn ENEE AEE E AEE 198 Dolsk User Interlace ernir teeraa ETE a IT 198 Al LOGN aerer E 199 3 3 16 2 TEMPPO Test Manager SettingS ssssssnnsnsnsnsnsnsnsnsnrrrnsrenne 199 KAL e eee ne ne ene a ee ea en eee ree nn ee ere cree 201 Bo L6i222 TESE Step Cell arriendo riin Eai aTi 201 IRLA ANAY Saa a a A A 202 IIAG d NEWS SDO dereie a A A A A T 203 5 5 10 2 5 TESE DaCKaG O ri
65. and abbreviati HEPES Requirements Plan ZE 1 4 Relationship with other documents oo 418 Overview of the document Inherit attributes a 2 General description of the product Lon Relationship with existing projects m Purpose of the product f Error Werfication State Po Delimitation and embedding of the 5 Overview of the required function Delete TE nets Additional Test Levels Attribute Values Hardware and software specificat amp Device type CAR G 002 Milestone M1 Product users TA Acceptance Test M 3 Detailed description of the required prac TI System Test x i 3 1 Scope of delivery iha 2 Platform Windows 7 64 bit i nces scenarios of interac EI Regressiontest yes ED Test location Offshore 3 4 1 2 Open 3 4 1 3 Save J 3 4 1 4 Exit Apraly Discard G Bu G amp amp amp Figure 181 New common values Not common values displayed in grey can only be removed But if a user wants to apply a grey value to all selected items he activates the button Assign to all test cases Then this value is written in red with a grey background color see Figure 182 Page 156 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad Ioj Project Test Structure Edt Test Execution Evaluation Tools Windows Help e Test Structure Notepad RTF Import with Tes System Test W3 Z x H db WH no tte r Not
66. can update the existing TEMPPO test cases and test packages by activating the menu item Update structure gt from Ranorex Document selecting the corresponding csproj file and pressing the button Open If the update process is started in Figure 59 you can select the properties attributes attribute inheritance requirements requirement inheritance of test packages and test cases which should be retained after the update You can import test cases add meta information in TEMPPO change them in Ranorex update them in TEMPPO and keep the meta information Page 59 User Manual Edition March 2014 TEMPPO V6 0 Description of Use F Update J x Should the following attributes of the existing test structure be retained during the update process E Attribute inhertance E Requirements E Requirement inhertance Figure 59 Retaining existing test case package attributes 3 1 3 1 7 3 Universal Automation Interface UAI File based The purpose of this interface is to provide a possibility to manage test cases of proprietary automation tools in TEMPPO By this TEMPPO is independent from an automation tool You can create an automated test case by specifying any executable exe bat pl and the parameters which are handed over to the executable for test case execution The test case result is written to a file TEMPPO parses this file and sets the result within the test suite appropriately First of all you
67. cancelled and the user gets an information message If an XML file contains a test suite filter and it is imported to a test structure or vice versa the corresponding test suite filter is imported and an information window is shown The imported test suite filter is shown the first time when a test suite is opened and the filter dialog is called or the filter combo box is clicked 3 3 11Test structure XML Export This feature allows exporting the entire test structure or just a part of it into an XML document When a test structure is open and the root node or a test package is selected the menu item Test Structure Export Structure is enabled On activating this menu item a file open dialog is displayed When pressing the button Save the test structure is saved as XML file based on teststructure dtd 3 3 12Test structure XML Update This feature allows updating the entire test structure or test packages based on an XML document if you are using other tools for manipulating the test structure The update process adapts the test structure to XML file but keeps TC ids and TP ids and real updates of TCs and TPs are detected If you activating the menu item Test structure gt Update gt XML document a file open dialog comes up where you can select the XML file After pressing the button Open the XML document is read and checked against teststructure dtd If an error is detected the import process is cancelled If the syntax
68. cases in TEMPPO will be named according to the JUnit method name followed by the class name in parentheses testWethod SubClassOfTestCase Fi TEMPPO Testmanager Demo Notepad joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help a Test Structure JUnit System Test V1 lal x Wod b Hg E No filter M AL JUnit E Ea 1 Framework Tests El S 1 junit tests extensions Extension Test General Attributes Test Steps EI Automation Requirements History Plan Execution History o Jul 1 1 test Running Errorin Test Setup qunit t ade 4 2 test Setup Errorin Test Setup junit tes eer aered in tore I a 1 2 junit tests extensions Active Test Test Gy 1 2 1 test ctiveTest unttests extension Name ftestRunningErrorinTestSetup unittests extensions ExtensionTest ihg 1 2 2 testActive Repeated Test0 junit tests 1 3 junit tests extensions RepeatedTest Test Owner Testmanager Updator Testmanager oly 1 3 1 test Repeated Once junit tests exten why 1 3 2 test Repeated Mare Than Once qunit t oly 1 3 3 test RepeatedZero junit tests extens Type C Manual f A tomated Test Case ah 1 3 4 test Repeated Negative junit tests ex Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 28 Test Goal Lock Apply Discard Figure 342 Step 5 Names of test cases JUnit test methods Basically you are free to edit and change the automatically created structure and the names of test p
69. completely new O SubusecaseNewcompletelynew H Use case File gt Open i 49 UsecaseFileOpen SB Taxks 3 For Help press Fl Figure 359 Design Test Cases Page 278 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Designer IDATG Mame Delay mSec Priority Condit Ente names s SCS jo i anditons Event Actions User Defined Fields Stark Window Destination Window Browse Designators Commands for Test Script Description Input data New file name Enter name Expected Result Name entered Cancel Figure 360 Task Flow Step If the user has finished the modeling process he can start TEMPPO Designer IDATG s test case generator Depending on the selected options TEMPPO Designer IDATG will automatically generate test cases until the desired coverage is reached For instance 2 test cases would be generated for the task flow above if Step Coverage is selected To import these test cases into TEMPPO the user just has to press the Save button x P The data can now be transmitted to SITEMPPO Proceed Qxsxxx el Yes Send data to SITEMPPO Mo Save data as ML File Nein Abbrechen Figure 361 Save dialog For manual test cases the generated steps are displayed in TEMPPO TEMPPO fields are mapped to TEMPPO Designer IDATG fields as follows e Instruction Description e Input Commands for Test Script e Expected Expected Result For au
70. creating moving cutting copying and pasting one or more test steps within a test case or test structure wide to other test cases The column layout can be individually adapted by moving and hiding columns When pressing P show preconditions above the Test steps Edit Buttons all the preconditions from the test case and the test packages above are displayed see Figure 49 If the first test steps of a test case are implemented the preconditions can be hidden by pressing P When pressing P show preconditions beneath the Test steps Edit Buttons all the postconditions from the test case and the test packages beneath are displayed see Figure 49 If the first test steps of a test case are implemented the postconditions can be hided by pressing F When pressing L a new line for Instruction Input and Expected result is inserted The cell height is always 3 lines during editing When pressing Apply the cell height is adapted to the whole line The default cell height can be Page 51 User Manual TEMPPO V6 0 Edition March 2014 Description of Use configured in TEMPPO settings The test step number is created automatically With the two arrows 1 T you can reorder steps by selecting a step and pressing the proper button The test step numbers are updated automatically Test steps can be deleted by selecting them and pressing a General Attributes Test Steps Ei Atomation Requirements History Plan Execution History
71. description of the requir External interfaces of the product User interfaces Editor Pane Postcondition a 3 6 Other product features required 1 Performance 2 Resource Security 4 Safety 5 Portability 6 Reliability 4 Maintenance 6 Reuse 4 Usability H S 4 snecficatiaons for oroiect oneik F Postcondition User interfaces Editor Pane Figure 30 Test package without reference to a document name or chapter First of all you create a new test structure or open an existing one After this the test structure can be filled in the following ways Importing an RTF formatted document Import Test Cases from Excel TEMPPO is able to import test cases from an Excel list First you have to save your Excel file as csv and select a test package El Import Structure From RTF Document Update b l From XML Document 1 a Export Structure From Ranorex Document Apply requirement updates From CSV f Figure 18 Menu Import Test Cases from Excel When activating the menu Test Structure gt Import Structure gt From CSV Figure 19 is displayed In that dialog you can assign Excel columns to TEMPPO attributes They are automatically selected if their names match Mandatory attributes Name and ID have to be assigned otherwise an import cannot be performed Fixed attributes like test goal state can be assigned to any Excel attributes Attribute values have to be
72. di Hew Tile opened no changes nr 23 05 2006 15 53 07 Mew Test Package 1 Schlosser Dietmar 23 05 2006 15 57 36 Figure 160 Test structure Find locks In principle TEMPPO differs between 2 locks User locks e g select a TP TC and locks caused from exports see 3 1 4 7 1 The following lock types are possible e Test case e Test package e Test result test case in test suite e Test suite root e Test structure root e Version Locks can be found either in the test structure or test suite Page 138 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Test structure When activating the menu item Find locks menu test structure Figure 160 is displayed By selecting one or more locks and pressing the button Unlock selected elements locks can be removed e Test suite When activating the menu item Find locks menu test suite Figure 160 is displayed By selecting one or more locks and pressing the button Unlock selected elements locks can be removed If the corresponding user that still believes in his locked items presses the button Save he will get the following message that the lock have be removed in the meantime Lock Exception x fA Saving not possible because the lock was suspended by the administrator Figure 161 Lock deletion message When closing the window by pressing OK he can only discard his changes 3 2 1 2 Showing a lock state The locking state of the item is shown by
73. filters can be copied to project ones and vice versa 3 3 10 1 Predefined filters There are a lot of predefined filter which are useful for each user i wl Figure 228 Predefined filters 3 3 10 2 Create filter You can create a new filter when pressing the button New filter in Figure 228 Page 182 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Name MA Conditions Figure 229 Filter Properties Pressing the Save Button the new filter is saved to the database if a new name was entered Otherwise the information window comes up TEMPPO Note Fiter name already used Please enter a different name Due to missing meta data assignments some filters might not be usable in the opened project and therefore not visible Figure 230 Filter name already used After saving the new filter Figure 231is shown The new filter is inserted and selected in the list box the filter criterion is displayed and the table Impact to selected Window is updated xD DO p Testmanager DS Market IN Y AUS rT Page 183 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Figure 231 Selected filter 3 3 10 3 Change filter You can change existing filters by pressing the Edit filter button This button is only enabled when a filter is selected that is not the empty filter No filter Arer E x RD Ti bg 29 04 2013 13 00 33 2
74. have to set some general parameters in the TEMPPO settings For creating such a test case you have to select UniversalFile Figure 60 Test case settings for Universal Automation Interface and fill in the following data In the text field File you have to enter the path without drive letter see chapter 3 3 16 2 8 2 and the file name of the executable or you use the File Chooser In the Additional Arguments field you can specify command line parameters which will be added to the arguments specified in the Administrator and passed to the executable during test case execution In the Command Line Preview the whole list of parameters is displayed la x Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test 11 H dadb HM EE no fter 2 General description of the product 3 Detailed description of the required product features E 341 Scope of delivery E 3 2 Sequences scenarios of interactions with the environmen 3 3 User goals 3 4 Required tunctions of the product AL 3 4 1 File Administration O EME 3414 Mew fi 3 4 1 1 1 New file opened no changes fi 3 4 4 1 2 New ffile opened changes oo 3 4412 Open 1341 3 Save 53 414 Exit 3 4 2 Edt Functions 3 4 3 Print Functions La 3 44 Search Functions BAJ 3 4 44 Find EGS 44 41 41 Find up El 3 441 141 Case sensitive 3 4 4 1 1 2 WinRunner Check Stat
75. identically If they re different the default value will be set If the owner is selected and the user is not available in TEMPPO the current importer is used as owner Page 37 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Test step The 3 attributes Instruction Expected Input can be assigned with exactly 1 step User Defined Attributes Any UDAs can be assigned with Excel attributes If a value to be assigned doesn t exist it will be created automatically To assign the attributes above please click the checkbox LA Import CSV ump a eae You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case Name Title User defined ID ID Test Goal Path Precondition Postcondition Priority Priority E State Regular Error Test Step Instruction E input Expected Attributes Version Figure 19 Assign Excel to TEMPPO attributes After pressing OK the user is informed about errors of the import Al test cases were importiert For the following test cases a problem was detected and a default value was used Test Case TEMPPO Attribute Error Example Testcase Document Properties Example Testcase Document Properties Cramer No user with the name nn1 exists Cre
76. is checked the temporary automation files will be deleted after automation 3 3 16 2 8 2 Universal File Automation Interface For UFAI Universal File Automation Interface you have to activate the automation tab and select Universal File Universal File User Interface Tree Drive Letter C Test Step Cells Analysis Error Path C Documents and Settings atw10905 Newsboard Test Package Test Suite Database Test Automation V Upload result files to database gt Sik Test WinRunner Result Viewer C WINNT system32 notepad exe Universal Socket Adapter temppo test tools adapters CDefaultAutoToolAdapter Result Path C Documents and Settings atw10905 QuickTest Pro gt Test Partner gt JUnit TEMPPO Designer IDATG Ranorex Commands Change Management gt Bugzilla ClearQuest Telelogic Change JIRA Arguments Restore Defauits OK Cance Page 208 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Figure 265 Settings Universal File The meanings of the parameters are as follows Drive Letter is that letter where path of all test executables start For each test case a path has to be added without a letter drive In this way it is possible to Support scenarios where test executables have to be started from varying drive letters You only have to change the Drive Letter setting in the Administrator Result Path mandatory This is the
77. product features Bay 3 4 Required functions of the product 3 4 1 File Administration B4 3 4 11 New 3 4 1 4 4 New file opened no changes failed 3 4 1 1 2 New file opened changes passed earch Functions B 3 4 4 1 Find E 3 4 4 14 Find up E 3 4 4 1 1 1 Case sensitive blocked BB 3 4 41 1 2 WinRunner Check Stat on hold 3 4 41 1 3 QuickTestPro Test case not implemented EJ 3 4 4 1 1 4 Test Partner Test case not executed oY 3 4 4115 UAI not executed Figure 85 Test Execution M tributes TR Previous Results Plan General Attributes Test Steps J amp tomstion alee ee File New pickQ Message gt a Aun Datei Ba Neu ffnen Speiche Speiche Execution History Requirements History P Seite eir Drucker Beende Messagebox No Editor Pane click cleared Untitled Notepad in title har Lock Epply Test execution assistant shows all the fields of a test step and allows the user to enter an actual result as well as a bug ID By pressing one of arrow buttons user can navigate to next or previous test step Page 79 User Manual TEMPPO V6 0 Edition March 2014 Description of Use x User defined ID tc537 Mame Mewn fle opened changes FE Details TANEET SE fr 1 Instruction File Mew pick Expected Message gt save changes ioii Datei Bearbeiten Format amp nsicht 7 Strg h ffnen Strg Speichern Strg
78. report Only attributes can be chosen that are indicated as test suite attributes in the Meta Data Editor see 5 3 Page 70 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Test object Version v2 RC01 41 1 1 x H d b HW EE ho fter EF 12 Test object Version sre ROO i 3 Detailed description of the required g General Details Export Info Attributes Predecessor Plan Attribute values Lock Apply Discard Figure 73 Attributes 3 1 4 1 2New Based on a predecessor This mode is used to create a new test suites for sprints If your test cycle consists of 4 sprints a summarized test is necessary With this feature you are able to chain test suites and to generate an overall report The test suite will be created on a branch of the current selected test structure version Therefore it is possible to set a predecessor test suite and all possible settings are pre selected With defining predecessors you get information of previous test executions and previous results of each test case with bug IDs It s not necessary anymore to open another test suite for getting the result and bug ID from a previous test execution of a test case The following steps are necessary to do e Select an existing test suite e Test structure pre selection e
79. reports from your test structures and test suites A test structure or test suite report can be created from any node within the structure even from a single test case Reports on current select node root TP TC in a test structure or test suite can be opened via the context menu Report selected Reports of several test structures versions or test suites are called by the menu item Evaluation gt Progress charts The following reports are possible e If atest structure is opened reporting for test structure is opened via Evaluation gt Report selected gt Opened Test Structure e If atest structure is opened reporting for more test suites is opened via Evaluation gt Report selected gt Several Test Suites e If atest suite is opened reporting for test suite is opened via Evaluation gt Report selected gt Opened Test Suite e If atest structure is opened reporting for more test suites is opened via Evaluation gt Report selected gt Several Test Suites Different report settings can be defined for user level and for projects In tab Personal settings the user sees its own defined settings and in tab Project settings all settings defined for this project are visible Page 116 User Manual TEMPPO V6 0 Edition March 2014 Description of Use default Setting TEMPPO default setting NewReportSetting_Report depth 07 03 2013 15 22 06 Report Template 16 02 2012 16 36 07 TC Review Template Y Test creation report Excel
80. start and end line in its data base Getting the output By default TEMPPO Test Manager expects the result output to be produced on the stdout stream of the executable For an executable MyExec exe TEMPPO generates a result file named yyyymmdd_hhmm_MyExec out and redirects stdout of MyExec exe to this file The prefix is a date time stamp that denotes the time when the test executable was started This file is stored in the directory specified as Result Path in the TEMPPO Test Manager settings Test Automation Similar to result files TEMPPO Test Manager expects error output of test executables to be printed to stderr TEMPPO Test Manager will generate an error file yyyymmdd_hhmm_MyExec err and redirect stderr of MyExec exe to this file The file is put to the directory specified aS Error Path in the TEMPPO settings Test Automation If the script does not write to stdout or stderr the user can use the built in variables lt lt ResultFile gt gt and lt lt ErrorFile gt gt in the arguments settings The variables will be replaced at execution time by the paths specified in the TEMPPO Test Manager Settings plus the file names generated by TEMPPO Test Manager see above If the executable expects the file name for the result or error output as command argument they have to be specified by using lt lt ResultFile gt gt or lt lt ErrorFile gt gt otherwise TEMPPO cannot read them Example All scripts should take t
81. structures in the needed version TEMPPO Requirement Manager Page 30 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Import the requirement structures via XML into database d2 TEMPPO Requirement Manager e Check In the requirement structures TEMPPO Requirement Manager e Assign the needed requirement structures of the test structures to the project P2 TEMPPO Administrator e Import the test structure via XML TEMPPO Test Manager 3 1 2 3 Extending the Test Structure Sometimes quite a few chapters in the requirement specification contain a lot of information During test structure generation you will of course get just one test package for each such chapter The problem is that you will have to create a lot of test cases for these test packages due to the abundant information which will lead to a badly arranged test structure The solution is to split them up Such a refinement can be done by adding further test packages 3 1 2 3 1 Adding Test Packages New sub test packages can be added by activating the menu item Edit gt New gt Test Package or Edit gt New gt Test Package before A new child node is created below or before the selected one and a new name has to be entered The default name is New Test Package Let s consider the following example The test structure is created manually The requirement Search Functions consists of 2 sub requirements each described in exactly one chapter
82. the JUnittest class cases junit tests extensions Al Tests 4 Set package default values 5 Settest case default values into the TEMPPO test package 6 Summar JUnit tems to import 5 new testcases willbe added 4 new test packages willbe added TEMPRFO Extension JUnit Page 262 User Manual TEMPPO V6 0 Edition March 2014 JUnit Figure 339 Step 5 The summary of the import wizard Fi TEMPPO Testmanager Demo Notepad l lo x Project Test Structure Edt Test Execution Evaluation Tools Windows Help gt Test Structure JUnit System Test v1 Ioj x a 1 Framework Tests A w 1 junit tests extensions ExtensionTest General Plan Requirements rs hyg 1 1 1 test Running Error In Test Setup junit t Name lint poo he kg 1 1 2 test Setup Error In Test Setup junit tes EI w 2 junit tests extensions ActiveTestTest Owner Testmanager Updator gt mjg i 2 1 testActive Test unit tests extension Crested 12 2012 15 48 24 Updated Bo he hg 1 22 testactive Repeated Testi junit tests E 3 junit tests extensions Repeated Test Test Type Test structure 1 3 1 test Repeated Once junit tests exten hy 1 3 2 test Repeated More Than Once junit t Wy 1 3 3 test RepeatedZero junit tests extens wel System Test j hig test Repeated Negative junit tests extensions Repeated Test Test te793 Lock Apply Discard TEMPPS Designer DATS C Figure 340 Step 5 The result of
83. to create the test structure and test cases in your document a second time For this purpose TEMPPO offers an additional importing feature that enables the generation of test cases When generating test cases from RTF documents you mix the phases design and implementation It s very important to consider this fact because you still have to carry out tasks from the design phase after test case import Ht Pilichtenheft_Notepad_withTC rtf Microsoft Word f oj x ea os Textk rper gt gt F AleEbenenan A Inhaltsverzeichnis aktualisieren Ae w sl oy Datei Bearbeiten Ansicht Einf gen Format Extras Tabele Fenster Livelink Frage hier eingeben xk a t 2 ge jE Aq Tabelengittern Arial lil F uU E PS eae ee Elk an A 34 2 7 lime Dater 3 4 2 04VVord rapi 34 7 4e5et Font l 4 oF 341 2aNew file opened changes 4 a o 6 The test case pursues the aim of testing the Fs function New with changes i a Message zio f j Save Datei Bearbeiten Format Ansicht z a a i changes le Strath fe n ffnen Strg c Speichern Strg S y a Speichern unter s i Seite einrichten ji Drucken Strg F al Beenden Fel F a Ea Pane JE E Ea Untithed E 2 o ipad in a title bars EEE o 34 1 24 O0nen a o 34 1 d4 5ave E o 34 1 44Exit 3 4 2 Edit Functions 947414Undoq a Se 34 2 24Cut a 34 2 54Copy4
84. update function Add new test cases and test packages to the test structure Remove obsolete test cases and test packages You can access the update function through the TEMPPO menu Tools gt JUnit gt Update This menu is activated only when a test package is selected There is no means to update the whole test structure at once A wizard guides you through the steps necessary to update a TEMPPO test package The following steps are encompassed 2 Introduction Explains the steps of the update procedure Test Class Selection Provides a list of JUnit test classes you may update Only classes found in the classpath are listed here see 6 2 Add New Test Cases Provides the hierarchical structure of new test cases i e such that were found in the suite defined by the selected JUnit class but not in the selected test package Select all test cases that should be imported into TEMPPO Remove Obsolete Test Cases Provides the hierarchical structure of obsolete test cases i e such that were found in the selected test package but not in the suite defined by the selected JUnit class Select all test cases that should be removed from the selected test package Package Default Values Allows to set default values for all new test packages Test Case Default Values Allows setting default values for all new test cases Summary Shows a list of your choices from previous steps Here is a sample update sequence To simulate some changes we
85. was checked successfully you can specify to retain some TP TC properties like test case name attributes attribute inheritance requirement inheritance test steps which will be kept after the update process Only the other content is updated Page 188 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Requirement inheritance Test Steps Test Goal Figure 238 Select properties to be retained After pressing OK the test structure is checked of any user locks If a user has locked an item the test structure can t be checked in and the update process is cancelled with a corresponding message If there aren t any locks the test structure is checked in with label Checked in by XML update and the new latest version is completely locked during the update process If you update only a part of a test structure the selected TP and root TP of XML have to be the same otherwise the update is not started 3 3 12 1 1 Update process The update process is done as follows The XML structure becomes the new test structure Each item is recursively compared with itself in the latest test structure version by its ID If the item has been changed the changes are applied and Updated and Updator are written History is written like current behavior If a mandatory history comment is configured for that project it will be ignored If the item hasn t been changed nothing happens Reorder If an item is
86. with activated inherit flag have set the same value Regular Validation Prionty the value is selected otherwise there is ai Verification State no selection Combo boxes If all selected TPs with activated inherit flag have set the same value the value is displayed otherwise the selection is empty ml Additional Test Levels F E F xE The tab Inheritance displays the COMMON bDirectinked attributes inherited Attnbutes Inhertance state of the inheritance flag of the selected TPs If the checkbox is not activated alni i cas ee Ntinheted all selected TPs do not inherit any 7 inherited partially attributes If the checkbox is activated Vineis all selected TPs inherit their attributes If the checkbox looks like E Inhented partially the common state is mixed TPs with and without attribute inheritance M Inherited Page 151 User Manual Edition March 2014 TEMPPO V6 0 Description of Use 3 3 1 2 1 5 Test Package tab Requirements The tab Requirements contains 3 sub tabs Direct linked Requirements Inherited Requirements and Inheritance Tab Direct linked Requirements displays the requirements which are directly linked to a TP Requirements assigned to all selected TPs are displayed as usual in white background color Requirements assigned to not all TPs are displayed in a spec
87. 1 1 2 Mew file opened char oe 3 4 1 1 3 Mew Test Package on Bb E 3 4 1 1 3 41 New Test Case i beag Onen of Merge Lock Apply Discard bot Figure 222 Test case merge If working on a branch an additional button Merge appears besides Lock Apply and Discard the current test case After pressing the button Apply the user is automatically asked if he wants to apply the changes on the latest version V3 Additionally the message shows the information if the same test case was also changed in the latest version Merge advice x The test case was modified in this branch version Do you want to apply the changes alao in the main latest version Remark This test case was also updated in main latest version by Testmanager Figure 223 Merge advice If the user presses Yes the following window appears where the user can select which parts of the test case will be merged x Select the content which has to be merged m Attributes M Test Steps W Automation r Requirements W Plan Figure 224 Merge selection If nothing is selected test case is latest version remains unchanged 3 3 9 Compare Version management also includes comparing a test case or test package with a another one If you select a test case or a test package in the current version of a test structure and activate the menu item Compare Page 179 User Manual TEMPPO V6 0 Edition March 2014 Description of Use i Tree Ei C
88. 14 Generated basic test structure Headings above level 3 e g 3 4 1 1 3 4 1 4 were not imported due to limiting the test structure depth to 3 A numbering was added to the test package names because of checking generate numbers and start with A reference to the imported document was applied to all generated test packages which made them be displayed with the yellow folder icon TEMPPO generates test packages for the whole document structure Of course you ll never create any test case for chapters like Introduction Annex SO you should delete the corresponding test packages Such an initial test structure may be extended by adding more test packages if necessary For each package that is a leave in the test structure tree at least one test case should be defined TIP for an import If an rtf document gets very huge e g embedded graphical objects 50MB TEMPPO is not able to read in such a huge WORD document Replace all the graphical objects with nothing and the import of this rtf document will work 3 1 2 2 4 2 Generating a complete test structure In certain circumstances you may have already written down your test cases in a document e g test case specification This happens if you don t have a test Page 23 User Manual TEMPPO V6 0 Edition March 2014 Description of Use management tool other than a text editor When the time has come to introduce TEMPPO to your project obviously you don t want
89. 14 Description of Use All other settings are not relevant when generating a basic test structure and will be explained later Importing the document displayed in Figure 12 with settings displayed in Figure 13 will generate the test structure displayed in Figure 14 Please consider that importing is applied on the selected test package Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help O x Test Structure Notepad RTF Import System Test pui A Notepad RTF Import EH 1 Introduction HH 2 General description of the product General Attributes Details Requirements History Plan EF a 3 Detailed description of the required g 1134 Scope of delivery Document C temp Pfichtenheft_Notepad rif Ea 3 2 Sequences scenarios of inter C 3 3 User goals Mame Fy 3 4 Required functions of the prodi eee a 3 4 1 File Administration Chapter S411 Mew 33 4412 Open m0 341 3 Save opo E 341 4 Exit Precondition Ea 3 4 2 Edit Functions Detailed description of 3 H 3 4 3 Print Functions Z Required functions of t EP 3 4 4 Search Functions be 3 4 5 Help System 3 5 External interfaces of the prodi Postcondiftion H 3 6 Other product features require EH al 4 Specifications for project managemel Postcondition 5 Obligations of the client F 6 Literature tn 7 Annex Precondition Figure
90. 2 S4455 019 SamPE CHIS ra naa A NEE NA AN 134 3 1 5 6 6 Report Templates ssssssssnsnnursnrsnrnrsnsnrnnrnrnnennrnrsnrnrnnne 136 3 1 5 7 Import from another projects sssssssrerserrrrererrrrenrrrrnnre 136 2r EXPO lO XAMIL sacdissshennses ee a A ATENE RS 136 ILS IMPETON XAMES TRP fE rrr TEAN 137 32 MuUtruUSer anty orrera Tn TA a E A 137 Dak KOCK MOGSS aenn n N A ETS 137 2il FNOK m UNO CK erea A EA EAEn 138 S 2els2 SMOWING E IOCK State rirerire Maae eek aaeigeans 139 S22ei5 Creating a VElSION arriti aii e eae aaa alee 140 S221 CVGatinG atest SUuIVe t2ices antec ca aa a A sie eeee ise tane 140 PARS FINGINGAMVAlIG NOCKS sicccihoiaihindnetsanewepeitecuumisananereitieannionaesans 140 S 242 REPOSAN G wikis tessa heroes ear E 141 32 21 Refreshing Manually tsssccannraherienamedaanpaesimenansaadadaedeemmewanns 141 3 2 2 1 1 Reloading the whole test structure test suite 005 141 3 2 2 1 2 Refreshing recursively cccccceseccccssscccccusennnceureeeeeenssegs 141 3 2 2 1 3 Refreshing on certain user ACTIONS ccceeceeeeeeeeeeeeeeeeeees 142 3 3 General principles and user prompting c cece cece e ee eeeeeeeeeeeeeeees 142 3 3 1 Multi selection Mode cicocscsccancniesaacsnansecesaceiouranansaanmaanereassseunen 142 Sone MUIEISSSIECHON rrinin AETA I 143 3 3 1 2 Display of assigned attributes and requirements ssscsesersrss 148 Sedal TESE SU UCTU Cainii E E E EE EE E A 148 Boel A2 TESES Ute uniera E
91. 2012 E Test object Version XYZ RCO3 16 02 2042 A Test object Version XYZ RECOS COPY 16 02 2012 az o EA Test Suites for W241 2012 02 16 Fite 1 editable version A version 2 of Test obeject RCO1 16 02 2012 J editable version Tree style Yersions only Labels only i Yersions and Labels ClearCase style Order fe ascending D descending Cancel Figure 105 An extra branch for each test execution Typically each test execution has its own branch which is directly beneath the main line and contains just one test suite This is because faults in test cases are usually corrected in the main line of the version tree versions 1 2 3 4 in the example If every new test execution branches directly off the main line it will always have the most up to date definitions of test cases Grouping test executions within a common branch is possible yet not recommended due to the suggested procedure described above Only highly experienced users should consider departing from this approach 3 1 4 7 Test case execution with an exported test suite In projects for certain domains tests can t be executed in the office on the desktop PC but must be executed offline e g in a test car for the automotive domain For this purpose TEMPPO provides features which enable e to export a test suite into an export database e execute test cases and store the test results in this export database e afterwards import the t
92. 2012 16 43 56 Updated 20 02 2012 16 43 57 Type Task Package Number of TCs 0 Test Category i Description Lock Apply Discard Figure 355 Task Package Tab general In addition attributes can be set which are later inherited and used for test cases generated by TEMPPO Designer IDATG It is necessary to assign attributes to task packages and not to test cases because test cases may be generated more than once Each time test cases are generated again all the previous information will be lost Therefore the meta information of test cases generated by TEMPPO Designer IDATG is stored in task packages Page 276 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Designer IDATG Fi TEMPPO Testmanager Demo Notepad Z olx Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test M3 l Zl E x H d gt H E No filter AL Notepad RTF Import with TCs re TEMPFO Designer DATO Tasks i 1 1 New Task Package General Attributes Details Requirements History Plan 7 D 2 Introduction 3 General description of the product Inherit attributes a mi 4 Detailed description of the required product teal 5 Specifications for project management r 6 Obligations of the client ie Regular ie Wein ster Priority Top r o Ga 7 Literature E a Annex Error C verification State Designed Additional Tes
93. 3 8 Versioning Configuration management is a task that covers all phases in the test process TEMPPO does not have a connection to current CM tools like SVN ClearCase or MKS Supporting a large palette of CM tools from a very powerful but expensive one like ClearCase to a cheap one with restricted functionality would be a challenge For example ClearCase offers attributes for each administration unit VSS does not have such commands Therefore the developers of TEMPPO decided to implement an own solution for maintaining versions of test structures with test cases In TEMPPO it is only possible to check in an entire test structure baseline where whole means the hierarchical order of all test packages and test cases as well as their data In contrast to other CM tools where check in and check out are separate steps checking in a test structure in TEMPPO will check it out again i e a new editable version is created automatically Naturally you have the possibility to restore any version of the test structure that has been checked in Versioning is meaningful when you have to change extend your test structure due to version changes of your application You create and activate versions in TEMPPO using Test Structure Version The following example should illustrate how the CM features of TEMPPO work Consider the test structure displayed in Figure 215 Initially there exists just one version of the test structure version 1 on the
94. 342 4 Paste e o 34 2 5 Deletef w 3 4 2 6 5elect Al t E r P ab 3 11 19 Bei 35 7pi Ze 17 5p MAK AND ERW B Englisch us X Seite 11 Figure 15 Test Case Specification Like described in 3 1 2 2 4 1 open the Import Settings by activating Test Structure gt Import Document Structure Page 24 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Import Settings X Document JC stemp Pilichtenhet Motepad withT Crt V Generate document path Heading Mask Heading Limit test structure depth to f Generate numbers and start with f V Generate test packages W Import description IW Generate test cases Ca Import test goal Fixed test step columns Atest case is identified by a table with following headers M Instruction Jaction E Inget input M Expected Output mM Ignore empty table rows do not create empty test steps User defined test step columns T Comment Iv Action image Jaction image OK Cancel Figure 16 Import Settings for generating a complete test structure Additionally to the settings illustrated in Figure 13 you can do the following e Generate test cases If checked test cases will be generated Test cases will be generated from document paragraphs which are formatted with the standard formats Heading 1 Heading 9 or Uberschrift 1 berschrift 9 in German documents Addit
95. 4 4 1 414 Test Partner Test case 2 7 3 4 44 2 Find down oe ho 3 442 Replace 34 6 Help System E T 3 5 External interfaces of the product E e 3 6 Other product features required ni ga 4 Specifications for project management a Obligations of the client ro 6 Literature EJ automation Requirements History Plan Execution History General Attributes Test Steps Expected Merge Lock Apply Discard bo Figure 70 Test Suite Now that you have a test suite with all desired test cases you are ready to start for the test execution and recording of results Depending on the test cases test execution is manual automatic or mixed The selection information included TPs excluded TCs will be displayed if the root node of the test suite is selected see Figure 71 Page 69 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Testmanager Demo Notepad lel xj Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Test abject Version swe ROO v1 1 1 H d gt b WH ho fter A EEA 3 Detailed description of the required g Ell 3 4 Required functions of the prodi General Details Export Into Attributes Predecessor Pian Eh 3 4 1 File Administration 3 444 New Mame Test object Version v2 RCO g 3 44144 New file ope i 3 4 1 41 2 New file ope Owner Testmanager Updetor Testma
96. 5 Speichern unter Action image 000 Seite einrichten Drucken Strg P Beenden Baa El Create a new bug Close Figure 86 Test Execution Test Execution Assistant 3 1 4 1 5 2 Set result s With context menu Set result s it is possible to set test case results for multi selected test cases Additionally you can set values for test result attributes if test result template is active Page 80 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Set Result s xj Set Result s to i failed not executed I blocked not implemented on hold Overwrite existing resus Test Result template Attribute Assigned defaut value Brower version Firmware Figure 87 Set result s 3 1 4 1 6 Plan In test structure test designers estimate the Planned test execution time After test case execution testers enter the Actual test execution time If this time is different to the plan value you can apply that value to the latest version as new Planned test execution time by pressing the Merge button Fi TEMPPO Testmanager Demo Notepad i i oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version sw R01 41 1 1 Wo d P H GP EE no nter AL Test object Version XYZ RCO 3 Detailed description of the required product features l 3 4 Required functions of the product General AES Test Steps rorenc
97. 5 Projects Fi TEMPPO Administrator Testmanager _ Oo x Database bo Roles E Users 8 Metadata LA Projects B Locke E License DE x Ss aAa F Demo Motepad m Example for versioning E Link test cases to requirements Ee Notepad generated EM Notepad RTF Import E Notepad RTF import with TCs m Notepad System amp Acceptance Test ee User documentation Ee Mew Test Structure Figure 317 Administration of Projects The Project tab is only active if the user has a role with sufficient rights A TEMPPO Superuser has access to all projects If allowed due to role privileges you can create projects delete test suites labels branches test structures or even entire projects and assign metadata to projects 5 5 1 Creating a project A new project can only be created in TEMPPO Administrator After pressing the button New Figure 318 is displayed The user specifies a unique name and a description TEMPPO automatically supplies the creation date and owner which is taken from the Windows account Page 245 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi Project Properties l l x General bo Roles Test Case template Test Result template Created 20 02 2072 15 31 05 Mandatory history comment Owner Testmanager Type TEMPPO Project Description Demo project Figure 318 Project Properties New Project Fi Project Properties X General amp Roles T
98. 53 3 1 3 1 6 Upload paste reference IMAGES cccceeeeeeeeeeeeseeeeeeenes 55 LEL Automated testcases 245 6 oul eis EAER 56 3 1 3 2 Reworking the Test Structure sssssssssssssrnnsussersnsnrsernrnnens 62 Sob TEStCasSe EXECUUOMniriypi snaa E E 62 Jd Starting Test EXCCucion sitercisiteus scariest aaesti O Ir 63 3 1 4 1 1 New Based on current test structure ssssrssssresrrrrerrne 65 3 1 4 1 2 New Based on a predecessor cccccssseccesseeneeenreeeeeeenssees 71 3 1 4 1 3 Copy Based on an existing test SUITEC ccccceeeeeeee eee eeeees 75 3 1 4 1 4 Special Based on an existing test suite with restrictions to test results76 3 1 4 1 5 Manual Test Execution ssssssssssnssrsnrnrnernsrnrsnrnrnnrnrenens 77 DO Plaun T A 81 3 1 4 1 7 Test Result AttriDUtes cccccceeeeccccssccccccueeneenereeeeeeenssegs 82 SAA ALS Previous RESU Szer E N Aa NS 82 3 L419 Enter NEW DUG entry scissstcuwetaci toatontiaceniget saaweniiaietadionstens 83 3 1 4 1 10 Automated Test Execution cccccccssscccceseenneenueeeeeeeessegs 86 3 1 4 1 11 Mixed Test EXeCuuion vis cwicadicnavoniacenigst saavenriakomaihanseens 87 3 1 4 1 12 Setting several reSults ccccccecccccssceccecneeneeeureeeeeeesssegs 87 3 1 4 2 Pausing and Continuing Test Execution sssssssssersrrerrrrerene 88 3 1 4 3 Editing Test Cases during Test Execution sssssssersrrersrreren 88 3 1 4 3 1 Adding new test cases during test case execution
99. 9 04 2013 12 53 53 If Market iN aus E Figure 232 Edit filter Depending on the selected filter the conditions are displayed Filter name is read only filter conditions can be changed See Figure 229 3 3 10 4 Delete filter You can delete an existing filter by pressing the Delete filter button This button is only enabled if the selected filter is not the empty filter No filter Page 184 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Arre E o gt E l Li Dir ery Per 1 LO PL is Li ati DO Al state in review 29 04 2013 13 00 33 adj 29 04 2013 12 56 53 amiy cancel Figure 233 Delete Filter After activating the Delete filter button the reconfirmation window comes up Figure 234 Delete filter If pressing Yes the information window comes up and the filter is deleted if it is not used by a test structure or suite Figure 235 Filter deleted After deleting a filter the No filter is highlighted in the list box 3 3 10 5 Defining the filter criterion The values of the following attributes can be used as described in Table 2 Fixed UDAs test case name owner tester bug ID test result requirements Page 185 User Manual TEMPPO V6 0 Edition March 2014 Description of Use First of all you have to choose an attribute and an operator IN NOT IN If IN or NOT IN is selected the combo box value changes to a t
100. 94 User Manual TEMPPO V6 0 Edition March 2014 Appendix Merge actual execution time X _TEMPPO Evaluation Analyse O Z O X pt Aalysebybug IDOE X PCC reationprogress O X TY OS Execution progress xt T ST C Personal report setting X XXIX x O O Project report setting X x x x x Ret a e a PY Reg uirement Requirement analysis S S x o o oOo o o TEMPPO Requirement e 1 a to XML ps Tmportfrom CSV _ _ _ E EEEE ad oe oe a ee po Import from XM XP po pen XT po Requirement X x x pi Requirement Structure X X po Split XY po Update XT po ersions XY TEMPPO Others Multi Selection X P po Copy XY poopy XY po EXport Import filter X FP po iter XX X X XT New implies applying a filter _ po Order XY po ask ist XX XK po ersions XE XE XY SO Page 295 User Manual TEMPPO V6 0 Edition March 2014 Appendix 13 7 UAI Adapters An adapter is used to convert the results returned from an automation tool into a format which can be processed by TEMPPO Currently 2 adapters are provided 13 7 1CDefaultAutoToolAdapter The result string returned after a test case has been executed must have following format line 1 result passed failed blocked not implemented on hold line 2 summary begin line n summary end 13 7 2CAPOXIAdapter Taken from APOXI user s guide After finishing the test an exit code is returned to the client which is 1 if the test was
101. ATTRIBUTE TSUITE gt lt ATTLIST TEST SUITE id CDATA REQUIRED gt lt ATTLIST TEST SUITE name CDATA REQUIRED gt lt ATTLIST TEST SUITE lastupdate CDATA IMPLIED gt lt ATTLIST TEST SUITE lastupdateby CDATA IMPLIED gt lt ELEMENT TP DESCRIPTION PRECONDITION POSTCONDITION REQUIREMENT TP TEST RESULT gt lt ATTLIST TP name CDATA REQUIRED gt lt if zero length then name New Testpackage generated gt lt l if it already exists add 1Y T 2p xas gt lt ATTLIST TP t st category CDATA FIMPLIED gt lt t If it does not exist lt autom create it for the test level of the containing test structure gt lt ATTLIST TP document CDATA IMPLIED gt lt ATTLIST TP doc name CDATA IMPLIED gt lt ATTLIST TP chapter CDATA IMPLIED gt lt ATTLIST TP inherit requirements Crue Talse falge gt lt ATTLIST TP lastupdate CDATA IMPLIED gt lt ATTLIST TP lastupdateby CDATA IMPLIED gt lt ELEMENT TEST RESULT TESTGOAL PRECONDITION POSTCONDITION RESULTOUTPUT REQUIREMENT TEST STEP RESULT AUTOMATION ADD TEST LEVEL USER DEFINED ATTRIBUTE USER DEFINED ATTRIBUTE TRESULT gt lt ATTLIST TEST RESULT tc id CDATA REQUIRED gt lt 1ATTLIST TESI RESULT user defined id CDATA IMPLIED gt lt If It already exists in Containing t st Structure aqd 1Y ue aw gt lt ATTLIST TEST RESULT name CDATA REQUIRED gt lt if zero length then name New T
102. DSN ODBC UAI CLI Database Hardware Test Director Graphical User Interface Software Data Source Name Open Database Connectivity Universal Automation Interface Command Line Interface Page 287 User Manual TEMPPO V6 0 Edition March 2014 Appendix 13 Appendix 13 1 DTD Schema for XML Import Test Structure lt ELEMENT TEMPPO EXCHANGE PROJECT TS TP gt lt NOTE these attributes will not be part of the TEMPPO exchange format creator CDATA IMPLIED too many error possibilities creator will be importer created CDATA IMPLIED date will be taken from import NOTE following elements we currently ignore PROJECT ES SE lt Common PCDATA elements gt lt ELEMENT DESCRIPTION PCDATA gt lt ELEMENT PRECONDITION PCDATA gt lt ELEMENT POSTCONDITION PCDATA gt lt ELEMENT TESTGOAL PCDATA gt lt ELEMENT INSTRUCTION PCDATA gt lt ELEMENT INPUT PCDATA gt lt ELEMENT EXPECTED PCDATA gt lt ELEMENT VALUE PCDATA gt lt ELEMENT PROJECT DESCRIPTION REQUIREMENTSTRUCTURE TS gt es Currently IGNORED gt lt ATTLIST PROJECT name CDATA REQUIRED gt lt the TEMPPO project must already exist gt lt ELEMENT TS DESCRIPTION TP gt lt currently IGNORED gt lt ATTLIST TS name CDATA REQUIRED gt lt ATTLIST TS test level CDATA IMPLIED gt lt if it does not exist autom create LE e lt ATTLIST T
103. Database Roles E Users a Metadata Projects locks fea License a Notification MB ISITEMPPO 5 7 Users Guide E a Database Access File E Documents and Settings atw 1 12h9 DesktoplsitemppolsersGuidev57 mdb_ Wa Connect Database Name Database Version Figure 289 Administrator Database Access Oracle MS SQL Server You must specify the database name SID the schema name ask your database admin the name or IP address of the database server Host and the port number Port at which the database server is listening for incoming connections Contact your database administrator for this information Furthermore you can activate the checkbox Login manually that activates the manual login window before displaying the TEMPPO main window The currently selected DSN is the active one i e TEMPPO uses its connection parameters to connect to a database Using button Test you can verify your settings A message will inform about the result of the verification By clicking Connect the TEMPPO Administrator will establish a connection to the database user and password are required for Oracle This will cause the tabs Users Projects Migration and Roles getting enabled if the user logged in is allowed to do so by his assigned roles Information about the database will be displayed in the bottom of the tab 5 2 Roles The access to TEMPPO functionality is managed by roles In the follow
104. E Test Structure Notepad RTF Import with TCs H 4b H E Mo filter ote E 3 3 User goals a a 3 4 Required functions of the product Er a 3 4 1 File Administration o Ee a 3 4 44 New a fl 3 4 4 1 4 Mew file openec 3 4 1 1 2 New file openec fH 3 4113 New Test Packe E i 3 4 2 1 Undo i 3 4 2 2 Cut 3 4 2 3 Copy Zi 3 4 2 4 Paste 3 4 25 Delete E 3 4 26 Select Al T 3 4 2 7 Time Date ae 3 4 2 8 Word Wrap 5 4 2 9 Set Fort oe 4 3 4 3 Print Functions eu 3 4 34 Page Setup pS 3 4 3 2 Print 2 P 3 4 4 Search Functions EA 34 41 Find o B 3 4 4 1 Find up A 444142 WinRunner Bev E 3 4 4 1 1 3 QuickTest o 344145 UA ff 3 4 4 1 2 Find down Fi 34 4 2 Replace 93 45 Help System H a 3 5 External interfaces of the product j Other product features required Figure 172 Selection with lt Ctrl gt e Select contiguous TEMPPO V6 0 Description of Use First select a test package or test case then press lt Shift gt and select a test package or test case The items from the first selected item to the last item are selected but only the visible items are selected see Figure 173 Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution Ew e Test Structure Notepad RTF Import with TCs M4 H E Mo fiter E 3 3 User goals a E 3 4 Required functions of the product a a 3 4 1 File Administration
105. EF Al 2 1 1 Destination Entry via speller B E m A 241 414 Speler usage 2353 oe Eb az 414 Speller usage 2353 ae Eii 1 Speller_ Usage _Toyen 26 11 2002 15 08 02 EB dw fd 2114 _1 Speller_Usage_ Town 26 11 2002 15 27 17 pee MW B 2 1414_2 Speller_Usage Street 28 11 2002 15 08 04 offi 2 1 1 1_2 Speller_Usage Street 28 11 2002 15 27 21 Gl oe l H O BB 214 Speller_Usage_Zip_codes 28 11 2002 15 08 Oi p io pf 21141_4 Speller_Usage_Zip_codes 28 11 2002 15 27 2 de O E 2 4 14_5 Speller_Usage_house_numbers 28 11 2002 1 bE te ffi 2 1 1 1_5 Speller_Usage_house_numbers 26 11 2002 15 A O A 2 1 1 2 Best match line rs A 3 2141 2 estan oe O Gl 211 21 Best_Match_Line_Town 2607 efi 2141 24 Best_Match_Line_Town 2607 H O Ql 244 2_2 Best_Match_Line_Street fi 241 22 Best_Match_Line_Street sis O M2112 _3 Best_Match_Line_Housenurmber e fil 2112 _3 Best_Match_Line_Housenumber H O Ql 2 44 2_4 Best_Match_Line_Intersection 2608 efi 241 24 Best_Match_Line_Intersection 2608 Pee 244 2 5 Best_Match Line _Special_Destination 2609 efi 211 2_5 Best_Match_Line_Special_Destination 2609 H O B 2444 Auto Expand and Auto Delete function 2355 m PE H S 244 4 Auto Expand and Auto Delete function 2355 m 4 F 4 a Sa Figure 113 Manual import of test results 3 1 4 7 4Unlocking the test suite As a last resort it is possible to manually unlock a test suite see chapter 5 5 6 3 1 5 Evaluation In this pha
106. EFINED ATTRIBUTE TSUITE EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE TSUITE be zero length string gt lt if it does not exist lt ATTLIST USER DEFINED ATTRIBUTE TSUITE be zero length string gt lt if it does not exist name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically lt l cannot created gt lt Se cannot created gt 13 3 DTD Schema for XML Import Results with CLI lt xml version 1 0 encoding UTF 8 gt lt ELEMENT TEMPPO EXCHANGE LOGIN RESULTS gt lt ELEMENT lt ELEMENT lt ELEMENT lt ELEMENT USER PCDATA gt PASSWORD PCDATA gt PROJECT PCDATA gt LOGIN USER PASSWORD PROJECT gt lt ELEMENT lt ELEMENT SUMMARY RESULT lt ATTLIST RESULT testsuiteid CDATA REQUIRED testcaseid CDATA REQUIRED value CDATA REQUIRED PCDATA SUMMARY gt gt gt lt ELEMENT RESULTS RESULT gt Page 291 User Manual TEMPPO V6 0 Edition March 2014 Appendix 13 4 DTD Schema for XML Export User Profile with CLI lt ELEMENT LOGIN ROLES BUGZILLA gt lt ATTLIST LOGIN name CDATA REQUIRED superuser CDATA IMPLIED result CDATA REQUIRED gt lt ELEMENT PROJECT PCDATA gt lt ELEMENT ROLE PROJECT gt lt ATTLIST ROLE name CDATA REQUIRED gt lt ELEMENT ROLES ROLE gt lt ELEMENT EMAIL PCDATA gt lt ELEMENT PASSWORD PCDA
107. EHSA 3 4 4 Search Functions aM Testmanager 20 02 2012 13 22 51 XML File la 3 4 4 4 Find G 3 4444 Find up E 3 444414 Cas El 3 4 41 412 win Lock Apply Discard Figure 240 Export XML information TEMPPO identifies an XML file by a unique ID 3 3 13 2 Import After exporting an XML file it may be edited outside of TEMPPO e g users or test automation tools are filling in some values Valid values are e Result Failed Passed Not_executed Blocked Not_completed Not_implemented On_hold e Result Output Plain text e Tester MS Windows account or a defined user account e Tested DDMMYY HH MM SS If other values are changed they will be ignored Importing an XML file can be started by activating the menu item Import Test suite gt from XML The import is independent from the selected node TEMPPO detects the part to be imported The following possibilities are offered for importing x How should TEMPPO handle conflicting test results during import S Import only newer test results i Import all test resus ores Figure 241 XML Import e Manually choose test results to import When activating this option Figure 242 is shown In the right part of the window the current result state of test cases in the central database is shown together with their execution date NOT importing date Test cases that may cause conflicts are colored blue The left side of the window shows the test resul
108. ELEMENT USR FIELD VALUE gt lt ATTLIST USR FIELD name CDATA REQUIRED gt lt ELEMENT AUTOMATION EMPTY gt lt ATTLIST AUTOMATION tool SilkTest WinRunner UniversalFile UniversalSocket JUnit UniversalFile gt lt ATTLIST AUTOMATION file CDATA IMPLIED gt lt ATTLIST AUTOMATION data CDATA IMPLIED gt lt ELEMENT ADD TEST LEVEL EMPTY gt lt ATTLIST ADD TEST LEVEL name CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt Page 290 User Manual Edition March 2014 lt ELEMENT USER DEFINED ATTRIBUTE EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE length string gt lt if it does not exist lt ATTLIST USER DEFINED ATTRIBUTE length string gt lt if it does not exist TEMPPO V6 0 Appendix name cannot be zero it will value it will CDATA REQUIRED gt 5 be automatically created gt CDATA REQUIRED gt lt be automatically created gt cannot be zero lt ELEMENT USER DEFINED ATTRIBUTE TRESULT EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE TRESULT name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically lt l l cannot created gt Ss cannot created gt be zero length string gt lt if it does not exist lt ATTLIST USER DEFINED ATTRIBUTE TRESULT be zero length string gt lt if it does not exist lt ELEMENT USER D
109. EMPPO and after executing them outside of TEMPPO the results are imported 3 3 13 1 Export The export XML feature can either be used to execute automated TCs somewhere offline and export results later or export the test suite to an XML file for other matters In this case the test suite shouldn t be locked A test suite can be exported if a test suite is already opened any node test suite root or TP is selected and the menu item Export test suite gt to XML is activated Test suite export to AML xX 3 Should the test suite be locked after export The file can only be imported if a lock j set M Lock Test Suite Figure 239 Lock confirmation After entering a name the XML file is stored to the file system conforming to testsuite dtd The testsuite dtd can be found in your TEMPPO XML directory After exporting a test suite to an XML file all exports also to the export DB are listed in the Export Info Page 190 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad joj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Version 2 of Test abject ROOT 12 1 1 MH d b H GP E No titer SE version 2 of Test object REO Eimi 3 Detailed description of the require Ea 3 4 Required functions of the pi Eb La 3 4 1 File Administration BA 3 4 1 1 New E 3 41141 New gile r i 3 4 1 41 2 New file
110. F FEN 3 4 1 4 3 New Test Packe a Test Structure Notepad RTF Import with TCs T A i i a Ea 3 1 Scope of delivery 2 2 2 2 GE 2 3 2 Sequences scenarios of interaction P25 ow 3 3 User goals a Timez Sia 3 4 Required functions of the product gemia o word Wrap EE 5 4 1 File Administration M4 W GP EE No iter Motepad RTF Import with TES E1 Introduction E 2 General description of the product m 3 Detailed description of the required product ERRE 4 1 1 New fi 3 4 1 1 1 New file opened ne fi 3 4 1 1 2 New ffile opened c Sao 3 4 5 Print Functions Le Page Setup meee a 4 Search Functions Sie 5 4 4 1 Find WES EES ge H a 3 4 4 Search Functions 3 45 Help System 3 5 External interfaces of the product TE H E 3 6 Other product features required a ss E 4 Specifications for project management T Bi 0 5 Obligations of the client a 35 E sternal interfaces of the product _ 6 Literature Soa 0 7 Annex 1 eee a Figure 171 Before and after Select all e Select non contiguous TEMPPO V6 0 Description of Use For selecting non contiguous press lt Ctrl gt and select test packages and or test cases A test package is selected itself and not its sub tree i e without children see Figure 172 Page 145 User Manual Edition March 2014 F TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution
111. Fields Severity 1 Critical Headline Ce O O Optional fields Description attachement ratl_mastership Resolution aa Keywords 2 Symptoms 2 Priority Project b customer Note_Entry Owner customer_severity bi cms Figure 95 Clearquest Now the report is added to the tracking tool and in the column Bug ID you find the hyperlink to your report see Figure 97 Page 85 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Limitation With IBM Rational Clearquest s interface it is not possible to attach directly the test report BjNew Bug TEMPPO x r Standard Fields Project Test Project v Summary First bug entry in JIRA Componentis feo Version s f4 9 Version s 4 o 2 0 Assignee Priority Major Environment a zl Description A bug ocurred fa Attachment Add Test Report V m Custom Fields Unknown 1 0 Backport to Version 20 Ge Release Note oren Figure 96 JIRA Fi TEMPPO Testmanager Demo Notepad 7 i xi Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO V1 4 k O x M dad bN EE no fter ion XYZ RCO1 M escription of the required product features uired functions of the product General Attributes Test Steps E Atornetion Re
112. IStING Project wniscieioischiciceieiiicelehinidoniaueietss 16 3k22 Building the Test Structure sacuiwuntiwadeenpeccerestnadaunsdrewel AA 17 Sds2 2 F Creating a test StrUCtUFeesneenerise ati aE EEOAE 17 222A Opening a TeSt SUCUL E oirre reren ETATEN 19 l2 Reopen a tese E osere aa E EEE T 20 3 1 2 2 4 Importing an RTF formatted document sesssssseressrrrrerens 20 3 1 2 2 5 Import Test Cases from Excel sssssssssrssrsrrsrrnrrrenrrrrerrne 26 SEAAG B ld manually ssrin E eeii 28 S22 f AMG IMPOR Esrar aa E a OER 28 3 1 2 3 Extending the Test Structure iriiiisriiriiari i aaa aa 31 3 12 31 Adding Test Packages cxcscmintuniniciauaeniceetoeeaisanndanlveeee 31 3 1 2 3 2 Categorizing Test PackaGeS cccccccccssscscccsneeneeeureeesecsnssegs 34 3 42 33 Referring CO CO CUIMENIIUS riroraa a aa 36 3 1 2 3 4 Referring to requirement numbers or namMeS sssesssssseses 39 S124 Designing Test CASES ci siires ien Ea A E E AAA 42 3 1 3 Test Case Implementation sssssssssssesssnssnrnrsnsnrnnennrnrnnrnrnnrnrnnens 50 3 1 3 1 Implementing Test Steps nsssssesessssnsnrnrnnnunsnrsnrnrsernrnnrns 50 3 1 3 1 1 Preconditions and POStCONGItIONS c cece cece eeeeees 50 Silissulas WES tes 2 ciara ene tie tauer es inteee sateen eames aeareneaenaeas 51 Silizdales Test Creation ASSISCAN neersien eaa EENE E AREE PLE R 52 3 1 3 1 4 Keyboard edit mode sssssssssssssrssssrsnrnrsnennsnrsnsnrsnrnrenens 53 Jeke Adding More COUM S eerie EN ENEA
113. If the metadata does not exist it is saved to the metadata pool and the assignment to the project is made 2 Type in a match criterion of the metadata and click on the arrow of the combo box All metadata entries that match the criterion are listed in the combo box Choose one press the button ok and confirm the assignment question 5 4 1 2 Delete Metadata Entries Choose the right metadata tab and click the button Delete If the metadata is not referenced in any project the metadata is deleted 5 4 1 3 Move ownership In the TEMPPO Administrator there is the possibility to move the ownership of a metadata After pressing the button Move Ownership the following dialog comes up Page 234 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator E Move ownership to i x atwi12hg Tester1 tester testers tester4 testers tester tester Testmanager BAA eS eS eS eS ee oe FS Schema Owner temppo_um erea Figure 300 Move Ownership The new owner of the metadata can be chosen 5 4 2 Test Levels In Figure 301 all test levels are displayed with name owner and creation date Fi TEMPPO Administrator Testmanager Oj x DE xX amp schema Owner 13 02 2012 13 04 07 Schema Gwner 13 02 2012 13 04 07 schema Owner 13 02 2012 13 04 07 T Regression Test schema Owner 13 02 2012 13 04 07 T System Test schema Owner 13 02 2012 13 04 07 Figure 301 Metadata Test Levels A new test level ca
114. JUnit test cases Select test cases EH Framework Tests Select All FH junit tests extensions Extension Test a E test Running Error In Test Setup x O testRunning Errore in Test Setup 4 Set package default values 5 Settest case default values Deselect Jl it Summary O test SetupError Dont Tear Down E test Setup Error In Test Setup Bo junt tests extensions Active Test Test El testactiveTest z O test ctive RepeatedTest a H testActive Repested TestO O testActive RepeatedTesti AS junt tests extensions Repeated Test Test test Active Repeated Test junit tests extensions Active TestTest TEMPRFO Extension JUnit ee Prey Next gt Finizh Cancel Figure 336 Step 3 All or a subset of JUnit test cases can be selected F Import JUnit Tests x Steps Package Default Values Introduction Enter default values for the new test packages in TEMPPO Select a JUnit test class 3 Select a set of JUnit test enor Details C JSES 4 Set package default values Hame lt generatect 5 Set test case default values 6 Summary Creator Testmanager Created generatedt Twpe Test Package Test Category Description Jv Add to description TEMPPO Extension JUnit co Prey Finish Cancel Fi Import JUnit Tests x Steps Package Default Values Introduction Enter defaut values for the new test packages in TEMPFO Select a JUnit test class 3 Select a set of
115. JUnit test canes 4 Select absoltete TEMPPO test cases 5 Set package default values 5 Settert case default values 7 Summat Select the obsolete TEMPPO test cases to remote TEMPRO Extension Panama Prey Next gt Finish Cancel Figure 348 Step 4 An obsolete test case was detected and we mark it for being removed In the next steps default values for JUnit test suites and test methods can be entered just like in the import procedure F Update JUnit Tests xj Steps Package Default Values 1 Introduction Enter default values for the new test packages in SiTEMPPO 2 Select a JUnit test class 3 Select new JUnit test cases 4 Select obsolete TEMPPO General Detaas test cases Nar Set package default values Set test case default values Owner jatw108s2 Summary oa Test Package v Test Category Description This description applies to all new JUnit test suites IV Add description Updated by TEMPPO from JUnit Suite TEMPPO Extension Panama lt lt Prev Next gt gt Frish Cancel Figure 349 Step 5 Test package default values can be entered In step 6 Test case values can be entered Fi Update JUnit Tests Steps Summary Introduction Select a JUnit test class 1 Review your settings S Dalect niw JUnik bed cares You choose to update the TEMFFO test package J Select obsolete TEMPPoO Al JUnit Tests te
116. Li Case sensitive not executed 4 2 3 4 Select nodes or subtrees 5 Entertest suite name 6 Determine the logical expression 7 Remove test cases manually TEMPPO Test Suite Generator lt lt Prey Figure 78 Remove unwanted test cases Finish Cancel After clicking Finish the new test suite is created based on the settings of the predecessor test suite Now that you have a test suite with all desired test cases you are ready to start for the test execution and recording of results The predecessor information will be displayed if the root node of test suite is selected and tab Predecessor is activated O x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version lt 2 Reis 1 1 1 l za x H d gt b HW E Mo fitter Aa est object Version Xv2 RCO3 a 3 Detailed description of the required g General Details Export Info Attributes Predecessor pian ca Test Suite Test object Version 72 RCO W1 1 1 editable version 2 Test object Version XYZ RCOZ W1 1 1 editable version 3 g Test object Version v2 RCOS 1 1 1 editable version Figure 79 Predecessor The predecessors of a test suite can be changed with the buttons Insert Into Chain Remove Chain and Remove From Chain The predecessors are sorted by the sequence so that the last row is the current test suite The sort can be changed with the combo box Sort bottom up
117. Manual lock e Automatic lock If you are working with manual lock mode you always have to press the button Lock before having the exclusive right to work on that item On the other hand you simply have to select an item and it is automatically locked if another user does not lock it This feature can be configured in TEMPPO settings Page 137 User Manual TEMPPO V6 0 Edition March 2014 Description of Use i DSM Chooser ser Interface Gl Test Automation IY Switches on off a database chooser window on TEMPPO startup H Commands Change Management fi O Timeout in seconds displaying DSM chooser Locking E Switches onioff to lock the whole test structure before checking in and to prevent check in it an tem iz locked Check for new test structure version when saving an tem in main latest wersion Switches onJoffto check if the entire test suite is unlocked before exporting Locking Made Locking mode in test structure and test suite automatic C manual History i 0 Number of history recordsa to load Restore Defaults Cancel Figure 159 Settings gt Database gt Locking The following chapters are describing the locking in manual mode 3 2 1 1 Find locks unlock xi Unlock selected elements See RAL OEE Detailed description of the required product features User Super 23 05 2006 16 13 33 Wl Exit Yes file open changes nn 23 05 2006 15 53 55 M New file opened changes nn 23 05 2006 1553 37
118. PO Administrator Testmanager d Database 2 Roles E Users Metadata LA Projects Lacks License Test Levels Test Categories H Attributes E3 Uploads tf Requirement Structures Pf User Fields Oo Be x amp if Atribute Tvpe Creation Type IO x A Contact 4 Device type a Difficutty J Milestone l Platform Priority Al Property al Req priority 4 Req State J Req Type Ad Statue J Test location a Affects Architecture SL Firmware version 4 Regressiontest SL Window client Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager atw112h9 Testmanager Testmanager Testmanager Testmanager Testmanager 14 02 2012 14 54 30 14 02 2012 14 54 30 16 02 2012 11 22 20 14 02 2012 14 54 30 16 02 2012 14 12 37 16 02 2012 11 11 40 16 02 2012 11 10 33 14 02 2012 14 54 30 14 02 2012 14 54 30 16 02 2012 11 11 05 14 02 2012 09 22 13 14 02 2012 12 25 25 14 02 2012 09 13 34 14 02 2012 14 64 29 16 02 2012 11 13 05 16 02 2012 14 13 39 Requirement Requirement Test Case Requirement Test Result Test Suite Test Case Test Case Requirement Requirement Test Case Requirement Requirement Requirement Requirement Test Case Test Result Test Suite Figure 305 Metadata Attributes imported imported manually created imported manually created manually created manually cre
119. PPO Administrator and select the export database If you start TEMPPO with the export database you are informed that TEMPPO is open in a restricted manner see Figure 110 which means that only the Test Execution Find and Evaluation functionality is available and only the test suite window is opened Test structures are not displayed in that restricted mode TEMPPO x i You are connected to an esport database TERIPPO will be started in arestiched manner The exported test suite willbe opened automatically now ysis al Figure 110 Warning TEMPPO in a restricted manner During test case execution the following values text fields can be changed Result Output Result text for the whole test case Actual Result For each test step Bug ID Results Test results for each step passed failed blocked not executed 3 1 4 7 3Importing test results Returning from test case execution the testers want to import the results to the central database You have to connect to the LAN and select the central database in the TEMPPO Administrator After opening TEMPPO Test Manager you have to open the corresponding test structure and suite The read only test suite is marked with a small lock see Figure 111 and colored blue if it matches to the test suite in the export database Page 95 User Manual TEMPPO V6 0 Edition March 2014 Description of Use x b Notepad RTF Import with TCs Tree
120. RTF Import with TCs System Test Puz J Notepad RTF Import with TCs EHLI 1 Introduction 2 General description of the product General Attributes Details Requirements History Pian a 3 Detailed description of the required product E 3 1 scope of delivery Mame Fie Administration 2 3 2 Sequences scenarios of interactions a Ee 3 5 User goals Owner Tester Updator Testmanager Ela 3 4 Required functions of the product et 1341 Fie Administration Created 16 02 2012 16 45 49 Updated 16 02 2012 11 28 57 ESS 411 New p 3 4 1 1 1 Mew file opened no fi 3 4412 New file opened ch Murer of TOs 2 3 4 1 1 3 Mew Test Package c o ime i Test Category bi 0 3 41 2 Open i R444 Save r Merge Lock Apply Discar Gr Type Test Package Figure 218 Items not available in prior versions You can restore the version of a test structure by activating it in the versions dialog with button 2 Activate selected version You cannot change a test structure in a version which is not latest However you can create a branch of a structure version and apply changes to that latest version in the branch When you activate version 2 V2 and try to insert a new test package you will get the following message You are trying to change atest structure that is already checked in 1 The only possibilty to make changes is to create a branch Do you want TEMPPO to create a branch for yout
121. S msna 287 13 Appehdikcopoieai aa 288 13 1 DTD Schema for XML Import Test Structure sssessesssrerssrsresas 288 13 2 DTD Schema for XML Import Test Suite c cece cece cece eee eeeeeees 289 13 3 DTD Schema for XML Import Results with CLI ccccceeeeeeeeees 291 13 4 DTD Schema for XML Export User Profile with CLI 000e 291 13 5 Predefined FUNCHONS 45 ic tenseninadcenneedenihedanidunsastaeerannecunpaoenein nee 292 13 6 PRFEGETINGRROICS siedinunneiqnii stat a E AEN 292 13 6 1 Functions to be applied to a role sssnssssssnnnsnnnsnsnnsnrnrnnensrnnnns 293 137 UALAGaDEPS iria E E i 296 13 7 1 CDefaultAUtOTOOlIAdapterr cccsscccccsssenecccceeeceeessceceeuueeneannrenes 296 LZA CAPOXIAGGDEECR ciccsitiiencint sisninicsenscssGsaiaitiaumnmanceencueqamniasaeaenn 296 13 735 How to implement an adapter ccccecccccssscccccuuennnecureeeseeenssegs 296 Aal SSlASSe renne O Err 296 Ll3 A32 COGS SIMD DC araara AA ET Oa 297 13 7 3 3 Implementation and integration stepS s ssssesssrsrssrsrserss 298 User Manual TEMPPO V6 0 Edition March 2014 Overview 1 Overview Managing the test process involves a large number of engineering disciplines like project management risk management high and low level design development and metrics collection Normally testers manage their test cases with Word tables or Excel sheets The main disadvantages are that test cases cannot be maintained easily gr
122. S version CDATA IMPLIED gt lt Added 31 5 2004 gt lt ELEMENT TP DESCRIPTION PRECONDITION POSTCONDITION REQUIREMENT TP TC gt lt ATTLIST TP name CDATA REQUIRED gt lt if zero length then name New Restpackage generated gt lt l at at already EGxusts add Iy My ae te Se lt ATTLIST TP test category CDATA IMPLIED gt lt la af it does not exist autom create it for the test level of the containing test structure gt lt ATTLIST TP document CDATA IMPLIED gt lt ATTLIST TP doc name CDATA IMPLIED gt lt ATTLIST TP chapter CDATA IMPLIED gt lt ATTLIST TP inherit requirements true false false gt lt ELEMENT TC TESTGOAL PRECONDITION POSTCONDITION REQUIREMENT STEP AUTOMATION ADD TEST LEVEL USER DEFINED ATTRIBUTE gt Aire on TG user defined id CDATA FiIMPLIED gt lt l af 10 already exists in containing test structure add 1 2 Se lt ATTLIST TC name CDATA REQUIRED gt lt if zero length then name New Testcase generated gt lt if it already exists in containing test package add 1 adh ts Si TE lt ATTLIST TC situation Error Regular Error gt lt ATTLIST TC val ver Validation Verification Validation gt lt ATTLIST TC priority Top High Medium Low Top gt lt ATTLIST TC state Designed In Work Ready for Review Ready Approved Designed gt lt ATTLIST TC inheri
123. Since TEMPPO 5 7 report preview is displayed in Microsoft Word or Microsoft Excel Page 132 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Gh RPreview doc Microsoft Word Mel x Datei Bearbeiten Ansicht Einf gen Format Extras Tabele Fenster Livelink Frage hier eingeben x OSE RBGIEGRIFS 4BBPI 9 PERBEBAT gt fista ara u F x ueso B a scr vs Ges ian Re 1 14 15 With view latest baseline 4 Owner nni Test Goal check the update with view together with a latest version and not a baseline Path Systemtest Introduction Purp ose of the document With view latest baseline 4 Created 10 06 2008 15 33 49 ID tc54636 RPreview doc C DOCUME 1 atw10905 LO CALS 1 Temp RPreview doc SITEMPPO Report 11 06 2008 08 41 Priority High Situation Regular Test Case Type Verification State In Work Type manual Updator nni Updated 10 06 2008 15 33 49 Precondition Offline true Test levels Acceptance Test Test Steps Nr Instruction Input_ _ Expected_ Comment TN ooo Connect to Screen with my available Press Finish to New process updated Validity of the document SHS R ol P B So te Dl i MAK AND ERW UB Englisch US Figure 152 Report Word Ej Microsoft Excel RPreview xls olx a Datei Bearbeiten Ansicht Einf gen Format Extras Daten Fenster Livelink Frage hier eingeben
124. TA gt lt ELEMENT BUGZILLA EMAIL PASSWORD gt 13 5 Predefined Functions Cannot be changed 13 6 Predefined Roles The following roles are predefined in TEMPPO e TEMPPO Super user All functions activated e TEMPPO Key User Most important or used functions activated e TEMPPO Key Tester Important function concerning Test Suite e TEMPPO Tester Most important functions concerning Test Suite e TEMPPO Requirement Editor All functions in Requirement Manager plus all functions concerning requirements in TEMPPO and TEMPPO Administrator e TEMPPO Editor All functions for creating Test Packages and Test Cases e TEMPPO Reporter All functions for creating reports and analysis e TEMPPO Guest All functions for viewing and exporting data Those roles can be changed except TEMPPO Super user Page 292 User Manual TEMPPO V6 0 Edition March 2014 Appendix 13 6 1 Functions to be applied to a role An X means that it can be de activated for a role Rig o U 5 r o Y z Bi U U o oye Z A K S TEMPPO Adminstrator administrates x _ oo pC Administrate projects X X X XK Administrate roles X X X X X __ Change includes assignment of roles to users id Administrate test structures oT XK P ti Administrate test suites EX XP O pd Assign Requirements X 1x FP T i tt id sign Testcategory X TX FP T y Pp Assign Testlevel O X TX po Assig
125. TEMPPO V6 0 Edition March 2014 Description of Use DOORS seats TEMPPO Requirement Test anager Manager DEV1 1 0 DEV1 1 0 Test Structure Req1 3 Req1 V3 1 1 i PLM1 1 0 Req2 import update Rea2 let a ales 1 0 R Req p eq3 Req3 TC2 Req ees ce aa Y lt i Req2 Req3 OR Req3 FE Reni ine DEV2 2 0 DEV2 2 0 1A S TC5 Req1 Req1 Req5 Nw Cais Feu Req TC6 Req3 Req3 Sopy of DEV1 Reqi Req2 Req3 lt Test Suite TC1 TC2 TC3 Copy of DEV2 TC4 Reqi 5 TC5 Req2 of TC6 Req3 t KK AKA Figure 243 DOORS TEMPPO data exchange The module Sales specifies requirements which are refined in the module PLM1 which for their part are refined in the modules DEV1 and DEV2 DEV1 and DEV2 certain baseline or latest version are imported into TEMPPO and provide a base for the test cases organized in a test structure For test execution a test suite is created where test results are recorded which can be reflected onto the linked requirements When exporting the test results to DOORS the imported modules are copied DEV1 and DEV2 and the requirements in the copies will be flagged with test results Since a single requirement can be covered by several test cases Req2 in DEV1 rules are applied to build unique results for requirements
126. Test suite name e Logical expression e Remove test cases manually In the first step the test suite tree is shown Figure 80 where you can select an existing test suite that will be used for pre select all settings in the wizard Page 71 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard E x Steps Select Test Suite 1 Introduction Select an existing Test Suite 2 Choose creation mode 3 Select an existing Test Suite 4 Select nodes or subtrees Notepad RTF Import with TCs 5 Enter test suite name Erw S PAATE EE te eee SIA Test Suites for V1 1 2012 02 16 nissan 9 V1 1 1 editable version 7 Remove test cases manually p aiibi i vererven i Test object Version XYZ RCO1 16 02 2012 VW editable version TEMPPO Test Suite Generator lt lt Prev Next gt gt Cancel Figure 74 Select a test suite Figure 75 shows the first step for creating a test suite It shows the whole test structure and the test packages are pre selected like the predecessor If you want to consider a whole test structure with all the test packages and test cases for test execution select the root node and press Next Bj Test Suite Wizard x Steps Test structure pre selection 1 Introduction Select test packages hold lt STRG gt and lt Shift gt for mutti select 2 Choose creation mode 3 Select an existing Test Suite 4 Select une or subtrees Notep
127. TestPartner Test Partner E User Interface gt Tree User name Admin Test Step Cells gt Analysis Newsboard TestPartner_SQL gt Test Package Test Suite C temp Database Test Automation Silk Test WinRunner Universal File Universal Socket gt QuickTest Pro gt JUnit TEMPPO Designer IDATG Ranorex Commands Change Management gt Bugzilla gt ClearQuest Telelogic Change JIRA Figure 269 Settings TestPartner The meanings of the parameters are as follows Page 212 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e User Name User name in TestPartner for executing the automated test cases e Password The password for the user in TestPartner e Database Name of database when logging in to TestPartner see Figure 269 e Temporary Path Has to be set for storing TestPatner s temporary data Use the Default button to restore the default arguments If the check box in the bottom of the tab is checked the temporary automation files will be deleted after automation TestPartner Logon o o t Tha TestPartner E irom Compuware User Mame Admin Password ee Database TestPartner Configure cne Figure 270 TestPartner Login 3 3 16 2 9 JUnit For Junit see chapter 6 JUnit User Interface H Tree Test Collector at scch panama junittool Simple TestCollector gt Test Step Cells 7 Analysis Arguments cp C temp junit4 7 g
128. Tested 10 12 2002 14 53 48 E testBagSimple Addin samples money I testBaysubtr Pa a Tester atw10s2 E te st8eqgSumAdajundt amples money Me Type Test Result E testecectSenple Adder samples mone Result up junit tramevork AssertionFailedError Bi tesiMoneyGagE quala jund samples mors at junit s4mples money MoneyTeat testilszero HoneyTest java 54 Oo betiMoreyBaghath jund samples mone br Sun c flect WativenethodaAccessoriIapl invokeO Native Hethod E tesiMioneryEquatn jund samples money W at sun ceflect WativenethodAccessorlapl invoke Nativetethodicces E testmoneyHashijunt samples money Mo at sun reflect DelegatingMethodAccessorlIupl invoke DelegatingMetl E testhormatize2jund samples money Mor at 4t scch panana junittool TestRunner doRun Unknow Source Pie b tA lesiNormaire jund samples morty Mor E te sthcemaizes pand sampdes money Mor A testPrirtipund campies money MoneyTes TesiGoa E te tSnpieAdayjund samples money Mon E testSenpieBagAddijund samples money Hl testSinpieMutiply junt samples money A E testSenpiettegate urd samples money h E testSerpieSubtract und samples money E testSenpityQunt samples money Money Figure 353 Failed test case result message and stack trace 6 6 Known Issues Unsupported JUnit extensions Currently only standard JUnit test classes are supported i e JUnit test cases are expected to be an instance of junit framework TestCase and JUnit suites are ex
129. Testmanager 15 02 2012 16 55 06 6 31 kEyte rfinport_1 329320751 2691 632 _1329320751 395 png Testmanager 15 02 2012 16 45 51 6 31 kEyte uninstall lac Testmanager 14 02 2012 14 02 51 2 67 kByte uninstall lagder Testmanager 14 02 2012 14 07 15 2 67 kByte Figure 309 Metadata Uploads If you activate Delete all non referenced uploads a confirmation window see Figure 310 is displayed before deleting all non referenced uploads Delete unreferenced uploads X 7 Do you really want to delete all unreferenced uploads Figure 310 Confirmation window 5 4 6 Requirement Structures With requirement structures you can assign requirements to test cases or test packages In the list you see all existing requirement structures see Figure 311 You can create new requirement structures with TEMPPO Requirement Manager Page 241 User Manual Edition March 2014 Fi TEMPPO Administrator Testmanager Database bo Roles E Users Metadata LA Projects Lacks License TEMPPO V6 0 TEMPPO Administrator O x Test Levels Test Categories attributes GB Uploads Requirement Structures C User Fields Components Customer requirements Import Learning Project Use Cases 1 Link test cases to requirement Notepad Notepad 1 Requirements for user documentation SW requirements User requirements Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmana
130. Z RECOS 16 02 2012 Labels only ClearCase style a Test object Version XYZ RCO3 COPY 16 02 2012 Order te edabe erly ie ascending gt descending Cancel Figure 100 Open an existing test suite After the test suite is opened you can proceed with your test execution as described in the previous chapter You can repeat this cycle as many times as you like 3 1 4 3 Editing Test Cases during Test Execution As stated in the introductory paragraphs of the test execution chapter it might well be that you detect faults in your test cases just before you want to execute them If you want to edit also cut copy paste test steps before or during test case execution it is the best way to select the test case and call the menu item Edit test case The test structure is highlighted and the test case is automatically selected Page 88 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fnd and Replace F3 Edit test case Sao Details Select All Crrl 4 f Tee b Run automated Set Resultis er Edit Refresh recursively Ea love Ownership g Analyse selected E Report selected Then add e g a test step see new test step 4 in Figure 101 The Apply and Discard buttons become enabled When pressing the Apply button the changes done in the test structure will be applied to the test suite and you can execute this new or edited test step Fi TEMPPO Testmana
131. a Project Plan e g MS Project is written that contains tasks for all test activities Input for the plan is given by the general budget for testing activities estimated number of test cases to be developed number of resources milestones estimated effort of executing a test case bug analysis regression testing testing fixed bugs effort Page 13 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 1 3 Defining Test Case Attributes After the implementation phase you will have a lot of test cases even in small projects and it s very likely that you want to have just a few of your test cases bundled for test execution because you don t have the time to execute all of them and therefore you decide to execute the high priority ones only there are several testers each of which should execute several test cases Furthermore we could consider that you want to get a survey of your test cases or test results under certain criteria For example it could be interesting for you how many test cases have the implementation state ready which means they can be executed how many high priority test cases are failed TEMPPO offers features for both situations namely the filtering of test cases for test execution see 3 1 4 1 and the creation of analysis charts see 3 1 5 1 But for being able to use these features it is indispensable to define attributes The following test c
132. aa EAE 204 aLL TESE SUE EN a 205 316 2 Database poa o aa E 205 3 LOZ WESt AUTOMO eesin a EEEa E EEE 207 DLG ZAS JUAN cso a NE a A 213 3 3 16 2 10 TEMPPO Designer IDATG cccc i cccsseeuseeuveeuseeuueeuueeunes 214 SOO kE RANOTO oee EESO news uaeniasacvens 214 ISAGA COMMS areri a E EOT 215 3 3 16 2 13 Change Management cccccccccccssccccccneennnecueeesesenssegs 216 4 TEMPPO ManaGe rk agiticitciscinrtseisierdisncasiersisiriieeesunrsreisderivandeureeennndes 221 AT Database Connect sisaecueninerderndeonnedecuniaennaceenecuaienrdearmndeamendes 221 A2 USEF Management iniesenincavhatcniaiednbaveksarsemensnianbedanaiadudimeuteieeiatees 222 AP MS WINGOW Iodi ereenn ra 223 4 2 2 L gin WILK DASSWOFG senres aaa E AAE 224 A223 USer Propere S peri rore T e EOE 224 4 3 DatabdaSe MIgratO Nisserne aaa a aaeeea 225 5 TEMPPO Administrator csssccccnnncccccnnnececenneeeeeeneeeeeeenneeeeeennneeeennnunnees 226 SL Database COnMeCUOM us iscsnaaseadica aaa aaa a 226 S2 ROl eaa a a a a 227 Jo User managemen riiseni a a a a 229 SE LDAP pocnaa a A r 230 Jol EDAP COMECUOMioceen a i 231 Sa d 2 Importing Users from EDAP siccsossavtinwn sie censeeeeniwaiaeanaeria eae 232 5 3 1 3 Synchronizing users with LDAP ssssssessssssssrsrnnrsrrnrerrerrnas 233 54A Metadata aa a a 233 SA General Behavior eprore a E A T 234 5 4 1 1 New Metadata Entries s sessssssussnnsnnnnunnnnnnnnnnnnnnnnnnnnnnnenrne 234 5 4 1 2 Delete Metadata Entries cccc
133. ackages and test cases However the update function see below relies on the names to maintain the relationship to the JUnit test classes Page 264 User Manual TEMPPO V6 0 Edition March 2014 JUnit Referencing the JUnit class file In the Automation panel each test case contains a reference to the file where its code is defined This is a JUnit class file and its path is written like in Java E g a reference that reads junit samples VectorTest refers to a class file Junit samples VectorTest class F TEMPPO Testmanager Demo Notepad zZ joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help gt Test Structure JUnit System Test 41 l x H q P H gf E Mo filter ALA JUnit B S 1 Framework Tests a b 1 junit tests extensions Extension Test General Attributes Test Steps B Automation Requirements History Plan Execution History 0 1 1 test Running Error in Tests a 1 2 testSetupError InTest Setup funit tee Tadi JUnit Jy 2i a 1 2 junit tests extensions Active Test Test why 1 2 1 testActive Test junit tests extension File junit tests extensions Extension Test c olay 2 9 testActive Repeated Test0 junit tests ae al 1 3 junit tests extensions Repeated Test Test Script Data why 2 1 test Repeated Once junit tests exten dy 1 3 2 test Repeated More Than Once qunit t est RunningErrorin Test Setup oy 1 3 3 test RepeatedZera junit tests extens ahg 1 3 4 t
134. activated F inherit Legend T Notinherited Notierted all selected TCs do not have any eee inherited attributes If the checkbox is activated meite all selected TCs inherit their attributes If the checkbox looks like E Inherited partly the common state is mixed TCs with and without inherited attributes W Inherited Page 149 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 2 1 2 Test Case tab Requirements The tab Requirements contains 3 sub tabs Direct linked Requirements Inherited Requirements and Inheritance Tab Direct linked Requirements displays the Direct inked Requirements requirements which are directly linked to a test case tesena Requirements assigned to all selected test cases are eauiemen parti displayed as usual in white background color Requirements assigned to not all test cases are feno rone le displayed in a special color grey background color pess ComponentA R2 If you want to assign such a requirement to all ems os selected TCs select it and activate the context menu wa Se EES It is displayed in red color as well as new linked requirements The tab Inherited Requirements displays the Inherited Requirements mea requirements which are inherited from test packages Requirements assigned to all selected test Requireme parta cases are displayed as usual in white background color Requirements assigned to not all test
135. ad RTF Import with TCs i Enter test suite name I a Introduction Determine the logical expression Ea General description of the product T Ramcwitest caver manai E aan psoas of the required product features cope elivery Sequences scenarios of interactions with the environment eg User goals fa Required functions of the product F File Administration H Edit Functions H E Print Functions J Search Functions a Find Replace i Za Help System a External interfaces of the product eg Other product features required H A sf Finish Cancel TEMPPO Test Suite Generator lt lt Prev Figure 75 Test structure pre selection test packages In the 3 step you have to enter name together with a description for the test suite Figure 76 When pressing Next you have to determine the logical expression Figure 77 which is pre selected like the predecessor Page 72 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard 7 F x Steps Determine the test suite 1 Introduction Enter test suite name 2 Choose creation mode 3 Select an existing Test Suite 4 Select nodes or subtrees 5 Entertest suite name Test object Version XYZ RCO2 6 Determine the logical expression 7 Remove test cases manually Created 16 02 2012 14 19 55 Owner Testmanager Type Test Suite Description
136. after reloading the whole tree 3 1 4 3 2Adding and changing test packages during test case execution During test case execution it might be necessary to create new test packages on a branch see Figure 104 and use them also in the latest version later on Page 91 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad iol x Project Test Structure Edt Test Execution Evaluation Tools windows Help e Test Structure Notepad RTF Import with TCs System Test W111 M d4 b H GP E no ter l QU Notepad RTF Import with TCs 2 HE 1 Introduction i L 2 General description of the product General Attributes Details Requirements History Plan 2 8 3 Detailed description of the required product 1 A 3 1 Scope of delivery ID ltp721 a 3 2 Sequences scenarios of interactions m 3 3 User goals l INew Test Package onthebranen OOOO O 2 Se 3 4 Required functions of the product Mame Mew Test Package on the branch 24 H 3 4 1 File Administration Sr 293 444 New lf 3414141 New fle opened no Created 16 02 2012 15 50 36 Updated 16 02 2012 15 60 37 3 4 1 4 2 New file opened ch Z 13 414 3 New Test Package E 3 4 1 2 Open Number of TCs 0 a 3 4 1 3 Save o m 3444 Exit Test Category 3 4 2 Edit Functions 3 4 3 Print Functions H 3 4 4 Search Functions bn 3 4 5 Help System H Ea 3 5 External interfaces of the product Fl EJ 3
137. age The buttons are only enabled if the selected node has been changed since it was loaded loj x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test 3 l al E x U di amp HH E No filter A Notepad RTF Import with TCs Fb 4 Introduction Cet Ea 2 General description of the product General Attributes Test Steps Ei atomation Requirements History Plan Execution History Ej 8 3 Detailed description of the required product lL 3 1 Scope of delivery User defined ID ftc7a2 m 3 2 Sequences scenarios of interactions 3 3 User goals erie log 3 3 4 Required functions of the product EP a 3 4 1 File Administration Owner Testmanager Updator Testmanager o a a 3 4 1 1 Windows Login i Created 20 02 2012 10 26 12 Updated 20 02 2012 10 53 04 2 oi 153 4 1 2 Mew Type Manual f Automated Test Case A 3 4 1 3 Open S414 Save aa tesst goal o bli 3415 Exit 3 4 2 Edit Functions RL 3 4 3 Print Functions pF E 3 4 4 Search Functions 3 4 5 Help System H A 76A Peternal intertares the nrn ict 5 a Lack Apply Discard Figure 213 Apply Discard 3 3 7 Newsboard The newsboard informs the user about changes done on the current test structure version It can be opened by calling the menu item Test Structure gt Newsboard In Setting
138. ager At least one TEMPPO Superuser has to be defined 4 3 Database migration Fj TEMPPO Manager system iol x Database Users Al Migration Database Version 6 8 Build 46 Application Version 6 0 Build 0 Database must be migrated Attention You may need administration privileges for migration Index Tablespace temppont Data Tablespace sitemppoindex Save Migrate Migration Loy Figure 287 Manager Database migration This tab is only active if the Administrator is connected to the database see Database Connection Database migration due to version changes of TEMPPO is done here If migration is needed the buttons are active Migrate processes the built in migration script with button Save the migration script can be saved to a file SQL script for Oracle VB Script for Access The saved script must then be executed outside of TEMPPO Page 225 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator 5 TEMPPO Administrator The following configuration settings are defined with the TEMPPO Administrator tool Database connection Test automation settings Roles User management except TEMPPO Superuser Metadata Projects License server connection Configuration settings are written into the admin properties file which is read by TEMPPO on application startup Therefore TEMPPO must be restarted before any configuration changes take effec
139. aluatior Test Structure Motepad RTF Import with TCs Systen M4 gt W o5 E monter AL Notepad RTF Import with TCs E E1 Introduction E 2 General description of the product a 78 3 Detailed description of the required prod L341 Scope of delivery 2 at Aiak hil cenarios of interacti DE EG 3 4 2 Eat Functions 3 4 3 Print Functions m 3 4 4 Search Functions 3 4 5 Help System i E 3 5 External interfaces of the product BATEA 3 6 Bua ours ERU iaia F TEMPPO V6 0 Description of Use Figure 170 Selection with lt Ctrl gt lt A gt or menu Select All If a test package without children is selected when pressing Select all then nothing changes Test packages and test cases can be selected with lt Ctrl gt see Figure 172 or with lt Shift gt see Figure 173 After pressing Select all sub trees of the test packages and the selected test cases are marked see example at Figure 171 Page 144 User Manual Edition March 2014 Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Er Test Structure Notepad RTF Import with TCs H o d gt HW E No filter a 3 3 User goals Sa 3 4 Required functions of the product Pa 3 4 1 File Administration Sao 3 4 1 1 New fi 3 4444 New file opener Fi TEMPPO Tester1 Demo Notepad 2 New e pena Project Test Structure Edit Test Execution
140. am under test did not match the expected result as specified in the JUnit test case The execution of the test case had errors and no results could be compared There are basically two possibilities The call from TEMPPO to the JUnit test class failed E g because the JUnit class did not exist in the classpath the specified test method did not exist or the class method were not implemented according to the JUnit interface The execution of the JUnit test case had errors E g the JUnit test case or the program under test threw an uncaught exception or even the whole program under test crashed Page 272 User Manual TEMPPO V6 0 Edition March 2014 JUnit Table 4 Possible test execution results Ei TEMPPO atw108s2 JUnit extension tests T E io x Project Test Structure Edt Test Execution Evaluation Tool Windows Help Test Suite Sample JUnit execution 1 1 1 H 4b HW QD Semple Juin execution E Al nd Tests PB punt samples Vector Test El teshlapectyjund samples Vector Test OB testCortanciurd sampes Vector Test GB testlementatijure samples Vector Test WB tectRencveBlemert purdt samples Vecto E testCioneqund samples VectorTest pa User Defined E teig A lesRemove Ajumi samples Vecio Test part cargies money MoneyTest Owner ahis ADBA sanpes emai Created 10 12 2002 14 21 01 eriBaghegate und samples money Moe E testBaghctiquate und sampes money A
141. and 3 3 16 2 13 Change Management Select the change management tool which is used in TEMPPO for adding bugs to test steps Page 216 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Change Management rface T Active Change Management Tool HT Test Step Cells Bugzilla C Telelogic Change gt Newsboard j Test Suite A JIRA Database Test Automation Sik Test WinRunner Universal File Universal Socket QuickTest Pro Test Partner gt JUnit gt TEMPPO Designer IDATG Ranorex Commands Office gt Bugzilla gt ClearQuest Telelogic Change JIRA Figure 276 Settings Change Management 3 3 16 2 13 1 Bugzilla The following parameters have to be specified if using Bugzilla e Basic Authentication If the checkbox is activated a proxy server authentication user password can be used e URL The http address of your Bugzilla server e User User name who will post the bug e Password Password of user Page 217 User Manual TEMPPO V6 0 Edition March 2014 Description of Use User Interface H Tree Test Step Cells gt Analysis gt Newsboard interna gt Test Package H Test Suite E SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSESSSCSSCSCSSCSCSCSCSSSCSSS Database Test Automation Sik Test Waamer http atinzp10qa ww300 atos net 2849 bugs_sitemppo_internal Universal File Universal Socket testmanager atos net gt QuickTest Pro Test Partn
142. anual Test Execution For every test case you process its test steps The sequence of test cases and test steps is arbitrary you may proceed in any order that suites your needs best For easier navigation from one test case to another the buttons on top of the test suite tree can be used first previous next and last A Test Step can be given the following results not executed the test step hasn t been executed yet initial result y passed the actual behavior matches the expected one X failed the actual behavior does not match the expected one blocked the test step couldn t be executed because some pre condition failed S not implemented the test step couldn t be executed because the SW part to be tested is not implemented amp on hold the test step couldn t be executed because the SW part to be tested is postponed to another milestone Page 77 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 210 x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 V 1 1 1 x M 4 gt N GP EE No fiter ALJ Test object Version XYZ RCO1 M 3 Detailed description of the required g 3 4 Required functions of the prodi Autonretion Requirements History Attributes TR Previous Results Plan Execution History Sa 3 4 1 File Administration EEES Attributes Test Steps BA 3 4 1 1 New 3 4 1 1 1 New file o
143. apply the following before the update procedure is started remove test package Framework Tests to simulate a new test package create a new test case in package junit samples VectorTest to simulate an obsolete test case Page 266 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fi TEMPPO Testmanager Demo Notepad Z ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Sucre Urt System Test VN a M dab MG EE no nter D TEMPPO Designer DAT J Juni ES 1 Framework Tests ce 1 1 junit tests extensions Extension Test O wqhy 11 1 testRunningErrorinTest Setup qunitt iaJ 1 1 2 test Setup Error n Test Setup junit tes ID prez 1 2 junit tests extensions Active Test Test o hajg 1 2 1 testactive Test unit tests extension ogy 1 2 2 testActiveRepeatedTest0 unit tests Neme Framework Uses ce 1 3 junit tests extensions Repeated Test Test why 1 3 1 test Repeated Once junit tests exten dy 1 3 2 test Repeated More Than Once junit t Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 29 oy 1 3 3 test RepeatedZera junit tests exten ahg 1 3 4 test Repeated Negative junit tests ex General Attributes Details Requirements History Plan Owner Testmanager Updator Testmanager Type Test Package Number of TCs amp Test Category a Description Imported by TEMPPO fram JUnit Suite junittests exten
144. ar Chart 3D Line Chart Stacked Horizontal Bar Chart Stacked Horizontal Bar Chart 3D Stacked Vertical Bar Chart Stacked Vertical Bar Chart 3D Vertical Bar Chart Vertical Bar Chart 3D Orientation You can choose the orientation of the labels on the x axis Representation Data can be represented absolutely or relatively use option buttons at bottom right If Accumulate is activated data on y axis is displayed accumulated Time Settings If you select in x axis and or Group by a date time attribute you can configure the chart by setting a start and an end date Additionally the units days weeks months or years can be set Page 131 User Manual TEMPPO V6 0 Edition March 2014 Description of Use chart EE Data X Axis Dos CT Groupby T Chart Vertical Barchat o Orientation r a3 horizontal S vertical ap Les Representation absolute relative Accumulate Time Settings s f Stet 09122004 Milestone End 09 12 2004 Priority medium E Top ut 122 bes E Figure 151 Report Chart Settings 3 1 5 6 4Previewing and Saving You can either preview the report that will be generated or immediately save it to an Word or Excel file Button Preview Depending on the size of your test structure test suite and network speed the generation of the report preview or file may take a while because a lot of data must be loaded from the database
145. ase attributes are predefined in TEMPPO Type Manual Automated Situation Regular Error Priority Top High Medium Low State Designed In Work Ready for Review Ready Approved Test case type Verification Validation Test Level Module Test Integration Test System Test Acceptance Test Regression Test In most cases the predefined attributes will fulfill your needs and you just have to decide which ones to use defined in the test plan If you cannot come along with them you have the possibility to define your own ones so called user defined attributes For detailed information on how this is done in TEMPPO see 5 4 4 3 1 1 4 Baseline Import Requirements SiTEMPPO Requirement Manager is used for requirement engineering or for importing and updating your requirements in TEMPPO s database from external tools like DOORS or RequisitePro If the requirements are ready for test case creation the requirements are baselined using also the view concept The requirement engineer defines a filter from requirement attribute e g All requirements that are implemented and of high priority and freezes that requirements to a baseline On the other hand the requirement engineer imports and later updates the requirements from the external tools For details refer to TEMPPO Requirement Manager s User Manual 3 1 2 Test Design Test Design covers the tasks of Working with Projects Buildin
146. ased on a report setting to the specified file Remark If there are a personal and project setting with the same name the personal one is taken If there are a personal and project filter with the same name the personal one is taken The file is specified only by name The extension is specified by report type specifies a file path name Only considered in conjunction with option profile closes TEMPPO after test execution Only considered in conjunction with option run print this message hides TEMPPO during test execution Only considered in conjunction with option run print information for license request Use the batch file TEMPPO bat in the installation directory for running TEMPPO with command line options TEMPPO Dat expork Teste tructure my Proet Tie est Structure Vlz export xml Page 282 User Manual TEMPPO V6 0 Edition March 2014 Plug ins 9 Plug ins TEMPPO offers a plug in mechanism which automatically loads the implemented Java interface packed into a jar file Each plug in must be deployed in its own jar file and must be installed in the directory lt TEMPPO installation directoy gt plugins A jar file always contains a manifest file which must contain at least the property Plugin Class which must provide the fully qualified name of the class implementing the plug in It s needed for loading the class Example for content of a manifest file Manifest Ver
147. ases are also highlighted in the test suite tree 3 1 5 5 Progress charts TEMPPO offers a feature which allows you to create flexible progress charts for test structures and test suites On one hand you can compare progress of test case creation and on the other hand you can display the progress of test suites by comparing the results 3 1 5 5 1Creation Progress If a test structure is opened and menu item Creation Progress is activated Figure 126 is shown By pressing the button Select Test Structures Figure 127 Page 105 User Manual TEMPPO V6 0 Edition March 2014 Description of Use is displayed where you can select from the test structure version tree with the mouse together with lt CTRL gt pressed the versions to be displayed If you want to display several consecutive versions you have to select the first one keep holding the lt SHIFT gt key and select the last one in the tree normal selecting behavior The following chart types are available e Horizontal bar chart e Horizontal bar chart 3D e Line chart e Stacked horizontal bar chart e Stacked horizontal bar chart 3D e Stacked vertical bar chart e Stacked vertical bar chart 3D e Vertical bar chart e Vertical bar chart 3D With the radio button Orientation you can display the description of the x axis either vertically or horizontally The data can be switched from absolute to relative and vice versa Using the checkboxes States the chart can be customize
148. asks by activating the menu item New gt Task Package or New gt Task Package before F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test u3 H d gt WH E Mo filter dJ Notepad RTF Import with TCs fam Task Package Ctri At T a 3 Ger Ga Test Package before sil 4 Det Find and Replace F3 2 e SS fi Test Case Ctrl Alt th 5 Spe Bal 6 Obli show Details Dl Test Case before Select ll Owner Testmanager Up A task package contains all properties of a test case ID fixed name owner created updator updated test category optional description Fi TEMPPO Testmanager Demo Notepad i joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test 15 H d gt WH E No filter Abd Motepad ATF Import with TCs oe 1 TEMPPS Designer DATS Tasks 11 New Task Package General tributes Details Requirements History Plan Introduction General description of the product ID pras Detailed description of the required product fea Specifications for project management usecase FiesNew O _ Obligations of the client Name UIse case File gt New Literature Owner Testmanager Updetor Testmanager Crested 20 02
149. at it is not possible to launch an application on a remote computer without any additional software e At port number the socket connection for automation will be opened e Adapter is the tool specific implementation for the handling of results received via the socket to convert it into a format understandable by TEMPPO Select here the implementation for your tool For more information on adapter implementations see 13 7 e Arguments are the command line arguments for the automation application In the arguments parameters can be used for the configuration Parameter sdbtcid internal unique database id for the test case Page 210 User Manual TEMPPO V6 0 Edition March 2014 Description of Use user defined id of test case test case name project name Version automation file Example Administrator configuration Arguments tc dbtcid ts dbtsid f file args O O O O O O O test suite name Test case configuration Additional Arguments atw108s2 3 xyz Data sent over socket tc 213 ts 1158 f x test scripts jlms_checkout xml args atw108s2 3 xyz 3 3 16 2 8 4 QuickTest Pro For QuickTest Pro you have to specify the following parameters e Application Path path to QTPro exe e Temporary Path path where temporary files are stored e Result Path path where all the result runs are stored e Result viewer path to QTReport exe QuickTest Pro User Inter
150. ate Devroom for Product Create Devroom for Product Owner No user with the name nn1 exists Assign Members to Devroom Assign Members to Devroom Owner No user with the name nnd exists Assign Group to DevRoom Assign Group to DevRoom Cramer No user with the name nn1 exists Import Masterplant Incremental Import Masterpiant Incremental Cramer No user with the name nn1 exists Import Masterplant Incremental Import Masterpiant Incremental Priority Normal is an invalid value for this field so the default value was used Y Figure 20 CSV Import Result Build manually XML Import Page 38 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 2 3 4Referring to requirement numbers or names On the other hand there is the possibility to link requirements to test packages as well as test cases In some projects it might be necessary to track the requirements or rather their IDs from defining until executing test cases But before linking those to test packages it might be necessary to define and assign them for the project see chapter 5 4 6 In TEMPPO Requirement Manager you can create requirement structures In TEMPPO Administrator requirement structures are assigned to TEMPPO projects After that you can link the test cases to these requirements You have two possibilities to relate requirements to test packages or cases Add and or inherit from parent test packages 3 1 2 3 4 1 Add Requirement For adding a req
151. ated imported imported manually created manually created manually created manually created imported manually created manually created Here you can add delete and view attributes In the master screen the selection grouped by type can be changed by the box above When pressing the window Attribute Properties is opened A name can be entered and user name and creation date are suggested automatically In addition the attribute has to be categorized for a test case test suite or and test result A test suite attribute may also be used for test execution attributes but not for a test case s one This implies that the usage of an attribute can be changed after creation The boxes for categorizing are disabled if the attribute is already used In tab Details the possible attribute values must be defined Page 238 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator x eneral Details Browser Created 20 02 2012 15 18 12 For Use of y Test Case Daner Testmanager 7 Test Package Type Atribute T Test Suite E Test Result E Reguiremernt Description cancel Fi Properties of New Entry x General Details EF Browser Chrome E Browser Firefox ED Browser Netscape E Browser Opera Cancel Figure 306 Attribute Properties An attribute cannot be deleted if it s already used in a test case 5 4 4 1 Copy and rename of UDA For user defined attributes the
152. atwor426 psenllbespr1085 PSE SES MEC L Linz AUSTRIA i Moritsch Karin abwof3cl psekblbespr713 PSE SES MEC L Linz AUSTRIA 13 Moritsch Karin atw1Obme karin moritschi PSE SES MECL Linz AUSTRIA 14 Niederwieser Peter atwlOmce Peter Wiederwie PSE SES MEC L Linz AUSTRIA 15 Obermueller Peter abl 2S peter obermuell PSE SES MEC L Linz AUSTRIA Import Close Figure 295 Importing users from LDAP You can search for a last name first name login windows group department location and a country By clicking the button Clear you can delete the search preferences Clicking the Search button will perform the search and the result is shown in the table below The search can be cancelled at any time by clicking the button Cancel l User cancelled the search Figure 296 Cancel a LDAP search If you are searching for a Windows group or if the search output is very large the result of the search might not be complete because the performance of the LDAP server varies So if you are searching for a specific user try to find him by searching for the department or other criterias After selecting one or several users in the table the button Import is enabled By clicking this button you can import the selected users into TEMPPO If you select a user that is already a TEMPPO user the user is updated You can cancel the import at any time by clicking the button Cancel Page 232 TEMPPO V6 0 TEMPPO Administrator
153. ber there still remains the problem that you have edited a test case on the branch Very likely you will need these changes for all further test Page 89 User Manual TEMPPO V6 0 Edition March 2014 Description of Use executions that will be branched from the latest version of the main line What can you do to solve that problem There are two possibilities On one hand you can merge each single edited test case After pressing the Apply button the user is automatically asked to merge the changes Remark The Merge button can always be pressed if enabled x The test case was modified in this branch version Would you like to apply the changes also in the main latest version Additionally TEMPPO Test Manager checks if the test case to be merged is already changed in the mean time and informs the user Merge Warning x The test case on main line was updated by Mh 1 so The merge will overwrite this version in the main line If pressing Yes you may select which content should be merged into the latest version see Figure 102 Eimerse x Select the content which has to be merged Attributes IW Test Steps m Automation iCal Requirements Jw Plan Figure 102 Merge content The corresponding content is copied from the selected branch to the latest version of the main line which means that the current version of this test case parts general attributes test steps automation requirements plan i
154. box looks like tertedpsrtaty the common W Inherit Legend F Not inherited Inherited partially W Inherited state is mixed TPs with and without inherited requirements Page 152 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 2 21est Suite After activating the menu Edit gt Show Details the tab Attributes TR is displayed e tab Attributes TR see Figure 177 The attribute values that are assigned to all selected test cases are displayed as usual The attribute values assigned to not all test cases are displayed in a special color grey background color New added attributes are displayed in red color ioj Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version v2 RECOS CORY M 1 1 Wo d P HH w Mo fitter ALl Test object Version v2 RCOS COPY ii Se 3 Detailed description of the required g I a 3 4 Required functions of the prodi attributes TR Plan Ej 3 4 1 File Administration amp a 3 44 1 New Hy Atribute values e 4 25 3 4 4 Search Functions I aa 3 4 4 1 Find ya SS Et k ESEA 4 Find up Ta M a fl Ea 34 41 41 53 QuickT EE 3 4 4114 Test Pe BY 3 444115 UA no Apply Discard amp 8 amp amp amp amp Figure 177 Attributes TR 3 3 1 2 3Filter in multi selection mode If there is a multi selection and a filter is set only those items that match are
155. cases SES sesa are displayed in a special color grey background req683 Component AR3 ig Of course it is not possible to edit anything ae a ere The tab Inheritance displays the COMMON rectineea Requirements innented Requrements inheriancs state of the inheritance flag of the selected gt gt gt ase TCs If the checkbox is not activated MW inherit Legend E Not inherited H Netiheted all selected TCs do not have any REEE inherited requirements If the checkbox is activated merte all selected TCs have at least one inherited requirement If the checkbox looks like M 4ps the common state is mixed TCs with and without inherited requirements W Inherited 3 3 1 2 1 3 Test Package tab General This tab is reduced to the combo box for test General Attributes Requirements category If all selected test packages have rs set the same value the value is displayed If oo EE there are test packages with different test categories an entry with Several Categories is selected If there is no selection an empty entry is selected Page 150 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 2 1 4 Test Package tab Attributes The tab Attributes contains 3 tabs Direct linked Attributes Inherited Attributes and Inheritance Tab Direct linked Attributes displays the General Test Packages Test Casel comm
156. ce At first a test case package is searched and selected The user has to click again for replacing the occurrence and then the next one is searched If the test case package is locked the test case package isn t changed e g the next one is searched e Replace All in Test Case package To use this feature a test case package have to be selected first otherwise the button is disabled At first a test case is searched and selected The user has to click again for replacing all occurrences in this test case package If the test case package is locked the test case package isn t changed Page 172 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Replace All The selected field of all test cases packages is changed which contains the text After replacing all a message is shown see Figure 212 with the number of replaced test case and number of test case package which couldn t be replaced because of locks etc TEMPPO i x Fi 1 Search ino test cases if completed and 7 replacements in 3 test cases were done Figure 212 Replace result The replace functionality is disabled if the user has not the right for changing test case s in test structure test suite 3 3 6 Apply Discard When working with test structures or test suites you can save your changes within test cases or test packages using the button Apply By pressing button Discard your changes will be undone after a confirmation mess
157. chanism which is implicitly used for test execution When you create a test suite TEMPPO Test Manager automatically checks in your current Page 62 User Manual TEMPPO V6 0 Edition March 2014 Description of Use test structure This means that its state test packages test cases test steps is conserved no further editing is possible within this version and it can be restored any time in future To give you the flexibility of still being able to correct faulty test cases during test execution another action is performed automatically at test suite creation A branch containing a new editable version of the test structure is created you are prompted for a descriptive name and your new test suite is connected to it TEMPPO allows you to edit test cases in this branch as long as no result has been recorded for any of their test steps From then on no further editing is possible and thus your test results cannot get lost Of course you can still edit test cases in a different version of your test structure typically in the latest version on the main line In your next test execution again a branch off the main line will be created for you and the corrections you applied there will be visible in the new test suite The complex matters of test execution are explained in greater detail in the following chapters 3 1 4 1 Starting Test Execution Before the first test execution there exists usually just one version of the test structure v
158. cks by the current user in database Maybe another instance of TEMPPO Test Manager is running by the current user or TEMPPO Test Manager wasnt previous shut down cleanly Do you want to remove the locks nsure that no other TEMPPO Test Manager is running by the current user Figure 165 Locks found in the database on starting quitting TEMPPO 3 2 2 Refreshing 3 2 2 1 Refreshing manually 3 2 2 1 1Reloading the whole test structure test suite You can reload the whole test structure test suite by pressing the reload button ES on top of the tree see Figure 166 This has the same effect as manually reopening the test structure test suite Ei TEMPPO Testmanager Demo Notepad E Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x a Test Structure Notepad RTF Import with TCs System Test W5 b i A Notepad RTF menej whole tree H 1 Introduction 2 General description of the product i 5 3 Detailed description of the required prod 3 1 Scope of delivery a 3 2 Sequences scenarios of interacti 3 3 User goals i 3 4 Required functions of the product EL 3 41 File Administration ob Eb a 3 4 1 1 Mew o B a411 Mew file opened Error Hi 3 41 12 New file opened E 3 41 1 3 Mew Test Packac 3 44 2 Open Requirements History Flan Execution History General Attributes Test Steps Fy Automation Inherit attributes Priority Medium S
159. closes the window and no project is opened Page 16 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Testmanager Demo Notepad z oj x Project Test Structure Edt Test Execution Evaluation Toole windows Help Figure 4 Main Window project opened 3 1 2 2 Building the Test Structure A test structure contains test packages and test cases which can refer to requirements This can be established in 2 ways and or e Referring to chapters in documents e Referring to requirement numbers or names 3 1 2 2 1Creating a test structure TEMPPO allows opening only one test structure at a time which means that a test structure can only be created if no other one is already open Furthermore test structures are related to projects so the project which shall own the test structure to be created must be open too 3 1 2 2 1 1 Creating an empty test structure When activating Test Structure gt New gt Empty Test Structure the window shown in Figure 5 is displayed You may enter a name and a description Also a test level has to be related to the new test structure Fi Test Structure Properties x General Mame Notepad System Acceptance Test Owner Testmanager Updator Created 19 05 2010 14 03 04 Updater Type Test Structure SITEMPPO Designer D473 T Test level System Test a Description This test structure Figure 5 Test Structure Properties By clic
160. cseccseceseccueeuueeeneeuueeuresuneeuues 234 SAd MOVGOWMMEESIID erene aana a a a 234 DAZ TESE LEVEIS vererien en ETE E NE ENTE i 235 Sito VESECALCGOMES anin a a 236 SkA ARTIDUCOS cagainn a a E E A EA AN 237 5 4 4 1 Copy and rename of UDA sssssssssssssrsrrsrsrrsrenrrrrnrrrrerenrrrenan 239 Peas UPOS eo rE ar 240 S450 Req irement SUPUCIUFES 7s sctrecocseurssdsschrerecie nrn iiin nn Terk Eria 241 Site User Fed S aera T A T ATO NOA 244 Deo POJO E aa a E ei yeccmmiaaaineet aan 245 Jordi SEALING a Di OCCU sirri ias rinn TE rI rN TE ri 245 392 GODYVING a DFO CCE wisccssacesscevansrseartesodavitasenssanessumtenssieexkdesonarete 246 S53 TESE CASE template vysie iire EN E ETA NEN 247 S5 Create NeW TeSt CaSe inciri AO 248 5 5 3 2 Unlock save existing test case s ssssssessnsensnrunsnsnnnrnrnnnrensns 248 5 5 3 3 Test case template and filter susessssssessnnnnnrunnnnsnnnrnnnnsrenens 249 SoA TESEreSulttemplatE rnanera Aa 249 SDD Deletion S renneri aaa E E NE 249 5 5 6 Test Suites check consistency unlock ss ssssssssssssnesnssrnnensrnrnns 250 5 5 7 ASSIGN Metadata sirrane iarere SE ARRET EEE U 250 5 5 0 MOVC OWINGISMIlDsccunnsvanensss sat consasateenassremmasnaetancsauenasannnne cee 250 5 5 9 Freeze Unfreeze s sssesssssssnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnne 251 IO LOCK aieea niente nee ma heneidad deus waacieniide sperma scentaaoeut 252 5 7 LICENSE Server CONNMECHON sccrscctercnscenprnsassaa
161. ction for the Figure 93 Create a new bug entry Now a dialog for creating a bug or change request opens see Figure 94 Fill in the data of the bug and may activate the combo box Add test report In the end you press Submit The panel for Telelogic Change is displayed dynamically So the list boxes beneath the box State are dependent on the selected State All fields at the Telelogic Change window are mandatory for the change request Page 84 User Manual TEMPPO V6 0 Edition March 2014 Description of Use xi Reporter dietmar schlosser atos net Product Bugzilla Test Version Junspecitied Component Test Platform Hu v Operating System windows 7 Priority critical 7 Severity Top Assigned to L O O GC FO O URL esses Summary ftest Description description E ores Add Test Report V Pi New PR TEMPPO xi Reporter uidl9720 Synopsis P Description Add Test Report D State preview Application Build Version any 7 Occurrence Jany v Application Name Any ht Requirement Reference P Functional Area Any ha Severity any 7 Required For Car Release any 7 Submitter Name On Behalf Of System ID Any hd Submitter s Priority any v Discovered During Any hf attechmentt TT S Description FO attachment2 oT g Description P attachment 3 0 S Description FO Cancel Figure 94 Bugzilla Telelogic Change iNew bug remo x Mandatory
162. ction is empty ml Additional Test Levels and Attribute Values The values that are assigned to all selected test cases are displayed as usual white background color The values that are not assigned to all test cases are displayed in a special color grey background color If you want to assign such an attribute to all TCs select it right mouse click and activate nal es IEE Such attributes or new assigned attributes are displayed in red color Tab Inherited Attributes displays COMMON eaaeaoue innentea atirbutes innestare state of TCs which have inherited attributes _ E fro maqa TP Regular 5 Validation Priority Top Radio buttons If all selected test cases with Bii ea e Ne ae activated inheritance have set the same value the value is selected otherwise there is no selection Combo boxes If all selected test cases with activated inheritance have set the same value the value is displayed otherwise the selection is empty m Additional Test Levels and Attribute Values The values that are assigned to all selected test cases are displayed as usual white background color The values that are not assigned to all test cases are displayed in a special color grey background color Additonal Test Levels x wp F E The tab Inheritance displays the COMMON birectinkedAtnbutes innented Attributes Inheritance state of the inheritance flag of the selected TCs If the checkbox is not
163. cumulated together This means that one same test case is counted as often as it occurs in the test suites On the other all requirements without any link to test cases are displayed Page 114 User Manual TEMPPO V6 0 Edition March 2014 Description of Use By pressing the button Save As the chart can be saved as jpg or png file Tab Data In tab Data number of test results are displayed as table and exported to csv Test Suites Select Test Suites New Test Suite W6 1 1 New Test Suite V6 1 1 Requirement Structures Select Structures Components Notepad Requirement attributes 7 not executed blocked notcompleted notimplemented on hold Chart Horizontal Bar Chart 7 oO Sort nc reg 0 alphabetical Func_req23 o 0 descending Func reg34 o o Func reqs o o Values Func _req26 Loo oO A Func_req27 o 0 Only zero values Fu 28 0 E DEn o Func_regs o a Refresh o Func reg31 1 o 0 Figure 136 Requirement analysis over several test suites Data In tab Detailed Data for each requirement a column Requirement Structure and columns for test results with the TC IDs are displayed For each result cell a list of comma separated values is shown as follows lt test case ID gt lt test suite name gt lt test structure version gt lt next test case ID gt lt test suite name gt lt test structure version gt Page 115 User Manual TEMPPO V6 0 Edition March 2014 Description of Use
164. d By pressing the button Save As the chart can be saved as jpg or png file Page 106 User Manual TEMPPO V6 0 Edition March 2014 Description of Use i chart E pata Select Test Structures Chart Line Chart Orientation E horizontal i vertical Representation Test Cases absolute relative States lv Designed i eee a z z I Inork ic 5 z ci z i l 5 o g V Ready tor Review Test Structures M Ready States E pesigned Bin Work H Ready for Review Ready Tipp ek Fj Select Test Structures i l 3 x H5 Tests Linz reviewed E Tree style L igtest itest l_igtest Seely OC BRZ20 NA tee VOM O02 0007 H6 Tests Linz latest hilestone b Wien Testcases latest a Branch ascending ellenstein l6 wiern latest Saved by Opata ie Franch NWaviiap post l6 tests fate st Branch ost IE _Igtest ranch Versions only Labels only Versions and Labels ClearCase style Order c descending Branch 1 Tests Linz fate st Branch z ien L igtest x Figure 127 Select Test Structures 3 1 5 5 2Execution Progress There are 3 analysis available e Standard Execution progress of test suites can be created For several test suites which can be selected results and planned values a chart can be created Page 107 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Filtered Additionally a filt
165. d by the client and agreed to by H UO 7 Annex the development department These features contain all functions interfaces and other product features A number of points should be taken into account in describing the features Owner Testmanager Updator Testmanager Type Test Package Every required feature should be Uniquely identified be eee see ls eee oe es ee ee ths ee eel be Figure 28 Assigning a test category When creating test packages you may determine appropriate test categories Normally you start test case design with the chapter Required functions of the product that should cover all task based tests In further steps of test case design you identify GUI layout tests in chapter External interfaces User interface Such test packages should be given the test category GUI layout test They pursue the aim to cover tests for input syntax check completeness of GUI masks etc Furthermore you categorize the test packages below Other product features required that cover mandatory quality attributes like performance mass or stress test The result of the steps above is displayed in Figure 29 Page 35 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Ioj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test V1 H gt b Hyg E Mo fitter AL N
166. d description of the required product features E 3 4 Required functions of the product 3 4 1 File Administration B4 3 4 1 1 New 3 4 1 1 1 New file opened no changes failed fi 3 4 1 4 2 New ile opened changes passed 3 4 4 Search Functions B A 3 4 4 1 Find 3 4 4 1 Find up fi 3 4 4111 Case sensitive blocked E 3 4 4 1 1 2 WinRunner Check Stat on hold 3 4 4 1 1 3 QuickTestPro Test case not implemented E 3 4 41 1 4 Test Partner Test case not executed E 3 4 4 1 1 5 UAI not executed General Details Export Info Attributes Predecessor Plan Name Test object Version XYZ RCO1 Owner Testmanager Updator Testmanager Created 16 02 2012 13 47 29 Updated 16 02 2012 14 36 01 Type Test Suite Description whole structure Release canidate 01 IncludedTPs New Find ExcludedTCs Lock Apply Discard Figure 84 Test Execution Test Case Results 3 1 4 1 5 1 Test execution assistant Test execution assistant supports you in executing each step by displaying each step in an own window It can be called by selecting a step and pressing the button Test Execution Assistant Fi TEMPPO Testmanager Demo Notepad o E ol xj Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 41 1 1 M 4 gt N B No nter QA Test object Version XYZ RCO1 3 Detailed description of the required
167. d on Example for versioning Link test cases to requirements Notepad generated E Notepad RTF Import 1 editable version EH Notepad RTF Import with TCs 2 1 Test Suites for V2 1 20124 4 editable version g Version 2 of T 2 Branch 3 editable version oe Notepad System amp Acceptance T Fi User documentation Figure 326 TEMPPO Administrator Locks If you select any item of the tree and press the button Find locks the corresponding locks are displayed in the table Depending on the selected item and of course the available locks the table will be quite large 01 x Database Roles Users metadata A projects B Locks License amp Demo Notepad 7 Example for versioning Demo Not Notepad 244 editable v Test Pac Find tp555 export dat 20 02 201 s cba aa Demo Not Notepad v2 44 editable v Test Pac Search F tp554 export dat 20 02 201 E Notepad RTF Import Demo Not Notepad W214 editable w Test Pac Help Syst tp55 export dat 20 02 201 1 editable version Demo Not Notepad W211 editable w Test Pac Replace tp556 export dat 20 02 201 E Notepad RTF Import with TCs Demo Not Notepad W244 editable w Test Pac Print Fun tpS61 export dat 20 02 201 i Demo Not Notepad W214 editable v Test Pac Set
168. d or test suites Frozen test structures can be exported Frozen test suites cannot be exported No import to frozen test structures test suites is possible A new test suite can only be generated from a frozen test structure in any branch version but not in the main version If a main version is frozen and activated a new test suite cannot be generated the new test suite menu item is not enabled If a branch version or latest version is frozen and activated a new test suite can be generated and the new test suite menu item is enabled If a version is checked in and is frozen no branch can be generated and therefore no new test suite can be generated The frozen test structure test suite cannot be edited There is only the possibility to generate analysis or reports and filters 5 6 Locks This tab is only active if a user with corresponding rights is connected to the database In TEMPPO Administrator it is also possible to find locks When activating the tab Locks in the left part of the windows the projects together with test structure versions and test suites are displayed Page 252 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Bj TEMPPO Administrator Testmanager loj x Database Roles Users metadata CA Projects Locks License of I Excludetest suites Suppress export locks amp Toes Tes Sv Test Site versen taba Tope vane Tet case toca Leck tcke
169. d the corresponding method is called 2 JUnit where the actual result is compared to the expected result in the test method and 3 the classes of the program under test that is executed during the test To run the tests TEMPPO provides its own TestRunner that calls the JUnit test methods and collects their results Thus for executing JUnit tests TEMPPO can be used interchangeably with other JUnit test runners like Junit swingui TestRunner TEMPPO Test Runner Call JUnit test method Return test result JUnit Framework Call method to test Return calculated value Program Under Test Note To execute the JUnit tests the classpath has to contain not only contain the JUnit test classes but also the classes of the program under test Page 271 User Manual Edition March 2014 TEMPPO V6 0 JUnit 6 5 2 Interpreting the Test Results The execution of JUnit test cases yields one of the three results listed in Table 4 In case of a failure or blockage a description of the reason and the stack trace showing the position where the failure occurred is given in the Resu t Output field in the panel General of the test case as shown in Fig 108 TEMPPO JUnit Description Result Result o m n l i The test case was executed and the actual result returned by the program under test matched the expected result as specified in the JUnit test case The test case was executed and the actual result returned by the progr
170. dation e abaua relaie Accumulate Li Lit v m T m t 20 4 Tim Settings start 09 06 2000 end 09122008 oo Figure 156 Test execution progress graph within one Test Suite 3 1 5 6 6Report Templates Some report templates are provided in your TEMPPO installation directory These are mainly templates for Test plan and Test execution report 3 1 5 7 Import from another projects You can import report settings from another project You have to press the button Import report setting from another project then the following window opens x El Demo Notepad ana a Eeport Template Figure 157 Import from other project Select a report setting and then this setting is added to the actual setting 3 1 5 8 Export to XML For exchange you can export your report settings to an XML file Press the button Export report setting to XML file and then a file dialog opens After selecting the path and file name press Save Then the file is exported to XML Page 136 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 5 9 Import from XML TRP file For importing report settings press the button Import report setting from XML or TRP file and then the following file dialog opens x Look in Ee Eigene Dateien gl ii E E KA 5 Aktien 5 Media Go TE 9 Artikel 9 My Meetings B Audi Eigene Musik CC_TestFactory 2 Eigene Bilder fm
171. directory where all the result files are stored Upload result files to DB if checked the result files will be loaded into the db if unchecked the result file are stored in the file system Error Path mandatory The directory where all error output files are stored Result Viewer optional An editor which is best suited for viewing result and output files Arguments optional Command line arguments which are valid for all test executables Contrarily individual arguments can be specified separately for each test case Note that the test executable is called with both argument strings concatenated 3 3 16 2 8 3 Universal Socket Automation Interface This interface allows test automation via a socket connection I e when starting a test execution TEMPPO will establish a local socket connection on a specified port send the path to the script to execute over this socket and read the test results from this socket Via an adapter implementation it s possible to handle the tool specific format of the delivered result output For configuration of USAI Universal Socket Automation Interface you have to activate the automation tab and select Universal Socket Page 209 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Universal Socket User Interface gt Tree Drive Letter C Test Step Cells Analysis Application Path Newsboard Test Package IP Address localhost Test Suite Database Test Aut
172. done with the TEMPPO Manager tool Database connection User management create a TEMPPO super user Database migration 4 1 Database Connection la Database Users Ai Migration OSN User documentation C Ps Databaze oracle SID Jakes schema temppo_um Host Jatinzpt ga Fort f 521 User jatw112h9 W Login manually DE Test User femppo_um Password Connect Database Mame Database Version Figure 281 Manager Database Oracle In this tab you can define various database connection configurations where each is identified by a DSN Data Source Name A new DSN can be created using theL button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the button If you delete all DSNs TEMPPO will not be able to connect to a database For each DSN you have to specify several connection parameters which are explained in the following TEMPPO supports two database management systems selectable in the field database Depending on the chosen one you must specify several connection parameters Access For Access you just simply have to specify the path to Access mdb TEMPPO automatically creates an ODBC entry Page 221 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Manager iol x Database Users uy Migratiari PENA Cerat C Pai Database Jaccess File CAProgram Fil
173. e TEMPPO is not able to verify the correctness of your document So please ensure that you ve done the correct settings and your document fulfills the needs for importing such as headings formatted with Heading 1 Heading 9 or berschrift 1 berschrift 9 in German documents and proper test step tables 3 1 2 2 5Import Test Cases from Excel TEMPPO is able to import test cases from an Excel list First you have to save your Excel file as csv and select a test package Page 26 User Manual TEMPPO V6 0 Edition March 2014 Description of Use E Import Structure From RTF Document Update From XML Document l a Export Structure From Ranorex Document fF Apply requirement updates From CSV 4 Figure 18 Menu Import Test Cases from Excel When activating the menu Test Structure gt Import Structure gt From CSV Figure 19 is displayed In that dialog you can assign Excel columns to TEMPPO attributes They are automatically selected if their names match Mandatory attributes Name and ID have to be assigned otherwise an import cannot be performed Fixed attributes like test goal state can be assigned to any Excel attributes Attribute values have to be identically If they re different the default value will be set If the owner is selected and the user is not available in TEMPPO the current importer is used as owner Test step The 3 attributes Instruction Expected Inpu
174. e main interest of the customer Therefore misbehavior is more likely to be accepted by the customer Weak interrelationship to other functionality Low test case whose main concern is testing functionality that is not frequently used or not in the main interest of the customer Therefore misbehavior is more likely to be accepted by the customer Complexity of underlying SW is small inherit attributes Page 44 User Manual TEMPPO V6 0 Edition March 2014 Description of Use You also have to specify a working or development state for the test case This is necessary for reporting analysis and creating test suites For example the test manager wants to create a test suite only with test cases that are ready for test execution If such an attribute does not exist or has a wrong value the test execution will fail The working state consists of the following values Designed The test case is created and the data in the tabs General Attributes Requirements are specified This state was introduced for the purpose of supporting test teams that separate the work into designing and implementing test cases This is the default state of a newly created test case In Work The test case already contains test steps but is not ready implemented Ready for Review This state is not obligatory it can be used for projects where test specification reviews are mandatory Ready The test case is already implemented
175. e will be visible after the next start of that application The global settings dialog can be opened via the menu Global Settings shortcut in the TEMPPO start menu Following settings are global e User Interface e Logging 3 3 16 1 1 User Interface The user interface can be configure via following settings e Font size for multi line fields e Language e Look amp Feel Page 198 User Manual TEMPPO V6 0 Edition March 2014 Description of Use me ser Interface zs ay Fell tele User Interface esses opgang General f Font size For multi line Fields Examples description instruction 1 Language Fa ie English a German Look amp Feel f Metal i CDEMotiF f Windows Windows Classic Restore Defaults Cancel Apply Figure 254 Global Settings User Interface 3 3 16 1 2 Logging You can also change the location of TEMPPO s log directory Default value is the user s profile Directory to store log files E Documents and Settings fuchscl temppoilog S Restore Defaults Cancel Apply Figure 255 Global Settings Logging 3 3 16 2 TEMPPO Test Manager Settings Specific settings e g tree display automation tools etc can be configured in the settings dialog in TEMPPO This dialog is opened via Windows gt Settings On the left side there is a tree where the user can select the setting group which Page 199 User Manual TEMPPO
176. eading numbers in your report CA TEMPPO report setting in project Demo Notepad es o lt pn i Name NewReportSetting W Generate Heading Numbers Limit depth of report Summary Options Display Number of C Test Case Test Steps Figure 142 Report General Textual Settings Continuous Report Test Package Test Case Test Case Attributes Test Result Attributes Test Step Requirements For each reported object you can define which data the report shall contain If you don t want to show Test Packages Test Cases Test Case Attributes Test Result Attributes Test Steps or Requirements click on the checkbox above the lists Multi select allows moving several values to the right part of the window Page 121 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Page 122 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Test Case Attributes Selected Attributes Milestone Add columns with popup menu in table header or Page 123 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Name NewRieportSetting pras Requirement Header Footer Text Continuous Report Test Package Eos Test Packag El Test Case L Test Case A Define the sequence and size of columns by drag d Inherited Ww ere attributes Select Requirement Structure csv Available Attributes Selected Attr
177. ecifies the text to be displayed on labels for creation progress chart Name Date Version Label Execution Progress Label Specifies the text to be displayed on labels for execution progress chart Figure 259 Settings Analysis 3 3 16 2 4 Newsboard You can configure if Newsboard window is automatically opened if a test structure is opened Page 203 User Manual TEMPPO V6 0 Edition March 2014 Description of Use _ Newsboard G User Interface Test Step Cels E Display Newsboard automatically when opening a test structure Start automatic gt QuickTest Pro gt Test Partner JUnit _ gt TEMPPO Designer IDATG Figure 260 Settings Newsboard 3 3 16 2 5 Test package You specify if user defined ID of test packages is editable User defined ID E Editable user defined ID of test package Figure 261 Settings Test package Page 204 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 16 2 6 Test suite You specify if test suites are sorted by name or date in the open dialog Test Suite Sort User Interface Tree Test Step Cells Specifies the sort criteria for test suite in the open dialog of test suites Analysis Name Date Newsboard gt Test Package i Database Test Automation Silk Test WinRunner Universal File gt Universal Socket QuickTest Pro Test Partner gt JUni
178. ed using test package categories test levels and test case attributes Specifying a logical connector in the last line can extend the expression If you have already defined a filter for your test issue you can select it and press the button Apply The filter s logical expression is applied Bj Test Suite Wizard x Steps Determine the test suite 1 Introduction Select and apply fiter or attributes values and logical operators 2 Choose creation mode 3 Select nodes or subtrees Fitter No filter v Apply 4 Enter test suite name Attribut Val 5 Determine the logical oe ama expression 6 Remove test cases manually Category Gui Layout Test AND Created lt 16 02 2012 AND Platform Windows 7 AND Regressiontest yes AND Req_State Implemented TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 67 New Logical expression When pressing Next the user can remove test cases that should not be executed Figure 68 The de selection can be realized with the lt CTRL gt and lt Shift gt keys Page 67 User Manual TEMPPO V6 0 Edition March 2014 Description of Use For default handling before V3 3 press Finish and all test cases remain in the test suite that will be displayed Bj Test Suite Wizard i x Steps Rework Test suite Introduction Select obsolete test cases hold lt STRG gt and lt Shift gt for mutti select Choose creation mode Select node
179. elect the requirement structures when the assignments should be updated By clicking Apply the test structure is checked in and then propagation is executed Ei Apply requirement updates X Apply Cancel Figure 35 Apply requirement updates All links are changed to the new version of the requirements Deleted requirements are unassigned from the test cases Updating a requirement structure does not cause that a task list is created a task list 3 3 15 is created internally if the test structure is updated to the latest requirement structure version If there is no implicit propagation to the latest requirement structure version Figure 36 is shown TEMPPO Note x Laj i l There are no newer checkeddn requirement structures versions Figure 36 No requirement structure for updating 3 1 2 4 Designing Test Cases Since there is an integration of TEMPPO Test Manager and TEMPPO Designer IDATG there are 2 possibilities for designing test cases On the one hand the traditional one with TEMPPO Test Manager and the one with TEMPPO Designer IDATG see chapter 7 The last step of the design phase is the design of test cases Note that test case design does not include the implementation writing test steps or test scripts The conceptual work of test case design has to be accomplished outside of TEMPPO E g if you apply an equivalence partitioning technique you will usually create a table with classes of i
180. emove hyperlink zE Eownaad Figure 194 Menu hyperlink For creating a hyperlink it is necessary to select at least one character in editable text fields and activate the context sensitive menu Hyperlink see Figure 194 which opens the Hyperlink window see Figure 195 E web S Fie Database URL Jett fn Figure 195 Hyperlink to the web You have the possibility to enter a link to the web specified by an HTTP address or to the file system see Figure 196 m B web File Database File C AProgram Fiesi TEMPF O 6 0qunicher properties OK Cancel Figure 196 Hyperlink to the file system In case of changing drive letters moving file shares and other similar problems it may be better to upload the files to the database For referencing an upload you have 2 possibilities you can upload a new file or use an existing one and create a reference on it The philosophy of this concept is to upload a file only once and create more references on it if necessary Page 162 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Upload Properties of launcher properties X General Eg launcher properties tl Origin C AProgram Files TEMPPO 6 OWauncher properties S Size 2 10 kByte Created 16 02 2012 17 55 04 Owner Tester References 0 Type Upload Description Figure 197 Upload properties Upload a new file You have to activate the Upload button
181. eneral Attributes Test Steps E Aitometion Requirements History Plan Execution History FH 3 Detailed description of the requir 3 2 Sequences scenarios of 3 4 Required functions of the g Datei Bearbeiten Format Ansicht 3 4 1 File Administration FA 3 4 1 1 New Strgt h Offnen Strg O Speichern Strg S D 3 4 1 1 2 New file Speichern unter 2 3 4 1 2 Open a 3 4 1 3 Save Seite einrichten 3 4 1 4 Exit Drucken Strg P 1 3 4 2 Edit Functions L 3 4 3 Print Functions Beenden 2 3 4 4 Search Functions in fi 3 4 5 Help System 2 3 5 External interfaces of the k 3 6 Other product features rec ga 4 Specifications for project manag C 5 Obligations of the client Untitled Notepad in title bar a 6 Literature i07 Annex Figure 17 Generated complete test structure Test cases were generated due to the tables in the chapters 2 1 1 1 and 2 1 1 2 The data in column Action was used for test step Instruction the data in column Output for Expected the image for column Action Image The column Comments was ignored A reference to the imported document was applied to all generated test packages which made them be displayed with the yellow folder icon This test structure can still be extended by adding more test packages or test cases if necessary For each package that is a leaf in the test structure tree at least one test case should be defined Of cours
182. epad RTF Import with TCs IT 1 Introduction 211 1 Purpose of the document General Test Packages Test Case 201 2 Validity of the documert aoe m E 1 3 Definitions of terms and abbreviati Attributes nequremems Plan Iw Inherit 2 Relationship with earlier and follow componente Components WI 3 Purpose of the product C iien 4 Delimitation and embedding of the 5 Overview of the required function Delete 6 General restrictions lt Hardware and software speciicat Product users M 3 Detailed description of the required prac JS8 210 Well SUE ES ae ap 3 1 Scope of delivery Ty Assign to all test cases 3 4 1 2 Open 3 41 3 Save J 3 4 1 4 Exit Apraly Discard G Bu G amp amp amp Figure 182 Assign to all test cases If the button Apply is pressed all common values white background color and red foreground color are set for the selected items All values that have been removed on the GUI will be removed from the selected items Changes are not applied to locked items which are displayed in a list see Figure 183 Fi Locked Items x Locked Items kaSr Mew Test Case bees Mew Test Case 1 Figure 183 Locked Items If the button Discard is pressed all changes in all tabs will be discarded Page 15 7 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 1 4 Move Ownership Now the function move ownership can be applied for any number
183. equired Ea 4 Specifications for project management a 5 Obligations of the client All 6 Literature Lae of Lock Apply Discard Figure 206 Referenced test case with Back button 3 3 2 2 Edit hyperlinks If you select a hyperlink web file system upload and activate the context sensitive menu mouse over hyperlink and choose the menu hyperlink Figure 196 is shown where you can change the e link into the web e link into the file system e upload e link for the auto tool e link with a command e link to another test case 3 3 2 3 Remove hyperlinks If you select a hyperlink web file system upload and activate the context sensitive menu mouse over hyperlink and choose the menu Remove hyperlink the hyperlink is removed But take care that an upload remains in the database To remove obsolete uploads see chapter 5 4 5 3 3 2 4 Download an upload If you select a hyperlink upload and activate the context sensitive menu mouse over hyperlink and choose the menu Download Figure 207 is shown to select a directory for the file download Page 168 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Select a destination directory x Look in B Eigene Bilder bi E E Eal KA im Media Go Desktop ini T Em Sample Pictures Faj TRrir JPG P E sseers7sa_s454620 3jpq Sl urtitied omp Pieler irna AF S96ar375a_8454628_24 3 jpg E EH cut jpg Desktop File name e
184. equirement attributes MEE Aand ni e Filter Calculate gl Chart i Data Sort Test Results alphabetical ascending C descending Values All C Only zero values C No zero values cee Figure 123 Test Suite Requirement Analysis with Attributes 3 1 5 3 Analysis by Bug ID project Consider the situation of a new version of the test object and a list of bugs are fixed in order to retest but you do not know the test cases or test structures TEMPPO Test Manager offers the possibility to load or enter a list of bug IDs and display the linked information Test structure Version Test Suite Test Case Test Case ID and Bug ID If a project is opened the corresponding analysis window can be activated and Figure 125 is displayed You have the possibility either to load a comma separated file of Bug IDs or enter them directly After pressing the button Analyse the window shows the Bug IDs together with Test structure Version Test Suite Test Case Test Case ID Page 104 User Manual TEMPPO V6 0 Edition March 2014 Description of Use rr x Bug IDs Ealnare ale O02 1003 100 Load Fil Analyse Test Structure Test Suite Testcase us simo Payee S Notepad System amp Acceptance Test W1 1 1 editable wersion Field test w01 New file opened changes bce 1 oe Notepad System amp Acceptance Test W1 1 1 editable version Field test w01 New File ope
185. equirements specification In this case you also have the possibility to split the requirement e g Search Functions into two test packages This is the suggested way to create a good test structure Test packages will keep their red color since there is no chapter that is directly related to them Page 32 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help 10 x Test Structure Notepad RTF Import with TCs System Test u i x MH WwW w E Mo fitter d Notepad RTF Import with TCs Fl 1 Introduction FA a 2 General description of the product Sao 3 Detailed description of the required prode 13 1 Scope of delivery Document C temp Pfichtenheft_Notepad_withTC rtf HO 3 2 Sequences scenarios of interactic General Attributes Details Requirements History Pian i Ea 3 3 User goals Mame Aad 3 4 Required functions of the product BP 3 4 1 File Administration Chapter 3 4 4 A 342 Edit Functions E 0 3 4 3 Print Functions are naian Sao 3 4 4 Search Functions 3 4 44 Find Precondition 3 4 4 2 Replace 3 4 5 Help System Ee 3 5 External interfaces of the product J 3 6 Other product features required FA al 4 Specifications for project management A 5 Obligations of the client Al 6 Literature i 7 Annex file t
186. er gt J Unit TEMPPO Designer IDATG Foaia Commands Office Change Management gt ClearQuest Telelogic Change JIRA Figure 277 Settings Bugzilla 3 3 16 2 13 2 IBM Rational Clearquest The following table shows the parameter matching of TEMPPO and Clearquest TEMPPO Clearquest User Repository Schema repository Page 218 User Manual TEMPPO V6 0 Edition March 2014 Description of Use ClearQuest ClearQuest URL http 192 168 146 7 Path to HTTPS Certificate Connection Test Automation Silk Test WinRunner Universal File Universal Socket tl achein gt QuickTest Pro gt Test Partner Password eeeesseesee gt JUnit gt TEMPPO Designer IDATG Ranorex Commands Office El Change Management Bugzilla gt Telelogic Change JIRA Authentication Figure 278 Settings IBM Rational Clearquest eS Rational Microsoft Internet Explorer provided by CAT Sieme ns File Edit view Favorites Tools Help Back gt x a A q Search SY Favorites g2 Address e http 192 168 146 7 cqweb login Go i gt van Please enter your User Name and Password ClearQuest Web User Name Password Schema Repository cq_aktx Database tpo user database is mov Login i ne Figure 279 Login to Clearquest 3 3 16 2 13 3 IBM Telelogic Change The following parameters have to be specified if using Telelogic Change
187. er can be set for execution progress which is applied on all selected test suites This analysis is slower because all data have to be loaded from database for filtering e Requirements only A requirement analysis of several suites over several requirement structures can be created All data will cumulated to one chart 3 1 5 5 2 1 Standard You create an analysis chart of several test suites by activating Evaluation gt Progress charts gt Execution gt Standard if at least a test structure is opened It is only possible to create a test suites chart of a single test structure When opening that analysis the chart is empty and you can select the test suites in a window that opens if you press the button Select Test Suites Possible settings e X axis Tester Test suites e Y axis Test cases Planned execution time e Group by Result If Test Suites is selected for x axis the checkbox Show O values is greyed because it makes no sense Additionally you can un display all obsolete results and plan values The following example Figure 128 shows the accumulated values of 3 test suites All 3 test suites contain 24 in sum therefore 24 test cases were planned 5 test cases were executed and 19 test cases were not executed Page 108 User Manual TEMPPO V6 0 Edition March 2014 Description of Use A Test Execution P ress Ste Test Suite Selection Test object Version XYZ RCO1 Test object Overall test suite analysis
188. ersion 1 on the main line In TEMPPO every last version gets the label latest signaling that the test structure in this version is checked out for editing The version tree can be displayed any time by selecting Test Structure gt Versions Although you never get directly in touch with the version tree during the course of test execution references to it will be made frequently in the following paragraphs This is necessary in order to illustrate as clearly as possible what is going on behind the scenes as you proceed Just For Demonstration A Edit MS VI editable version i check In Activate Tree style C Versions only Latest test structure version in the main Labels only line This version is checked out for editing i Versions and Labels ClearCase style Order f ascending i descending Close Figure 61 Initial version tree before any test execution Usually when you think of starting a new test execution you don t want all of your test cases to take part in it Some of them may not be fully worked out others may test features that are not yet available in the current version of your test object For the purpose of selecting a proper subset of your test cases TEMPPO provides the concept of test suites By means of a logical expression you can filter out the desired test cases Page 63 User Manual TEMPPO V6 0 Edition March 2014 Description of Use A new Test Sui
189. es For WinRunner SilkTest the meaning of the settings is as follows e Application Path Executable of the automation tool e Temporary Path Directory for temporary automation files created by TEMPPO during the execution of automated test cases e Result Path Directory for result files created by the automation tool The created result files are read from TEMPPO for obtaining the automation results e Result Viewer The result viewer is for opening and viewing the result files It depends on the result file format which viewer can be taken use a text editor e g notepad for WinRunner result files use QuickTest Professional Result Viewer for QuickTest use SilkTest for SilkTest result files e Arguments The automation tool is called via its command line interface This field shows the arguments which are passed to the automation tool during the call Normally the default arguments should fulfill your needs for test automation but for special cases the arguments can be adapted study the command line specification of the automation tool first For the definition of the argument you can use the parameters lt lt TestFile gt gt automation file to execute lt lt ResultBaseDir gt gt Result Path and lt lt ResultDir gt gt generated directory for results during automation Attention Not every tool supports all parameters Use the Default button to restore the default arguments If the check box in the bottom of the tab
190. es The test cases linked to the requirements are displayed as e Chart e Numbers Page 100 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Test case IDs Page 101 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Requirement Analysis xi Requirement Structures e al Bela Requirement attributes Fitter Calculate chart E Data E Detailed Data lest Cases aj Chart Stacked Horizontal Bar Chart o 1 2 3 4 5 6 7 Sort as i f alphabetical GEN FN 0030 C ascending descending GEN FN 0020 GEN FN 0030 032 Values C All GEN FN 0030 031 Only zero values GEN FN 0030 020 No zero values GEN DB GEN CD 0030 Coverage Average number of TC s per requirement 1 41 TC s GEN DI 0010 Percentage of requirements covered by TC s 70 59 Requirements GEN DI GEN CD 0020 GEN CD 0010 GEN CD GEN FN GEN FN 0030 013 GEN FN 0030 01 GEN FN 0030 011 b aee Figure 118 Planned coverage xl Requirement Structures peAa N a Requirement attributes v Filter Calculate Chart E Data E Detailed Data Pa Chart Stacked Horizontal Bar Chart Da Test Cases o 4 8 12 16 20 Sort Requirement name 1 alphabetical Requirement name 10 ascending descending Requirement name 11 Values All Only zero values Requirement name 12 Requirement name 13
191. esi TE MPF 6 0 temppo mdb SF Test User Password Connect Database Mame Database version Figure 282 Manager Database Access Oracle MS SQL Server You must specify the database name SID the schema name ask your database admin the name or IP address of the database server Host and the port number Port at which the database server is listening for incoming connections Contact your database administrator for this information The currently selected DSN is the active one i e TEMPPO uses its connection parameters to connect to a database Using button Test you can verify your settings A message will inform about the result of the verification By clicking Connect the TEMPPO Manager will establish a connection to the database user and password are required for Oracle This will cause the tabs Users and Migration getting enabled Information about the database will be displayed on the bottom of the tab 4 2 User management Fi TEMPPO Manager temppo_um l Z ioj x Database 2 Users AW migration __ lastname Firstname Login E Tester E tester2 E Testmanager temppo_um Figure 283 Manager User management This tab is only active if the test manager is connected to the database see Database Connection Users are created changed and deleted here The list shows all currently existing users Page 222 User Manual TEMPPO V6 0 Ed
192. est Case template Test Result template admin admin W C C Manager atw112h9 E m C E E E nn nn Testslavet B m mi a r r Cancel Figure 319 Project Properties Roles In the tab Roles roles can be assigned to users see Figure 319 By pressing OK the project is created Then the project can be edited and worked on in TEMPPO 5 5 2 Copying a project A new project can only be copied in TEMPPO Administrator If a project selected and the button Copy current project is pressed Figure 318 is displayed Page 246 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Copy project aos Do you really want to copy the project Demo Notepad Only the assigned meta except requirement Structures and user roles are copied Figure 320 Copy project confirmation The user is asked whether he wants to copy the current selected project including all assigned meta data except requirement structures If the user presses Yes the project including assigned users plus meta data except requirement structures is copied 5 5 3 Test case template x General Roles Test Case template Test Result template Test Case template valid only for new and updated test cases fexclusively viewed test cases Fixed attributes O ule validation Pacey Tp kd T Error C Werffication State Designed gt Mandatory fields W Precondition is mandatory M Po
193. est Repeated Negative junit tests ex Lack Epply Figure 343 Step 5 Reference to the JUnit class file Referencing the JUnit test method In addition each TEMPPO test case knows the name of its JUnit test method This information is kept in the Script Data field of the Automation panel see above The values of the JUnit class file and the test method name are editable for each test case However if you change these values TEMPPO will no longer be able to find the JUnit test method In addition the synchronization with a newer version of the JUnit class file will be considerably hampered see update function below 6 4 Update JUnit test cases JUnit test suites and their test methods evolve over time The update function makes it possible to synchronize these changes with the TEMPPO test structure contents As mentioned above the names of test packages and test cases are used as references to the corresponding JUnit suites and test methods So in order to make the update work as you would expect it do not change any of the following items Names of test packages Names of test cases a Entries in test case Automation tabs Page 265 User Manual TEMPPO V6 0 Edition March 2014 JUnit 6 4 1 Description and steps The update function allows you to update the JUnit test cases as well as their hierarchical structure in accordance with changes in the corresponding JUnit test classes There are two tasks for the
194. est results into the origin database e remove a test suite from such an export database Consider the following situation You have a test team of 2 or more testers and have a central database For test case execution it is necessary to unplug the notebook or workstation from the database LAN and execute the test cases somewhere else e g in a Car 3 1 4 7 1Export a test suite First of all you have to be connected to the central database with the TEMPPO Administrator After starting TEMPPO Test Manager you select project test structure and open the test suite containing the test cases to be executed offline Note that a set filter is concerned for export which means that only the visible test suite is exported When activating the menu item Export Test Suite the exporting process to a local MS Access database is started At first you select the directory for the export database see Figure 106 The default database name is TEMPPO_export mdb Page 93 User Manual TEMPPO V6 0 Edition March 2014 Description of Use RS r i OsCS Look in E temp Fi gt E m T o extd7680 Zuletzt atg vernendete 9 lEreg Riala ieee co reszuk Deskto E Eigene Dateien Fr a Aarbeitzplatz T File name temppo_export ma Save Peers Files of type Microsc Access Database mdi 7 Cancel i Figure 106 Save dialog If the export database already exists you get the following message Figure 107
195. est tst opened Postoondition Postcondition file testixt closed Lock Apply Discard bot Figure 26 Adding new test packages without direct relations to document chapter You can add test packages that do or don t refer to requirements in random hierarchical order It is up to you if the structure remains comprehensible When activating the tab Details a special precondition and a special postcondition for this test package may be specified This is suggested if all contained test cases have a common setup phase In the table below all preconditions and postconditions of the parent test packages are listed Page 33 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Oj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test v1 q x H gt b Hyg Mo fitter AL Notepad RTF Import with TCs Fb 4 Introduction Hh 2 General description of the product General Attributes Details Requirements History Plan EF w 3 Detailed description of the required prod 2 213 1 Scope of delivery Document C temp Pfichtenheft_Notepad_with TC rtf i E 3 2 Sequences scenarios of interactic ea 3 3 User goals Mame 3 4 Required functions of the product BP 3 4 1 File Administration Chapter 3 4 2 Edit Functions 3 4 3 Print Func
196. estcase generated gt lt if it already exists in containing test package add 1 2 gt lt ATTLIST TEST RESULT type Manual Automated Manual gt lt ATTLIST TEST RESULT tester CDATA REQUIRED gt lt ATTLIST TEST RESULT tested CDATA REQUIRED gt lt ATTLIST TEST RESULT situation Error Regular Error gt lt ATTLIST TEST RESULT val ver Validation Verification Validation gt lt ATTLIST TEST RESULT priority Top High Medium Low Top gt lt ATTLIST TEST RESULT state Designed In Work Ready for Review Ready Approved Designed gt SITATILIOT TEST RESULT Inher Pequirements true Talse Tialsen gt lt LATTLIST TEST RESULT result Failed Passed Not executed Blocked Not completed Not implemented On hold Not executed gt lt ATTLIST TEST RESULT lastupdate CDATA IMPLIED gt lt ATTLIST TEST RESULT lastupdateby CDATA IMPLIED gt lt ELEMENT REQUIREMENT DESCRIPTION gt lt ATTLIST REQUIREMENT REQUIREMENTID CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt lt ELEMENT TEST STEP RESULT INSTRUCTION INPUT EXPECTED ACTUALRESULT BUGID USR FIELD gt lt ATTLIST TEST STEP RESULT test step id CDATA REQUIRED gt lt ATTLIST TEST STEP RESULT result Failed Passed Not executed Blocked Not implemented On hold Not executed gt lt
197. et Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex El Commeands News Command i SEI El Change Management H Bugzilla H Clear Quest Telelogic Change i JIRA Arguments 2 lt TestFiles gt batch on run create_text_report on speed fast fun_minimized delete temporary test automation files Restore Defaults JK Cancel Figure 57 TEMPPO Test Automation Settings Set WinRunner mode to Verify The default mode of WinRunner is Debug which means that no log file is written TEMPPO needs a log file to parse and extract the results If no log file is written TEMPPO shows an error message C Temp TEMPPO18072005112300 db crvx asc Das System kann den angegebenen Pfad nicht finden TestPartner For specifying an automated test case it is necessary to select the tool TestPartner The text field Script Data is used for entering the script name The convention is lt script name gt lt Testpartner project name gt The text field file is obsolete Page 58 User Manual Edition March 2014 TEMPPO V6 0 Description of Use Fi TEMPPO Testmanager Demo Notepad l Oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test W1 2 General description of the product 3 Detailed description of the required product features ool 3 41 Scope of delivery Ea 3 2 Seque
198. eted and one new entry is made e g All V35 1 1 merge The tab has the following columns e Date changed on e User changed by e Property possible values Requirement UDA Test Level Steps General All if item is merged e Name Name of Property when Property is in General Steps name wv WW when Property is All name is Version of merged Item e Action possible values add change delete merge e Info additional comment for changing reason Page 46 User Manual Edition March 2014 e Version of history entry With button Display all entries all history entries of all test structures can be loaded Action is depending on Property possible values e Requirement add delete e UDA add delete e Test Level add delete e Steps add change delete e General change Info Name User defined ID or Test goal e All merge 2 TEMPPO V6 0 Description of Use Project Test Structure Edit Test Execution Evaluation Tools Windows Help gt Tes ucture Notepad RTF Im Kapp SX No fiter E Notepad RTF Import with TCs H 1 Introduction 2 TEMPPO Designer IDATG Tas fff 2 4 Use case File gt New ca 3 General description of the produc E 3 1 Relationship with existing pi eE 3 2 Relationship with earfer anc Zi 3 3 Purpose of the product iJ 3 4 Delimitation and embedding Zl 3 5 Overview of the required fu E 3 6 General restriction
199. ew customer account 2 a single well delineated test goal e g create a new customer account in the data base 3 a sequence of test steps e g 1 Log in 2 Open customer creation dialog consisting of instruction input data and expected result Additionally attributes may be defined for test cases like 1 test situation does it test a normal operation or an error condition 2 state is the test case still in work or ready for execution 3 priority how important is it to execute this test case before the product is released 4 type manual i e test steps have to be performed by a human operator or automated Page 9 User Manual TEMPPO V6 0 Edition March 2014 Introduction The Test Process All testing activities deal with planning designing implementing executing and managing a sometimes quite big amount of test cases TEMPPO supports a well defined approach to these activities We can distinguish five phases in the test process Test structure Engineering Analysis y Prioritize TEMPPO Evaluation TEMPPO TEMPPO Requirement Analysis amp Wanaaer Reports Test Manager Designer Engineering g Elicitate Implement Specify Test cases Engineering Baseline View b n Design Engineering Execute Import Update Test results Bug entry Bug ID Test cases Test cases equirements impor update Change ffline T Management Management paren a external
200. ext field together with the button There you can enter e A string with a wild card or e Press the button for selecting several values After pressing the button Figure 236 is displayed and the attribute values are selected by moving them to the right Pressing OK applies the selection to the filter window The selected values are displayed separated by a comma Now the user can edit this line Because the comma is used to separate the selected values commas in the selected values have to be escaped with a WY e g Component 3 No blank is allowed commas has to be escaped with a A Build In Clause r LA Filter Properties 28 Name New Fiter rConditions Attribute Value Miestne v OIN Y MN2M1 3 M3 ao y X se v Y v v gt x lt M estone IN M1 2 M1 3 M3 AND Hide Empty Subtrees Attribute Valu Value Wild S e card set allowed 3 Yes if operators IN NOT IN are selected Yes if a set of values can be selected Yes if editable is Yes Fixed Situation Test Case Type Additional Test Level Type Fixed Il Test Level Test Category Requirement Fixed Ill Priority State Page 186 User Manual TEMPPO V6 0 Edition March 2014 Description of Use pugiD yy Nyy yw Test Y N result Created Y N Y N N Y Updated Require Y Y N Y Y Y Y N ment Table 2 At
201. face H Tree Application Path C Program Files x86 HP QuickTest Professional bin QTPro exe Test Step Cells Analysis Temporary Path C temp Newsboard Test Package Test Suite Database Test Automation Result Viewer C Program Files x86 HP Run Results Viewer bin reportviewer exe Silk Test WinRunner Arguments wscript lt lt TestFile gt gt Universal File Universal Socket Test Partner JUnit TEMPPO Designer IDATG Ranorex Commands Change Management Result Path C temp New Folder delete temporary test automation files Restore Defauits ox canca Figure 267 Settings QuickTest Pro TEMPPO uses the data table iterations from the QTP test case Page 211 User Manual TEMPPO V6 0 Edition March 2014 Description of Use x Run Data Table iterations Run one iteration only gt Run on all rows f Run from row 2 to row E Recover Local System Monitor i Log Tracking When enor occurs during min session pop up message box Object synchronization timeout 20 seconds Disable Smart Identification during the run session Save image of desktop when error occurs if test is run by the HP Business Process Morutor OF Cancel Apply Help Figure 268 QTP Run Settings 3 3 16 2 8 5 TestPartner TestPartner requires NET Framework 2 0 For Compuware TestPartner you have to activate the automation tab and select
202. fic subset of your test cases for test execution 2 verify the test goals or end of test criteria For this purpose a test case in TEMPPO can have several attributes which enable flexible filtering and the creation of analysis charts and reports under specific aspects And you should check during the test design phase whether the attributes provided by default are sufficient Otherwise you would define additional ones such that your needs will be fulfilled Test design Test design is either done with TEMPPO Designer available as Add on please refer to chapter 3 3 16 2 10 or with TEMPPO Test Manager With TEMPPO Test Manager you will think about organizing your future test cases in some way Since a simple list of dozens of items is not easy to survey a hierarchical grouping of test cases seems adequate TEMPPO supplies the concept of test packages which may contain test cases or for building up hierarchical structures again test packages The whole tree of test packages and test cases is called test structure According to the various implementation levels during a development process from coding the components and assembling them integration to completing the system the test process has various test levels where you may test the stand alone components module test the growing application integration test and finally the complete system system test Furthermore your customer might execute an acceptance test for verifying w
203. g the Test Structure Extending the Test Structure adding more test packages Designing Test Cases test case design Page 14 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 2 1 Working with Projects A project is the starting point in TEMPPO and contains one or more test structures You can either start by creating a new project or opening an existing one Deleting a project can only be done with the TEMPPO Administrator see 5 If you are an advanced user you can skip this step and directly choose a previously opened test structure in the Test Structure menu see 3 1 2 2 3 3 1 2 1 1Creating a Project A new project can only be created in TEMPPO Administrator Log on to TEMPPO Administrator and choose the tab Projects Then press the button New Figure 2 is displayed Project properties contains 4 tabs General Roles Test Case Template Test Result Template In the tab General user specifies a unique name description and the possibility to determine if the testers have to add a mandatory comment for each Save operation of a test case In the tab Roles the test manager configures the roles for each tester If a user has no role in a project he won t see it In the tab Test Case Template the test manager appoints defines a basic test case He can configure standard attributes define mandatory attributes or determines if a test case has to be at least one link to a requi
204. ge field If it s 1 its ignored Maximum height thumbnail of a user defined image field If it s 1 its ignored Test Step Cells Multiline table V On off for refreshing the cell content when changing the column width 52 Height of multiline rows during editing default is 52 Test Package Test Suite Image columns Database Test Automation 1 Maximum width of thumbnai of a user defined image field If it s 1 it s ignored H Sik Test WinRunner 100 Maximum height of thumbnai of a user defined image field If it s 1 it s ignrored Universal File gt Universal Socket QuickTest Pro Test Partner JUnit gt TEMPPO Designer IDATG Ranorex Commands Change Management Restore Defaults Lok _Cancet_ Figure 258 Settings Test Step Cells 3 3 16 2 3 Analysis You can change the settings for analysis value different colors Label length for progress 100 Limits the label length of the chart requirement names in order to keep the chart readable Creation Progress Label Version Specifies the text to be displayed on creation progress chart labels Execution Progress Label Date Specifies the text to be displayed on execution progress chart labels Page 202 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Analysis Color settings Color settings for analysis Normal Siightiy Progress charts Label length for progress charts 100 Creation Progress Label Sp
205. ger Demo Notepad IOl x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version 2 ROOT v1 1 1 imj X H 4b WH E Mo fitter i Test object version xY Fuco a 3 Detailed description of the required g Elia 3 4 Required functions of the prod Requirements History Attributes TR Previous Resuts Plan Execution History A 3 4 1 File Administration General Attributes Test Steps Automation BAN 3 441 New A 34111 New efi Ey ed Search FUncHORS File Mew pick Message gt save Unbenannt Ed 5 changes Al z Find g Datei Bearbeiten 3 4414 Find up 34441414 Cases G 3 4 44 4 2 WinPur 3 4 4 1 1 3 QuickT E 34 4144 Test Pe Speichern unter Fl 3 4 41 1 5 UA no gt ffnen Speichern RTF Import with Tos duction eral description of the product ied description of the required product features scope of delivery sequences cenarios of interactions with thi User goals Required functions of the product 3 4 1 File Administration A 3 4 1 1 New fil 3 4 1 1 1 New file opened no change 3411 2 New file opened changes E 3 41 2 Open E 3 41 3 Save offnen E 3 41 4 Exit Speichern 3 4 2 Edt Functions 3 4 3 Print Functions 3 4 4 Search Functions soot E E EP Merge Lock Apply Discard Sq Datei Bearbeiten Format Tz Figure 101 Editing test cases during test case execution But remem
206. ger Testmanager Testmanager 15 02 2012 11 24 15 13 02 2012 16 50 26 14 02 2012 09 34 44 14 02 2012 14 54 30 14 02 2012 11 13 39 13 02 2012 17 05 45 14 02 2012 10 32 11 14 02 2012 09 20 13 14 02 2012 09 20 49 14 02 2012 09 19 32 Manual Manual Manual IEM RequisttePro Manual Manual Manual Manual Manual Manual Figure 311 Metadata Requirement Structures Test Levels Test Categories Attributes Uploads Requirement Structures J User Fields f x a show requirement attrintes __ Components Testmanager S Learning Project Use Cases 1 Figure 312 Show requirement attributes Testmanager Testmanager Testmanager 16 02 2012 11 2415 13 02 2012 16 50 26 a 14 02 2012 09 34 44 14 02 2012 14 54 30 Manual Manual Manual IBM Requisite Pro With the button Show requirement attributes the assigned attributes are shown in a new window see Figure 313 It s only possible to un assign attributes when the requirement structure is not imported Page 242 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fj Meta Data Editor Ea Attributes Requirement Selected values h Attribut Find I Available values Figure 313 Requirement attributes With a double click on an attribute tab attributes the properties of the attribute are shown see Figure 314 It s not possible to change the requirement attribute because it s impo
207. gt X OBA RBBIGRIFH AaB FI MEGO Bias 0 F KU E SS ROY FA B a ta ua a D BS ib D Fj y P4 Bearbeitung zur cksenden Bearbeitung beenden l Al v f eee ee eee vz 3 Name of Test Structure Systemtest i i 4 Owner nn i i 5 Description i 6 Updator i Updated i i Details New Test Package 10 Owner nni i i 11 Description i 12 Test Category i i 13 Path Systemtest New Test Package 14 Created 10 06 2008 15 33 49 15 Document Name i i 16 Document Chapter H i Updator nn1 i 18 Updated 10 06 2008 15 33 49 19 Precondition i i F New Test Case 21 Test Goal i i Path Systemtest New Test Package New Test Case 23 Created 10 06 2008 15 33 49 i i 24 ID tc12383 25 Priority Top i i 26 Situation Regular Test Case Type Validation i 28 State Designed i i 29 Type manual i i 30 Updator nni 31 Updated 10 06 2008 15 33 49 32 Precondition i i 3A Tast Stane H M 4 gt bi Temppo_Reporting lal gt f Bereit NF Figure 153 Report Excel Page 133 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 5 6 5Sample Charts Test case creation progress test structure Graphical settings Y axis Sum of test cases X axis Created Group by State Date Unit 1 Month Accumulate Data yes Display data absolute Chart Selection 3D Stacked Bar Chart Bi chert EE Data
208. gt lt if it does not exist it will be automatically created gt lt ATTLIST USER DEFINED ATTRIBUTE value CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt 13 2 DTD Schema for XML Import Test Suite lt ELEMENT TEMPPO EXCHANGE PROJECT TS EXPORT ID TEST SUITE gt lt Common PCDATA elements gt lt ELEMENT DESCRIPTION PCDATA gt lt ELEMENT PRECONDITION PCDATA gt lt ELEMENT POSTCONDITION PCDATA gt lt ELEMENT TESTGOAL PCDATA gt lt ELEMENT RESULTOUTPUT PCDATA gt lt ELEMENT INSTRUCTION PCDATA gt lt ELEMENT INPUT PCDATA gt lt ELEMENT EXPECTED PCDATA gt lt ELEMENT ACTUALRESULT PCDATA gt lt ELEMENT BUGID PCDATA gt lt ELEMENT VALUE PCDATA gt lt ELEMENT PROJECT DESCRIPTION gt lt ATTLIST PROJECT name CDATA REQUIRED gt lt ELEMENT TS DESCRIPTION gt lt ATTLIST TS name CDATA REQUIRED gt lt ATTLIST TS test level CDATA IMPLIED gt lt if it does not exist autom create Page 289 User Manual TEMPPO V6 0 Edition March 2014 Appendix lt ATTLIST TS version CDATA IMPLIED gt lt ATTLIST TS lastupdate CDATA IMPLIED gt lt ATTLIST TS lastupdateby CDATA IMPLIED gt lt ELEMENT EXPORT ID EMPTY gt lt ATTLIST EXPORT ID value CDATA REQUIRED gt lt ELEMENT TEST SUITE DESCRIPTION TP USER DEFINED
209. h 2014 Description of Use Figure 133 Select test suites Additionally you have to select the requirement structures by pressing the button Select Structures LA Select Requirement Structure Components Tesimana 16 02 2012 11 2 Manual Pe Learning Project Use C 14 02 2012 14 5 IBM Requisit 14 02 2012 11 1 Manual Notepad Tesimana 13 02 2012 17 0 Manual Figure 134 Select requirement structures Each time you change anything on test suites or requirement structure selection button Refresh get enabled If you press button Refresh chart is refreshed Test Suites Select Test Suites New Test Suite V6 1 1 Regressiontest Test Obeject 1 123 beta W8 1 1 Requirement Structures Components Notepad Fune reg22 Fune reg23 Fune reg26 Fung regq2 Fung reg28 Func rego Fung reg30 Fune regal 2 Fune regqa2 Al Fung rega3 Func_reqa I Only zero values Fune_rega No zero values Fune regq45 i reqhes reg Refresh req 85 requeay Mfailed E passed Mnotexecuted Bblocked Mnot completed Hnotimplemented Mon hold wn a E a a a E Figure 135 Requirement analysis over several test suites Chart Tab chart The following chart types are available e Horizontal bar chart e Horizontal bar chart 3D e Stacked horizontal bar chart e Stacked horizontal bar chart 3D All test cases of the selected test suites with links to the selected requirement structures are
210. h test step and for each automated test case too The bug ID would point to a problem report in a bug tracking tool like Bugzilla IBM Telelogic Change IBM Rational Clearquest or JIRA Before you can generate a bug automatically you have to configure the corresponding settings in TEMPPO settings Change Management El User Interface Tree Test Step Cells Bugzilla gt Analysis gt Newsboard Test Suite Clear Quest Database JIRA Test Automation Silk Test gt in Runner Universal File Universal Socket Active Change Management Tool Telelogic Change QuickTest Pro gt Test Partner JUnit gt SITEMPPO Designer IDATG Ranorex Commands New Command Java32 Change Managemen _ ar anagemerit H Bugzilla Clear Quest Telelogic Change JIRA Restore Defaults oo Cancel Figure 92 TEMPPO settings For creating a new bug select the corresponding cell bug ID step and press the button Create a new bug entry see Figure 93 Page 83 TEMPPO V6 0 User Manual Description of Use Edition March 2014 General Attributes Test steps Ei Actometion Requirements History Attributes TR Previous Results Plan Precondition Select the Lser detine attribute in the combobox Attribute im select the 222 NOT IM operator Push the button right beside the wale field sele
211. he command line parameters o myResults res e myErrors err Additionally each script should take some individual parameters Assume test_case bat corresponds to a TEMPPO test case and should be started with individual parameters f i like this test case bat f i fo myResults res e myErrors err Page 61 User Manual TEMPPO V6 0 Edition March 2014 Description of Use In this case the user specifies the general settings for all test cases in the TEMPPO Test Manager Settings Arguments o lt lt ResultFile gt gt e lt lt ErrorFile gt gt and the individual settings in the TEMPPO test case automation tab File temppo test case bat Additional Arguments acy ea If we assume a drive letter setting U the preview window shows a full command line like this U temppo test case bat f i o lt lt ResultFile gt gt e lt lt ErrorFile gt gt where lt lt ResultFile gt gt and lt lt ErrorFile gt gt will be replaced with generated file names including the paths specified in the Administrator at execution time For example lt lt ResultFile gt gt will be replaced with C Documents and Settings atwlt5q2 Result 20021202 1723 test_ case out 3 1 3 2 Reworking the Test Structure Possibly you will have to rework your test structure after a review or due to changes of the software under test Editing of the test structure is supported by the Cut Copy Paste functionality Edit gt Cut Copy Paste
212. hether the delivered product agrees with the ordered features You have to decide how many test structures you want to build one for all test levels or different ones for different test levels Especially for the system test it is highly recommended to build a test structure that closely resembles the structure of chapters in your requirement specification For that sake TEMPPO Supports the automatic creation of test structures out of RTF formatted text documents Now that you have prepared everything to organize and execute test cases you are ready to start with their design During test case design only test case Page 11 User Manual TEMPPO V6 0 Edition March 2014 Introduction names test goals and the links to the requirements are fixed This is useful because you will quickly get an overview of the number of test cases and their distribution to test packages And it is still early enough to set corrective measures if e g the number of planned test cases turns out to be way too high or even too low For a high rate of error finding it s suggested to make use of well tried test case design methods like Equivalence Class Partitioning or Boundary Value Analysis for details refer to 2 Test Case Implementation In this phase three main tasks have to be accomplished i writing manual test cases test step definition ii writing automated test cases test script programming iii implementing test frameworks Only the first
213. i Li Mew Ca Open K 4 gt mM 8 Reopen M Test onec version ae ay nies a 3 Detailed descripti EHA 3 4 Required ful Run automated Al Attributes Details Requirements History Plan Set Pesut ID ipsso F Export Test Suite F 2 3 Import Test Suite Mame Fina up Ela 3 4 4 1 BRE Find locks fi 344144 Cases Created 15 02 201217 0 Updated 16 02 2012 13 2 EE 3 4 4 1 4 2 WinRur BD 3 4 4 1 1 3 QuickT of 3 4 4 1 14 Test Pe Number of TCs 46 EJ 3 4 4 1 1 5 UA no Test Category Description Lock Apply Discard Cwner Testmanager Updator Testmanager Type Test Package Figure 98 Automated Test Execution 3 1 4 1 11 Mixed Test Execution A mixed test suite contains both manual and automated test cases The test execution doesn t differ from the one described above but is just a mixture of them If a test package contains both manual and automated test cases and Run automated is invoked on it only the automated test cases will be executed All manual test cases in this test package must be carried out afterwards 3 1 4 1 12 Setting several results For regression testing it is often convenient to set results for several test cases at once e g if you already know the results of the test cases First you have to select a Sub tree in the test suite and then activate the context menu Set result s and afterwards Figure 99 is shown You can choose
214. ial color grey background color New requirements are displayed in red color If you want to assign such a requirement to all selected TPs select it and activate the context menu S Such requirements or new displayed in red color The tab Inherited Requirements displays the common state of selected TPs which inherit their requirements Requirements assigned to all selected TPs are displayed as usual in white background color Requirements assigned to not all TPs are displayed in a special color grey background color Of course it is not possible to edit anything here The tab Inheritance displays the COMMON birectinkea Requirements inneried Requirements Inhertance Direct inked Requirements Requirement is assigned to all selected items Requirement ID Requirement Name req685 ComponentA R2 a req686 ComponentB R1 req687 Componente R3 ih linked requirements are Inherited Requirements Legend Inheritance Requirement is assigned to all selected items Requirement ID Requirement Name E req683 ComponentA R3 req684 ComponentAR1 x req685 _ComponentA R2 Te state of the inheritance flag of the selected TPs If the checkbox is not activated Notinherited all selected TPs do not have any inherited requirements If the checkbox is activated merta all selected TPs have at least one inherited requirement If the check
215. ibutes Eoo Figure 143 Report Textual Settings Tabular Report Test Package Test Case with its attributes Requirements and Test Step If you don t want to show Test Packages Test Cases Test Steps click on the checkbox above the table Multi select allows moving several values to the right part of the window For unselecting a column double click on it or open context menu and press remove Additionally you can define the sequence of columns by swapping the column headers and for defining the width of columns in the report you have to move the border of columns For each requirement structure the attributes can be reported selectively If you do not want to report requirement attributes in general right click on header and deselect Requirement attributes Page 124 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Test Package Attributes Test Package Attributes Selected Attributes b 4 4 Test Case Selected Attributes ID Name Owner Test Case Attributes Test Case Attributes Page 125 User Manual Edition March 2014 TEMPPO V6 0 Description of Use DA TEMPPO report setting in project New Project Define the sequence and size of columns by dragging in table header Requirement attributes Selected Attributes Figure 144 Tabular Report Page 126
216. ing tab Roles the predefined TEMPPO roles are listed On the one hand roles can be edited or adapted and on the other side new roles can be created Page 227 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi TEMPPO Administrator Testmanager O x Database S Roles E Users a Metadata LA Projects Lacks E License D E X TEMPP Editor schema Owner 13 02 2012 13 04 02 TEMPP Guest schema Owner 13 02 2012 13 04 06 TEMPPO Key Tester schema Owner 13 02 2012 13 04 04 TEMPPO Key User schema Owner 13 02 2012 13 04 00 ia TEMPPO Reporter Schema Owner 13 02 2012 13 04 01 TEMPPO Requirement Editar schema Owner 13 02 2012 13 04 03 T TEMPPO Superuser schema Owner 13 02 2012 13 03 59 TEMPPO Tester schema Owner 13 02 2012 13 04 06 Figure 290 Roles Adding editing and deleting are allowed In the tab General you can fill in the name and description or change the icon In the tab Details the rights are listed Fi Role properties x General Details B TEMPPO Key Tester Created 13 02 2012 13 04 04 Creator Schema Owner Type Role Change icon 16x16 Pixel Description eves Fi Role properties xj General Details Update 4 Test package Assign test categories Edit ad 5 Link requirements Merge Test case Assign test case attributes Assign test levels Edit Link requirements OOoOogd T r r r r r r r Cancel Page 228 User
217. ioj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Hewsboard Notepad RTF Import with Tes vWa i E x Updated 20 02 2012 10 56 58 Changed since last login 20 02 2012 E h 00 24 f min 00 59 fa Apply Notepad RTF Import with TCs v3 General Changed Test Package File Administration 20 02 2012 102659 Testmanager Testeri Changed Test Package Mew 20 02 202104656 amp Testmanager Testeri Changed Test Case Mew file opened no changes 20 02 202103018 amp Testmanager Testeri Changed Test Case New file opened changes 20 02 2012 105304 Testmanager Testeri Changed Test Package General description of the product 16 02 2012 18 00 46 Testeri E Testmanager Changed Test Package Windows Login 20 02 202102613 FF Testmanager E Testmanager Changed Test Case Login 20 02 2012 10 56 57 amp Testmanager E Testmanager Changed Test Case Case sensitive 20 02 2012 1053 05 Testmanager E Testmanager Changed Test Package Find up 20 02 2012 10 53 05 amp Testmanager E Testmanager Test Package Windows Login 20 02 2012 10 25 59 FF Testmanager E Testmanager Test Case Login 20 02 2012 102612 Testmanager E Testmanager Page 174 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Ei TEMPPO Testmanager Demo Notepad i ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows He
218. ion March 2014 TEMPPO Administrator A frozen test structure cannot be edited any more It can be opened in read only mode A freeze action on a non latest version means that it is not possible to create any branches If a test suite is selected and the freeze button is pressed this test suite is frozen which means that the test suite is not editable any more No results can be added or changed The test suite can be opened in read only mode The precondition of freezing a test suite is that the corresponding test structure version is frozen Every frozen test suite can be unfrozen explicitly This means that the frozen test Suite is selected and the unfreeze button is clicked After the unfreeze action is done the test suite is editable again Every frozen test suite can be unfrozen implicitly too This means that the test structure version has to be unfrozen first If the user pressed the unfreeze button for a test structure version he is informed if there are frozen test suites and that these frozen test suites and the test structure version will be unfrozen too The user can unfreeze all or cancel the action If a frozen test structure or test suite is selected the freeze button changes its text in icon and bubble help to unfreeze By pressing the button the test structure or test suite can be made editable The default TEMPPO Superuser and the Key User role get the rights to freeze unfreeze test structure versions an
219. ion effort for all test cases see Figure 44 Page 48 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad E ol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Motepad RTF Import with TCs System Test 41 HM d gt b W GP EE monter ake na 1 Introduction Locked by Testmanager H 2 General description of the product General Plan Requirements 3 Detailed description of the required product f 0 3 1 Scope of delivery Ea 3 2 Sequences Scenarios of interactions fea 3 3 User goals Planned test execution time 3 h 30 min 0 59 Sao 3 4 Required functions of the product EP 3 41 File Administration EM 3 444 New 2 3 fi 3 4 1 1 1 Mew ile opened no fi 3 4 1 4 2 Nev file opened ch Gd 3 4 1 2 Open LI 3 4 1 3 Save ob bli 414 Exit 3 4 2 Edt Functions AF i F HE 3 4 3 Print Functions ER seal D Figure 44 Planned execution time for whole test structure Additionally the designer enters a Planned tester for each test case who is planned to execute it For Analysis of test structure Planned Tester is available to view whereas the analysis of different Test execution efforts makes no sense Test Cases NN 1 NN Schlosser Dietmar Planned tester Figure 45 Chart Planned Tester Planned test execution time and Planned Tester can also be used for test st
220. ion to the standard attributes owner creation date priority and working state Such attributes like working state tester sample phase etc help the test manager to realize his objectives of the test plan Therefore it should be planned before creating a test structure or a test execution which attributes are used Especially for pursuing the test objectives it is important to define these attributes in TEMPPO During the test process you may be asked always the same questions like Page 237 TEMPPO V6 0 TEMPPO Administrator User Manual Edition March 2014 How is the progress of test case development in comparison to the last day week month How many test cases are ready for test execution How many test cases are ready for regression testing How many test cases of the current test suite are passed failed Besides test case attributes you can assign attributes to test suites and test case results too These attributes can be used for different issues E g during test case execution the version of the SUT software under test sometimes changes But the test manager wants to know which test cases were executed with which SUT version or which SUT versions are used in the test suite Moreover predefined attributes provides the users from making mistakes when writing the necessary information Attributes are also used for filtering analyzing and reporting the test structure or the test suite Fi TEMP
221. ionally the paragraph after the heading which Should become a test case must contain a test step table This table must contain columns which describe instruction input and expected output of test steps These columns may have arbitrary headers like Action for the instruction see Figure 16 Furthermore you can suppress the generation of empty test steps in case of empty table rows by checking ignore empty table rows The hierarchical position of the test case in the test structure will correspond to the heading level in the document e Import test goal Enabled if checkbox Generate test cases is checked If checked all the text after the heading until the next heading will be imported to the test case s Test goal e User defined test step columns Since TEMPPO offers not only the 3 Standard columns user can define additional columns that are also used for import Importing the document displayed in Figure 15 with settings displayed in Figure 16 will generate the test structure displayed in Figure 17 Page 25 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Please consider that importing is applied on the selected test package 10 x Project Test Structure Edit Test Execution Evaluation Tools Windows Help z Test Structure Notepad RTF Import with TCs System Test V1 M 4D N s non Notepad RTF Import with TCs H 1 Introduction E 2 General description of the produ G
222. ish Cancel Figure 333 General description of the following steps In the next step the JUnit test class can be selected All classes with names that start with All Tests are shown with a folder icon all other classes get a sheet icon This is in conformance with the TestRunner of the original JUnit distribution The icons are to some extent misleading because they suggest that only test classes with folder icons will be converted to TEMPPO test packages However each class that can be selected in this step will be converted to a potentially hierarchically structured test package Page 259 User Manual TEMPPO V6 0 Edition March 2014 JUnit F Import JUnit Tests i X Steps Test Class Selection _ Introduction Select the JUnit test class to be imported Z Select a JUnit test class 3 Select a set of JUnit test saeu rls West ers a 4 Set package default values A 5 Setted egsa detaultysiies 4 ActiveTestTest junit tests extensions L 6 Summar AllMembers Supplier Test org junit tests experimental theories D AllTests junit tests extensions E AllTests org junit tests L AlTests junit tests AllTests junit tests runner L AlTests junit samples T Alitests junit tests framework JUnit Classpath p ATemp_PVAtTeststellung PYAyunitd Mote Only classes that are inthe JUnit classpath can be selected Finish TEMPPO Extension JUnit zz Prey
223. it 3 4 2 Edit Functions 3 4 3 Print Functions Fp E 3 4 4 Search Functions a 3 4 5 Help System Figure 203 Source test case Then click right mouse button for context menu select Hyperlink and select the test case AA x web S Fie Database E Commana EA Manual Test Case o User goals Ea Required functions of the product O EE File Administration i E ad Windows Login i Login E E New E Open E Save Cancel Figure 204 Select test case After pressing the OK button the selected test case is displayed by its ID when moving the mouse over the hyperlink Page 166 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test is H 4 WH E No fitter d Notepad RTF Import with TCs B04 Introduction E 2 General description of the product 5 rA 3 Detailed BESCHElOn of the required product m 3 2 Sequences scenarios of interactions Pr 93 3 User goals Login a ra 3 4 Required functions of the product 21 H 3 41 File Administration H a 3 4 1 1 Windows Login 2 File Mew pick Editor Pane cleared hi 3414141 Login Se 3 Untitled Notepad in title bar aasa New a 344 22 Mew aE aene gh BA 3 4 1 2 3 New Test Package c 3413 Open i 3 4 14 Save 3 4 4 5 Ext E E 3
224. it for an answer on a ping heart beat e Ping repeats Number of pings heart beats sent to TEMPPO Designer IDATG 3 3 16 2 11 Ranorex e Result path Path to directory of the result file s e Result viewer Application to open result file s Page 214 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Ranorex User Interface Tree Test Step Cells gt Analysis gt Newsboard gt Test Package Test Suite Database Result Viewer Result Path C Documents and Settings atw10905 Test Automation gt Silk Test WinRunner Universal File Universal Socket QuickTest Pro Test Partner gt JUnit gt TEMPPO Designer IDATG gg Ranorex Commands Change Management gt Bugzilla gt ClearQuest Telelogic Change JIRA Figure 273 Settings Ranorex 3 3 16 2 12 Commands Commands are used for hyperlinks with parameters By pressing the New Command on the right side you can create a new command see Figure 274 Then a new tree node is created with the new command see Figure 275 A command is defined by its name path and arguments The name has to be unique Page 215 User Manual TEMPPO V6 0 Edition March 2014 Description of Use TEMPPO Designer IDATG fa Commands Restore Defaults Figure 274 Settings Command TEMPPO Designer IDATG Commands Restore Defaults ok cano Figure 275 New Comm
225. ition March 2014 TEMPPO Manager User management in TEMPPO Manager is used to create the first super user who has afterwards the rights to do all the administrative work in TEMPPO Administrator without any database password SQLSERVER if a superuser is created the following procedure has to be executed via a console or EnterpriseManager by an sysadmin exec sp_addsrvrolemember N sid N sysadmin The first step is to create a Super user that can either be with MS Window login or a self created one with password It is not allowed to start TEMPPO twice with the same login This could cause inconsistencies in the database 4 2 1 MS Window login For creating a super user with MS Windows login you have to connect to the database without activating the checkbox Login manually Fi TEMPPO Manager temppo_um Ioj x 1 Database E Users aie Migration Schema ftemppo_um Host fatinzp 0ga Port f 521 User fatw112p9 B Login manually F Test User jtemppo_um Password ge Disconnect Database Mame Oracle Database Version Oracle Database 10g Enterprise Edition Release 10 2 0 5 0 Production With the Partitioning OLAF Data Mining and Real Application Testing options Figure 284 DB connect to create MS Window Login When pressing the button Connect Figure 283 is displayed A new super user can be created by clicking the button Create new user The inpu
226. ity is divided into four main setting areas where each of them again is subdivided into several parts The areas are described in the following chapters 3 1 5 6 1 1 General In the general settings area you define the rough layout and contents of your report Components Here you choose the components your report shall contain Dependent on your selection the tree is changed for doing the relevant settings The following components are available Title Page General Information about Test Structure Text Charts Progress Chart Additionally you have to select the layout Continuous or Tabular and the Format for the report HTML Microsoft Word or Microsoft Excel Page 118 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 4 TEMPPO report setting in project New Project Name NewReportSetting E Settings eh Text E Title Page l Continuous Report Test Package L General Information of Test Structure o Test Case A Requirement E Chart Layout Format HTML Microsoft Word Figure 140 Reporting General If Microsoft Excel is selected then you can define a header and a footer within the settings If HTML is selected reports know from prior TEMPPO versions 5 6 or lower can be saved Please consider that Microsoft Word limits the width of pages to 22 inches http support microsoft com scid kb 3Ben us 3B95109 amp x 14 amp y 10 Title Page You can cust
227. ive e g 10 7 03 Delimiter Specifies the delimiter for order numbers e g delimiter in 10 7 3 is Specifies the base for order numbers i e the number added to the internal order which is 0 based User Interface Tree Test Step Cells Save changes automatically suppress confirmation dialog Automatic save H Test Package Test Suite Database Test Automation Sik Test Delimiter for numbering e g gt WinRunner Universal File 1 Defines where numbering starts Universal Socket gt QuickTest Pro gt Test Partner gt JUnit gt TEMPPO Designer IDATG Ranorex V On off for recursive numbering g 1 2 3 Commands Change Management gt Bugzilla ClearQuest Telelogic Change JIRA Restore Defauits ok _ _cancet_ Figure 257 Settings Tree 3 3 16 2 2 Test Step Cells For the test step cells some settings can be changed see Figure 258 Property Default Description value Refresh when resizing activated Switches on off refreshing the row heights in a multi line table when changing column widths or table bounds Multiline height sets the minimum height of the edited row in pixels in a multi line table Page 201 User Manual TEMPPO V6 0 Edition March 2014 Description of Use You cannot set the number of lines for the test step editor but the pixels 52 pixel correspond to 3 lines Maximum width of thumbnail of a user defined ima
228. kbox LDAP a field for configuring LDAP connections is shown see Figure 244 After a successful connect you can import users from a LDAP server or you can synchronize the existing TEMPPO users with the LDAP server For imported users you can see the LDAP server from which the user was imported If a user was created manually the value in the column LDAP server is not set Page 230 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator 5 3 1 1 LDAP Connection io x Database Poles Users a Metadata LA Projects E Lacks E License C i IY LDAP Testeri tester testers tester4 testers tester Aana eS es Connect ta LOAF Server DSN atos C ri Host scalidap atos net Port fes Base User DomaimUser wg a0atw 129 Fazsword E onnect HE Import users E Synchronize Usera Figure 294 Connection to the LDAP server You can define various LDAP connection configurations where each is identified by a DSN Data Source Name A new DSN can be created using the L button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the tt button For each DSN you have to specify several connection parameters which are explained in the following You must specify the name of the server Host the port number Port the domain name Base and the user data User and Password to connect to the LDAP serve
229. king OK Figure 6 is shown The test structure is opened in the main window In the title bar of the test structure its name test level and version are displayed In the left pane an empty tree is displayed and in the right part the test structure properties are documented Page 17 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Testmanager Demo Notepad E me x Project Test Structure Edt Test Execution Ewaluation Tools windows Help Test Structure Notepad System amp Acceptance Test System Test Ma i m x H gt b Hg E Mo fitter iotepad System amp Acceptance Test General Plan Requirements Name Notepac System amp Acceptance Test Owner Testmanager Updator Created 15 02 2012 13 26 40 Updated Type Test Structure TEMPPO Designer DATE O Test level System Test Description This tast structure is used for Lock Apply Discard Figure 6 Empty Test Structure General 3 1 2 2 1 2 Creating a test structure based on a requirement structure This feature allows you to create the same structure like in a requirement structure For each requirement a test package and a dummy test case is created plus automatic link to the requirement When activating Test Structure gt New gt Based on a requirement structure the window shown in is displayed All requirement structures are Shown which are assigned to the opened project and checked in see a
230. le Fi TEMPPO Testmanager Demo Notepad i loj x Project Test Structure Edit Test Execution Evaluation Tool Windows Help Test Structure Notepad RTF Import with TCs System Test 1 x Introduction General description of the product General Plan Requirements Detailed description of the required g Specifications for project managemel Mame Notepad RTFimportwithTCs Obligations of the client Literature Owner Testmanager Updator Testmanager Aroren Created 15 02 2012 16 36 29 Updated 15 02 2012 16 44 37 H 9 General description of the product 1 Type Test Structure Esa 10 Detailed description of the required H E 11 Specifications for project managen TEMPPS Designer IDATS D m 12 Obligations of the client 1 143 Literature 1 Test level System Test H14 Annex 1 Description Lock Appl Discard Figure 23 name of test package already exists 3 1 2 2 7 3 Transfer data via XML Import the test structure from one project P1 to another project p2 same database e Export the test structure via XML TEMPPO Test Manager e Assign the needed requirement structures of the test structures to the project P2 TEMPPO Administrator e Import the test structure via XML TEMPPO Test Manager Import the test structure from one database di export to another database d2 project p2 import e Export the test structure via XML TEMPPO Test Manager e Export the requirement
231. lected za Prey Met gt Finish Cancel Figure 346 Step 2 The correct JUnit test class is automatically selected TEMPPO Extension Panama In the next step new test packages and test cases will be detected Since we removed two test cases in the import step see Fig 90 they will be detected as new We also removed test package Framework Tests see above so it will also be detected as a new JUnit test suite Fi Update JUnit Tests Sa E xj Steps Add Hew Test Cases 1 Introduction Select the new JUnit test cases to add 2 Select a JUnit test elass 3 Select new JUnit test canes SLES 4 Select obsoltete TEMPPO junit samples VectorTest Select Al test cases i 5 Setpackage default valves testClone junit samples Vector Test 5 Settes cose default values El testRemoveAll junit samples vectorTest Dessert Al T Summar 5 Kj Frai sank Tezi TEMFF Extension Panama lt s Prey Next Finish Cancel Figure 347 Step 3 Two new test cases and a new test package are detected automatically Now the test case Obsolete TestCase that we created just before see above will be detected as obsolete because it is not contained in the JUnit test class junit samples VectorT est Page 268 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fj Update JUnit Tests Steps Remove Obsolete Test Cases 1 Introduction 2 Select a JUnit test class 2 Select new
232. lg v3 5 x d Mewsboard Notepad RTF Import with Tes Updated 20 02 2012 10 56 56 Refresh Changed since last login w 20 02 201 z E h 00 24 fo min 00 59 fo Apply Notepad RTF Import with TCs v3 General o etone o Tye ame version Dae Updator Changed 51 Test Structure Notepad RTF Import with TCs VW 20 02 2012 10 53 05 Testmanager Testmanager Mew 51 Test Structure Notepad ATF Import with Tos V3 16 02 2012 16 36 30 E Testmanager E Testmanager Test Structure Notepad RTF Import with TCs System Test v3 wo WH EE no iter d Notepad RTF Import with TCs gt FA 1 Introduction na 2 General description of the product m 3 Detailed description of the required product os Eg 3 1 Scope of delivery m 3 2 Sequences scenarios of interactions ae E 3 3 User goals 3 4 Required functions of the product O B 3 4 1 File Administration EGR S411 windows Login gt il 1 1 1 Login o B E 3 4 1 2 New fie L 3 4 1 3 Open General Attributes Test stepa E Automation Requirements History Plan Execution History User defined ID teraz Mame fLogin Owner Testmanager Updator Testmanager Created 20 02 2012 10 26 12 Updated 1 02 2012 10 56 57 Automated Test Case Lock Appl Discard ey of hanual free uJ 3 4414 Save Figure 214 Newsboard 3
233. ling Changes in the latest version of the test structure will now not affect Release 1 E g when inserting a new test package and test case the new items are only available in the latest version of the test structure see Figure 217 In the prior versions items are not available of course see Figure 218 You can see the active version of your test structure in the title bar of the test structure explorer Page 176 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad l jol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test va ga 2 0 Product users M a 3 Detailed description of the required product H031 Scope of delivery General Attrinutes Test Steps El Avtomeation Requirements History Flan Execution History 3 2 Seguences Scenarios e E r Instruction Expected La 34 Required functions of the product f j ile Srinietrastion Enter accountin test domain and Login successful 7 Pa password i l E 3 4 1 2 1 Mew file opened no 3 4 1 2 2 New file opened ch na BY H i 3 4 1 2 3 Mew Test Package c 3 44 3 Open LEa d Sawe r Lock Apply Discard Figure 217 New items in latest structure version 5 x Project Test Structure Edt Test Execution Evaluation Toole Windows Help est Structure Notepad
234. lly created An example of such an XML file is shown below lt xml version 1 0 encoding ISO 8859 2 gt lt IDOCTYPE TEMPPO_ EXCHANGE SYSTEM Test structure dtd gt lt TEMPPO EXCHANGE gt lt TP name HumanResources gt lt TC name Search_1T1 test_goal Transition bead situation Error gt lt STEP instruction input expected lt USR_FIELD name Actor alte Seen Connery gt lt USR_FIELD name ExecutionRequest value gt lt USR_FIELD name Data value line 1 line 2 line 3 gt lt STEP gt Page 54 User Manual TEMPPO V6 0 Edition March 2014 Description of Use lt STEP instruction input expected lt USR_FIELD name Actor ae err Connery gt lt USR_FIELD name ExecutionRequest value lt USR_FIELD name Data value line 1 line 2 gt line 3 gt lt STEP gt lt TC gt lt TP gt lt TEMPPO_EXCHANGE gt 3 1 3 1 6Upload paste reference images For adding pictures to such a column you have to select such a cell press the right mouse button and activate the menu Upload Delete Paste Copy or Reference Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help x Test Structure Notepad RTF Import with TCs System Test V1 q x M d b HW EE no fiter ALJ Notepad RTF Import with TCs 1 Introduction 2 General description of the product General Attributes Test Step
235. ls 7 E New Tes Select All Dare Gl New Tes G Tree b Copy Ctrl C Fa Paste Ctrl Order Edit Refresh recursively fa Move Ownership Analyse selected b E Report selected Figure 188 Context menu delete x DY Do you really want to delete these tems Figure 189 Acknowledgement for deleting After the acknowledgement of the user the delete process starts If the items are locked or the user doesn t have the right to delete foreign items a list of these items which couldn t be removed is displayed see Figure 190 Page 159 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Locked Items x Locked Items kaor Mew Test Case aSa Mew Test Case 1 Figure 190 Locked Items 3 3 1 6 Set test results The function Set Result s can be applied either for a whole sub tree or for any number of selected test cases Activate Set Result s in the context menu see Figure 191 and afterwards Figure 192 is shown 4 P FR amp ay No riter El a 1 New Test Suite i New Test Package i Gl New Test A Find and Replace Fa 2 ae LM iew Test Po eeepecgice el New Test Packa Select All tree O p Run automated Set Resultis er Edit OS Refresh recursively Ea Move Ownership g nalyse selected b EF Report selected Page 160 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Figure 191 Context menu Set Re
236. lso Figure 7 Fi Select Requirement Structure E xX Mew Requirement Str atwi0905 25 08 2009 10 55 15 Manual Figure 7 Select Requirement Structure After selecting one requirement structure another window is shown see Figure 8 You may enter a name and description Also a test level has to be related to the new test structure Page 18 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Test Structure Properties i x General Mame Mew Requirement Structure added Owner Testmanager Updator Created 19 05 2010 14 06 10 Updated Type Test Structure SITEMPPS Designer UDAT C Test level EGEE Description cancel Figure 8 Test Structure Properties By clicking OK the test structure is created based on the requirement structure For each requirement a test package and a test case is created Both have a reference to the requirement described in 3 1 2 3 4 The test structure is opened in the main window see Figure 9 Fi TEMPPO Testmanager Demo Notepad jol x Project Test Structure Edit Test Execution Evaluation Toole Windows Help Test Structure Notepad generated System Test v1 d Notepad generated BE 1 Introduction i 2 General description of the pri General Attributes Test Steps E Sctometion Requirements History Plan Execution History ES 3 Detailed description of the pri fa 3 1 Scope of delivery ee 3 2 Se
237. m to test a specified requirement On the other hand an error case checks the application if e g a faulty input is rejected You may also select the purpose of test case execution for verification or validation Furthermore you can select a value of the attribute priority which mirrors the topic of risk oriented testing Each test case is given a priority attribute which reflects the test case s importance either from the customer point of view or from the complexity point of view It is important to note that risk oriented testing is no substitute for a complete run of all test cases However it should be taken as a guideline telling which tests have to be performed prior to shipment even when time is short After shipment the remaining tests still have to be carried out Suggestion for the definition of test case priority attributes usually they should be defined in the test plan Top test case whose main concern is testing functionality If this functionality is not implemented properly the customer may be disgruntled Interrelationship to other functionality is very strong such that system behavior may be concerned High test case whose main concern is testing an often used functionality Therefore misbehavior would be immediately evident Strong interrelationship to other functionality or complex algorithm involved Medium test case whose main concern is testing functionality that is not frequently used or not in th
238. main line In TEMPPO every last version gets the label latest signaling that the test structure in this version is checked out for editing Page 175 TEMPPO V6 0 User Manual Edition March 2014 Description of Use Eiversions o Edit properties of selected version Example for versioning Edit tf Vi editable version L check In Check in active version Activate Activate selected version id Merge gt Tree style Merge all test cases into latest version of main line Versions only f Labels only Change tree style i Versions and Labels ClearCase style gt Order ie ascending 2 descending Close Figure 215 CM Version tree before first check in If you check in the test structure by using the Check in active version button in the Versions dialog you have the possibility to specify a label Release 1 Then the version tree looks like displayed in Figure 216 The test structure gets checked out immediately and version 2 is created The symbol 2 signals the active version which is again latest Se Example for versioning Edit VI Release 1 ener ae l Ga V2 editable version 1 Check In E Activate id Merge m Tree style Versions only C Labels only Change tree style abels ClearCase style r Order _ ie ascending t descending Close Figure 216 CM Version tree after checking in and labe
239. mation about it in the sub tabs Server info License usage Log Page 254 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator 5 7 1 Using a license server ona computer with several network interface cards When working on a computer with several NICs network interface cards the connection to the license server might cause problems because the wrong IP address is sent to the license server This problem can be solved in two ways 1 Reorder your network cards Open Control Panel Network Connections Menu Extended Extended Settings The NIC connected to LAN must be the first in the list see screenshot Erweitert Netzwerkkarten und Bindungen Reihenfolge der Anbieter Die Verbindungen werden in der Reihenfolge autgefuhrt in der Netzwerkdienste darauf zugreifen Yerbindungeri TE LAN Yerbindung VMware Network Adapter Mnett Local Area Connection 4 Wireless Network Connection Bindungen fur LAN Yerbindung ch File and Printer Sharing for Microsoft Networks 3 Internet Protocol TCP IP El Client for Microsoft Networks 3 Internet Protocol TCP IP Figure 330 Order of network interface cards 2 Add TEMPPO start option Open lt Installation Directory gt launcher properties with a text editor Add Djava rmi hostname lt IP address gt to TEMPPO vmargs g TEMPPO vmargs Xms128m Xmx256m DentityExpansionbLimit 1000000 Djava rmi hostname 158 226 235 13 Page 255 Use
240. me change 07 05 2013 13 46 38 Testmanager Test Goal o A E 46 Other product features reqi E E 5 Specifications for project manage 4 TT E 6 Obligations of the cient E 7 Literature lt w Figure 41 History tab Within current test structure version the number of history entries loaded x can be configured in settings see 3 3 16 2 4 If there are more history entries the button Search next is still enabled und the next x lines could be loaded It also possible to view all history entries of all test structure versions by pressing the button Display all entries and save them to CSV file The additional comment Info can be configured to be mandatory in TEMPPO Administrator gt Project properties For each project this mandatory flag can be set If the mandatory flag is set on a history comment is popped up on apply Figure 42 Page 47 User Manual TEMPPO V6 0 Edition March 2014 Description of Use AI x Figure 42 History comment e Plan Since testing is a project within a development project TEMPPO offers possibilities for test project planning TEMPPO do not wants to replace project planning tools like MS Project but presents features for resource and test execution planning Test case designers or test managers have also the task to estimate the execution effort for each test case as well as to appoint a tester who execu
241. mentation It has to extended by parsing the result handed over from the automation tool package ext import java io Reader import temppo test tools adapters IAutoToolAdapter import temppo test tools adapters IResult rE Implementation of adapter for universial automation interface oy public class MyAdapter implements AutoToolAdapter public IResult getResult Reader returnFromAutoTool throws Exception Result ret new Result TODO add parsing of returnFromAutoTool here and set result and summary Example use buffered reader to process returnFromAutoTool line per line BufferedReader br new BufferedReader returnFromAutoTool read all lines and search for result and summary String line null StringBuffer summary new StringBuffer while line br readLine null if line startsWith Result process result here if line equals Result FAILED meee result IResult FAILED else if line equals Result PASSED bee result IResult PASSED Page 297 User Manual TEMPPO V6 0 Edition March 2014 Appendix else vest is for summary summary append line summary append System getProperty line separator ret summary summary toString mi return ret xk Implementation of result interface Ki class Result implements IResult String summary e int result BLOCKED public String getSummary return summary p
242. mns T Comment i Expected image JK Cancel Figure 13 Import Settings for generating a basic test structure For the generation of a basic test structure following settings can be applied Generate document path The path of the imported document is set for each test package in tab Details Heading mask Specify the name of the heading if it is different to the Standard one Heading Uberschrift 1 2 3 It is initialized with Heading Limit test structure depth to If checked limits the imported document hierarchy to the specified level This means that headings with a level higher than the specified will not be imported Generate numbers and start with If checked a hierarchical numbering will be generated for each test package and added as a prefix to its name like heading numbering in MS Word Generate test packages If checked test packages will be generated Test packages will be generated from document paragraphs which are formatted with the standard formats Heading 1 Heading 9 or berschrift 1 Uberschrift 9 in German documents Their hierarchical position in the test structure will correspond to the heading level in the document Import description enabled if checkbox Generate Test Packages is checked If checked the test package description will be imported Tables and graphics are not considered Page 22 User Manual TEMPPO V6 0 Edition March 20
243. mo Not Notepad v2 44 editable v Test Case WinRunn te701 export dat 20 02 201 Notepad System amp Acceptance T Demo Not Notepad W214 editable v Test Pac Find up tp650 export dat 20 02 201 Fi User documentation Demo Not Notepad W211 editable w Test Pac Find down tp651 export dat 20 02 201 4 Demo Not Notepad w2 1 1 editable v Test Pac Relations tp521 export dat 20 02 201 x Figure 328 Unlock 5 7 License Server Connection Fi TEMFPFPO Administrator Testmanager q joli Host Port fatinzpt Oga www930 my t solutions net 2013 Disconnect Server into License usage Log Server Mame atinzp1 Oga MAC address O0 30 05 F 6 4 40 Started 06 02 2012 03 05 07 Version 5 5 Build 10 14 10 2010 11 35 Licensed for Department SIS SOL AD CTE AUT Mame Pichler Rainer Figure 329 License server connection The licensing mechanism allows two ways of using TEMPPO e local license a valid license file license dat must be located in the TEMPPO installation directory e g c programme temppo 5 4 e license server an existing license server is specified in this tab for installing a license server see chapter JLMS Installation in the TEMPPO Installation Guide You must specify the name of the machine or IP address and the port number usually 2000 where the license server is running When connected to it you can see infor
244. must be specified All automated test cases in the specified test suite will be executed Optionally TEMPPO is closed with the exit parameter Separated list of values where the names for project test structure version and export file must be specified The whole test structure is exported to the denoted file XML format Separated list of values where the names for project test structure version test suite and export file must be specified The whole test suite is exported to the denoted file XML format Checks if there are locks by current user Considered in conjunction with option export_teststructure and export_testsuite Separated list of values where the user and password must be specified The user profile is exported to standard out or to an XML file parameter file updates the results of test cases which are described in the xml file For the xml file the DTD has to be used see 13 3 Page 281 User Manual Edition March 2014 report lt project test structure version test suite filter report setting file gt file lt file gt exit help hide license TEMPPO V6 0 Command Line separated list of values where the names for project test structure version test suite name filter report setting file must be specified and TEMPPO is opened with the specified version of the test structure and optional a filter and test suite and writes a report b
245. n 0 59 ee a 3 4 4 Search Functions 2 3 4 4 1 Find Actual test execution time fo h 48 min 0 59 E t 34 441 Find up E 3 4 4 1 1 1 Case sensitive blocke R 34 41 12 WinRunner Check Ste 3 4 4 1 1 3 Quick TestPro Test ca Ea 3 4 4 1 4 4 Test Partner Test ca EY 3 4 4 1 1 5 UAI not executed Lock Apply Discard General Details Export Into Attributes Predecessor Plan Figure 89 Test suite Plan 3 1 4 1 7Test Result Attributes There is the possibility to assign attributes to test cases for execution in tab Attributes TR of a test case result Only attributes can be chosen that are indicated as test result attributes in the Meta Data Editor see 5 3 Fi TEMPPO Testmanager Demo Notepad P Ioj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 72 RCO 41 1 1 MH d b H GP EE no tter s Test object Version rZ AEO Eim 3 Detailed description of the required product features Flo 3 4 Required functions of the product Ceneral ES Test Steps E Automation a 5 4 1 File Administration Requirements History Attributes TR Previous Rezuits Flan Execution History m G 85 41 14 New file opened no change ag MH 34 1412 New fie opene changes trite vets O O OSO O Attribute wal ay 3 4 4 Search Functions T ee 3 4 44 Find E t 34 411 Find up BH 3 4 4 1 1 1 Case sensitive blocke R 34 4
246. n Plan a E34 File Administration Requirements History Attributes TR Previous Results EF Ss Mew 3 4 1 1 1 Mew file opened no change lA 3 4 1 1 2 Mev file opened changes Planned tester Testert a 3 4 4 Search Functions Execution History Elid 3 4 4 1 Find u 34411 Find up Planned test execution time i h 30 min 0 697 BH 3 4 4 1 1 1 Case sensitive blocke R 3 4 4 1 1 2 WinRunner Check Ste Actual test execution time f h 4 min 0 59 ig Merge 3444143 QuickTestPro Test ca E 3 444144 Test Partner Test ca B A 3 4 4 1 1 5 UAI not executed Lock Apply Discard Figure 88 Test suite Test Case Plan That information is not only available for test cases but is also viewed for test packages and the test suite itself When clicking on root node test managers can view the accumulated values for Planned test execution time and Actual test execution time for whole test suite Page 81 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad S loj xi Project Test Structure Edt Test Execution Evaluation Tools windows Help Test Suite Test abject Version lt 2 RCO v1 1 1 Ss 3 Detailed d esr aquired product features I Ay 34 Rg locked by EET P 3 4 1 File Administration sl 3 4 4 1 New o 3 4 1 1 1 Mev file opened no change 3 4442 New file opened changes Planned test execution time 3 g fo mi
247. n main latest is overwritten For advanced TEMPPO users there is a possibility to merge ALL test cases and test packages from a branch or main version to the latest version of the main line e g after finishing test execution and test case updating You can open the version window and press the Merge all test cases into latest version of main line button Page 90 User Manual TEMPPO V6 0 Edition March 2014 Description of Use ee Motepad RTF Import with TCs Edit Ew EAM A Test Suites for W441 2012 02 16 I Check In LW editable version fe Activate M Merge all test cases into late Versions only Labels only e Versions and Labels ClearCase style r Order O azcending descending Close Figure 103 Versions After pressing the merge button a warning window comes up that asks you if you are sure to go on If you commit this window the latest version will be checked in and checked out again Then all test cases of the branch version are copied to this checked out version 3 1 4 3 1Adding new test cases during test case execution As a matter of fact new test cases have to be added to test case execution although that test phase already started Therefore such test cases have to be created in the corresponding test structure branch versions If the pre selection of test packages sub trees and the logical expression when creating the test Suite match the test cases appear in the test suite
248. n UDA XX Po Assign Uploads TX XY pt Assign UserFields EX x FP Pt onsistency checker TX TFT ti FreezeTest Structure X TF ti id Freeze Test Suite X J TF Pp Move ownership TX td freeze Test Structure X ti freeze Test Suite X FFT plc test suites EX Administrator pt id Testecategories EXT XT XT XE XX S Page 293 User Manual TEMPPO V6 0 Edition March 2014 Appendix Test levels po plots XXX XK ser feds ma ee Po User User defined attributes attributes PPP PPP aa structure Apply requirement updates O Pe Pac Edit main LATEST po export XY Ee ne ee AOA po UnitInterface TX po tock items X x Test structure root TP TC Z Z o TEMPPO Test package Assign requirements __ X X I T To ooo O Assign test categories XL L eee D 7 Edit xxix x x moe eee i TEMPPO Test case Assign requirements S allowed if user is TC editor _____ Asian test Assign test level sss X XO A e ELT TAATA A A OPET T P R OP DS e Edit X xp x x x x f Consider User concerns only the deleting __ Merge T if user is editor of a version TEMPPO Test suite Assign test suite attributes eaa l SS SS Oo is only allowed if test suite has no test Edit pe E op E ee E A A A S S po mport x e e S S Remove from export database e S a S D a Unlockitems X L T XK TEMPPO Test result Assign test result attributes X X P A i T E a Implies Run automated and Set results multi Page 2
249. n also be used to administrate automated test cases Here test steps are stored as a test script on the files system On one hand TEMPPO supports the tools WinRunner and QuickTest Professional of HP http www hp com SilkTest of Microfocus and TestPartner of Microfocus Page 56 User Manual TEMPPO V6 0 Edition March 2014 Description of Use http www microfocus com Ranorex http www ranorex com and on the other hand there is a Universal Automation Interface UAI With the context menu item Test automated test case or Edit gt Test automated test case the test case can be started on trial i e the result of test case isn t saved The result is shown in a message box 3 1 3 1 7 1 WinRunner QuickTest Professional SilkTest TestPartner For specifying an automated test case it is necessary to enter the tool WinRunner QuickTest Professional SilkTest TestPartner the file name of the script plus path a file selection dialog is opened The text field Script Data is used for passing parameters to the automation script Currently only SilkTest uses this feature Fi TEMPPO Testmanager Demo Notepad E l Joj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test v1 2 General description of the product 3 Detailed description of the required product features LL 31 Scope of delivery General Attributes Test Steps
250. n be added by pressing the button New in the tab Test levels and Figure 302 is displayed Page 235 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator F Properties of New Entry xi 8 Ej Properties of New Entry X General Details General Details p Sub system test Created 20 02 2012 15 14 46 Owner Testmanager Type Test Level Description eves Figure 302 New Test Level In this window general information like name creation date and owner and a Description of the test level can be entered In the second tab Details additional test levels can be added Additional test levels are related to a test level Furthermore it is possible to add supplementary test levels for the purpose of using test cases in different test levels For example there is a test structure related with test level System Test which contains the additional test levels Acceptance and Regression Test Each test case in this test structure can now be assigned to one or both of the additional test levels see 3 1 2 4 It s not possible to delete test levels which are already used in projects test structures or test cases 5 4 3 Test Categories Test categories are used to denote test packages that contain only test cases of a special type Page 236 User Manual Edition March 2014 Fi TEMPPO Administrator Testmanager Database 9 Roles E Users Metadata LA Projects Lacke E Licen
251. n be deleted in the task list window if all tasks are closed The task list has to be selected and via the context menu item Delete task list a confirmation window comes up Confirming with OK deletes the task list Task lists can be exported to Excel for further working on it Page 197 User Manual TEMPPO V6 0 Edition March 2014 Description of Use DA TEMPPO Schlosser Dietmar ADIS Eee Driving Information System Project Test Structure Edit Test Execution Evaluation Tools Windows Help lt gt Task ists ae ex Eee ADIS requirements Advanced Driving Information System V1 gt V2 i New Requirement New route requirement 5 tc41002 Blue displayed route contains white arrows after es 041716 Blue displayed route contains white arrows after ec Export i tc41717 Blue displayed route contains white arrows after each manoever General zx Delete task Est Delete Name ADIS requirements Advanced Driving Information System V1 gt V2 Created 27 08 2010 Version update V1 gt V2 Figure 253 Task List 3 3 16Settings TEMPPO differs between global and application specific settings 3 3 16 1 Global settings Global settings concern all TEMPPO applications Test Manager Requirement Manager Administrator and Manager i e when a global setting is changed it s changed for all applications If an application is running an a global setting is changed the chang
252. nager 7 3 4 4 Search Functions El 3 4 4 1 Find a 3 4 4 414 Find up Type Test Suite fi 344111 Cases a HEE 3 4 4 1 4 2 WinRur Description wwihole structure fF 3 4 4 143 QuickT Release canidate 01 LEE 344114 Test Pe H E 344411 5 UAI no Created 16 02 2012 13 47 29 Updated 16 02 2012 13 47 29 Ihcluded TPs Mew Find ExcludedT CE Lock Apply Discard Figure 71 Information about included TPs and excluded TCs The tab Details displays the logical criterion of the test suite It can be changed Since there aren t any results yet recorded Fi TEMPPO Testmanager Demo Notepad E lel Es Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version lt 2 RCO1 41 1 1 M d b H GP E no tter A Test object RERA RCO Efa 3 Detailed description of the required g Fad 3 4 Required functions of the prodi General Details Export Info Attributes Predecessor Flan EHA 3 4 1 File Administration Attribute Value EAA 3 411 New 2 34444 new gieope Jf J x iE 3 4 1 1 2 New file ope ey 8 3 4 4 Search Functions El 3 4 41 Find a 34 41 41 Find up il 344444 Cases fF 3 44 14 2 WirRur fF 3 4 4 1 4 3 QuickT LEE 3 44 14 4 Test Pe EV 3 4 4 145 UA no Lock Apply Discard Figure 72 Test suite logical expression In the test suite tab Attributes you can set attributes which can also be shown in the
253. name 18 tc13615 tc13618 tc13620 tc13622 tc13624 Requirement name 19 tc13630 tc13631 tc13633 tc13634 tc13635 tc1 3636 Requirement name 2 tc13449 tc13450 tc13451 tc13452 te13453 tc 3868 tc13869 tc13638 tc13639 tc13640 tc13641 tc13644 tc13645 tc13648 tc13661 tc13662 tc13663 tc13664 tc13665 tc13666 tc13667 Requirement name 22 _ tc13684 tc13685 tc13686 Requirement name 23 tc 13688 tc13690 tc13693 tc13695 tc13696 tcl 3698 tc13699 Requirement name 24 tc13972 tc13973 tc13974 te13976 tc13977 tc13978 tc13979 Requirement name 29 _ tc13972 tc13973 tc13974 tc13976 tc13977 tc13978 tc13979 Requirement name 3 tc13455 tc13456 tc13457 tc13458 tc13459 Requirement name 31 c13988 tc13990 tc13993 tc13994 tc13995 tc13996 tc13997 Donitirermnant mama 27 he 1 20297 be 12022 kei ROR be 1 IARA be 1 RARR be 1 2020 kei aaan Figure 121 Test Structure Requirement Analysis Detailed Data Page 103 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F Requirement Analysis x Requirement Structures m meee Requirement attributes v Filter Calculate G chart E pata r Chart stacked Horizontal Bar Chart 3D v Test Results o 1 2 Sort alphabetical ascending descending Values All C Only zero values No zero values ose Figure 122 Test Suite Requirement Analysis Fi Requirement Analysis i x Requirement Structures Module 14 v R
254. nces Scenarios of interactions with the environmen Eg 3 3 User goals 3 4 Required functions of the product Ea 3 4 1 File Administration oO B4 3411 Mew o E 3 4 1 1 1 Mew file opened no changes fi 3 444 2 New file opened changes 59 3 4 1 2 Open m 3 41 3 Save O po hei 341 4 Exit 3 4 2 Edit Functions 3 4 3 Print Functions Ee 4 3 4 4 Search Functions b AAG 3 4 41 Find O E 344141 Find up fil 3441141 Case sensitive 3 4 4 1 1 2 WinRunner Check Stat HE 3 44443 QuickTestPro Test case g 3 4 4 1 1 4 Test Partner Test case 34 4415 UA 5 x General Attributes Test Steps EJ Automation Requirements History Plari Execution History Toal TestPartner File 4 Script Data Scriptname project Lock Apply Discard Figure 58 Create TestPartner test case 3 1 3 1 7 2 Ranorex For importing test cases and folders from Ranorex you have to select test structure root activate the menu item Import structure gt from Ranorex Document and a open file dialog is displayed where you can select a Ranorex project file csproj After pressing the button open the file is imported and test cases and test packages are generated The following table shows the mapping Ranorex Test suite Test case Folder Record Table 1 Ranorex TEMPPO mapping After importing a Ranorex test suite you can add change or delete test cases in the Ranorex studio When finished you
255. nded to select the checkbox Unlimited number of threads For loading time CPU usage goes up If you work on a terminal server it is recommended to specify a number of threads Please ask SiTEMPPO team to specify the best value for your test environment Serial Data is loaded serialized Only recommended when a small amount of data Closing unused database During loading test structure several connections database connections are opened Define a duration when unused connections should be closed History entries Number of history records loaded at once from DB Further records can be loaded on demand Recommendations For parallel mode the number of threads should be 2 number of processors on database server The setting for closing unused database connections depends on usage of TEMPPO e If you are opening frequently different test structure or versions then you should define a longer duration Then opened database connections are reused and no additional resources are needed permanently for connecting disconnecting to database For example 30 minutes e If you are working only in one test structure version for a long time then you can define a short duration Opened database connections are closed and used resources are released For example 10 minutes Page 206 User Manual TEMPPO V6 0 Edition March 2014 Description of Use H User Interface Test Automation Switches on off a database chooser window
256. ned no changes cad 1000 Notepad System amp Acceptance Test W1 1 1 editable version System test Ve New File opened no changes tca 1003 System amp Acceptance Test W1 1 1 editable version Integration test w3 3 4 4 1 1 Case sensitive MP 34411 1004 oe Figure 124 Analysis by Bug ID project 3 1 5 4 Analysis by Bug ID test suite TEMPPO Test Manager offers you the possibility of analyzing the suite for creating a list of test cases that are referenced by certain bug IDs By activating the menu item Analyse selected gt Bug ID Figure 125 is displayed Fj Analysis X Bug ID owhe Analyse Jame eao But 10 1 1 1_1 heading up route guidance on 2416 1 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 2_3 3D Map 2649 2649 A bug ID like 1 is reported in different test steps of the same test case 10 21 11 Zooming rules 2650 1 10 2 1 1_1 Zooming rules 2650 1 10 2 1 1_1 Zooming rules 2650 1 Figure 125 Analysis by Bug ID test suite In the text box Bug ID you can enter the bug ID or a regular expression if you want to create a list of more or all test cases that are referenced By pressing the button Analyse the test case list is shown and can be saved as csv file by pressing the button Save By selecting a test case in the window Analysis the c
257. node in the tree Is the tree root selected the whole tree is searched whatever direction is selected 3 3 5 1 1Find Test Case Test Package There are three possibilities for finding test case s package s e Find Next With clicking Find Next the first test case package is searched and selected in the tree The first occurrence is marked too With the next click the next occurrence is marked If there are no more occurrences in the test case the next test case package would be searched If there is no element anymore a message is shown see Figure 210 e Find Next Test Case package With clicking Find Next Test Case Package the first test case package is searched selected in the tree The first occurrence is marked too With the next click the next test case package is searched If there is no element anymore a message is shown see Figure 210 Find and Replace x Lol A i 1 Mo more occurrences Found Figure 210 No more occurrences found e List occurrences With the button List occurrences the searching result is shown in a list see Figure 211 When clicking a test case package in the list this requirement is selected in the tree Case sensitive Testmanager 16 02 2012 11 03 55 Login Testmanager 20 02 2012 10 26 12 New file opened changes Tester 16 02 2012 16 45 51 Figure 211 List occurrences 3 3 5 1 2Replace Test Case Test Package There are also two possibilities for replacing e Repla
258. nput values and test cases covering different combinations of those A unique name must be applied to the resulting test cases and they are ready to be inserted into the appropriate test package in the TEMPPO test structure With the menu item Test Structure gt New gt Test Case a new test case is created below the selected test package This menu item is enabled if a test structure is opened and a test package is selected It can be activated by the menu or aright mouse click A new child node GI manual or El automated is created below the selected one and a new name has to be entered The default name is New Test Case Page 42 User Manual TEMPPO V6 0 Edition March 2014 Description of Use The test cases tab consists of the tabs General Attributes Preconditions and Postconditions Test Steps Automated Requirements History Execution History and Plan During design you just use General Attributes Requirements and Plan General You have to specify the name type either manual or automated and the goal of the test case The test case developer should be able to implement test steps based on this description The automation tab is only enabled in case of automated test cases Furthermore a User Defined ID is suggested by the system that can be edited In many projects requirements get unique IDs It is recommended to use these IDs plus some serial number as test case IDs You can search for test cases by ID or name b
259. ntral database won t be overridden by yours Later your result will be written into the database The other result is lost Import all test results All test results of already executed test cases are overwritten by your results Manually choose test results to import When activating that possibility Figure 113 Manual import of test results is shown In the right part of the window the current result state of test cases in the central database is shown together with their execution date NOT importing date Test cases that may cause conflicts are colored blue The left side of the window shows the test results of the exported test suite Now you can activate the checkboxes of test cases that you want to import Note All test results that are marked are overwritten in the central database after closing the window with OK Page 96 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Test result comparison Test Suite in Export Database Test Suite in Master Database El w A Test Suite for export a lA Test Suite tor export a B O SA1 Main Menu 2351 Er ai Main Menu 2351 Pe CD BBD iL Main Menu 28 11 2002 15 07 54 aes fi 11 Main Menu e LC BB 1_2 Main Menu 28 14 2002 15 07 56 pei 12 Main Menu be CD BD 1_3 Main Menu 28 11 2002 15 07 59 SE _3 Main Menu El W a 2 Destination Entry Ea 2 Destination Entry Ee Al 2 1 GeneralPrinciples Bal 241 GeneralPrinciples ag A211 Destination Entry via speller
260. o O Temp_PvAiTeststellung_PVAyunita 7 H Mewsboard he Test Suite El Test Automation pe Silk Test Hin Runner Universal File H Universal Socket Quick Test Pro Test Partner b TEMPPO Designer IDATG i Ranorex Fl Commands New Command Tallow duplicate names in same hierarchical level i Javas El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 331 Settings for import and execution of JUnit test cases 6 3 Import JUnit test cases 6 3 1 Description and steps The import function reads JUnit test cases as well as their suite structure from a JUnit test class It creates a new test package in TEMPPO which contains further test packages and eventually test cases according to the suite structure found in the JUnit test class The generated test cases refer to JUnit test methods You can access the import function through the TEMPPO menu Tools gt JUnit gt Import This menu is activated only when an item in the test structure is selected that can host a new test package i e a test package or the root node of the test structure A wizard guides you through the steps necessary to import the JUnit test cases The following steps are encompassed 1 Introduction Explains the steps of the import procedure Test Class Selection Provides the list of JUnit test classes you may import Only classes found in the classpath are listed here
261. o copy a certain test suite with the restriction of test results The following steps are to do e Select an existing test suite e Test suite name e Test cases with special results For the first 2 steps see 3 1 4 1 3 In the 3 step you can select test case results that will filter the test suite Only the selected ones will be in the new test suite Page 76 User Manual TEMPPO V6 0 Edition March 2014 Description of Use UU x Steps Choose test cases included with following test result 1 Introduction 2 3 4 Enter test suite name 5 Test suite should include test cases with following results NV failed Slee j herp passed V not completed V not executed V not implemented TEMPPO Test Suite Generator lt lt Prev Next gt Finish Cancel Figure 82 Special Restrict test suite Newly created test cases are added to restricted test suites Consider the following situation you activated the latest test structure version and created a new manual test case Now you create a new test suite based on an existing one with the logical expression type manual In step 5 of the wizard choose Test suite should include all test cases except those which are passed Now the new test suite will not only contain the failed test cases of the previous test suite but also the newly created test case although its result is not executed 3 1 4 1 5 M
262. of selected test cases and test packages but the right has to be considered test New Test Package ff New Test Case im Bee gt Brew Teste AfindandReplace Fs ae MENew Te Show Details Di New Te Select All ol New Te JCC B ree d y Git Ctrl x Copy Ctrl C A Paste Ctrl X Delete Delete T Order ey Edit OS Refresh recursively ta Move Ownership g Analyse selecter Ei Report selected Figure 184 Context menu Move Ownership eres Figure 185 Move ownership After the process moving the ownership a summary is shown see Figure 186 x Humber of tems with new owner 9 DD Number of locked tems 0 Humber of tems with identical owner 0 Figure 186 Summary If the user doesn t have the right to move the ownership of foreign items or the item is locked a list of items is displayed see Figure 187 These items aren t changed Page 158 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Locked Items i x Locked Items kaor Mew Test Case aSa Mew Test Case 1 Figure 187 Locked Items 3 3 1 5 Delete This function is now available for any number of selected test cases or test packages but the user has to have the right m F FI wr jes r Li on New Test Package i is Gl A Sass M He A fien Tes D Mew b Find and Replace F3 r HE Show Detai
263. oles Test Case template Test Resutt template V Test Result template activated Attrinute Mandatory Assigned defaut value Figure 322 Test result template 5 5 5 Deletions The delete button is active if a node project test structure version test suite in the tree is selected By clicking it the corresponding object is deleted after you confirmed the verification message Page 249 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator You cannot delete the main latest label or any latest label in a branch 5 5 6 Test Suites check consistency unlock The buttons Check Consistency of a selected test suite and Unlock selected test suite are active if a test suite is selected Furthermore it is possible to unlock a whole test suite structure In case of problems during exporting and importing test suites it may happen that references remain in the central database To solve these problems it is necessary to unlock the test suite Figure 317 shows the locked test suite Test Suite for export The Lock button becomes enabled when the test suite is selected If you unlock a test suite structure no more imports are possible After that exported test suites are of no more use and can be deleted from the Export Database 5 5 7 Assign Metadata For a chosen project all kinds of metadata test level test category attributes uploads requirement structures user fields can be assigned to the project
264. olored yellow Fi TEMPPO Testmanager Demo Notepad To Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Motepad RTF Import System Test pu m Ej x MH E Mo filter Ald Notepad RTF Import Et 24 Introduction H E 2 General description of the product General attributes Details Requirements History Plan E a 3 Detailed description of the required prod 0 3 1 Scope of delivery ry fps g a Sequences scenarios of interactions with the environment i 3 3 User goals searchFuncions 5 3 4 Required functions of the product Mame search Functions E D 3 4 1 File Administration EH E 3 4 2 Edit Functions E 3 4 3 Print Functions Crested 15 02 2012 16 26 59 Updated 16 02 2012 09 37 12 Jg 3 4 4 Search Functions SELERI Search up Owner Testmanager Updator Testmanager Type Test Package oof 3 4 4 2 Search down Number of TCs 0 3 4 5 Help System E fa 3 6 External interfaces of the product Test Category E E 3 6 Other product features required ve io Description EH 4 Specifications for project management i 5 Obligations of the client a 6 Literature oo 7 Annex Lock Apply Discard ai Figure 25 Adding new test packages that are directly related to requirements Now consider the opposite situation The functionalities for searching up or down are not described in separate chapters of the r
265. om Assign Group to DevRoom Cramer No user with the name nn1 exists Import Masterpiant Incremental Import Masterpiant Incremental Cramer Mo user with the name nnd exists Import Masterptant Incremental Import Masterptant Incremental Priority Normal is an invalid value for this field so the default value was used Figure 20 CSV Import Result 3 1 2 2 6Build manually If the requirement specification is not imported to TEMPPO the user has to create test packages manually activate the menu item Edit gt New gt Test Package It is strongly recommended for each test package to specify a document chapter where the respective requirement is defined Therefore in the next chapters only a test structure based on a requirement specification is considered 3 1 2 2 7XML Import TEMPPO is able to generate a whole test structure with test packages test cases metadata requirements attributes and all the information of test cases etc by importing an XML file The XML Import can be started by pressing the menu item Test Structure gt Import Structure gt From XML Document This menu item is only enabled when a test structure is open and selected or a test package is selected The XML document to be imported can then be chosen in a file dialog The XML document is checked against the DTD Document Type Definition See 13 1 Your XML file has to have the first line lt DOCTYPE TEMPPO_EXCHANGE SYSTEM Test structure dtd gt whereas
266. omation Connection delay 120 Seconds Sik Test WinRunner Adapter temppo test tools adapters C DefaultAuto ToolAdapter Universal File Arguments f file args test QuickTest Pro Test Partner gt JUnit TEMPPO Designer IDATG Ranorex Commands Change Management Bugzilla gt ClearQuest Telelogic Change JIRA Port Number 3333 Upload result fles to database Result Viewer c winnt notepad exe Restore Defaults ok Cance Figure 266 Settings Universal Socket The meanings of the parameters are as follows e Drive Letter is that letter where path of all test executables start For each test case a path has to be added without a letter drive In this way it is possible to Support scenarios where test executables have to be started from varying drive letters You only have to change the Drive Letter setting in the Administrator e Application path must point to the executable which will be launched by TEMPPO if a socket connection is not possible when test execution was started After starting the application TEMPPO will wait a defined delay to give the application enough time to startup before retrying to open the socket connection This delay is 5 seconds per default e The IP address from the host where the application is running has to be specified If the host isn t the local host 127 0 0 1 the application path cannot be configured The reason for this limitation is th
267. omize the title page of your report here which can contain a title project name status the name of the author and the current date Header Footer You can customize the header and footer for you report There are buttons for using the defined keys for page number date time etc Page 119 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Page Right Fages Date Time Fath Fie name Name NewReportSetting El Settings General 2 Title Page Figure 141 Report General Settings 3 1 5 6 1 2 Text Text settings are relevant for the textual data contained in your report and how they are displayed General Text Settings Page 120 User Manual TEMPPO V6 0 Edition March 2014 Description of Use First you can choose the Layout if you want your data to be displayed in continuous text or table format Furthermore you can set Format options Do not ignore information fields with empty values Do not generate heading numbers You can limit the size of your report by defining the depth absolutely You can use the slider to limit the reported test structure or test suite tree depth to a fixed level You can add Summary information_about your test package by checking Number of Test cases and or Test Steps The amount of contained test cases test steps will be reported for each test package either in absolute form or by percentage Finally you have the possibility to Generate h
268. ompare db Cut Ctrl x a version window comes up where you can select the version of the test case to be compared The versions window does only show the versions in which the test case exists After selecting a version the button Compare gets enabled ee Notepad RTF Import with TCs Display E11 Test Suites for v1 1 2012 02 16 m Tree style tA D7 aolteble varsin E viehe only Eb v2 o EbV24 Test Suites for V2 1 2012 02 16 Labels only Wedd editable version e Yersions and Labels a w221 Clear Case style L MI editable version PaE ie ascending Figure 225 Compare selecting a version When pressing the button Compare Figure 226 Figure 227 is shown The two versions of the test case or test package are displayed with their differences in red color Page 180 User Manual Edition March 2014 Fi Differences W1 W224 Fl Mew file opened no changes El General be User defined ID tc636 fa Mame Mew tile opened no changes i Owner Testeri Updated 2012 02 20 i Type manual Attributes FI Test Steps a Ha sg New step is added on branch errr Fanas H Plan General description of the product Gr General beUser defined ID tp520 Updated 2012 05 22 i ents Test Category This general description of the product being crea G Attributes el New file opened no changes The test case pursue
269. on Error return code of test method invocation Page 256 User Manual TEMPPO V6 0 Edition March 2014 JUnit Table 3 Terms used in TEMPPO and JUnit 6 2 Configuration Two configurations are necessary to use the JUnit extension test collector and classpath The configuration is done in the TEMPPO application via menu Windows gt Options once for the whole TEMPPO session The classpath is entered in the Arguments field in the usual format cp path1 path2 As in the JUnit framework it must point to both the JUnit tests and the Java classes under test The test collector is the part of the JUnit extension which searches for JUnit test cases in the specified classpath Following test collectors are available SimpleTestCollector searches for JUnit classes in files matching the pattern classFileName endsWith class amp amp classFileName indexOf S lt 0 amp amp CclassFileName indexOf Test gt 0 LoadingTestCollector searches for JUnit classes by instantiating all class files in the classpath and verifying if class containsSuiteMethod class extends junit framework Test amp amp Cclass isPublic amp amp class hasPublicConstructor Page 257 User Manual TEMPPO V6 0 Edition March 2014 JUnit Settings x JUnit l User Interface Tree Test Collector at sch panama junittool Loading Test Collector ew Test Step Cells Analysis Arguments c
270. on There a different ways for creating a new version e g check in of a version or creating a new branch for test suite During the creation process the current version is locked so that no other user can create a version based on the same version Is the version already locked the following dialog is shown Lock information q X FA Current label i locked Mew version could not be created Figure 163 Version locked 3 2 1 4 Creating a test suite You can only create a new test suite if the test structure and all of its items are not locked Otherwise you cannot create a test suite and you will get the following dialog see Figure 164 after pressing the Finish button on the test Suite wizard LIM ij x N j There are locks intest structure Do you want to continue with creating atest suter Figure 164 Test structure locked 3 2 1 5 Finding invalid locks On starting and quitting TEMPPO the whole database is checked for any locks which were set by you Normally there should be no one left But if there is one Page 140 TEMPPO V6 0 Description of Use User Manual Edition March 2014 see Figure 165 this is an invalid lock which can have two reasons Either you are currently running a second TEMPPO Test Manager or your last TEMPPO session terminated abnormally crash etc If so you should confirm the dialog by pressing Yes to remove all invalid locks TEMPPO Test Manager a x Warning Found lo
271. on TEMPPO startup 10 Timeout in seconds displaying DSN chooser Locking F Switches on off to lock the whole test structure before checking in and to prevent check in if an item is locked E Check for new test structure version when saving an item in main latest version Switches on off to check if the entire test suite is unlocked before exporting Locking Mode Locking mode in test structure and test suite automatic manual Loading Mode Loading mode for opening test structure parallel serial T Untimited number of threads Maximum number of threads 2 Close unused database connections after min 15 History 20 Number of history records to load Figure 263 Settings Database 3 3 16 2 8 Test Automation 3 3 16 2 8 1 WinRunner and SilkTest C Program Files Seque SikTestipariner exe D temppo Siktestiimp D temppo Siiktestiresult gt C WINNT notepad exe i jWinRunner q resexport r lt lt TestFile gt gt Universal File QuickTest Pro Test Partner JUnit V delete temporary test automation files TEMPPO Designer IDATG Ranorex Figure 264 Test Automation SilkTest WinRunner If you plan to manage automated test cases in TEMPPO you define the automation settings here First of all you have to choose the automation tool Page 207 User Manual TEMPPO V6 0 Edition March 2014 Description of Use which will run your test cas
272. on state of all selected TPs that Nave genera Attroutes Requirements not set the inherit flag _ Type and Situation radio buttons If all selected TPs without inherit flag have set the same value the value is selected otherwise there is no selection Priority and State combo boxes If all selected TPs without inherit flag have set the same value the value is displayed otherwise the selection is empty ml Additional Test Levels and Attribute Values The values that are assigned to all selected test TPs are displayed as usual white background color The values that are not assigned to all TPs are displayed in a special color grey background color If you want to assign such an attribute to all TPs select it right mouse click and activate we Pes E EES Such attributes or new assigned attributes are displayed in red color Direct inked Attributes inherited Attributes Inheritance l Priority Top ka State Designed Attribute Values io TP Type User case F xD Tab Inherited Attributes displays common Toere Test Packages Test Case state of TPs which have inherited attributes General Attributes Requirements _ from a TP Direct inked Attributes Inherited Attributes Inheritance a Radio buttons If all selected TPs
273. on units are files or directories Branch A linear sequence of versions is called a branch It is possible to split off the main branch and create a new sequence of versions independent from the main branch Check In Out As soon as an administration unit has been entered into the CM tool it may only be changed if a new version is created for it The act of making it editable is called checking out After an administration unit is checked out any editing operations are allowed for it A new version is created when the unit is checked in No further edition on this version is possible CM Configuration Management Configuration is the process of identifying and defining the items in the system controlling the change of these items throughout their lifecycle recording and reporting the status of items and change requests and verifying the completeness and correctness of items IEEE Std 729 1983 Label In virtually any CM tool it is possible to attach a name to a version number By doing so it is possible to make the version history of administration units usable Even after many successive versions these important states can be easily found and restored by means of their descriptive label Main line Main branch The linear sequence of versions starting at the initial version Merge Merging from version V1 to V2 means to take over changes in V1 to V2 Test Case A set of test inputs execution conditions and e
274. onding requirements will not be exported importer 4 0 Figure 246 Export Wizard step 2 Results for found modules will be exported results for not found modules will be skipped If a requirement is covered by more than one test case a unique result will be built according to following rules for description of test results please refer to 3 1 4 1 5 e not executed if all test cases are not executed e passed if all test cases are passed e failed if at least one test case is failed e blocked if no test case is failed and at least one is blocked Page 194 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e not completed if at least one test case is passed and all others are not executed e not implemented if at least one test case is not implemented stronger than on hold e on hold if at least one test case is on hold When the export is finished the user will be informed via message box TEMPPO Z Test suite successfully exported to Doors Figure 247 Message box export finished The Export can be canceled at any time by clicking the cancel button in the progress monitor Progress P Starting server Pad Cancel Figure 248 DOORS Export progress monitor The User is asked for confirmation then and if he confirms the export is stopped Cancel 93 Do you really wank to cancel the import process Figure 249 Doors Export confirm cancel
275. one result and optionally set the checkbox Overwrite existing results and after clicking Apply all test results are set If other users have locked test cases it is not possible to set the result of course You will be informed if results couldn t be set Page 87 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Set Result s E x Set Resut s to Cc passed not executed blocked C not implemented on holed O Overwrite existing results Apply Close Figure 99 Set Result s If a test case contains no test steps it remains not executed 3 1 4 2 Pausing and Continuing Test Execution If there are a lot of test cases you will want to pause test execution and continue at a later time TEMPPO Test Manager allows you to close your test suite any time you like Later on you can reopen it by activating Test Execution gt Open The dialog shown in Figure 100 will be displayed This dialog also shows the version tree extended by the test suite beneath the version where it was created During the opening process the adequate version of the test structure is loaded automatically Fi Open Test Suites E x Notepad RTF Import with TCs Tree style ra Wersions only EAA A Test Suites for W11 2012 02 16 le v1 1 1 editable version A Test object Version XYZ R001 16 02 2012 Versions and Labels A Test object Version XYZ RCO 16 02 2041 2 A Test object Version Y
276. op edit mode of current table cell lt ESC gt stop edit mode but changes are lost lt TAB gt lt Shift gt lt TAB gt jump to next previous table cell only if not in edit mode LT move one test step down up lt Ctrl gt lt TAB gt leave test step table So if you want to edit test steps without using the mouse you have to proceed like this lt F2 gt start edit mode Make your changes in the current cell lt F2 gt stop edit mode lt TAB gt jump to next table cell lt F2 gt start edit mode and so on 3 1 3 1 5Adding more columns For creating test steps you have 3 fixed columns Instruction Input and Expected Result In test projects it is sometimes necessary to add more columns for test steps Page 53 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad a joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test 01 H P H gt E Mo fiter lA Notepad RTF Import with TCs gt E 1 introduction c 2 General description of the product EF 8 3 Detailed description of the requires pope A 3 41 Scope of delivery pen a 3 2 Sequences scenarios of in a 23 3 User goals 5 ra 3 4 Required functions of the pri E 3 4 1 File Administration EL 3411 New o B New file opened no changes Locked by Testmanager tc536
277. orizontal bar chart e Horizontal bar chart 3D e Line chart e Stacked horizontal bar chart e Stacked horizontal bar chart 3D e Stacked vertical bar chart e Stacked vertical bar chart 3D e Vertical bar chart e Vertical bar chart 3D With the radio button Orientation you can display the description of the x axis either vertically or horizontally The data can be switched from absolute to relative and vice versa Using the checkboxes Results the chart can be customized By pressing the button Save As the chart can be saved as jpg or png file Page 111 User Manual Edition March 2014 chart FA Data Test object Version XYZ RC01 Test object Version XYZ RC02 Test object Version XYZ RC03 N Test Results 0 Test object Version XYZ RCO1 Test object Version XYZ RCO2 Test object Version XYZ RCO3 Test Suites E failed E passed M not executed TEMPPO V6 0 Description of Use Test Suite Selection Test suite analysis depending on fitter settings Press Select Test Suites for choosing test suites and setting filter Value Components req6s4 req 35 Components IN req683 req634 req685 Figure 131 Text Execution Progress Filtered Chart If you activate the tab Data the values are displayed as table and be saved as CSV file Page 112 User Manual TEMPPO V6 0 Edition March 2014 Description of Use E cren E vaa v Result Test Suites Test object Ver
278. osninaneensacsarenseranonnanseore 254 5 7 1 Using a license server on a computer with several network interface cards 255 Ord TEMO aiie ceceelnste ation nen eee nee atten nel heed rela nial 256 6 2 GONMGUTAUION roria T A eeammanesae et eee eeiae tenes 257 6 3 IMPDO JUNICLESE CASES aeriana irose r AE ar 258 Gad Description and Stop Snairnani ienaa a NAAA TEA 258 6 3 2 References to JUnit test CASES ssssssssssnessrnrsernrnnrurrnrunrnrnnne 263 6 4 Update JUNIE test CaSe Suonannnsiriver enira a N TEANA 265 6 4 1 DESERIPTHOM ANG Steps renne eao a aaa 266 6 4 2 References to JUnit test CASES ssssssssssnesernnsernrnnrnrrnrsernrenne 270 Oso TEST EXCCULION scanictcieicinat a E r E ar 270 OD Desceriptionmand Steps eaaa o a aa 270 6 5 2 Interpreting the Test ResultS ssssssnssnsssnnsnsnnsnsnrnnennrnrsnsnrnnnn 212 650 KNOWM ITSSUCS raae an a a a a 273 7 TEMPPO Designer IDATG vicisicvecstiisiwacivsnaeecddesscadvesvseesdtesiwecsisuneanua 275 Z t Greatng Task Packages aicina aA A A 276 7 2 DESIOM CSU CASES oec E E a TEETE 277 Jeo Updating Test Cases oranin TA A A A ATA 280 7 4 Restore Designed Test CaSe S sssssrrsrsrrnrrrrsrrrrrrrnrrrrnrrrrererrrrenan 280 S C mmand LING wiesissracincctanenitanenensiaadieaiaedae a aaa 281 9 PIUQ INS inea 283 9 1 Plug in Version Change Listener ssssssssssssnnsssnrnnnnrnnrnnsnesnrnrnnnn 283 DO Enteratu re aa a 284 11 TOMS ia a a a aE ne a i 285 12 AbDbDrevidtio N
279. ost and a later update won t work properly Page 263 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fi TEMPPO Testmanager Demo Notepad E Ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Helg Test Structure JUnit System Test v1 SE 1 Framework Tests 5 1 1 junit tests extensions Extension Test General Attributes Details Requirements History Plan Hkg 1 44 test RunningErrorinTest Setup junit t say 1 1 2 test Setup Error In Test Setup junit tes ID pres 2 junit tests extensions Active TestTest ay 2 1 testActive Test junit tests extension T Ry 2 2 testActive RepestedTest0l qunittests Mame junit tests extensions Extension Test T 1 3 junit tests extensions Repeated Test Test dy 1 3 1 test Repeated Once funit tests exten why 1 3 2 testRepeated More Than Once funit t Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 28 oy 1 3 3 test RepeatedZero junit tests extens Why 1 3 4 test Repeated Negative unit tests ex Owner Testmanager Updator Testmanager Type Test Package Humber of TCs 2 Test Category a Description parted by TEMPPO tror JUnit Suite jUnittests extensions AllTests Lock Apply Discard Figure 341 Step 5 Names of test packages JUnit test suites Naming of test cases A JUnit test case is implemented as a method of a sub class of TestCase and usually has a name starting with test The test
280. otepad RTF Import with TCs Fb 24 Introduction HHL 2 General description of the product General attributes Details Requirements History Pian E 5 3 Detailed description of the required prod ll 3 1 Scope of delivery ID ftp562 a 3 2 Sequences scenarios of interactic i 3 3 User goals l Pertormancse sd 5 3 4 Required functions of the product Mame Performance E 33 4 1 File Administration i EH 59 3 4 2 Edit Functions m 3 4 3 Print Functions Created 15 02 2012 16 45 57 Updated 16 02 2012 09 55 20 23 4 4 Search Functions H E3441 Find oon 3 4 4 2 Replace Number of TCs 0 Owner Testmanager Updator Testmanager Type Test Package Oi bei 345 Help System H 23 5 External interfaces of the product Test Category Performance Test 2 a 3 6 eal amie aa required Description This section describes the features which determine 2 Resource the speed of the product required values Standard 4 Security formulations such as rapid response times are A Safety required are to be avoided Exactvalues should best 5 Portability be Used 6 Reliability A number of examples of speed features include 7 Maintenance Real time time sharing batch 5 Reuse Response times 3 gas 288 nd p p Startup times Pecricalors TOF proje manageme Th roughput rate 5 Obligations of the client iui RAs tinn LB Literature i E 7 Annex T Figure 29 Complete Test Structure with Tes
281. oups of test cases cannot be divided flexibly no statistics can be provided automatically etc TEMPPO Test Execution Management Planning and rePorting and Organizer was developed to make the test process and test management easier and to provide methods for test case design and development as well as test case execution and integration of test automation tools TEMPPO consists of e TEMPPO Test Manager the test management application e TEMPPO Requirement Manager the requirement management application e TEMPPO Designer the application for test case and test data generation e TEMPPO Administrator the application for meta data maintenance e TEMPPO Manager the application for database migration The main parts of TEMPPO Test Manager are Editing and administrating automated and manual test cases including version control Integration of automated test case execution with WinRunner SilkTest TestPartner QuickTest Professional Ranorex or any other tool that supports a command line interface Flexible manual test case execution even with unplugged notebooks Professional analysis statistics and reporting This manual described the way of working with TEMPPO Test Manager Page 8 User Manual TEMPPO V6 0 Edition March 2014 Introduction 2 Introduction When we talk about testing we consider a test case to be the basic unit of discussion A test case is defined by 1 a descriptive name e g Create n
282. pe OOO Dama e rrin expected Actimimege aoua R Sut EE 3 4 4 Search Functions ff Unbenannt Edit Hd j save changes an ie win i 9 Datei Bearbeiten F A 4411 ind up D 3 4 4111 Cases E 3 4 4112 WinRur NE 3 4 4 1 1 3 QuickT Speichern E 3 4 4 1 1 4 Test Pe Speichern unter E 3 4 4115 UAI no e A Seite einrichten Drucken Beenden Messagebox Nd Editor Pane 2 click cleared Untitled Notepad in title S Look Apply Discard oF Figure 83 Manual Test Execution Test Step Results Test case results are calculated by accumulating test step results So a test case iS fil not executed if all test steps are not executed initial result lil passed if all test steps are passed W failed if at least one test step failed fil blocked if no test step failed and at least one is blocked W not completed if no test step failed or is blocked and at least one is passed not implemented if at least one test step is not implemented stronger than on hold Gi on hold if at least one test step is on hold Test case results are displayed within square brackets following the test case name Page 78 User Manual Edition March 2014 TEMPPO V6 0 Description of Use Fi TEMPPO Testmanager Demo Notepad ol x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 v1 1 1 3 Detaile
283. pected to be an instance of junit framework TestSuite Performance of removing obsolete test cases When a larger number more than 10 of obsolete test cases was selected for removing in the Update wizard you may experience a delay of more than 30 seconds after finishing the wizard dialog Malicious JUnit test cases Executing a malicious test case may have a negative effect on the TEMPPO application which runs in the same VirtualMachine as the JUnit test execution Currently no means are provided for setting an execution timeout or to manually cancel the test execution Reloading JUnit classes Once the unit test classes were loaded by the Java VM e g when they are executed they will not be reloaded until TEMPPO is restarted Classpath for JUnit test cases The classpath containing the JUnit test cases can only be set once for each TEMPPO session and not separately for each test structure or TEMPPO project Page 273 User Manual TEMPPO V6 0 Edition March 2014 JUnit If the classpath contains two class files with the same fully qualified name the file with the newest build date will be loaded Anonymous inner classes By statically creating the tests using anonymous inner classes that are not public the tests from this suite will not be executeable by TEMPPO With a JUnit TestRunner this construction works because there JUnit suites are executed as a whole whereas TEMPPO tries to instantiate and execute each test case by itself
284. ple Add junit samples money Mon Jy tetMoneyBagEquals unit samples money Mor Jy testMoneyBagHashQund samples money Mor Jy testMoneyEquals jund samples morty vero gt Figure 351 Step 5 The result of the update wizard 6 4 2 References to JUnit test cases The structure of test packages and test cases as well as their names are the same as with the import procedure Updating behaves in conformance with importing and relies on the naming patterns described above 6 5 Test Execution 6 5 1 Description and Steps Execution allows you to run the JUnit test cases from TEMPPO and to collect the test execution results in the TEMPPO database for further analysis Like any other automated test cases you can execute JUnit test cases by creating a test suite and running the selected test cases or whole test packages from context menu or menu Test Execution Run automated Page 270 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fi TEMPPO atw108s2 Unit extension tests n Bio a Project Test Structure Edt Test Execution Evaluation Took Windows Help Test Suite Sample JUnit execution V1 1 1 Uni Samnpes Vector lest Owner atwi lis Createct 10 12 2002 14 21 01 Be unt samples money Money Test Type Test Package Test Category z Descriptio Figure 352 Executing JUnit test cases Running a JUnit test case involves three levels of execution 1 TEMPPO where the JUnit test case class is instantiated an
285. possibility of copy and rename copy an existing UDA with or without values and rename it is offered Page 239 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi TEMPPO Administrator Testmanager _ Oo x Database bo Roles E Users Metadata LA Projects Lacks E License Test Levels Test Categories H Attributes E3 Uploads i Requirement Structures E User Fields L X fs fa Name Copy and rename Crested Attribute Type Creation Type J Affects Architecture Testmanager 14 02 2012 14 54 30 Requirement imported Testmanager 14 02 2012 14 54 30 Reguiremernt imported Testmanager 16 02 2012 11 22 20 Test Case manually created Testmanager 14 02 2012 14 54 30 Requirement imported Testmanager 16 02 2012 14 12 37 Test Result Test Suite manually created Testmanager 16 02 2012 11 11 40 Test Case manually created Testmanager 16 02 2012 11 10 33 Test Case manually created Testmanager 14 02 2012 14 54 30 Requirement imported Testmanager 14 02 2012 14 54 30 Requirement imported Testmanager 16 02 2012 11 11 08 Test Case manually created atw112h9 14 02 2012 09 22 13 Reguiremert manually created Testmanager 14 02 2012 12 25 26 Reguiremert manually created Testmanager 14 02 2012 09 13 34 Requirement manually created Testmanager 14 02 2012 14 54 29 Requirement imported 2 Test location Testmanager 16 02 2012 11 13 08 Test Case manually created window 7 client Testmanager 16 02 2012 14 13 39 Test Re
286. project test structure test package test case test suite that have the same owner as the project and that are not locked by other users is changed to the new selected one If a test structure was selected and the move ownership button is pressed the test structure the test packages and test cases with the same owner as the test structure are changed to the newly selected one If a test suite was selected the owner of the test suite is changed 5 5 9 Freeze Unfreeze lolx Database 9 Roles E Users 8 Metadata LA Projects Lacks License oe x e 2 la H Demo Notepad Ee Example for versioning Fe Link test cases to requirements ce Notepad generated MQ Notepad RTF Import EA Notepad RTF import with TCs Bet Eb Test Suites for W141 2012 02 16 Fl editable version A Test abject Version 2 R001 16 02 2012 Test object Version xY RCO2 16 02 2012 A Test object Version 2 RCO3S 16 02 2012 A Test abject Version V2 RCOS COPY 16 02 2012 tis O bg edabe version ee Notepad System amp Acceptance Test I User documentation S Mew Test Structure i editable version Figure 325 Freeze Unfreeze From the development process point of view it may be necessary for a test manager to freeze a test structure or a test suite for the purpose of providing and keeping it read only In general test structures and test suites can be frozen Page 251 User Manual TEMPPO V6 0 Edit
287. quences Scenarios fil 3 2 41 Sequences scer iser ety a el Requirement Structure __ Version 3 3 User goals _Path g q q i E 3 31 User goals Func_reqe6 Mew Notepad WH All E Inherit oe 3 4 Required functions of tk Mew implemented EHE 3 4 1 File Administratior requirements S411 New o 1103 41 11 New 1 2 Open fil 3 44 21 Open SE 3 4 1 3 Save ae F Figure 9 Generated Test Structure 3 1 2 2 20pening a Test Structure Using Test Structure gt Open will display the dialog in Figure 10 This menu item is only enabled if a project is opened Exactly one item can be selected and will be opened after pressing the button Open Additionally a test structure version see 3 3 7 can be selected if a non latest version should be loaded Page 19 User Manual TEMPPO V6 0 x Test Level S Link test cases to requirem Testmanager 14 02 2012 11 14 46 System Test vA editable version Notepad generated Testmanager 16 02 2012 15 07 System Test V2 editable version Notepad System amp Accepta Testmanager 15 02 2012 13 26 40 System Test WI W111 editable version V2 editable wersion nen Figure 10 Open Test Structure 3 1 2 2 3Reopen a test structure A faster way to open a test structure and the according project as well is to use Test Structure gt Reopen which displays the 4 last opened test structures It will only be enabled if no project is open
288. quirements History Attributes TR Previous Results Plan Execution History File Administration Expected Bug __Actionimage Actual R 3 4 1 1 New a P Unbenannt Ed cleare Datei Bearbeiten ffnen Speichern Speichern unter 3 4 1 1 1 New file opened no changes failec E 3411 2 New ile opened changes passed Search Functions File New pick Seite einrichten Drucken Beenden Untitled Notepad im title baw http Vatinzp1 Oqa 2849 bugs_sitemppo_internal show_bug cqi7id 5626 Lock Apply Discard 4l i EZA anh Be y Figure 97 Hyperlink to bug 3 1 4 1 10 Automated Test Execution For starting an automated test execution you have to select the test package which contains the test cases to run and activate Test Execution Run automated or the corresponding item in the context menu see Figure 98 TEMPPO Test Manager will then sequentially invoke the proper automation tool for each test case and fetch the result obtained by the tool after the automated run Page 86 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Before running automated tests the automation settings in TEMPPO s administration tool see 4 must be configured 10 x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Helg Test Sute Test object Vers
289. r The login name must be specified in the form of Domain User By clicking Connect the TEMPPO Administrator will establish a connection to the LDAP server If the connect to the LDAP server was successful the buttons Import users and Synchronize users are enabled You can import users by clicking the button Import users By clicking the button Synchronize users you can synchronize the existing TEMPPO users with the LDAP server Page 231 TEMPPO V6 0 TEMPPO Administrator User Manual Edition March 2014 5 3 1 2 Importing users from LDAP x Search Last Mame FO First Mame FO Login FO Windows group FO Department PSESESMEC nn ss SOSSCSCisS Location ine Country P Clear Department 1 Aigner Judith atw1z2083 judith aigner si PSE SES MEC L Linz AUSTRIA 2 Fuchs Clemens atwiDBs2 Clemens Fuchs PSE SES MECL Linz AUSTRIA 3 H inzl Thomas abwiOby1 thomas hain PSE SES MEC L Linz AUSTRIA 4 Hametner Andreas atwl ci andreas hametn PSE SES MEC L Linz AUSTRIA 5 Hametner Andreas akworeg pse Ydo core te PSE SES MEC L Linz AUSTRIA 6 Hampel Michael ati 13yv4 michael hampel PSE SES MECL Linz AUSTRIA 7 Hofmann Roland atwil4cs hofrannroland PSE SES MEC L Linz AUSTRIA 5 Holzlechner Manfred atw zsz manfred holzlec PSE SES MEC L Linz AUSTRIA J Kronegger Martin atw12903 martin kronegge PSE SES MECL Linz AUSTRIA 10 Mayrbaeurl Max atwi0sFS max mayrbaeurl PSE SES MECL Linz AUSTRIA 11 Moritsch Karin
290. r Exclusive edit mode Figure 251 Results for requirements 3 3 15Task lists After Test Structure gt Apply requirement updates a task list is generated It can be viewed via menu Test Structure gt Task Lists All the changed new and deleted requirements are listed The lists are represented by a tree structure Each list consists of one or many entries All Page 196 User Manual TEMPPO V6 0 Edition March 2014 Description of Use entries are marked as open the first time they are stored in the DB If the user clicks an entry the test case or test package of this entry is selected in the test structure window tod 71002 Blue displayed route contain te te41717 Blue displayed route contains Type Test Case ID te41002 Requirement ID 1450 Requirement Name Blue displayed route contains white arrows after each mancever Description TC will be marked as obsolete Tester Closing Date OK SINCE Version Reason of Creation Deleted Requirement Lock _ appt Discard Test Structure JADIS Phase 1 M d b H gh BR nofiter te41717 Name Current car position drive roundabout Owner Schlosser Dietmar Updator Created 27 08 2010 14 24 14 Updated 15 06 2011 09 26 18 Type G Manual Automated Test Case Test Goal SS lt Figure 252 Task due to deleted requirement Task lists ca
291. r Manual Edition March 2014 6 JUnit TEMPPO V6 0 JUnit Since TEMPPO V3 0 it is possible to manage and execute JUnit test methods with TEMPPO The following paragraphs describe the scope of the JUnit extension 6 1 Terms Testing terms are used differently in the JUnit community and in TEMPPO In order to clarify the meanings the following table serves as a reference Test The entire tree of test structure packages and test cases A hierarchy of test packages test suite Test package and test cases test suite A subset of test cases from the test structure intended for execution in a certain results test Contains recorded test test case A set of test inputs execution conditions and expected results developed for a particular objective Passed Test result indicating that the actual output matches the expected Failed Test result indicating that the actual output does not match the expected Blocked Test result indicating that an error or exception occurred during test execution no comparison of actual and expected output was possible Defined in JUnit by a suite method in an arbitrary class b the list of all test methods in a sub class of TestCase not exactly the same meaning Test suite as above not exactly the same meaning Test a method in a sub class of method TestCase Naming convention starts with test Failure return code of test method invocati
292. rement If these conditions are not fulfilled the test case cannot be saved For details see chapter JeDa In the tab Test Result Template the test manager configures result attributes for test case If a tester records a result and a test result template is activated he has to add a value for the mandatory attribute For details see chapter 5 5 4 After pressing the button OK the user is asked if he wants to assign immediately meta data If the user presses Yes Figure 323 is shown Page 15 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Project Properties X General G Roles Test Case template Test Result template mE New Project Created 15 02 2012 12 56 16 Mandatory history cormert Owner Testmanager Type TEMPPO Project Description This projectis used for user documentation eres Figure 2 Project Properties TEMPPO Administrator 3 1 2 1 2Opening an Existing Project F Open Project x Name rer rested Demo Motepact Testmanager 14 02 2012 10 50 01 User documentation Testmanager 14 02 2012 11 08 07 eres Figure 3 Open Project When activating the menu item Project gt Open the window Open Project Figure 3 with project name owner and creation date is displayed Exactly one project can be selected and is opened by clicking the OK button The name of the project is shown in the title bar of the main window see Figure 4 Cancel
293. reviewed and can be used for test case execution Approved This state is optional and mostly used for automated test cases Sometimes a test case is ready for execution but fails due to errors in the test script If a test case is executable as specified in its test steps test script it gets the state approved Additional test levels can be defined for using one test structure for different test levels For example if you have a test case for the standard test level System Test defined when creating the test structure see 3 1 2 2 1 and want to use the test case in a test execution for an acceptance test you can achieve this by adding Acceptance Test as an additional test level for this test case For the execution of the acceptance test you would then specify this test level as a filter criterion for your test suite see 3 1 4 1 Additionally you can set attributes specified in the Meta Data Editor see 5 3 which can also be used for creating a test suite By specifying a sub string in the Find field you can easily navigate to the attribute s to be related to the test case Multi select allows moving several values to the right part of the window see Figure 39 x Device type zi value tribute l ED wi A Milestone a car c R Offshore 4 Test location 0 Value tribute EF windows 7 64 bit Platform Device type J ED yes a Regressiontest EF CAR F A002 Device type al EF CAR F A003
294. rios of interactions with the environment User goals E a Required functions of the product File Administration Fl New D New file opened no changes D New file opened changes 7 Open a Save L exit J Edit Functions J Print Functions J Search Functions Find E Find up Di Case sensitive x Determine the logical expression 6 Remove test cases manually TEMPPO Test Suite Generator lt lt Prey Next gt gt Finish Cancel Figure 64 New Test structure pre selection whole test structure Bj Test Suite Wizard Steps Test structure pre selection Introduction Select test packages hold lt STRG gt and lt Shift gt for mutti select Choose creation mode Enter test suite name 4 2 3 Select nodes or subtrees 4 5 Notepad RTF Import with TCs SJ Introduction gA General description of the product 5j Detailed description of the required product features Z Scope of delivery E Sequences scenarios of interactions with the environment ey User goals Required functions of the product File Administration a New New file opened no changes Fl New file opened changes el Open Save L exit J Edit Functions h J Print Functions J Search Functions moe fr inc EH Find up Di Case sensitive x Determine the logical expression 6 Remove test cases manually TEMPPO Test S
295. rmat HTML Microsoft Word Microsoft Excel Preview _ Cancel Figure 150 Report of several test suites General Page 130 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 1 5 6 3 Chart Settings In the charts settings area you can customize the charts added to your report which represents the data of your test structure or your test suite in a graphical Way s It is possible to add more charts to your report by right a ae mouse click on chart and activate Add new chart By de ee selecting a chart right mouse click and activating Remove Rename chart chart a chart can be removed except the last one By Chart selecting a chart right mouse click and activating Rename chart or double click a char can be renamed Data Selection Choose units for the y and x axis and optionally a value subdivision Y axis sum of test packages sum of test cases default or sum of test steps can be displayed X axis test packages of first level designer date priority situation state type test levels and result only for test suite report can be applied If date is selected the time period considered must be specified Furthermore the time unit can be adjusted day week month year Group by is used for subdividing the values displayed on the y axis The selection possibilities are the same as for x axis Chart The following charts are available Horizontal Bar Chart Horizontal B
296. ro a Test case name Test package length name a name is generated automatically New Test Package New Test Case No Message is shown b User defined attributes Message is shown The user can continue the import invalid element ignored or stop import and return to the previous state The requirement structure can t be A message is shown The name of the found in the database requirement structure which released an error is written in the error file If the requirement structure doesn t exist in the database you have to import it before importing the test structure If the name of the requirement structure isn t defined correctly in the input file you have to correct it Now try it again A requirement can t be found in A message is shown see Figure 22 database The user defined id of the requirement which released an error is written in the error file Please correct the name in the input file and then try it again Page 29 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Figure 22 Information message error with requirements 3 1 2 2 7 2 Special cases Name of test package test case or Unique name is generated like 1 user defined ID exists 2 No message is shown See Figure 23 Test level category attribute name or Object is created No message is values doesn t exist shown Attribute name exists new value in Value is added to attribute XML fi
297. rrent selected image is copied to the clipboard e Reference If you activate the menu Reference you can create a reference to an image which is already uploaded in the database This function is used if you have to paste upload the same image several times Page 55 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Test Step Cells Mukiline table M Ono for refreshing the cell content when changing the column width i Newsboardl sz Height of muiline rows during editing defaut is 52 ko Test Suite Database mage columns fae ia Ja Waximum width of thumbnail of a user defined image field if it s 1 it s ignored i cile Te in Runner Ja Maximum height of thumbnail of a user defined image field i it s 1 it s ignrored H Universal File H Universal socket gt QuickTest Pra Test Partner HTEMPFO Designer DATS i Ranorex El Commands p Men Command i Javas El Change Management H Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Cancel Figure 54 TEMPPO Test Manager settings For very large images a viewer is integrated which can be started by double clicking the image See Figure 55 xi serol Scale iol Datei Bearbeiten Format Ansicht 7 Strg h ffnen Strg c Speichern Strg 5 Speichern unter Seite einrichten Drucken Strg P Beenden Figure 55 External viewer 3 1 3 1 7 Automated test cases TEMPPO ca
298. rted from DOORS or RequisitePro Page 243 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi Properties of Property x General Details Property Created 14 02 2012 14 54 30 For Use of 7 Test Case Owner Testmanager in Test Package Type Attribute Test Suite D Test Resutt m Reguiremert Description eres Figure 314 Properties of attribute 5 4 7 User Fields Fi TEMPPO Administrator Testmanager _ Oo x Database ka Roles E Users Metadata LA Projects B Locke E License Test Levels By Test Categories ot Attributes ES Uploads tf Requirement Structures CT User Fields Action image Testmanager 15 02 2012 16 14 56 Image Test Structure Actual screen shot Testmanager 20 02 2012 15 28 06 Image Test suite Comment Testmanager 15 02 2012 16 15 13 Text Test Structure Figure 315 Metadata User Fields For test steps new columns can be defined for test structures and test suites When pressing the button New see Figure 316 you can select between a text and image column for test structure or suite Page 244 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi Properties of New Entry X General gii hew Entry Crested 13 10 2010 11 13 29 Owner Testmanager Type Additional Test Step Column Type Usage Text Test Structure Image Test suite Figure 316 Additional test step column 5
299. ructure filter and the logical expression of a test suite Planned test execution time and Planned Tester can also be reported for test cases whereas for test packages only Planned test execution time is applicable Both attributes can be viewed in test suite that offers the possibility to enter an Actual test execution time which can be applied to latest version as a learned lesson For details see chapter 3 1 4 1 5 2 e Execution History Page 49 User Manual TEMPPO V6 0 Edition March 2014 Description of Use This tab shows only executed results over the complete version tree of the test structure For each test suite the following attributes are displayed Test Suite Version Result Bug ID Tester Tested Plan Execution History 16 02 2012 15 11 02 Test object Version XYZ RCO1 16 02 2012 15 11 23 07 03 4012 14 59 15 Figure 46 Execution History only executed results lf you want see all information for this test case over all test suites you have to activate the button Load Information for not executed test cases see Figure 47 General Attributes Test Steps IEI uion t00 Requirements History Pian Execution History Test object Version V1 1 1 editable 16 02 202 15 11 02 XYZ ROOS version V1 1 1 editable version V1 1 1 editable version V2 1 1 editable version 16 02 2012 15 11 23 O 03 2012 14 59 15 Figure 47 Execution Histo
300. ry executed and not executed 3 1 3 Test Case Implementation The implementation phase covers the tasks of Implementing Test Steps Reworking the Test Structure implementing test frameworks not covered by TEMPPO Test Manager implementing test scripts for automation not covered by TEMPPO Test Manager 3 1 3 1 Implementing Test Steps You continue your work in the tabs Test Steps and Automation of the test case tab 3 1 3 1 1 Preconditions and Postconditions You have to consider which preconditions must be fulfilled before the test steps can be carried out during test execution You specify this textually in the precondition table of the tab test steps Additionally you can see the preconditions defined in the parent test packages Additionally you can also define postconditions which mut be fulfilled after test steps execution You specify this textually in the postcondition table of the tab test steps You can see the postconditions defined in the parent test packages too Page 50 TEMPPO V6 0 Description of Use User Manual Edition March 2014 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help 5 x Test Structure Notepad RTF Import with Tes System Test W1 H 4d gt HW Eh no fter AL Notepad RTF Import with TCs H 1 Introduction H Ea 2 General description of the product 8 3 Detailed description of
301. s je E 3 7 Hardware and software Spe E 3 8 Product users of 4 Detailed description of the require E 4 1 Scope of delivery i Ss 4 2 Sequences scenarios of i S 4 3 User goals 2M 4 4 Required functions of the pi BY 4 41 File Administration E 4 4 1 1 Windows Login D Eee BE 4 4 1 2 New io beim 4 4 1 3 Open i io Gil 4 4 1 4 Save E 4 4 1 5 Exit o E Gi 4 4 2 Edit Functions EE 4 4 3 Print Functions Gi 4 4 4 Search Functions B i E 4 4 5 Help System 4 5 External interfaces of the pi General Attributes Test Steps an Date 20 02 2012 10 26 57 20 02 2012 10 26 57 20 02 2012 10 53 04 20 02 2012 10 56 57 07 03 2012 14 51 01 07 03 2012 14 51 01 07 03 2012 14 51 01 Testmanager Test Level Test Level 07 03 2012 14 51 01 07 03 2012 14 51 01 Testmanager Testmanager UDA Attribute Platform Windows 7 Acceptance Test System Test add Device type add CAR F 004 Type Validation gt change Verification 07 03 2012 14 51 01 Testmanager UDA Regressiontest add no 07 03 2012 14 51 01 Testmanager UDA Test location add Offshore 07 03 2012 14 51 01 Testmanager UDA Milestone M1 add 07 05 2013 13 46 22 Testmanager General User defined ID 07 05 2013 13 46 38 Testmanager General Na
302. s E Atomation Requirements History Plan Execution History E amp 3 Detailed description of the requirec i pened el Ne struction 3 2 Sequences scenarios of in n n i 3 3 User goals File New pick fA Unbenannt Editor Editor Pane cleared E 3 4 Required functions of the pre Datei Bearbeiten Format Ansicht EP 3 4 1 File Administration TE Stra N B moti H E ffnen Strg 0 Speichern Strg 5 3 441 12 Net le o 0 i w s fie l Speichern unter 0 3 4 1 2 Open l 3 4 13 Save Seite einrichten 3 4 1 4 Exit Drucken Strg P 1 3 4 2 Edit Functions _ o EE 3 4 3 Print Functions Beenden EH 3 4 4 Search Functions 3 4 4 1 Find 3 4 4 1 Find up i fi 3 4 4111 Case EJ 3 4 41 1 2 Quicl B 5 4 4 1 2 Find down 2 Upload 3 4 4 2 Replace i 3 4 5 Help System X Delete BAN 3 5 External interfaces of the pri aste Ctrl i B 3 5 1 User interfaces PER i B E n paste mage Reference R Figure 53 Upload new picture e Upload If you activate the menu Upload a file open dialog opens where you can select a file jpg png gif which is uploaded to the database e Delete If you activate the menu Delete the image is deleted e Paste If you activate the menu Paste the screen shot which is currently in the clipboard is pasted to the cell and also uploaded to the database The menu is disabled if the clipboard is empty e Copy If you activate the menu Copy the cu
303. s always just a view of the underlying test structure in the activated version Only test cases are visible that fulfill the criteria defined in the Page 68 User Manual TEMPPO V6 0 Edition March 2014 Description of Use logical expression Furthermore test packages where no test cases are selected at all are not displayed Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version 2 RCO1 W1 1 1 H dab HM EE no fter j Test object Version lt 2 RCO Bfm 3 Detailed description of the required g EAA 3 4 Required functions of the prod Requirements History Attributes TR Previous Results Plan Execution History A 3 4 1 File Administration General Attributes Test Steps EJ Automation ERG 3 411 New i nett 2 New m aaa er Instruction Expected Actionimage actual R 8 3 4 4 Search Functions E 3 4 4 1 Find E t 3 4444 Find up fl 344144 Cases f 3 444142 WinRur fF 3 4 4 143 QuickT LEE 3 4 4 14 4 Test Pe B ERR REI Test Structure Motepad RTF Import with TCs System Test 11 1 1 M d4 b H GP EE wo ter oe 3 4 4 4 Exit 3 4 2 Edt Functions 3 4 3 Print Functions E a 3 4 4 Search Functions EM 3 4 41 Find EF a 3 4 4 14 Find up Db be fi 34 41 14 Case sensitive a 3 4 4 1 1 2 WinRunner Check Stat HoE 3 4 4 11 3 QuickTestPro Test case 3
304. s it by pressing the button Cancel in the window Connection Status it is possible to avoid data loss by storing the current TEMPPO Designer IDATG project as XML file To restore this data and transfer it to TEMPPO the menu item Restore Designed Test Cases can be used This will cause TEMPPO Designer IDATG to open to load the XML file and to synchronize it with the task package structure received from TEMPPO By pressing Save the data can be transferred back to TEMPPO Page 280 User Manual Edition March 2014 TEMPPO V6 0 Command Line 8 Command Line TEMPPO offers following command line parameters Remark No blanks are allowed between commas open lt project test structure version test suite gt run lt project test structure version test suite gt exit export_teststructure lt project test structure version export file gt export_testsuite lt project test structure version test suite export file gt check_locks profile lt user password gt file lt file gt results lt xml file gt Separated list of values where the names for project test structure must be specified and TEMPPO is opened with the latest version of the test structure Optionally a special version and a test suite can be entered in order to open immediately a test structure version or a test suite Separated list of values where the names for project test structure version and test suite
305. s it can be configured that is it shown automatically after opening a test structure Since time is going on and newsboard doesn t poll user has to press the Refresh button to get the latest news Page 173 User Manual TEMPPO V6 0 Edition March 2014 Description of Use The display of newsboard can be configured by setting last login last hour last day last week or user defined If user defined is selected a date with calendar and text fields for time hh mm and the Apply button are editable If last login is selected the time stamp of user s last logout is chosen If a newsboard entry is activated the corresponding requirement is selected automatically except if one was deleted In the newsboard table the action new changed deleted requirement ID requirement name date of action and the person are shown Newsboard consists of 2 tabs lt name of test structure plus version gt and General The first one shows all activities new change delete on test cases and test packages in the current selected test structure version On the other hand General displays all other information New attribute assigned to the project changed attribute new attribute value new test suite new user new version If an item of newsboard is selected the corresponding one is also highlighted in the test structure if possible A deleted item cannot be displayed of course F TEMPPO Testmanager Demo Notepad E
306. s or subtrees E ENAT VAR P MAOR Test object Version XYZ RCO1 16 02 2012 Detailed description of the required product features E E Required functions of the product J File Administration E E New fi New file opened no changes not executed fi New file opened changes not executed J Search Functions 2G Find Find up E Case sensitive not executed nA pwn Determine the logical expression 6 Remove test cases manually Af QuickTestPro ed A fTest Partner Test case not executed A JUAI not executed TEMPPO Test Suite Generator lt lt Prey Figure 68 New Remove unwanted test cases Finish Cancel After clicking Finish the current test structure version V1 is checked in If you could open the version tree browser now you would encounter the following situation x oe Motepad RTF Import with TCs Edit Bevi EAHA Test Suites for W141 2012 02 16 I Check In W441 editable version boo editable worsion Activate id Werge Tree style Versions only Labels only Yersions and Labels ClearCase style Order ie azcending i descending Figure 69 Version tree after test suite creation Immediately after test suite creation three versions with identical test structures exist 1 2 latest and 1 1 1 latest The latter two of them are editable just the first one is checked in A test suite i
307. s the aim of testing the function Mev x GH General beUser defined ID tc536 ee Mame Mew file opened no changes i Owner Testeri Updated 2012 02 16 Type manual The test case purses the aim of testing the function Attributes Test Steps Tess pania EF Requirements bereqba7 Cancel V1 1 1 editable version El General description of the product EHGeneral User defined ID tp520 Updated 2012 02 16 i Lett Test Category This general description of the product being crea Gr Attributes TEMPPO V6 0 Description of Use _ Attribute Values Manna a Requi rements Requirements Figure 227 Compare test package differences 3 3 10Filter Users can see their test structures and test suites in a filtered way by creating and selecting filters i e for the purpose of hiding test cases that are not of interest All fixed and user defined attributes can be used to define a filter criterion Test structure filters are available for test suites Test Suite filters which are including result or tester are not available for test structures Page 181 User Manual TEMPPO V6 0 Edition March 2014 Description of Use TEMPPO Manager offers Personal and Project filters If the tab Personal Filter is activated all created filters are only displayed for the user A test manager may activate the tab Project Filter and creates filters that can be used for all project members Personal
308. s the first one is for searching in test cases and the second for test packages Both tabs provide the same features the only different between this two tabs is the different search content A test case in a test structure can be found via searching for e user defined ID e name e test goal e precondition e postcondition e test step columns instruction input expected e user defined fields A test case in a test suite can be found additionally by its tester s comment actual result and bug ID Only the text fields tester s comment actual result and bug ID can be replaced in test suites A test package in a test structure can be found via searching for e user defined ID e name e description e precondition e postcondition The search criteria can be specified using the wildcards 0 n arbitrary characters or and exactly one arbitrary character and is case sensitive The replace function searches for the test case and then the searched part will be replaced to the entered name Page 171 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Example You want to change the name of the test cases The part Test Case should be changed to the German name Testfall so you select Name in Search in and write in the text field for Test Case In the Replace with text field you write Testfall A searching direction can be chosen too The searching algorithm starts from the selected
309. se Test Levels P Test Categories aa Attributes Uploads tf Requirement Structures EF User Fields D x amp TEMPPO V6 0 TEMPPO Administrator loj x Gui Layout Test Maintenance Test Performance Test Portability Test State Based Test Task Based Test lability Test Schema Owner Schema Owner Schema Owner Schema Owner Schema Owner Schema Owner Schema Cwner Name mer rete 13 02 2012 13 04 07 13 02 2012 13 04 07 13 02 2012 13 04 07 13 02 2012 13 04 07 Reliability Test Schema Owner 13 02 2012 13 04 07 Resource Test schema Owner 13 02 2012 13 04 07 Reuse Test schema Owner 13 02 2012 13 04 07 Safety Test Schema Owner 13 02 2012 13 04 07 Security Test Schema Owner 13 02 2012 13 04 07 13 02 2012 13 04 07 13 02 2012 13 04 07 1507 2017 1 14 17 Figure 303 Metadata Test Categories Here you can add delete and view test categories When pressing l the window Test Category Properties is opened A name must be entered and user name and creation date are suggested automatically The same window is shown when applying El for editing the test category properties Fi Properties of New Entry xj General j New Entry Crested 20 02 2012 15 16 45 Owner Testmanager Type Test Category Description ores Figure 304 Test Category Properties 5 4 4 Attributes Attributes are applied to test cases test results and test suites They can be applied in addit
310. se test structures and test suites are analyzed and reports are created You may analyze any version of your test structure for switching to another test structure version refer to 3 3 7 3 1 5 1 Analysis The analysis feature is used to give you a quick overview about your test structure or test suite You create an analysis chart by selecting the node to analyze and activating Evaluation gt Analyse selected gt with current opened explorer project test structure test suite gt All In the Analysis dialog you can set values for X Axis and group values on the Y Axis The following charts for displaying the data are possible e Horizontal bar chart e Horizontal bar chart 3D e Line chart e Stacked horizontal bar chart e Stacked horizontal bar chart 3D e Stacked vertical bar chart e Stacked vertical bar chart 3D e Vertical bar chart e Vertical bar chart 3D There is also the possibility to save the chart as jpg or png file by pressing the button Save As Page 97 User Manual TEMPPO V6 0 Edition Figure March 2014 Description of Use 115 and Figure 115 show an analysis from a test structure and a test Suite displaying the number of test cases for each priority grouped by the state x gl Chart Data Test Cases M Axis state ba Group by WAE Chart vertical Bar Chart T ag 20 7O 60 50 30 20 Designed In Work Ready Ready for Review state
311. see 6 2 Test Case Selection Provides the hierarchical structure of test cases in the suite defined by the selected JUnit class Select those test cases that you want to import into TEMPPO Package Default Values Allows to set default values for all new test packages Test Case Default Values Allows setting default values for all new test cases Summary Shows a list of your choices from previous steps Here is a sample import sequence Page 258 User Manual TEMPPO V6 0 Edition March 2014 JUnit Fi TEMPPO Testmanager Demo Notepad f Project Test Structure Edt Test Execution Evaluation Tools Windows Help B TEMPPRO Designer CATG Uedate O x Figure 332 Starting the import procedure Fi Import JUnit Tests X Steps Introduction 1 Introduction z Select a JUnit test class f f 3 Select aset of JUnit test This wizard guides you through the steps necessary to import JUnit test cases into a TEMPPO cases test structure 4 Set package default values a eee ee Anew test case will be created for each imported JUnit test case A new test package will be 5 l created for each JUnit test suite reflecting the hierarchical structure of the imported JUnit test umm anm class Mote Updating is bated on name matching The generated names of the test cases and test packages should be preserved to maintain their relation ta the JUnit classes TEMPPFO Extension JUnit fe Frew Next EN Fin
312. sibility of recovering the test structure of the main line When pressing the merge button the following question will appear warning ee xl The merge will first check in the latest version in your main line and afterwards create a new latest version that is identical with your branch wersion Do you want to proceed Figure 221 Merge whole test structure If you proceed the version of the current branch version is copied to lastest version of the main line The current version applied label remains activated Currently there is no visual representation for merges in the version dialog like the merge arrows you would see in other CM tools On the other hand there is an individual merge that allows merging single test cases Page 178 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad p Oj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test W22 7 m Ej x SE S S E E Mo fitter ALI Notepad RTF Import with TCs E 1 Introduction m 2 General description of the product os 3 Detailed description of the required product f re 3 1 Scope of delivery ae a 3 2 Sequences scenarios of interactions v an ee Ea 3 3 User goals Ba 3 4 Required functions of the product ER 3 41 File Administration Ea 3 4 1 1 Mew o A 3 4 1 1 1 New file opened na c fi 3 4
313. sion 1 0 Plugin Name My First Plugin Plugain Versiton Ovi Plugin Author Muster Max Plugan Class temppo plugin api MyPlugin 9 1 Plug in Version Change Listener A TEMPPO plug in must implement the Plugin interface or one of its sub interfaces Plugin is the super interface for all plug ins It serves methods for basic plug in information and load and unload handling e g loading and saving plug in settings VersionListenerPlugin Is the interface for a concrete plug in which can be used It extends Plugin and serves as a hook for version change notification The plug in developer has to implement a class file packed into a jar file which extends VersionListenerPlugin This class file has to be implemented in the package temppo plugin api After starting TEMPPO the listener is registered and the actions of the plug in are executed when the version is changed in TEMPPO e g by activating another version of test structure by creating a new test suite Page 283 User Manual TEMPPO V6 0 Edition March 2014 Literature 10 Literature 1 Installation Guide TEMPPO V6 0 installation and startup guide March 2012 2 Glenford J Myers The Art of Software testing USA John Wiley amp Sons Inc 1979 ISBN 0 471 04328 1 Page 284 User Manual TEMPPO V6 0 Edition March 2014 Terms 11 Terms Administration unit This term denotes any object data that is managed in a configuration management tool Typical administrati
314. sions AllTests Lock Apply biscanu Figure 344 Starting the update procedure x Steps Introduction 1 Introduction 2 Select a JUnit test class oe i f ay Seleni nen intiena dees e AE a S to update JUnit test cases stored in a 4 Select obsolete TEMPPO test 5 ee Dac ae Cdies 5 Set package default values Welsch e j l The Update is based on name matching The JUnit test class will be searched for the names of the 6 Set test case default values ee La test packages and test cases stored within the TEMFFO test package you choose to update umm any TEMPPFO Extension Panama ex Prey West gt Finish Cancel Figure 345 Step 1 General description of the following steps Page 267 User Manual TEMPPO V6 0 Edition March 2014 JUnit xi Steps Test Class Selection Introduction Select a JUnit test class 1 Select the JUnit test class to update from 2 3 Select new JUnit test cases Pelem ihe cena lar 4 Select obsolete TEMPPO test cases Active TestTest AllMembers Supplier Test ih Set package default values BG Set test case default values junit tests extensions org juni tests experimental theories 7 Summary junit tests extensions org junit tests junit tests junit tests runner junit samples junit tests framework JUnit Classpath p ATemp_PVAtTeststellung PyAyunitd Mote Only classes that are inthe JUnit classpath can be se
315. st cases 5 Set package default walues with the JUnittest class 6 Set bert cone default values uni sampes ANT ests 7 Summat TEMPPO test cases 2 new test Cases will be added 1 obsolete test cases will be permanently removed TEMPP Extension Panama amon ae rms pu Page 269 User Manual TEMPPO V6 0 Edition March 2014 JUnit Figure 350 Step 5 The summary of the update wizard Fi TEMPPO atw108s JUnit extension tests Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Sample JUnit tests Module Test 1 H d gt W ame JLind test E E Al Jura Tests junit samples Vector Test Jy testCapacty junt samples VectorTest Jy testContains jiunit samples VectorTest General Jy testEiementAtguni samples Vector Test Neme Sample JUnit tests Jy tesiRemoveblement iund samples VectorTest Owner Mwi08s Jy testClone junt samples VectorTest Jy testRemoveAlgund samples WectorTest Crested 10 12 2002 13 41 07 BB junit samples money MoneyTest Teton A Jy testBsaghutpiiunit samples money MoneyTe Structur i Jy tesiBagtlegate und samples money Money Te Test Levet Tesi Ju lesiBeghotEquals junt samples money Money Jy testBagSimple Addijund samples money Mone Description Jy testBagSubtractijunt samples money MoneyT Jy testBagSumAdd und samples money MoneyT Jy testis Zero jundt samples money Money Test Ju tesiMiced Sim
316. stcondition is mandatory iw Test goal condition i mandatory gt Requirement IY Inherit requirements IY At least one requirement must be assigned User defined attriputes To Inherit attributes Attribute Mandatory Assigned default value Plan Planned tester No Planned tester Planned test execution time fo hla min 0 59 eres Figure 321 Test Case Template A Test Case template TCT supports you to create and update test cases in complete manner For a TCT you can define e Default values for the fixed attributes e g priority has to be In work if a test case is created e Mandatory fields user has to enter a test goal precondition postcondition Page 247 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator e Inheritance of UDAs and or defining UDAs as mandatory or with a default value e Inheritance of requirements and or linking at least 1 mandatory requirement e Default values for a planned tester and a planned execution time You can activate a TCT for the use case of creating and updating test cases but excluding the use case of just viewing locking unlocking test cases You can activate a TCT check also for viewing existing test cases E g if you activate the TCT after creating some test cases that do not fulfill the conditions and view them later you cannot click another test case without fulfilling
317. stmanager Updator Tester ad Paste Ctre T E Created 15 02 2012 16 45 50 Updated 16 02 2012 1712 24 o aste before o B Type Test Package ie d F ga Fe etc 2 ims Perr C 3 x Delete Delete alegory P Bb a 3 4 2 Test automated test case erai E 3 4 3 rrr eee Basa Edit Filter Ctrl F l h E a inai Ta Move Ownership Lack Apply Discard Figure 167 Refresh recursive menu also in the context menu 3 2 2 1 3Refreshing on certain user actions An item is automatically refreshed including its lock state and the presence of all direct children after the following actions selecting in the tree view pressing the Lock button If these actions are done on an actually deleted item the following dialog is shown and the item is removed from the view Li x A Cant find tem in database Maybe the tem was deleted by another user Figure 168 Deleted item information after trying to select or to lock 3 3 General principles and user prompting 3 3 1 Multi selection Mode TEMPPO offers a feature for multi select test packages and test cases in test structures and test suites The multi selection mode can be used for Assigning attributes requirements in the test structure Assigning test result attributes in the test suite Moving ownership in the test structure Deleting in the test structure Page 142 User Manual TEMPPO V6 0 Edition March 2014 Description of Use e Setting test results in
318. style 4 Yersions only EM Test Suites for W1 1 2012 02 16 Fl editable version om oe Test object Version lt 2 REOT 16 02 2012 Versions and Labels Labels only A Test object Version XYZ RCOZ 16 02 2012 E Test object Version XYZ RECOS 16 02 2012 ius Test object Version WYA RCOS COPY 16 02 2012 Order ClearCase style EHZ o A Test Suites for W21 2012 02 16 ascending Ete 7 editable version E Version 2 of Test obeject RCD 16 02 2012 J editable version D descending eres Figure 111 Locked test suites The opened test suite now shows the results of central database and not of your export database For importing the results from the export database you have to activate the menu item Import Test Suite All tests that were NOT executed for the first time cause no problems They are imported without any conflicts TEMPPO Test Manager provides 3 possibilities to import the test results to handle conflicts see Figure 112 Then an open dialog is shown where the export database has to be selected Fi Test Suite Import Settings How should SITEMPPO handle conflicting test results during import C impart all test results Manually choose test results to import oasi Figure 112 Test Suite Import Settings Import only newer test results If a user already imported a test result for a test case and you also executed the same test case Earlier the result in the ce
319. successful 2 if the test failed and 3 if the test was not completed Additionally the client gets also a string which contains the detailed test result passed failed number of errors and warnings 13 7 3How to implement an adapter 13 7 3 1 Classes temppo test tools adapters Schnittstelle a a AutoToolAdapter getResult ein aus returnFromAutoTool Reader Result getResullt Hs getSummary String My Adapter MyResult gertResult int getSummary Object getResult ein aus returnFromAutoTool Reader Result Figure 363 Class diagram of an adapter implementation Interface temppo test tools adapters tTAutoToolAdapter Page 296 User Manual TEMPPO V6 0 Edition March 2014 Appendix An adapter must implement this interface public IResult getResult Reader returnedFromAutoTool throws Exception This method is called during test execution for each test case Via returnedFromAutoTool the adapter must extract the result and return it as an IResult implementation Interface temppo test tools IResult The result returned by the adapter must implement this interface public int getResult Must return one of following results defined in IResult PASSED FAILED BLOCKED NOT_EXECUTED NOT_COMPLETED NOT_IMPLEMENTED ON_HOLD public String getSummary Must return the summary for the test result 13 7 3 2 Code Snippet The code snippet below can be used as body for an adapter imple
320. sult Test Suite manually created Figure 307 Copy of UDA Rename the attribute by changing the name of the attribute see Figure 308 If the checkbox Copy values is clicked the values of the attribute to copy example values of Milestone are copied too If the checkbox is not clicked only the attribute is copied not the values Fi Copy and rename of attribute X General virco 7 client Created 20 02 2012 15 21 23 Owner Testmanager Type Atribute M Copy values Description eres Figure 308 Copy and Rename 5 4 5 Uploads If you activate the tab Uploads Figure 309 you can Upload new files without any reference View uploads properties Delete uploads from the database Delete all non referenced uploads Page 240 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fi TEMPPO Administrator Testmanager _ Oo x Database bo Roles E Users Metadata LA Projects Lacks E License Test Levels E Test Categories Attributes Uploads i Requirement Structures E User Fielda e ow o e launcher properties Testmanager 14 02 2012 14 02 33 2 10 kByte logging properties Testmanager 14 02 2012 14 03 06 1 95 kByte rfinport_1 3293207502261 631 1329320750320 png Testmanager 15 02 2012 16 55 05 6 31 kByte rtimport 13293207502261 631 1329320750320 png Testmanager 15 02 2012 16 45 50 6 31 kEyte rtimport 132932075128691 632 _1329320751 395 png
321. sult s x Set Resultis to Failed i passed amp not executed blocked i not implemented on hold Figure 192 Set Result s You can choose one result and optionally set the checkbox Overwrite existing results and after clicking Apply all test results are set If other users have locked test cases it is not possible to set the result of course You will be informed if results couldn t be set see Figure 193 If a test case contains no test steps it remains not executed TEMPPO X Humber of test cases with new result 5 Number of locked test cases 0 Figure 193 Information message 3 3 2 Hyperlinks and Uploads Generally you can mark text as Hyperlink to the web Hyperlink to a file Hyperlink to an upload Hyperlink to a test automation tool or command Hyperlink to a test case 3 3 2 1 Creating hyperlinks Hyperlinks to the web to the file system to uploads to a test automation tool to a command or to a test case can be created for the following text fields Description project test structure test package Precondition test package test case Postcondition test package test case Test goal test case Instruction input expected test case Result output actual result bug ID test case in test suite Page 161 User Manual TEMPPO V6 0 Edition March 2014 Description of Use B Bold talic U Underline gt Hyperlink SS R
322. t You may start more than one TEMPPO Administrator application However take into account that all Administrator applications write to the same admin properties file 5 1 Database Connection Fi TEMPPO Administrator O x TE Deicbase Foes Users meaa Bi rroiects B locke icense DSM User documentation C Pad Database oracle SID jaktx Schema temppo_um Host Jatin ga Fort f 521 User fatwi12h3 wf Login manually Connect Database Mame Database Version Figure 288 Administrator Database Oracle In this tab you can define various database connection configurations where each is identified by a DSN Data Source Name A new DSN can be created Page 226 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator using theL button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the button If you delete all DSNs TEMPPO will not be able to connect to a database For each DSN you have to specify several connection parameters which are explained in the following TEMPPO supports two database management systems selectable in the field database Depending on the chosen one you must specify several connection parameters Access For Access you just simply have to specify the path to Access mdb TEMPPO automatically creates an ODBC entry Fi SiTEMPPO Administrator i Ioj x
323. t TEMPPO Designer IDATG Ranorex Commands Change Management gt Bugzilla gt ClearQuest Telelogic Change JIRA Restore Defauits OK Cance Figure 262 Settings Test suite 3 3 16 2 7 Database For the settings of database see Figure 263 Property Default Description value Show DSN Chooser on deactivated Switches on off a DB chooser on Startup TEMPPO startup DSN Chooser Timeout 5 Sets the timeout in seconds for seconds committing the chooser automatically Switches on off to lock deactivated Lock whole test structure before checking in in case of test suite creation Check new test structure deactivated Check for new test structure version version when saving an item in latest version This setting is used together with deactivated previous setting Example User1 edits a TC in latest version User2 creates new test suite Userl saves TC and the new test structure version is reloaded Check Locks in Test Suite Switches on off check of locks in test Page 205 User Manual TEMPPO V6 0 Edition March 2014 Description of Use before Exporting suite before exporting it Locking mode Sets the locking mode Loading mode Parallel When opening or refreshing a test unlimited structure there is a possibility to threads speed up loading data If you want to do that you have to select Parallel Parallel If you work on a single client PC it is recomme
324. t Newsboard gt Test Package Test Suite Database Test Automation Silk Test WinRunner V allow duplicate names in same hierarchical level Universal Fie Universal Socket QuickTest Pro Test Partner g Unit TEMPPO Designer IDATG Ranorex Commands Change Management 7 ClearQuest Telelogic Change JIRA Page 213 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Figure 271 Junit configuration 3 3 16 2 10 TEMPPO Designer IDATG TEMPPO Designer IDATG User Interface H Tree Application Path C Program Files x86 ldatg Bin ldatg exe Test Step Cells Connection time out 8 Communication time out 60 Test Suite n ee A Database iia gisi M Test Automation Ping repeats 5 Sik Test WinRunner Universal File Check in before updating with data of TEMPPO Designer gt Universal Socket gt QuickTest Pro Test Partner JUnit Ranorex Commands Change Management gt Bugzilla gt ClearQuest gt Telelogic Change JIRA Restore Defauits ok J Cance Figure 272 Settings TEMPPO Designer IDATG e Application path Path to IDATG exe e Connection time out Time for connecting successfully with TEMPPO Designer IDATG e Communication time out Time out for an existing connection without any activities After that time out TEMPPO sends a ping heart beat and waits the Ping waiting time e Ping waiting time Maximal time to wa
325. t Categories 3 1 2 3 3Referring to documents Test packages can refer to a chapter in some document e g Software Requirement Specification which usually defines some requirement s A test package is initially colored red but as soon as it refers to a document its color changes to yellow This happens if at least one of the following attributes is specified document file document name chapter Page 36 User Manual Edition March 2014 Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test pu MH d b W GP E monter L Notepad RTF Import with TCs FA 1 Intraduction E 2 General description of the product 5 3 Detailed description of the required pr 0 3 1 Scope of delivery 3 2 SEQUENCES Scenarios of intere 53 3 User goals 5 i 3 4 Required functions of the produi BL 3 4 4 File Administration EH E 3 4 2 Edit Functions AL 3 4 3 Print Functions 3 4 4 Search Functions BRL 344A Find 3 44 2 Replace i i 3 4 5 Help System Fy 3 5 External interfaces of the produi E A 3 5 1 User interfaces ft 3 6 1 2 Search Dialog 3 5 2 System interfaces TEMPPO V6 0 Description of Use O x x General Attributes Details Requirements History Plan Document P O E Mame Chapter Precondition Precondition Detailed
326. t Levels Atribute Wales Figure 356 Task Package Tab attributes 7 2 Design Test Cases If you have finished creating some task packages you can design and generate test cases by selecting the node TEMPPO Designer IDATG Tasks and call the menu item Tools gt TEMPPO Designer IDATG gt Design Test Cases Fi TEMPPO Testmanager Demo Notepad gt Project Test Structure Edt Test Execution Evaluation Toole Windows Help loj x e Test Structure Notepad ATF Import with TCs 2ystem Jy JUnit H 4 b H gh E No fiter a TEMFPO Designer ID47TG Design Test Cases Restore designed Test Cases AL Notepad RTF Import with TCs Eb re TEMPFO Designer DATO Tasks 11 New Task Package General Attributes Details Requirements History Plan 7 L 2 Introduction Sa 3 General description of the product Inherit attributes i A 4 Detailed description of the required product teal n E 5 Specifications for project management A 6 Obligations of the client Regular Validation Priority Top r i 7 Literature 8 Annex Error Verification State Designed Additional Test Levels Attribute values i E TP Type User case x Lock Apply Discard Figure 357 Design Test cases After activating the menu item Design Test Cases the window Connection Status Figure 358 and TEMPPO Designer IDATG itself are displayed Page 277 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO
327. t can be assigned with exactly 1 step User Defined Attributes Any UDAs can be assigned with Excel attributes If a value to be assigned doesn t exist it will be created automatically To assign the attributes above please click the checkbox LA Import CSV You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case Mame Title User defined ID ID V TestGoal Path V Owner Created By Precondition Planned tester Postcondition Planned test execution time W Priority Priority State Test Step Instruction Expected Attributes Fi Version Figure 19 Assign Excel to TEMPPO attributes After pressing OK the user is informed about errors of the import Page 27 User Manual TEMPPO V6 0 Edition March 2014 Description of Use All test cases were importiert For the following test cases a problem was detected and a default value was used Test Case TEMPPO Attribute Error Example Testcase Document Properties Example Testcase Document Properties Cramer No user with the name nnd exists Create Devroom for Product Create Devroom for Product Owner No user with the name nn1 exists Assign Members to Gevroom Assign Members to Devroom Cramer No user with the name nnd exists Assign Group to DevRo
328. t fields are explained in chapter 4 2 3 Page 223 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Manager Fi User properties x General Login jit 23456 Login TYPE F automatic C manual Last Mame Mustermann First Marne mend Comments M SUpErTUSET OK Cancel Figure 285 Create MS Window login 4 2 2 Login with password For creating a Super user with manual login you have to choose the radio button manual The input fields are explained in chapter 4 2 3 If you fill in also Last and First name they will be displayed in TEMPPO Test Manager instead of the Login Fi User properties x General Login Testmanager Login Type automatic manual Password pe oo Retype Password fees Last Name Mustermann O First Mame Mm E comments iCal Superuser OK Cancel Figure 286 Create manual login 4 2 3 User Properties For specifying a user the following data has to be entered e Login MS Windows NT XP 2000 7 login or manual one e Login Type automatic or manual e Password In case of manual login the password e Retype Password Retyping the password e Last name Will be shown in TEMPPO instead of login Page 224 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Manager e First name Will be shown together with last name in TEMPPO e Comment Text field optional e Superuser Check Box for the role Superuser can only be assigned in TEMPPO Man
329. t requirements true false false gt Page 288 User Manual TEMPPO V6 0 Edition March 2014 Appendix lt ELEMENT REQUIREMENT DESCRIPTION REQUIREMENTSTRUCTURE gt lt ATTLIST REQUIREMENT id CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt lt ELEMENT REQUIREMENTSTRUCTURE DESCRIPTION gt lt ATTLIST REQUIREMENTSTRUCTURE name CDATA REQUIRED gt lt cannot be zero length string gt lt ATTLIST REQUIREMENTSTRUCTURE version CDATA REQUIRED gt lt cannot be zero length string gt lt ELEMENT STEP INSTRUCTION INPUT EXPECTED USR FIELD gt lt ELEMENT USR FIELD VALUE gt lt ATTLIST USR FIELD name CDATA REQUIRED gt lt IATTLIST USR FIELD type text image text gt lt ELEMENT AUTOMATION EMPTY gt lt ATTLIST AUTOMATION tool SilkTest WinRunner UniversalFile UniversalSocket JUnit QuickTestPro TestPartner UniversalFile gt lt ATTLIST AUTOMATION file CDATA IMPLIED gt lt ATTLIST AUTOMATION data CDATA IMPLIED gt lt ELEMENT ADD TEST LEVEL EMPTY gt lt ATTLIST ADD TEST LEVEL name CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt lt ELEMENT USER DEFINED ATTRIBUTE EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE name CDATA REQUIRED gt lt cannot be zero length string
330. ta for the whole database which provides a pool of data that can be used in various projects If you want to use special metadata in a project you have to assign them see chapter 5 5 7 Page 233 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator The tab Metadata is divided into 6 tabs if the tabs are not enabled you do not have the right to see it The following values are predefined Test Levels module test integration test system test acceptance test regression test Test Categories state based GUI layout task based performance resource security safety portability reliability maintenance reuse usability Attributes none Uploads none Requirement Structure none User Fields none These tabs are described in the following chapters 5 4 1 General Behavior e Metadata are database wide e Metadata in a project can only be used if they are assigned to the project e Metadata names have to be unique within all projects 5 4 1 1 New Metadata Entries How to create a new metadata in TEMPPO First select the corresponding tab test level test category attributes uploads requirements user fields and click L There are two possibilities now 1 Type the name of the Metadata the description and press the button OK TEMPPO verifies now if the Metadata already exists If the metadata is existing you are asked if you want to assign this metadata to your project
331. tails on analyses see 3 1 5 1 Secondly you are able to create test suites based on test categories e g one for all functional test cases see 3 1 4 1 Page 34 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad O x Project Test Structure Edt Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test u m x H gt b Hyg Mo filter d Notepad RTF Import with TCs Fb 24 Introduction Bt 2 General description of the product General attributes Details Requirements History Plan Detailed description of the required prods Gr ll 3 1 Scope of delivery ID tr a 3 2 Sequences scenarios of interactic eo 3 3 User goals 5 Ay 3 4 Required functions of the product Mame Detailed description of the required product features E EJ 3441 File Administration i EH 59 3 4 2 Edit Functions m 3 4 3 Print Functions Created 15 02 2012 16 45 46 Updated 16 02 2012 08 50 22 Ela 3 4 4 Search Functions o H D34441 Find 3 4 4 2 Replace Mumber of TEs 2 i i E 3 4 5 Help System E 9 3 5 External interfaces of the product Test Category MERSE E E 3 6 Other product features required a Fal 4 Specifications for project management Description This section of the software requirements Ee 5 Obligations of the client specification must define the product features a 5 Literature requested prescribe
332. task can be covered by a test management tool like TEMPPO For test script programming several tools exist on the market The role of TEMPPO in this context is to provide a connection between a test case designed within a test package and the implementation of its test steps as a test script on the file system The implementation of test frameworks is completely outside the scope of TEMPPO Test Case Execution Now you can reap the benefits of hard test case implementation work and you are ready to create collections of test cases for test execution so called test suites by means of combining the attributes defined above So the appropriate test cases can be filtered from the pool of all available ones Therefore the number of test cases of a test suite is always a subset of those of the corresponding test structure For each test structure you can create as many test suites as you like E g you have the possibility to separate test execution tasks by creating special test suites for each tester Accordingly it is important to write a good test plan especially to plan attributes which are used here see planning phase If you recognize in the execution phase that there is an attribute missing this will cost some time to add it for each test case Evaluation This is the final phase of your test cycle After executing the tests and recording their results you will analyze them and provide reports which illustrate your testing activities and
333. tate lin Work se Attribute values L f Regular i validation it Verification Additional Test Levels E 3 41 3 Save ob blll 3 4414 Exit 3 4 2 Edit Functions 3 4 3 Print Functions H 3 4 4 Search Functions a 93 4 5 Help System E E 3 5 External interfaces of the product H os 3 6 oe noe kai amaramen p 1 hi m x E Milestone M1 E Platform windows 7 64 bit E Regressiortest yes EP Test location Offshore ma Acceptance Test x Figure 166 Button Reload for reloading the whole tree 3 2 2 1 2Refreshing recursively You can refresh an item including all sub items by selecting the refresh recursive function in the context menu see Figure 167 Attention The selected item with all sub items will be completely re loaded from the database so it may take a long time Page 141 User Manual TEMPPO V6 0 Edition March 2014 Description of Use F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tool Windows Help 5 tL LY Mew We Fi H d b We Find and Replace F3 E AJ Motepad RTF Ir EH 1 Introductior O x Show Details Fl Es Select All Ctri 4 2 General de Attributes Details Requirements History Plan EH 3 Detailed de E por i Tree 34 Scop ID tp536 o p 3 2 Sequi EA Compare A ps 3 35 User l Bea A 3 4 Regu db Cut Ctrl Mame Mew Eee pa Po ra 4 Be Copy Cirle Owner Te
334. te is created by activating Test Execution gt New This will cause the wizard shown in Figure 62 to be displayed There are 4 possibilities to create a test suite e New Based on test structure pre selection applying a condition and finally removing some test cases that won t be executed e Based on a predecessor new test suite is chained with an existing test Suite chain e Copy Based on an existing test suite only copying test suite selections to the new one e Special Based on an existing test suite defining restrictions on certain test results Bj Test Suite Wizard xl Steps Introduction 1 Introduction This wizard guides you through the steps necessary to create atest suite There are three possibilities to create a test suite 2 Choose creation mode 1 Based on test structure preselection applying a condition and finally removing some test cases that won t be executed Test structure preselection De Select nodes test packages or sub trees The default selection is the whole tree Enter test suite name Determine the logical expression based on that preselection Removing test cases that do not match the test suite 2 Based on an existing test suite only copying test suite selections to the new one Selecting an existing test suite Enter test suite name 3 Based on an existing test suite defining restrictions to certain test results Selecting an existing test suite
335. tem Show Details is deactivated E ew b kind and Replace F3 Show Details Select All E Tree Rat e Topy Ctrl C Paste Ctrl Delete Delete Order Edit 0S Refresh recursively fa Move Ownership g Gnalyse selected b E Report selected Figure 175 Show Details Page 147 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad p Ioj Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test 11 1 1 l E x H db WH no tte Notepad RTF Import with TCs ITM 21 Introduction 2a 1 1 Purpose of the document General Test Packages Test Caze od 1 2 Validity of the document ga 1 3 Definitions of terms and abbreviati Ea 1 4 Relationship with other documents Total number of selected TPs 49 j Ea 1 5 Overview of the document a 2 General description of the product Total number of selected TCs 2 ZE 2 1 Relationship with existing projects m 2 2 Relationship with earlier and follow 2 3 Purpose of the product gg 2 4 Delimitation and embedding of the Eg 2 5 Overview of the required functions P 2 6 General restrictions Ea 2 7 Hardware and software specificat i Eg 2 8 Product users M 3 Detailed description of the required prac ca 3 4 Scope of delivery 3 2 Sequences Scenarios of interac Fy 3 4 Required functions of the product Merge Apply
336. tes it The default value for the Planned Tester is the creator Do not estimate the effort for the test cases which passes Most time testers spend their time on bug analysis Therefore add that time also to the estimation F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help ll x Test Structure Notepad RTF Import with TCs System Test pu Wo d p H GP EE monter Et a 3 4 Required functions of the product EP 3 4 1 File Administration a a 3 4 1 1 Mew General Attributes Test Steps 4111 New file opened no Ei Automation Requirements History Plan Execution History E 3 4 1 1 2 Mew file opened ch D 3 41 2 Open He 3 41 3 Save 3444 Exit Planned tester Tester 3 4 2 Edit Functions Et 3 4 3 Print Functions Planned test execution time o h T min 0 59 H D344 Search Functions bs 3 4 5 Help System a 3 5 External interfaces of the product Et S 3 5 1 User interfaces 3 51 1 Editor Pane 3 5 1 2 Search Dialog a a 3 6 2 System interfaces Lock Apply Discard Figure 43 Tab Plan For each test case the execution effort is entered in the format of hours and or minutes On test package and test structure level the values are displayed accumulated After designing all test cases test manager clicks on test structure root select tab Plan and gets immediately the estimated execut
337. the TCT A TCT is concerned in two cases in TEMPPO When creating a new test case and unlocking editing an existing one 5 5 3 1 Create new test case If a TCT is activated and a new test case is created e the fixed attributes are set automatically e the UDAs with default values but without ticked checkbox Mandatory are assigned automatically e the inheritance flag of requirements is de activated e the inheritance flag of UDAs is de activated e the default values for planned tester and planned execution time are set automatically The new created test case can only be saved button Apply clicking another test case e if a precondition is entered and the corresponding checkbox in TCT see Figure 321 is ticked e if a postcondition is entered and the corresponding checkbox in TCT see Figure 321 is ticked e if a test goal is entered and the corresponding checkbox in TCT see Figure 321 is ticked e if at least one requirement is linked and the corresponding checkbox in TCT see Figure 321 is ticked e if an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 321 is ticked 5 5 3 2 Unlock save existing test case An existing test case can be unlocked saved without message e if a precondition is entered and the corresponding checkbox in TCT see Figure 321 is ticked e if a postcondition is entered and the corresponding checkbox in TCT see Figure 321 is ticked Page 248 User Man
338. the import wizard 6 3 2 References to JUnit test cases Structuring of test packages After importing a hierarchy of test packages and test cases according to the hierarchy of the suites defined in the JUnit test class is created The new test packages and test cases are named according to the JUnit items and a reference to a JUnit class and method is recorded in each test case Naming of test packages If the JUnit suite object is created by defining a test class e g new TestSuite SimpleTest class the test package is named according to this JUnit class The naming pattern is package subpackage class If a JUnit suite provides a descriptive name e g new TestSuite All JUnit Tests it is used instead If the JUnit suite object has no name and no defined test class e g new TestSuite the test package gets the current java object name of the JUnit Suite e g junit framework Suite 12345 Notice that this name doesn t refer to the JUnit suite and thus the reference is lost Since this will disable a proper update the JUnit suite should be always created either by giving it a name or by defining a test class It is highly recommended to create a JUnit suite by giving it a name or by defining a test class in the constructor Otherwise the referenced Test Package in TEMPPO will get the temporary object name of the suite e g junit framework Suite 12345 If this happens the reference to the JUnit suite is l
339. the quality of the tested product For this reason TEMPPO offers features which allow the creation of analysis charts and detailed customizable reports of test structures and test suites Page 12 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 Description of Use 3 1 The Test Process Phases As stated in the introduction chapter the whole process of testing software products can be split up into five phases 1 Test Planning 2 Test Design 3 Test Case Implementation 4 Test Case Execution 5 Evaluation The following chapters describe in detail how the tasks of these phases can be solved more efficiently by using the TEMPPO test management tool During all chapters a pseudo system test for the MS Windows Notepad application will illustrate the usage of TEMPPO more clearly 3 1 1 Test Planning The definition phase covers the tasks of Writing the Test Plan Writing the Project Plan Defining Test Case Attributes Baselining Importing requirements 3 1 1 1 Writing the Test Plan The test plan is a process document and writing is outside the scope of TEMPPO However it s the base document for all test topics during the development process and covers subjects like test requirements test management test documentation test goals end of test criteria etc Its contents are obligatory for all members of the test team 3 1 1 2 Writing the Project Plan As an output of the test plan
340. the required pr a 3 1 Scope of delivery i 3 2 Sequences fecenarios of inter E 3 3 User goals n aa 3 4 Required functions of the produ E E 43 4 1 File Administration O BA 3411 New fl 341141 New file open fi 3411 2 New file open fg 3 4 1 2 Open B 3 4 1 5 Save o be 3414 Ext 3 4 2 Edt Functions Ei 33 4 3 Print Functions l E ar 3 4 4 Search Functions Ed 3 4 4 1 Find Eb a 3 4 41 4 Find up FF 344142 TT r 344 4 1 2 Find down General Attributes Test Steps Ei Actomeation Requirements History Plan Execution History Precondition file testixt opened find dialog open M Case sensitive Cursor at EOF 1 Enter search phrase Specity search direction 7 a 3 4 4 2 Replace A tn EY 3 45 Help System Sia 3 5 External interfaces of the produ a dee 3 5 1 User interfaces fl 3 5 44 Editor Pane iy 3 5 1 2 Search Dialog i E 3 5 2 System interfaces ei 3 6 Other product features requirec 3 6 1 Performance m 3 6 2 Resource m 3 6 3 Security fi 384 Safety fi 3 65 Portability fi 3 6 6 Reliability m 3 6 7 Maintenance fi 3 6 8 Reuse fli 3 6 9 Usability H 4 Specifications for project managemery A 5 Obligations of the cliert B Literature 7 ANNEX E Postcondition file test tkt closed Wi Case sensitive El Figure 48 Test Case Preconditions and Postconditions 3 1 3 1 2Test Steps The test step editor provides functions for
341. the test suite When the multi selection mode is activated the items aren t locked automatically They are only locked during the time for saving If items are locked by other users the changes are not applied to these items They are displayed in a list 3 3 1 1 Multi selection The multi selection mode is activated when more than one item is selected If a user selects at least 2 items the right side detailed view is completely empty The user can only activate the multi selection mode when he has the right In an opened test structure test packages and test cases can be selected In a test suite only the test case can be selected Multi selection for test packages is not possible A multi selection can be done by using different keys e Select all For selecting all press lt Ctrl gt and lt A gt The user can also activate the context menu Select All Figure 169 or the menu item Edit gt Select All C Mew C Find and Replace F3 Show Details Select All ft Tree b A Cut Ctrl x Copy ctrl E ey Paste Ctrl 2 Delete Delete Order Refresh recursively fa Move Ownership gil Analyse selected p E Report selected Figure 169 context menu Select All The whole sub tree of the selected test structure or test package s can be selected see Figure 170 Page 143 User Manual Edition March 2014 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Ev
342. ther test interfaces For using TEMPPO Designer IDATG from TEMPPO it is necessary to tick the checkbox TEMPPO Designer IDATG on tab General of the test structure s root Fi TEMPPO Testmanager pemo Notepad OO lo x Project Test Structure Edt Test Execution Evaluation Toole Windows Help v Test Structure Notepad RTF Import with TCs System Test V3 oF x E J Motepad RTF Import with TCs E 1 TEMFPO Designer DATO Tasks H 2 Introduction General Plan Requirements E 3 General description of the product a 4 Detailed description of the required product teal Mame Notepad ETF Import wth Tes c 5 Specifications for project management m 6 Obligations of the client Owner Testmanager Updator Testmanager bn 7 Literature E g Apek Created 15 02 2012 16 36 29 Updated 20 02 2012 16 40 10 Type Test Structure TEMPPO Designer DATS T Test level System Test 7 Description Lock Epply Figure 354 TEMPPO Designer IDATG As a preparation for designing test cases in TEMPPO Designer IDATG it is necessary to create so called Task Packages in TEMPPO A task package is a special type of test package that has got an ID and the same attributes as a test case You can create any kind of task package hierarchy Page 275 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Designer IDATG 7 1 Creating Task Packages Task packages only can be created below the folder TEMPPO Designer IDATG T
343. thout having any script Attributes Page 43 User Manual TEMPPO V6 0 Edition March 2014 Description of Use By TEMPPO Testmanager Demo Notepad l Z joj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test 11 H 4b Woof RE ofiter E A 3 4 Required functions of the product Eb 43 4 1 File Administration sj 3 4 4 1 Mew Ee Recuirements History Plan Execution History eee i5 4 1 1 1 Mew file opened no General Attributes Test Steps E 3 4 1 1 2 New file opened che 3 4 4 2 Open 3 4 1 3 Save oo 3 44 4 Exit EF 1342 Poi puneuens Regular E validation Priority Medium ki o EHE 3 4 3 Print Functions ce 3 4 4 Search Functions Error ie verification State Jin work 3 4 5 Help System Ela 35 External interfaces of the product rA rs 4 User interfaces Additional Test Levels C Attribute Values C 3 5 1 1 Editor Pane 7 T Ta Acceptance Test EP Milestone M1 3 5 1 2 Search Dialog i bas a oe i 3 6 2 System interfaces E Platform Windows 7 64 bit oe a 3 6 Other product features required EP Regressiontest yes a 3 6 1 Performance EP Test location Offshore 3 6 2 Resource fll 3 6 3 Security fll 3 64 Safety b Figure 38 Attributes You have to specify whether the test case is a regular one or tests an error condition A regular test case pursues the ai
344. tight Continuous text Amost all test package attributes Almost all of test case att Test creation report Word tight Continuous text Test packages with description Test with preconditi Figure 138 Report settings With the buttons on the right side you can add change and remove settings New Edit see 3 1 5 6 1 Delete Setting s are deleted Copy to other settings Copy the selected setting s to other settings Example Select a setting in tab personal setting and press button In tab project setting the copied setting is added Import from another project see 3 1 5 7 Export to XML file see 3 1 5 8 Import from XML or TRP file see 3 1 5 9 With the buttons below you can save the report to directory or create a preview Pressing Save Report a file dialog opens where the directory has to be defined and then report is created 3 1 5 6 1New Edit When pressing the button New or Edit a new window opens for set the properties for creating a report see Figure 139 Page 117 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 4 TEMPPO report setting in project Demo Notepad SEE WT he ee ei Name NewReportSetting SB sctings General io Created 07 05 2013 11 41 09 _ E Continuous Report oe E Test Package Updated Test Package Attributes oe Test Case Attributes Test Step i Requirement Charts Figure 139 Report settings overview The reporting functional
345. tions Ea 3 4 4 Search Functions meee ee S 4 41 Find Precondition wd 34 4 2 Replace J Search Functions file testtxt opened be 345 Help System Es 3 5 External interfaces of the product H 3 6 Other product features required Fa 4 Specifications for project management a 5 Obligations of the client LU 6 Literature Postcondition He 7 Annex Precondition Postcondition file testixt closed Lock Apply Discard bi Figure 27 Precondition and Postcondition for test package 3 1 2 3 2Categorizing Test Packages After creating a test package you can select a test category Here all categories are available that are connected to the current test level for further details of test categories see 5 4 3 These are some typical test categories Task Based Test GUI Layout Test State Based Test In Figure 28 the test category Task Based Test was assigned to a test package After assigning a test category the node looks like 5 At first sight assigning test categories seems to be superfluous because they have no further influence on the test structure than being a flag for a test package A closer inspection makes their purpose plain Firstly you can obtain statistical information from your test structure or test suite like How many functional or performance test cases does my test structure contain How many functional test cases are failed For further de
346. tions of the implemented l nE E 3 4 3 Print Functions product requirements I 3 4 4 Search Functions 7 i 3 4 4 1 Find 3 4 4 2 Replace a 3 4 5 Help System EF 3 5 External interfaces of th 5 8 3 5 1 User interfaces 3 5 1 1 Editor Pane ffl 3 5 1 2 Search Diak Ej 3 5 2 system interfaces SB a nrar irt festi a Figure 32 Test package linked requirements The button Add requirement is always enabled if the test package is locked 3 1 2 3 4 2 Delete requirement If a test package is locked and at least one linked requirement is selected the button Delete requirement is enabled Fi TEMPPO Testmanager Demo Notepad i Joj xj Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test f oj xj M d gt b H o E mor a L Notepad RTF Import with TCs i 1 Introduction 2 General description of the prc General Attributes Details Requirements History Plan Si 5 3 Detailed description of the rec Bo be A 3 1 Scope of delivery Bees 3 2 Sequences Scenarios _ 3 3 User goals ei 3 4 Required functions of th oe ni 3 41 File Administration 3 4 2 Edit Functions 3 4 3 Print Functions Sa 3 4 4 Search Functions P Ee 3 4 4 4 Find 2 3344 2 Replace i 3 4 5 Help System 3 5 External interfaces of th 8 3 5 1 User interfaces Pb pe 3 5 1 1 Editor Pane Requirement ID
347. to open Figure 197 for specifying a special name and description Additionally owner creation date size the number of references and the type are displayed iieb File ES Database EI Command EJ manual Test Case Reference E ores Figure 198 Hyperlink database Use an existing upload You have to activate tab database and press button create reference to uploaded file to open Figure 199 which shows all uploads of the database For creating a new reference on an existing upload you simply have to select it and click OK in Figure 199 and Figure 198 Page 163 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Fi Uploads 7 X Find a size launcher properties Testmanager 14 02 2012 14 02 33 2 10 kByte logging properties Testmanager 14 02 2012 14 03 06 1 35 k Byte rfimport_1 3293207502261 631 1329320750320 png Testmanager 15 02 2012 16 55 05 6 31 kByte timpo 13293207502261 631 1329320750320 png Testmanager 15 02 2012 16 45 50 6 31 kByte Mfirnport_1 329320751 2691 632_1329320761 395 png Testmanager 15 02 2012 16 55 06 6 31 kByte Mfirnport_1 329320751 2691632 _1329320751398 prg Testmanager 15 02 2012 16 45 51 6 31 kByte uninstall joc Testmanager 14 02 2012 14 02 51 2 67 kByte Cancel Figure 199 Uploads The upload limit of a file is set to 0 5 MB by default and is specified in the file admin properties dbsettings upload limit 500000 But it is only information
348. tomated test cases only the path to the generated test script is displayed A test case is treated as automated if it has at least once been exported by TEMPPO Designer IDATG as a test script for an automation tool e g TestPartner Page 279 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Designer IDATG Ei TEMPPO Schlosser Dietmar Notepad i l O x Project Test Structure Edt Test Execution Evaluation Toole Windows Help LHil a Test Structure System amp Acceptance Test System Test v2 Ho d P H GP EE No iter ALI System amp Acceptance Test IDATG Tasks ea R IEE General Attributes Test Steps A eeen Requirements History Plan o Sub use case New already opened B a SUb use caze Mew REE Subus ECAS seMew ompletelynew 1 oe E oot eee 2 Input conte fia Use case File Open Enter name Input data Mew file ae fea 3 Detailed description of the required product feature name Lock Abi Discard tod Figure 362 Test cases generated by TEMPPO Designer IDATG 7 3 Updating Test Cases Chapter 7 2 describes the creation of task packages and the design and generation of test cases with TEMPPO Designer IDATG Of course it is possible to change the existing task packages or to add new ones by calling TEMPPO Designer IDATG again 7 4 Restore Designed Test Cases If the connection between TEMPPO and TEMPPO Designer IDATG is lost e g because the user abort
349. tributes meanings The user can write free text that may also contain wildcards like x any number of characters any single character Lal Filter Properties Value M1 2 M11 3 M3 Acceptance Test nni Implemented eee ki ee Validation Milestone IN M142 M13 M3 AND Additional test level Acceptance Test AND Planned tester nni AND Reg_State Implemented AND Test Case Type Validation Figure 237 Filter criterion 3 3 10 6 Edit filter criterion You delete and add lines of filter criterion When pressing the button the current line is deleted e L a line is inserted before the current one 3 3 10 7 Export filter It is possible to export filters to XML and import them again Via multi selection of filter and pressing the button Export filters to XML filter are saved to an xml file Page 187 User Manual TEMPPO V6 0 Edition March 2014 Description of Use 3 3 10 8 Import filter It is possible to import filters from XML by pressing the button Import filter from xml A filter import is rejected if the filter contains specific attributes that are not assigned to the project the filter is imported to An error message is displayed where the names of the NOT imported filters are listed The filter contents are checked and the import is only successful if the attributes match the ones of the selected project If the filter is not syntactically correct the import is
350. ts of the exported test suite Now you can activate the checkboxes of test cases that you want to import Page 191 User Manual Edition March 2014 TEMPPO V6 0 Description of Use e Import only newer test results If a user already imported a test result for an automated test case and you also executed the same test case o Earlier the result in the central database won t be overridden by yours o Later your result will be written into the database The other result is lost e Import all test results All test results of already executed test cases are overridden by your results Note All test results that are marked are overridden in the central database after closing the window with OK A Test result comparison 7 x Test Suite in XML File v New Test Suite B v Detailed description of the required product features Detailed description of the required product features c M Required functions of the product Required functions of the product c M lt A File Administration File Administration O Ga New E EN New O Bd new file opened no changes E New file opened no changes O BB new file opened changes 31 01 2004 13 27 10 TE New file opened changes 27 01 2004 13 27 10 Fuchs Clemens Test Suite in Master Database New Test Suite E Open normal 28 01 2004 13 27 14 Save Open Tile opened changes 27 01 2004 13 27 15
351. u can connect to a LDAP server and import or synchronize users In principal it is possible to use 2 different logins on the one hand user can login to TEMPPO automatically with their MS Windows account and on the other side you can create user logins named as you like Such manual logins need a password The same functions with the exception of role assignment are offered in TEMPPO Manager for details see chapter 4 2 Page 229 User Manual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator Fj User properties x General Poles amp Rights 4 TEMPRA Superuser Choose project User documentation as TEMPPO Editor W TEMPPO Reporter TEMPPO Guest I TEMPPO Requirement Editor M TEMPPO Key Tester hf TEMPPO Tester TEMPPO key User Figure 293 User properties Roles amp Rights To assign a defined role to a user select tab Roles amp Right and select a project Then check the roles the user should get for the chosen project and press the button apply Choose another project and assign roles to the user by clicking the required checkboxes and pressing apply A user can have different roles in different projects The TEMPPO Superuser role can only be assigned in the TEMPPO Manager Users tab If a new role is assigned to a user the user has to restart TEMPPO to have access to the functionality provided by the newly assigned role 5 3 1 LDAP By selecting the chec
352. ual TEMPPO V6 0 Edition March 2014 TEMPPO Administrator e if a test goal is entered and the corresponding checkbox in TCT see Figure 321 is ticked e if checkbox Inherit in tab Requirement is activated and the corresponding checkbox in TCT see Figure 321 is ticked e if at least one requirement is linked and the corresponding checkbox in TCT see Figure 321 is ticked e if checkbox Inherit in tab Attributes is activated and the corresponding checkbox in TCT see Figure 321 is ticked e If an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 321 is ticked If a TCT is activated and a test case with missing e g default attribute values is edited those are not added automatically 5 5 3 3 Test case template and filter If e a TCT is activated and e a filter is set and e anew TC should be created and e the test case don t fulfill the filter criterion the test case cannot be created You have to set the filter to No filter and start again the creation progress 5 5 4 Test result template A test result template supports you in test case execution You can define test result as mandatory or set a default value if a result is recorded In the following example 2 test result attributes are defined If you record a test result TR1 1 is assigned automatically and you have to specify a value for TR2 Otherwise the test case cannot be saved Fi Project Properties a X General R
353. ublic int getResult return result 13 7 3 3 Implementation and integration steps 1 Create following subdirectories in your TEMPPO installation directory gINSTDIRs dev srco ext INSTDIR dev bin 2 Create the file INSTDIR dev src ext MyAdapter java and implement the adapter 3 For compilation a JDK 1 5 is needed Execute following command in INSTDIR dev javac classpath lib temppo jar d bin src ext MyAdapter java 4 Pack the adapter into a jar file Execute following command in SINSTDIR dev jar cf adapter jar C bin ext 5 Add adapter jar to the classpath for TEMPPO and TEMPPO Administrator via extending common classpath in SINSTDIR launcher properties lib temppo jar lib lib jar lib commons codec jar Lio VCommons herpclient Jari lib commons Logging jar lib eommons cli jare lib unio jar lib registry jar lab sql jdbc jarslib oracle jar lib poqjdbc jar Page 298 User Manual TEMPPO V6 0 Edition March 2014 Appendix lib jcommon jar lib jfreechart jar dev adapter jar The adapter is now available in TEMPPO Administrator for Universal Socket configuration For configuration of UniversalFile admin properties has to be adapted o N D automation UniversalFile adapter ext MyAdapter Page 299 User Manual Edition March 2014 14 Index A Administration Database Connection 221 226 Database Migration 225 User Management 222 229 Analysis 97 Bug ID project 104
354. uirement you press the button Add requirement and Figure 31 is shown At first you have to select the requirement structure and its requirements are listed The requirement selection dialog allows you to link one more or all requirement s to the package If more requirements are linked they will be displayed in alphabetical order All requirements selected before are shown grey F Requirement selection X Notepad Find b a ea Func _reg23 User goals i d Gii Func _req24 Required functions of the product 4 a Func _reg25 File Administration 44 Af Func regz6 Mew ba Func regar Open Func_req2e Save Nata Fune read Exit eal Figure 31 Requirements Selection After pressing OK the requirement s are linked to the test package Page 39 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Ei TEMPPO Testmanager Demo Notepad l E z jol x Project Test Structure Edt Test Execution Evaluation Tools windows Help e Test Structure Notepad RTF Import with TCs System Test W1 L Notepad RTF Import with TCs Fe 1 Introduction H 2 General description of the pre General Attributes Details Requirements History Plan EF 8 3 Detailed description of the rec vow 34 Scope of delivery latent 2 3 2 Sequences scenarios fa 3 3 User goals o EM 34 Required functions of th 3 441 File Administration Func_reqed Required Notepad W1 A ce 342 Edit Functions func
355. uite Generator lt lt Prey Next gt gt Figure 65 New Test structure pre selection test packages Finish Cancel Figure 64 shows the first step for creating a test suite It shows the whole test structure pre selected If you want to consider a whole test structure with all the test packages and test cases for test execution you press simply Next Advanced users can limit the test structure by selecting test package s that should be in the test suite For selecting the test packages use lt CTRL gt or lt Shift gt keys Page 66 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Bj Test Suite Wizard E x Steps Determine the test suite 1 Introduction Enter test suite name 2 Choose creation mode 3 Select nodes or subtrees 4 Enter test suite name 5 Determine the logical Test object Version XYZ RC01 expression a Remove test cases manually Created 16 02 2012 13 39 43 Owner Testmanager Type Test Suite Description hole structure Release canidate 01 TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 66 New Name and comment In the 2 step you have to enter name together with a description for the test suite Figure 66 When pressing Next you have to determine the logical expression Figure 67 A logical expression can be defined which filters out the desired test cases It can be construct
356. unctions of th BE 3 44 File Administration ee Notepad 3 H 2 342 Edt Functions External interfaces of the product functions of the o EE 3 4 3 Print Functions product oa 3 4 4 Search Functions Fune_reqe SEQUENCES PEA 3 4 4 1 Find oe pereniallos at C 3 4 4 2 Replace interactions with 3 4 5 Help System the environment Ella 3 5 External interfaces of th 3 5 1 User interfaces fi 3 5 4 1 Editor Pane a 3 6 1 2 Search Diak a 3 6 2 System interfaces w x Lock Apply Discard T Figure 34 Requirement Inherited Figure 34 shows the selected test package 3 5 1 1 Editor Pane and an activated checkbox inherit which has the effect that the test package inherits the requirements from its parent or its parent External interfaces of the product Inherited requirements are displayed disabled so no selecting or deleting can be done The inherited requirements are grouped by the test package names and within each group by the requirements in alphabetical order After that the enabled not inherited but also alphabetically ordered part is displayed see Figure 34 If a user defines one requirement for two different levels within the inheritance tree both requirements are displayed within the requirement list It is not possible to define one requirement more than once within one inheritance level You might ask about the reason of linking the requirements to the tests and test packages The answer is quite eas
357. which even allows you to copy or move around complete test structure sub trees By using Edit gt Order gt Move Up Move Down you can change the order of test packages or test cases as well Edit and evaluation functionalities are also available over the context menu 3 1 4 Test Case Execution Test execution is an issue which must to some extent be connected with configuration management CM concepts like checking in a version and making it reproducible for later reference If you are unfamiliar with CM terminology please refer to chapter 3 3 7 In an ideal world you would first make your planned test cases ready for execution somehow conserve their state by means of CM functionality execute them on your test object and record results In reality however it often happens during test execution that you encounter a faulty test case Such faults are mostly caused by undocumented changes in requirements or they slipped through quality control after test case implementation Naturally you ll want to correct a faulty test case before executing it and your test management tool should support this action A different aspect is that other test cases which were already executed should certainly not be editable any more Otherwise you could run into the problem of accidentally changing or even deleting a test step that already has a recorded result TEMPPO Test Manager supports these seemingly contradictory needs with its versioning me
358. xpected image jpg Download j Files of type fan Files Cancel Figure 207 Destination selection 3 3 3 Move Ownership Owner of an item is the user who creates this item Move Ownership is offered for the following items e Requirement e Test Level e Test Category e Attribute e Upload e User Fields e Test Case e Test Package e Test Structure e Test Suite For Move Ownership of Projects see 5 5 8 For Metadata Select the corresponding metadata in the TEMPPO Administrator application Select the metadata you want to change and press the button Move ownership For Test Case Test Package Test Structure and Test Suite Select the item and click the menu item A list of all TEMPPO users is presented to the current user see Figure 300 on page 235 A new owner of the selected item can be chosen see also 5 5 8 3 3 4 Map of Meta Data project wide copy If parts of a test structure are copied from one project A to another project B the related metadata can be copied too At the beginning of the paste action the user is asked if metadata should be mapped too see Figure 208 Page 169 User Manual TEMPPO V6 0 Edition March 2014 Description of Use x Copy with Meta Data is only those assigned to opened project C all used in selected subtree Mote Insensitive tems are not used in selected subtree V Test Level J Test Category I Attribute M Upload P Additional Test Step Column oren
359. xpected results developed for a particular objective such as to exercise a particular program path or to verify compliance with a specific requirement IEEE Std 610 12 1990 Test Case Design Constructing test cases according to special methods e g equivalence class in a way such that from the description of the test package and from the requirement specification test cases can be derived independently Test Category Category Test Level Level of the test e g system test acceptance test Test Package Set of test packages and test cases Test Step Single instruction for testing usually with expected result Page 285 User Manual TEMPPO V6 0 Edition March 2014 Terms Test Structure The entire tree of test packages and test cases Test Suite A subset of test cases from the test structure intended for execution in a certain test their recorded test results Version A version denotes a certain state of an administration unit at a certain time There are two kinds of versions i checked in version which can t be changed any more and ii checked out versions Usually versions follow a decimal notation scheme starting with 0 or 1 For each new version the version number is incremented Version Tree A tree representation of all versions including all branches of an administration unit Page 286 User Manual Edition March 2014 TEMPPO V6 0 Abbreviations 12 Abbreviations DB HW TD GUI SW
360. y and will improve your whole process On one hand you can analyze your test structure regarding to test coverage e g how many test cases are related to the each requirement and on the other hand you can make a statement about the quality of the SUT e g how many bugs are related to a special requirement 3 1 2 3 4 4 Apply requirement updates Requirement structures and test structures live in fully separated environments So it can be that a latest test structure version works with a not latest requirement structure version This is always the case after an update of a requirement structure An automatic update of the current test structure version to the latest requirement structure version may not be wanted by the user and would cause problems anyway e g if more than one user work on this version It s only possible to update to the latest requirement structure version So an update to the latest requirement structure version can only be made manually initiated Open the TEMPPO test management environment and open the project and open the project and test structure The menu item Test Page 41 User Manual TEMPPO V6 0 Edition March 2014 Description of Use Structure gt Apply requirement updates is only enabled if the main LATEST version of the test structure is opened By Pressing the menu Test Structure gt Apply requirement updates Figure 35 is shown All assigned and updated requirement structures are shown in the list S
361. y with TEMPPO s find feature Fi TEMPPO Testmanager Demo Notepad i z ioj x Project Test Structure Edt Test Execution Evaluation Tools windows Help _ Test Structure Notepad RTF Import with TCs System Test W41 f ajx H da gt b H GP E no ter T 3 1 Scope of delivery a 3 2 Sequences ecenarios of interactions l E 3 3 User goals Eme Requirements History Plan Execution History a 243 4 Required functions of the product General e Test Steps 4 H E 3 4 1 File Administration 3 4 2 Edit Functions Jeg daira o fcss1 EH D 3 4 3 Print Functions EF a 3 4 4 Search Functions dane Case senstie 0 o A3441 Find RE Et a 3 4 4 1 1 Find up Owner Testmanager Updator Testmanager TERRE 41 1 1 Case sensitive wlll 34411 23 QuickTestPro r5 3 4 4 1 2 Find down Type Manual Automated Test Case 3 4 4 2 Replace _ B 3 4 5 Help System Test Goel The test goal of this test case is to test search function with case 6 QA 35 External interfaces of the product sensitive search strings o a 8 3 5 1 User interfaces fi 3 5 1 4 Editor Pane fi 3 6 1 2 Search Dialog Do 3 5 2 System interfaces El a 3 6 Other product features required m 3 6 1 Performance m 3 6 2 Resource A 3 6 3 Security i e lock Apply Discard Created 16 02 2012 11 03 55 Updated 16 02 2012 11 Figure 37 Manual Test Case General It is also possible to design automated test cases wi

User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents