Home

User Manual

1. Figure 344 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 o x B Database e Roles Users a Metadata Al Projects Locks amp License Al Demo Notepad e Example for versioning Demo Not Notepad Y24141 editable v Test Pac Find tp555 export dat 20 02 201 i ihe ee lala Demo Not Notepad W244 editable v Test Pac Search F tp554 export dat 20 02 201 Notepad RTF Import Demo Not Notepad v2 1 1 editable v Test Pac Help Syst tp557 expor dat 20 02 201 1 editable version Demo Not Notepad W211 editable v Test Pac Replace tp556 export dat 20 02 201 Notepad RTF Import with TCs Demo Not Notepad v2 1 1 editable v Test Pac Print Fun tp551 export dat 20 02 201 i Demo Not Notepad W211 editable w Test Pac Set Fort tp550 export dat 20 02 201 1 Test Suites for V2 1 2012 4 Demo Not Notepad V2 41 4 editable vw Test Pac Print tp553 export dat 20 02 201 E 141 editable version Demo Not Notepad W2 1 1 editable v Test Pac Page Setup
2. 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 80 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi New Bug TEMPPO mam xi Tes Widows SS Bi New PR TEMPPO i B epe OOOO O O swam m a fj fj o m o a fo fj o meson m somm O Y o eee el CO l N N Page 81 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 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 Limitation With IBM Rational Clearquest s interface it is not possible to attach directly the test report Page 82 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj New Bug TEMPPO Standard Fields Project Test Project Summary First bug entry in JIRA Componentss Version s 4 9 Version s 4 9 2 0 Assignee 7
3. Edit properties of selected version Example for versioning eg Eott A V4 editable version I Check In Check in active version Activate Activate selected version id Merge j Tree style Merge all test cases into latest version of main line Versions only C Labels only Change tree style ie Yersions and Labels C ClearCase style r Order ie ascending 3 descending Close Figure 227 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 228 The test structure gets checked out immediately and version 2 is created The symbol Ze signals the active version which is again latest ee Example for versioning Edit VI Release 1 ee iB V2 editable version Hi Tae PB Activate ig Merce p Tree style Versions only C Labels only Change tree style abels ClearCase style gt Order ie ascending i descending Close Figure 228 CM Version tree after checking in and labeling 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 229 In
4. FPostcondition Postcondition Detailed description of the regui User interfaces Editor Pane Lock Apply piscard 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 _ EJ Import Structure From RTF Document Update d From XML Document Export Structure From Rianorex Document F Apply requirement updates From CSV I LS MM Ld 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 to TEMPPO attributes 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 Page 33 User Manual TEMPPO V6 1 Edition January 2014 Descriptio
5. EMPPO Test _ Manager Test Execution Managing Planning and rePorting Organizer User Manual Edition January 2014 Copyright Atos IT Solutions and Services GmbH 2014 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 O On A U BR WN B eS _ a j j A WN e O OVGEVIG W sccis A Aaa a aaa 4 TNUPOGUCTON icira a a 5 Description OF US 6 niihin aA aa 9 TEMPPO ManaG eG iiceessnescesessicewuansieesaanatedveanmieadenintewnadetueseamaceeivends 234 TEMPPO AGMINISUALON iios i 239 TUTE cascinevuantiuvenanscarneidataceinavunn A 266 TEMPPO Designer CIDATG wecccsssscccccccncccccncnccsccussssccccccecccccsnnccccusnses 285 COMMANG LING serrr a EE 291 PIUO INS scnis Ea EAE 293 Lit ra t rer a a a a aa 294 TrM Sirianna a a a a aaa 295 AbbreviatiOnS sss2s 2 ss s220225u20u20u20u20u20un0nnnnnnnnnnn 297 APPENA D Geeeeer ner nnn a aa creer errr err errr rere 298 INGO a a a AE 310 User Manual TEMPPO V6 1 Edition January 2014 Overview 1 Overview Managing the test process involves a large number of engineering disciplines like
6. Figure 302 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 i oj x Database Users AY Migration Testeri tester Testmanager temppo_um Figure 303 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 235 User Manual TEMPPO V6 1 Edition January 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 w
7. El Lock Apply Discard 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 36 User Manual TEMPPO V6 1 Edition January 2014 Description of Use you have children test packages Therefore TEMPPO offers you to inherit requirements from parent test packages Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Help O x Test Structure Notepad RTF Import with TCs System Test 11 H d gt H o Eor L Notepad RTF Import with TCs Fe 1 Introduction HL 2 General description of the prc General attributes Details Requirements History Pian os 3 Detailed description of the rec ca 3 1 Scope of delivery F Inherit _J 32 Sequences scenarios E 2 33 User goals E 24 3 4 Required functions of th 3 4 1 File Administration Func_reqed Sec Notepad is i 3 4 2 Edit Functions External interfaces of the product functions of the 3 4 3 Print Functions product Ela 3 4 4 Search Functions Func_reqee sequences o ci Seong Editor Fane T or 3 4 4 2 Replace interactions weith EE 3 4 5 Help System the enviranment ea 3 5 External interfaces of
8. Of course it is not possible to edit anything here jreqes4 ComponentA R1 2 req685 ComponentA R2 h The tab Inheritance displays the COMMON brectinked Requirements innented Requirements inhertance state of the inheritance flag of the selected TPs If the checkbox is not activated F inherit Legend F Not inherited _JNotinnerted all selected TPs do not have any inherited requirements If the checkbox is activated M mets all selected TPs have at least one inherited requirement If the checkbox looks like nhertedpartaty the common state is mixed TPs with and without inherited requirements Inherited 3 3 1 4 Multi selection merge of changed TPs and TCs A so called Multi selection merge of changed TPs and TCs is done based on the changed TPs and TCs of the current selection Only the changed ones are merged Please do not mix this feature with the merge of all items If you press the button Merge all items are merged to the latest version after pressing the Yes in Figure 179 Page 150 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Merge Warning pmo Apohang the function of merging the selected test packages test cases mull merge overantes DEA those items in the latest version Figure 179 Merge information After finishing merge a result summary is displayed to the user It is not possible to merge an item if
9. 34 1 File Administration Merge Apply Pacard ti oO amp amp amp Figure 182 No filter Fi TEMPPO Tester1 Demo Notepad g l Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test w111 Menge Apply Discard amp 8 O amp amp amp Figure 183 Set Filter Page 153 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 5 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 184 Anew common value is written in red with a white background color see Figure 185 Fi Attribute value selection i xX Attribute Figure 184 Assignment dialog Page 154 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ei TEMPPO Tester1 Demo Notepad B x Project Test Structur
10. Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 297 Settings Bugzilla 3 3 20 2 12 2 IBM Rational Clearquest The following table shows the parameter matching of TEMPPO and Clearquest TEMPPO Clearquest URL Web address of Cleaquest for login User Repository Schema repository Page 231 User Manual TEMPPO V6 1 Edition January 2014 Description of Use ClearQuest el User Interface Tree Test Step Cell T ttp 92 168 146 77 gt Analysis p Newsboard Path ta HTTPS Certificate Test Suite Database Connection El Test Automation Silk Test User repository Hin Runner Universal File H Universal Socket Quick Test Pro eee admin H Test Partner TEMPPO Designer DATS i Ranorex El Commands New Command VEZ El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults Cancel Authentication Figure 298 Settings IBM Rational Clearquest E Rational Microsoft Internet Explorer provided by CATM Siem ens jk File Edit wew Favorites Tools Help O O AA Al Dan demu Oe User Mame Password Schema Repository co aktx Database tpo user database is mow Login ae ff ff Na Figure 299 Login to Clearquest 3 3 20 2 12 3 IBM Telelogic Change The following parameters have to be specified if using Telelogic Change e Server Port IP address or server name where Telelogic Change
11. Page 155 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs Systerm Test PyS H 4b W qh RE Mofiter oF Notepad RTF Import with TCs TR 41 Introduction Ee EE E a a t a 1 14 Purpose of the document General Test Packages Test Case sE 1 2 Validity of the document e o 2 41 3 Definitions of terms and abbreviati Attributes Requirements Plan 14 Relationship with other documents etn 94 5 Overview of the document 4 Inherit a 2 General description of the product s0 2 14 Relationship with existing projects Requiremen Requirement Requirement Str Wersion D 22 Relationship with earlier and follow 7 Componente Components W1 2 J 2 3 Purpose of the product Cy new 124 Delimitation and embedding of the 22 5 Overview of the required functions x Delete J 2 6 General restrictions 12 7 Hardware and software specificat TA Assign to alltest cases nE 2 9 Product users fl 3 Detailed description of the required proc PSNI E Ea nE 3 1 Scope of delivery 3 4 4 2 Open l a 341 3 Save ow 341 4 Exit 3 Apply Discard Furyk Figure 186 Assign to all test cases If the button Apply is pressed all common values white background color and red foreground color are set f
12. Strg h ffnen Strg Speichern Strg 5 Speichern unter Action image Seite einrichten Drucken Strg P Beenden pot 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 76 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Set Result s xj Set Result s to i failed not executed blocked not implemented on hold T Overwrite existing results Test Result template Attribute Assigned defaut value Brower version Firmware Figure 87 Set result s 3 1 4 1 6Plan 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 F TEMPPO Testmanager Demo Notepad O x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Test object Version 2 Acii 41 1 1 bb WH E no fter Test object Version lt 2 RCO 3 Detailed description of the required product features Eli 3 4 Required f
13. TEMPPO Test Suite Generator Figure 62 Test Suite wizard Introduction When pressing Next Figure 63 is shown where you can select one mode Page 60 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard l Steps Choose creation mode 1 Introduction 2 Choose creation mode New based on current test structure New based ona 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 Prev f Finish Cancel Figure 63 Creation mode selection 3 1 4 1 1New 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 61 User Manual TEMPPO V6 1 Edition January 2014 Description of Use ee E 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 nodes or subtrees 4 5 Enter test suite name Sie Notepad RTF Import with TCs petermine the logical E E Introduction aap General description of the product 6 Remove test cases manually P I Detailed description of the required product features eg Scope of delivery Sequences scenarios
14. LA Notepad generated E 1 Introduction a 2 General description of the pri General Attributes Test Steps fl Automation Requirements History Plan Execution History 3 Detailed description of the pre fa 3 1 Scope of delivery ee 3 2 SEQUENCES Scenarios oo fil 3 2 1 Sequences acer iser aes eure Requirement Structure version B 3 3 User goals Path 4 q F L E 3 3 1 User goals Func _reqe6 Mew Motepad WT Al E Inherit oe 3 4 Required functions of tr Mew implemented 3 44 File Administratior requirements B 3411 New TE 05 41 11 New o E 3 41 2 Open ff 3 44 24 Open 2 3 4 1 3 Save an 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 10 can be selected if a non latest version should be loaded Page 15 User Manual TEMPPO V6 1 Edition January 2014 Description of Use CAS x Ae Link test cases torequirem Testmanager 14 02 2012 11 14 46 System Test Wl editable version Notepad generated Testmanager 15 02 2012 15 0 System Test V2 editable version Notepad System amp Accepta Testmanager 15 02 2012 13 26 40 System Test wi W111 editable version V2 editable vers
15. est Running Error In Test Setup Lack Apply Figure 361 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 Entries in test case Automation tabs Page 275 User Manual TEMPPO V6 1 Edition January 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 th
16. Cal 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 in 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 87 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Re Notepad RTF Import with TCs Edit Bw EAA A Test Suites for W11 2012 02 16 C Check In p Merge all test cases into late Versions only Labels only Versions and Labels ClearCase style gt Order O ascending 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 phas
17. i Instruction i gt j F K Define the sequence and size of columns by dragging in table header Page 123 User Manual TEMPPO V6 1 Edition January 2014 Description of Use DA TEMPPO report setting in project New Project Name NewReportSetting Settings Test Package Test Case Test Step Requirement General a zan A Header Footer i Text EEG aouier Report V Requirement V Requirement attributes ao s Ava able Attributes Selected Attributes Ava able Atributes Selected Attributes Inherited Requirement ID Req State 7 Object ID Requirement Requirement attributes Requirement Description b gt Requirement Name To be tested by Object type Requirement Path VP1 Relevant Requirement Short Description gt IVP2 Relevant Requirement Structure imike type Version K Define the sequence and size of columns by dragging in table header ID Priority State Precondit Nr Instruction Input Expected Requirem Requirem Object ID Object type Figure 144 Tabular Report 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 LA TEMPPO reporting settings
18. lock Applir Discard Figure 362 Starting the update procedure Fi Update JUnit Tests x Steps Introduction 1 Introduction zZ Select a JUnit test class een ee ee ere This wizard quides you through UB SETS necessary ta update JUnit test cases stored in a a peed TEMPP test structure from a JUnit test class Cgres 5 Set package default values ote i i E ee eee E wey The update is based on name Pnz ruine T JUnit test class willbe searched for the names of the PE test packages and test cases stored within the TEMPPO test package you choose to update TEMPPO Extension Panama ce Prey West gt Finish Cancel Figure 363 Step 1 General description of the following steps Page 277 User Manual TEMPPO V6 1 Edition January 2014 JUnit E Update JUnit Tests x Steps Test Class Selection introduction Select the JUnit test class to update from q z Select a JUnit test class 3 Select new JUnit test cases PRICE ihe AEN Clea 4 Select obsolete TEMPPO test cases ih Set package default values junit tests extensions Set test case default values a org junit tests experimental theories 7 Summary juni tests extensions J AllTests org junit tests J AllTests junit tests E Alitests junit tests runner T AllTests junit samples _ Alitests junit tests framework JUnit Classpath fe ATemp_ Pv AtTeststellung PY Aayunita Note Only classes that are inthe JUnit c
19. 0 3 41 2 Open Zl 3 4 1 3 Save oe 3444 Exit Planned tester Testert F 53 4 2 Edit Functions O EHI 3 43 Print Functions Planned test execution time fo h fol min 0 59 Bt 3 4 4 Search Functions he 3 4 5 Help System Sa 3 5 External interfaces of the product c 3 5 1 User interfaces ff 3 8 1 4 Editor Pane fl 3 5 1 2 Search Dialog H 3 5 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 execution effort for all test cases see Figure 44 Page 44 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad olx Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Motepad RTF Import with TCs System Test 41 H d b H oF E Mo filter SMB cters AES A na 1 Introduction Locked by Testmanager H 2 General description of the product General Plan Requirements H 3 Detailed description of the required product f Ea 3 1 Scope of delivery Eg 3 2 Sequences cenarios of interactions 3 3 User goals Planned test execution time 3 h 30 min 0 59 Se 3 4 Required functions of the prod
20. 3 3 20 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 change 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 20 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 211 User Manual TEMPPO V6 1 Edition January 2014 Description of Use gg Er Interface j ape Lagging User Interface General E Font size For multi line Fields Examples description instruction 1 Language C lt English D EE cerman Look amp Feel i Metal i CDE Motif f Windows Windows Classic Restore Defaults Cancel Apply Figure 275 Global Settings User Interface 3 3 20 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 fuchsc temppoilog S Restore Defaults Cancel Apply Figure 276 Global Settings Logging 3 3 20 2 TEMPPO Test Manager Settings Specific settings e g tree display
21. 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 10 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 mechanism which is implicitly used for test execution When you create a test suite TEMPP
22. File c Documents and Settings atw1 12h9 Desktop sitemppolsersGSuideyS mdb S Wa Connect Database Name Database Version Figure 309 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 following 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 24
23. Test Structure Test Sute Notepad System amp Acceptance Test W1 1 1 editable wersion Field test w01 New File opened changes bce 1 Tr a Notepad System amp Acceptance Test W1 1 1 editable version Field test VO1 New File opened 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 ae 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 7 X Bug ID wohe OOOO Analyse User definediD Bug 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 2 1 1_1 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 re
24. User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 20 2 1 Tree Tree settings which can be changed are see Figure 278 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 recursive e g 10 7 03 Delimiter Specifies the delimiter for order numbers e g delimiter in 10 7 3 is 1 Specifies the base for order numbers i e the number added to the internal a order which is 0 based Automatic save Test Step Cells IY Save changes automatically suppress confirmation dialog Analysis Newsboard Automatic numbering Test Suite ne Databaze m Displays automatic numbering of test cases and test packages a ies I Ono for recursive numbering e g 1 2 3 Hin Runner Delimiter for numbering q Universal File H Universal Socket Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands Men Command SE El Change Management Bugzilla Clear Quest Telelogic Change a Defines where numbering starts Restore Defaults Cancel Figure 278 Settings Tree 3 3 20 2 2 Test Step Cells For the test step cells some settings can be changed see Figure 279 Property Default Description value Refresh when resizing activated Switches on off refreshing the row heights in a multi line ta
25. 5 5 3 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 You cannot delete the main latest label or any latest label in a branch 5 5 4 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 337 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 5 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 Metadata is defined project spanning The assignment is made per project Page 260 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator x Test Levels Test Categories Attributes Uploads ff Requirement Struct
26. Edition January 2014 F TEMPPO Testmanager Demo Notepad p Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with Tis System Test red 1 POHO of BE no fiter ALA Notepad RTF Import with TCs Fa 1 Introduction a 2 General description of the product 3 Detailed description of the required prod EA 3 1 Scope of delivery en 3 2 Sequences scenarios of interact a 3 3 User goals Seer 3 4 Required functions of the product ER 3 4 1 File Administration ob EMSA S441 New TERE e4111 New file opened H A 3 4 1 1 2 New file opened 83 4143 New Test Packar A 341 2 Open 43443 Save S414 Ext Eb Ga 3 4 2 Edit Functions eg 3424 Undo Requirements History General Attributes EI mnhertetniutes tE Regilla E Welidation Error fe Verification Additional Test Levels fe Acceptance Test x Test Steps TEMPPO V6 1 Description of Use B x Plan Execution History i Antonration Priority Meaium z state fin work T A Milestone wli EF Platform Windows 7 64 bit ED Regressiontest yes E Test location Offshore 3 4 2 3 Copy La 34 24 Paste ol 3 4 25 Delete abs aa eo mee Merge Lack EPRI Discard fo 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
27. Newsboard 3 3 20 2 5 Test suite You specify if test suites are sorted by name or date in the open dialog Settings x el User Interface gt Tree Test Step Cells Specifies the sort criteria for test suite inthe open dialog of test suites Analysis Mame Date p Newshoard hase El Test Automation Silk Test Hin Runner Universal File H Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex Fl Commands lew Command SSE ElChange Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaukts ores Figure 282 Settings Test suite 3 3 20 2 6 Database For the settings of database see Figure 283 Page 217 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 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 when saving an item in latest version version This setting is used together with deactivated previous setting Example Userl edits a TC in latest version User2 creates new test suite Userl saves TC and the new test structure version is re
28. Page 168 User Manual TEMPPO V6 1 Edition January 2014 Description of Use E 4 Manua 2 Auto General Plan Requirements Template Attributes Test Case template Test Resuit tempiate V Test Case template activated V Test Case template valid oniy for new and updated test cases except viewed test cases General Attributes Test Steps Requirements Pian Mandatory fields V Test goal condition is mandatory Figure 212 Test Case Template General A Test Case template TCT Supports testers to create and update test cases in complete manner For a TCT you can define e Mandatory fields user has to enter a test goal precondition postcondition see Figure 212 and Figure 214 e Default values for the fixed attributes e g priority has to be In work if a test case is created see Figure 213 e Inheritance of UDAs and or defining UDAs as mandatory or with a default value see Figure 213 e Inheritance of requirements and or linking at least 1 mandatory requirement see Figure 215 e Default values for a planned tester and a planned execution time see Figure 216 A TCT is concerned in two cases in TEMPPO When creating a new test case and locking editing an existing one You can activate a TCT for the use case of creating and updating test cases but excluding the use case of viewing clicking trough locking unlocking test cases Page 169
29. RC01 Test object Overall test suite analysis Version XYZ RC02 Press Select Test Suites for choosing test suites Test object Version XYZ RCO3 11 h min 3 h 4 min hart Vertical Bar Chart _ Show 0 values Fh 42 min Cnentation 1 honizontal 6 h 36 min i vertical 5 30 min epee aaa absolute relative passed not executed blocked J not completed l m not implemented 0 min i on hold ay H 5 D a ae LU IS S S S Test Suites Han gt E panned execution time E planned execution time O actual execution time W failed E passed aE X actual execution time E not executed O blocked M not completed W not implemented Eon 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 Not all combinations display valid values Output values x axis y axis Group by Test Suite me Test case IDs Result per test Test Suite Execution Time Tester Execution Time Page 107 User Manual TEMPPO V6 1 Edition January 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
30. Rest O Chart vertical Bar Chart 30 Orientation horizontal Test Results vertical Representation f absolute relative Accumulate Das ist jet Test Suites O blocked M failed Bnotimplemented M passed oe 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 ch
31. Such attributes or new assigned attributes are displayed in Direct inked Attributes Inherited Attributes inheritance Regular 3 Validation Prionty Top Error Veniication State Designed Test Levels Attribute Values io TP Type User case F E F E 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 The tab Inheritance displays the common state of the inheritance flag of the selected TCs If the checkbox is not activated Notinerted all selected TCs do not have any inherited attributes If the checkbox is activated Winhentes all selected TCs inherit their attributes If the checkbox looks like Direct linked Attributes Inherited Attributes Inheritance W inherit Legend F Not inherited E Inherited partially V Inherited E Inhented partly the common state is mixed TCs with and without inherited attributes Page 147 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 3 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 Requirements assi
32. 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 invocation Error return code of test method invocation Page 266 User Manual TEMPPO V6 1 Edition January 2014 JUnit Table 3 Terms used in TE
33. 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 72 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard Steps Choose test cases included with following test result 1 Introduction 2 3 4 Entertest suite name 5 Test suite should include test cases with following results Mv failed m blocked P passed V not completed V not executed V not implemented TEMPPO Test Suite Generator lt lt Prev Next gt 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 Manual Test Execution For every test case you process
34. User Manual TEMPPO V6 1 Edition January 2014 Description of Use 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 the TCT leave a locked TC H TEMPPO Testmanager Test Projec Broect TestStructure Eat Test Executon Evawaton Toos Windows Hep O st Structure Test Structure System Test V2 sera let en ait attr rts E Sone dil os General Pian Requirements Tempiate Test Case template Test Result template V Test Case template activated V Test Case template valid only for new and updated test cases except viewed test cases 7 Regular Validation Pronty Top Inhent attributes Attribute OS Figure 213 Test Case Template Attribute Page 170 User Manual TEMPPO V6 1 Edition January 2014 Description of Use V Test Case template activated Test Case template valid only for new and updated test cases except viewed test cases Test Steps Requirements Pian Mandatory fields 7 Precondition is mandatory V Postcondition is mandatory Lock If Apply Discard o 214 Test Case Template Test Step Test Case template Test Result template V Test Ca
35. User goals or Testmanager UDA Device type add 2 53 4 4 Required functions of the pr 07 03 2012 14 51 01 CAR F 004 S441 Fie Administration Testmanager Attribute Type Validation gt change b A a 4 4 1 1 Windows Login 07 03 2012 14 51 01 Verification Tur Logi Testmanager UDA Regressiontest add no 441 3 Open Testm UDA Test locati dd estmanager est location a 44 1 4 Save 07 03 2012 14 51 01 g B 4 4 1 5 Exit Offshore G42 Edt Functions add 4 4 3 Print Functions change i E Z 4 4 4 Search Functions 07 05 2013 13 46 38 Testmanager General Name change 44 5 Help System 07 05 2013 13 46 38 Testmanager General Test Goal change H 1 4 5 External interfaces of the pi W 4 6 Other product features req a g 5 Specifications for project manage TT i 6 Obligations of the cient C 7 Literature d etd Testmanager Platform add EES apiy New 07 03 2012 14 51 01 Figure 41 History tab Within current test structure version the number of history entries loaded x can be configured in settings see 3 3 20 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 ca
36. 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 closes the window and no project is opened Page 12 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad o x Project Test Structure Edt Test Execution Evaluation Tools 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 Note
37. i 3414 2 New file opened changes 3 44 2 Open i J 341 3 Save Offnen 53 444 Exit Speichern 3 4 2 Edt Functions 3 4 3 Print Functions 3 4 4 Search Functions pa R NE Merge Lock Apply Discard S Figure 101 Editing test cases during test case execution But remember 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 86 User Manual TEMPPO V6 1 Edition January 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 wersion 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 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 ESS ti Xt Select the content which has to be merged M Attributes Iv Test steps Ca Automation
38. 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 whether 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 7 User Manual TEMPPO V6 1 Edition January 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 Parti
39. jump to next previous table cell only if not in edit mode 1 tT 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 49 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools windows Help Test Structure Notepad ATF Import with TCs System Test pu H amp WH b a Motepad RTF Import with TCs Fb 441 Introduction E Ea 2 General description of the product E 8 3 Detailed description of the requirec 3 1 Scope of delivery ae ZE 3 2 Sequences scenarios of in i a 3 3 User goals ee 3 4 Required functions of the pre Et Al 3 4 1 File Administration a LN 34 11 New Pt fl New file opened no chars Locked by Testmanager tcS36 ffnen PRS E 3411 2 New fileo Seicher srota EE a 3 4 1 2 Open Speichern uniter ie 3443 Save T E 34144 Ext 3 4 2 Edit Functions 3 4 3 Print Functions Beenden Et Al
40. lo min 0 597 lo Anply Motepad RTF Importwith TCs v3 Seneral eton wo me hme vesn ate Upaator Changed a1 Test Structure Notepad RTF Import with Tos Wo 20 02 2012 10 53 05 E Testm nager E Testmanager Me 31 Test Structure Notepad ATF Import with TCs VW 16 02 2012 16 36 30 E Testmanager E Testmanager lest Structure Notepad RTF Importanti TCs sistem Test WS H d b W GP EE No iter J Notepad RTF Import with TCs 5 H A Introduction nge 2 General description of the product 3 Detailed description of the required product er E 3 1 Scope of delivery m 3 2 Sequences scenarios of interactions Sa Ea 3 3 User goals Aad 3 4 Required functions of the product I 3 441 File Administration O BA b411 windows Login 3 44 2 New a 2 3 4 1 3 Open General Attributes Test Steps Ea Avtoration Requirements History Plan Execution History User defined ID ftera2 Mame Login Dinner Testmanager Updator Testmanager Created 20 02 2012 102612 Updated 1 02 2012 10 66 57 Automated Test Case lock Apply Hierand ote Manual jen 2 3 4 1 4 Save ii d Figure 226 Newsboard 3 3 11Versioning Configuration management is a task that covers all phases in the test process TEMPPO does not have a connection to current CM tools like ClearCase or MKS Supporting a large palette of CM tools from a v
41. 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 groups 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 Man
42. 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 128 User Manual TEMPPO V6 1 Edition January 2014 Description of Use chart E pata nf Milestone X Axis DLST Group by Priority Orientation C horizontal vertical Cases Test Representation i absolute C relative Accumulate Time Settings sert oo1zz004 ent azz SSC none Priority E Medium E Top 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 Since TEMPPO 5 7 report preview is displayed in Microsoft Word or Microsoft Excel Page 129 User Manual TEMPPO V6 1 Edition January 2014 Description of Use RPreview doc Microsoft Word ais Datei Bearbeiten Ansicht Einf gen Format Extras Tabele Fenster Livelink Frage hiereingeben i OF id 2 t a iV s By 9 S a EREDA T o i standard Ari
43. 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 x Steps Introduction 1 Introduction This wizard guides you through the steps necessary to create atest suite There are three possibilities to create atest 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 Erter test suite name 3 Based on an existing test suite defining restrictions to certain test results Selecting an existing test suite Selecting test results to be considered Enter test suite name
44. 1 TEMPPO Administrator O x Test Levels Test Categories ot Attributes ES Uploads i Requirement Structures Pf 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 Testmanager Testmanager Testmanager 16 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 48 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 IBM Requisite Pro Manual Manual Manual Manual Manual Manual Figure 331 Metadata Requirement Structures Test Levels Test Categories Attributes GB Uploads Requirement Structures CT User Fielde f xE J show requirement attriutes iS Components S Learning Project Use Cases 1 Figure 332 Show requirement attributes Testmanager Testmanager Testmanager Testmanager 16 02 2012 11 24 18 13 02 2012 16 50 26 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 333 It s only possible to un assign attributes when the requirement structure is not im
45. 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 course 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 Wao EJ import Structure i From RTF Document Update d From XML Document Export Structure From Ranorex Document Apply requirement updates From CSW R 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 to TEMPPO attributes Page 22 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Mandatory attributes Name and ID have to be assigned otherwise an import ca
46. Administration a T 5i a 3 4 1 1 Mew E tomaton Requirements History Plan Execution History AE had 1 Mew file opened na goes Attributes Test Steps tH 3 4 1 1 2 New file opened che aoe a inherit attributes re 3 443 Save a 3 414 Exit SS Z H 3 4 2 Edit Functions Peger C validation Priority htedium FH 3 4 3 Print Functions H 0 34 4 Search Functions i Verification State linork ss 3 4 5 Help System eee Sie 3 5 External interfaces of the product jig 3 6 1 User interfaces well 3 5 11 Editor Pane i 3 5 1 2 Search Dialog a o E 3 5 2 System interfaces EAL 3 6 Other product features required I Regressiontest yes A 3 6 1 Performance EP Test location Offshore m 3 56 2 Resource m 3 6 3 Security Ho 3 6 4 Safety EF Platform windows 7 64 bit 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 aim 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 vi
47. Database Connection Fj TEMPPO Manager gt 10 Database Users ui Migrati ar OSN User documentation C Pas Database oracle SID Jats Schema temppo_um Host Jatinzpt a Fort h 521 User jatw112h9 M Login manually SF Test User temppo_um Password Connect Database Mame Database wersion Figure 301 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 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 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 234 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Manager lO x Database zers ui Migratiari DSM EREE O H Database access File CAProgram Filesi TEMPP O 6 0 temppo mdb g Test User Password Connect Database Mame Database Version
48. Execution Evaluation Tools Windows Help z lest Structure Notepad RTF Import with TCs System Test 1 44 gt N OP non Notepad RTF Import with TCs b 2 1 Introduction Vk age J 2 General description of the produ General Attributes Test Steps Ee Automation Requirements History Plan Execution History E a 3 Detailed description of the requir 3 1 Scope of delivery Nr Instruction Expected Action image Pp a i a 3 2 Sequences scenarios of p g E 3 3 User goals File New pickQ Editor Pane cleared ioj x E ay 3 4 Required functions of the Datei Bearbeiten Format Ansicht EG 3 441 File Administration E 1 New Strg N ffnen Strg 0 Speichern Strg 5 3412 Open i Speichern unter 3 41 3 Save ow Seite einrichten o Saa Ext Drucken Strg P Gb 1 3 4 2 Edit Functions 4 3 4 3 Print Functions Beenden 3 4 4 Search Functions E 3 4 5 Help System 1 3 5 External interfaces of the p B E 3 6 Other product features rec ga Specifications for project manage I Untitled Notepad in title bar 5 Obligations of the client J 6 Literature 9 7 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
49. Execution Progress Filtered chart FE Data Test object Version XYZ RC01 Test object i aids i decent on ter sake Version KYZ RC02 Press Select Test Suites for choosing test suites and setting fter Test object Version XYZ RC03 Test Suite Selection Chart Vertical Bar Chart Orientation horizontal vertical Representation Test Results absolute C relative Results 0 Components x reg684 reg635 Value Test object Version XYZ RCO2 Test object Version XYZ RCO3 Test object Version XYZ RCO1 Test Suites 3 Components IN req683 regq634 reg685 E failed passed W not executed iiia 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 109 User Manual TEMPPO V6 1 Edition January 2014 Description of Use DH Test Execution Progress Filtered LE cron E Dan r Test Suite Selection v Resuli Test Suites Test object Ver Testobject Ver Test object Ver failed passed not executed biocked not completed Chart Vertical Bar Chart not mplemented Test suite analysis depending on fiter settings Press Select Test Suites for choosing test suites and setting filter Onentation horizontal vertical Representation absolute relative Results 7 teaed V passed not executed W blocke
50. Exit O Bo Ext file open no changes fi Exit file open no changes O Dd Ext cancel file open changes fi Exit Cancel file open changes O Gd Exit No file open changes fi Exit No file open changes O Gd Ext ves file open changes fil Exit Yes file open changes Open file opened changes 27 01 2004 13 27 15 Fuchs Clemens Figure 253 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 16 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 http de wikipedia org wiki UTF 8 and http www utf 8 com 3 3 17Export Test Suite to DOORS This feature allows exporting Test Suite Results of test cases where requirements from DOORS Requirement Structures are linked to DOORS Page 199 User Manual TEMPPO V6 1 Edition January 201
51. Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution Er Test Structure Notepad RTF Import with TCs H o d gt H E Mo fitter a E 3 3 User goals Sea 3 4 Required functions of the product Soe 3 4 1 File Administration AMS 411 New BES 195 4114 New file opene TERE ee 103 4112 New file openec mie i4113 New Test Packs i 3 4 1 2 Open Fy 3 4 2 Edit Functions ee 5 4 2 1 Undo EET gt 3 4 2 7 Time Date m 3 4 2 8 Word Wrap oa 9 Set Fort 2 m 3 4 3 1 Page Setup LD 4 2 Print Sao 3 4 4 Search Functions CE 4 4 1 Find E a EER gt 4115 A B 3444 2 Find down Era H 3 5 External interfaces of the p ea it deg or Figure 171 Before and after Select all e Select non contiguous 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 TEMPPO V6 1 Description of Use Page 142 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution E Test Structure Notepad RTF Import with TEs H 4b WH E Mo fitter poe Eg 3 3 User goals a 3 4 Required functiona of the product Seo 3 4 1 File Administration o BAA 341 1 New Oi e 341 411 Mew fle openec il EER New iile op
52. 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 central 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 93 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi Test result comparison Test Suite in Export Database Test Suite in Master Database El u 1 Test Suite for export a l Test Suite for export a O A1 Main Menu 2351 A re ain Menu 2351 d e A BBD ii Main Menu 28 11 2002 15 07 54 2 bef 11 Main Menu gt O B i Majin Menu 28 11 2002 15 07 56 pf 1_2 Main Menu Pte O BBD 1
53. Manual TEMPPO V6 1 Edition January 2014 TEMPPO Designer IDATG F Connection status 4 x Locking structures OK Prepare data ating for TEMPPO Designer IDAT Gi to connect Figure 376 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 378 displays a sample step FR IDATG Task SubusecaseNewalreadyopened E loj x Project Edit Draw View Window Generate Help AEREA TCE S B 4 a aa Task SubusecaseNewalreadyopened Call_ menu Entername Press OK Window k k k k Closed Et i ry Press M X Ser Project Notepad System amp Acceptance Test Efe IDATG Tasks ee Use case File New o Sub use case New already o
54. Rezu E Requirement Description Cancel Fi Properties of New Entry x General Details E Browser Chrome EF Browser Firefox E Browser Netscape ED Browser Opera Cancel Figure 326 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 possibility of copy and rename copy an existing UDA with or without values and rename it is offered Page 252 TEMPPO V6 1 TEMPPO Administrator User Manual Edition January 2014 A TEMPPO Administrator Testmanager j Test Levels Test Categories Atinbutes E Uploads Requirement Structures ET User Feds oE X Gola e mi lst Schon Te _ Medenstein 4 New Entry eo New Entry Hee 7 Treiber Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Created 224 3 2013 13 46 46 12 09 2012 14 21 37 22 11 2013 13 46 45 22 11 2013 13 46 43 22 17 2013 13 46 44 22 11 2013 13 46 45 22 17 2013 1346 47 12 09 2012 14 21 01 12208 2012 14 22 11 22 11 2013 13 46 46 22 17 2013 1346 42 Figure 327 Copy of UDA Attribute Type Test Case Test Package Test Case Test Case Test Case Test Case Test Case Test Case Test Suite Test Case Test Case Test Case Creaton Type manuaay created manually created manuaay create
55. TEMPPO V6 1 Edition January 2014 Description of Use Ei Open Test Suites X Tree style S Motepad RTF Import with TCs Eee Versions only H 4 Test Suites for v1 1 2012 02 16 Fl editable version ben Test object Version XVZ RCO1 16 02 2012 Versions and Labels Labels only p Test object Wersion ye Reco 1 6 02 201 2 E r 2 Test object Wersion Ye R03 1 6 07 20 2 Spann goog E SUEOUaTOOTEICL ESD z Test object version xvZ RCO3 COPY 16 02 2012 l Order o EA Test Suites for V2 1 2012 02 16 ascending EHS 1 editable version H Version 2 of Test obeject RCO 16 02 2012 J editable version 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 offi
56. Tested General Attributes Test Steps EI History Plan Execution History ia Test object Version passer Testmanager 16 02 2012 15 11 02 XYZ RCO Test object Version 1 1 editabl Tits D6 Testmanager XYZ RCO1 Version 2 of Test 2 1 1 editable S79 Testmanager jobject RCO1 16 02 2012 15 11 23 07 03 2012 14 59 15 Figure 46 Execution History only executed results If 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 Requirements History Plan Execution History V1 1 1 editable version Test object Version V1 1 1 editable AT RCOOS COPY version V1 1 1 editable version V2 1 1 editable version 16 02 2012 15 11 23 0r 03 2012 14 59 15 Figure 47 Execution History 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 befor
57. 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 111 User Manual TEMPPO V6 1 Edition January 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 Surtees New Test Suite V611 Mew Test Sute Vei 1 Requirement Structures Select Structures Components Notepad Requirement attributes ka v Requirement faled passed notexecuted blocked notcompleted notimpiemented on hold Chart Horizontal Bar Chart h Funcregz2 o o o o o o J o A Fuere o o o o 0 oi 0 alphabetical Func o 1 a o o o o 3 ascending Fereg o 1 a o o w o Be Fucea o o o o o o o Func res o o o o o o I aes Funcrege o 2 2 o o o f o a Fuerer o a 1 Lo G o E c gt Only zero values Fucea 1 4 5 o oo o o BS eG Fucea 1 4 5 o o w 0 Fucea o o o o o o o Refre Funcreggo 4 4 5 o o o o Funcreast 1 4 5 o o o o Func reg 1 4 5 o o w o x Figure 136 Requirement analysis over several test suites Data In tab Deta
58. Type Test Package wo 3 4 4 2 Search down Number of TCs 0 3 4 5 Help System E fa 3 5 External interfaces of the product Test Category x H 3 6 Other product features required ie io Description E 4 Specifications for project management A 5 Obligations of the client a 6 Literature i OF Annex Lock Apply Discard bot 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 requirements 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 28 User Manual Edition January 2014 Fi TEMPPO Testmanager Demo Notepad TEMPPO V6 1 Description of Use lox Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import wih TEs H 4 gt H 45 E Mo titer hai AL Notepad RTF Import with TCs FL Introduction E ee 2 General description of the product a 3 Detailed description of the required prods EIF E 3 1 Scope of delivery hoy ZE 3 2 Sequences cenarios of interactic ais 333 User goals Te 3 4 Req
59. User Manual Edition January 2014 H Scheduler Ls i lt Mame 1 Locked by Strasser Johanna Scheduler Start Time 30 06 2012 13 55 Stop Scheduler Current State 0 12 Test Cases 31 12 2012 13 00 b a Curent State 4 4 Test Cases Create Payer 17 12 2012 142 17 12 2012 14 a Create Paye 17 42 2012 14 17 42 2012 14 a Edit Person 17 12 2012 14 17 12 2012 14 fel Record_test VF A22012 14 00 WPA 2012 E Figure 271 Finished Scheduler In Details information about executed test cases are shown 3 3 18 5 Protocol of Scheduler TEMPPO V6 1 Description of Use All test case executions of a scheduler can be shown by pressing Show L Scheduler Protoco Page 208 User Manual Edition January 2014 t 15 06 2012 t 15 06 2012 t 07 06 2012 t 01 06 2012 t 01 06 2012 t 01 06 2012 t 01 06 2012 t 01 06 2012 t 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 t 01 06 2072 t 01 06 2012 t 01 06 2072 F New Test Ej New Test Fs New Test a New Test Started T Finished Result 15 06 2012 15 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 passe 01 06 2012 passe 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 passe 01 06 2012 passe 01 06 2012 01 06 2012 01 06 2012
60. User Manual TEMPPO V6 1 Edition January 2014 Appendix else vest is for summary summary append line summary append System getProperty line separator ree summary summary toString return ret x Implementation of result interface 77 class Result implements Result String summary T int result BLOCKED public String getSummary return summary public int getResult return result L3 7 3 3 Implementation and integration steps 1 Create following subdirectories in your TEMPPO installation directory SINSTDIRS Gev sre ext SINSTDIR 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 S launcher properties libby bemppo jar libolibo jar 1ib commons codec 7 ar Lib commons nirtpclient 7 4ar 1ib commons l00q01inG ar Lib Vcommons Cli jary Lio junit are lib recistry Jar Lib sql d6c j ar lib oracl e jar lib oq dbc ar Page 308 User Manual TEMPPO V6 1 Edition January 2014 Appendix lib jcommon jar lib jfre
61. a scheduler Import an existing scheduler from other test suites see 3 3 18 3 e Run a scheduler Execute all test cases selected for scheduler now or at Start time see 3 3 18 4 e Protocol of a scheduler Visit all results set by scheduler see 3 3 18 5 3 3 18 1 Create Edit Scheduler After opening a test suite activating tab Scheduler and pressing button New Edit new window opens where all settings for the scheduler can be defined In register General e Name for scheduler e Scheduler Start Time Scheduler has to be started until this time Scheduler cannot be started after this date e Description for scheduler e Selection of test cases which has to be executed Page 204 TEMPPO V6 1 Description of Use User Manual Edition January 2014 In register Advanced e IP address Port An IP address and port can be defined for all automated test cases using Universal Socket Remark Selection of test cases All test cases in tree are shown in a list with a checkbox Only the selected test cases are executed when scheduler is started The execution of test cases can be ordered with the buttons beside the table mE FF scheduler Universal Socket IP Address Port Number Updator Updated Locked by Scheduler Start Time 17 12 2012 00 00 Description E Create Player Ej Create Player 1 E Edit Person New Test Case E Record_test iE Record_test 1
62. 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 104 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Filtered Additionally a filter 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 cas
63. 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 276 User Manual TEMPPO V6 1 Edition January 2014 JUnit Fi TEMPPO Testmanager Demo Notepad E ioi Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Stace Lr System Test MVI Se M db Mg EE no nter D TEMPPO Designer IDATG J Juni oe 1 Framework Tests ce 1 1 junit tests extensions Extension Test way 144 testRunningErrorlnTest Setup unit t coy 1 1 2 test Setup Error In Test Setup junit tes ID fo7e2 E 1 2 juni tests extensions Active Test Test o hajg 1 21 test ctiveTestjunit tests extension oh 1 2 2 testActiveRepestedTest0 unit tests Nemz Framework Mes ce 1 3 junit tests extensions RepeatedTest Test why 1 3 1 test Repeated Once junit tests exten ly 1 3 2 test Repeated More Than Once junit t Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 29 ody 1 3 5 test RepeatedZeraqunit tests extens ahg 1 3 4 test Repeated Negative junit tests ex General Attributes Details Requirements History Plan Owner Testmanager Updator Testmanager Type Test Package Humber of TEs amp Test Category a Description ported by TEMPFO trom JUnit Suite junittests extensions AllTests
64. case E Automation General Requirements History Plan Execution History Attributes Test Steps 7 3 4 41 2 Find down i 3442 Replace o 345 Help System H 3 5 External interfaces of the product H 4 3 6 Other product teatures required ag aed 4 Specifications for project management fa 6 Obligations of the client fi 6 Literature i T ANNEX 4 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 65 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 72 ROO 41 1 1 M d b H Gh EE No nter 7 TENE x a FE TE i amp 3 Detailed description of the required g El 3 4 Required functions of the proci General Details Export Info Attributes Predecessor Plan Eh a 3 441 File Administration O EA3411 New Mame Test object Version WZ RCO A 3441 14 New file ope fi 3411 2 New ffile ope Owner Testmanager Updator Testmanager r 8 3 44 Search Functions ag 4 3
65. command is defined by its name path and arguments The name has to be unique Page 228 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Sr x Commands l User Interface Tree New Command pw Test Step Cells Analysis H Newsboard Test Suite Database El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test Partner JUnit be TEMPPO Designer IDATG i Ranorex a mimands New Command SESE El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 294 Settings Command Hew Command El User Interface Tree Mame hew Command Test Step Cells Analysis Path CAorfice exe g H Mewsboard Test Suite Arguments Hest doc Database El Test Automation Pe Silk Test bitin Runner Universal File Delete gt Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex El Commands iD Command aan tT El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Figure 295 New Command 3 3 20 2 12 Change Management Select the change management tool which is used in TEMPPO for adding bugs to test steps Page 229 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Change Management l User Interface Tree Test Step Cells ie Bugzilla Analysis H Mewshoard Test Suite ClearQuest Active Cha
66. 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 113 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Omer Created Description Testmanager TEMPRG default setting NewRepotSeting Report depth Testmanager 07 03 2013 15 22 06 Report Template Testmanager 1602 2012 16 36 07 TC Review Template 3 Test creation report Excel tight Testmanager Continuous text Amost af test package attributes Aimost afl of test case att Test creation report Word tight Testmanager Continuous text Test packages with description Test cases with preconait JoHa 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 1 New Edit When pressing the button New or Edit a new wi
67. description of the required product features E Required functions of the product J File Administration New D New file opened no changes not executed D New file opened changes not executed J Search Functions Find Find up E Case sensitive not executed WinRunner Check Stat not executed E QuickTestPro ed AB Test Partner Test case not executed EJ not executed expression 6 Remove test cases manually TEMPPO Test Suite Generator lt lt Prev 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 Bi versions x w Notepad ATF Import with TCs Edit Evi EAA A Test Suites for V1 41 2012 02 16 C Check In LEF W414 editable versi irm Werge Tree style Versions only E Labels only f Versions and Labels ClearCase style Order O ascending 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 is always just a view of the underlying test structure in the activated version Only test cases are visible that fulfill t
68. from another project then the following window opens x Be ae mem Report Template eres 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 133 User Manual TEMPPO V6 1 Edition January 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 E Eigene Dateien Ri JE E Aktien O Media Go C Artikel 5 My Meetings E audi Eigene Musik CC TestFactory 2 Eigene Bilder fm Downloads Q My Podcasts F Eigene Datenquellen G My Received Files Cj error Report201 213021 30732 ey Eigene videos C error Report201 21402144468 5 Nerovision gt error Report201 2150241 33105 gt Obsorge frm gegl 0 0 Ranorex 5 HP O SAP C MO RAAT Schlosser Home E MENS Working jy SharePoint Drafts Cancel of File name Open Hebei Files of type mL Document File xml TEMPPO Reporting Property File tre Figure 158 Import report settings In the file dialog you can set the type of file to
69. 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 zero 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 25 User Manual TEMPPO V6 1 Edition January 2014 Descr
70. 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 232 User Manual TEMPPO V6 1 Edition January 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 ee ai Cells Server e922 2 paralysis pe Nlewsboard Port e644 Test Suite Database Context o Ars EN Database tutorials Telelogic Change H Silk Test WinRunner File of list box entries S H Universal File H Universal Socket n QuickTest Pro File of default values S Test Partner TEMPPO Designer IDATG Authentication TE User fata 0gs E Commands i H New Command Pazaword reanna i Java32 El Change Management Role user Bugzilla Restore Defaults OK Cancel Figure 300 Telelogic Change Page 233 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Manager 4 TEMPPO Manager The following TEMPPO configurations are done with the TEMPPO Manager tool Database connection User management create a TEMPPO super user Database migration 4 1
71. 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 expected 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 ina 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 295 Us
72. its father item doesn t exist in the latest version E New Test Case tc117254 D New Test Case tc117252 Gd New Test Case tc117256 Test cases Test Packages couki not be merge because its father test package does not exist in latest version Please select and merge it A New Test Package tp117253 Success B New Test Package tp117251 Success Figure 180 Merge summary Page 151 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 4 1 Test Suite After activating the menu Edit gt Show Details the tab Attributes TR is displayed e tab Attributes TR see Figure 181 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 ina special color grey background color New added attributes are displayed in red color Fi TEMPPO Tester1 Demo Notepad TENE Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 2 REOR COPY W11 1 Wo d Po H ghi no titer if sa 4 AL Test object Version v2 RCOS COPY Te AENA I amp 3 Detailed description of the required g EEE eaa eae El 3 4 Required functions of the prodi attributes TR Pian EHI 3 4 1 File Administration in i Eb a 3 4 14 New a i i g one ests Attribute Values i a2 Mew file i ee TS 3 440 Search Functions Firmware version 0 1 00 1 3 4 44 Find I beg 34 414 Find
73. 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 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 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 73 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Pi TEMPPO Testmanager Demo Notepad PF ioj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RE01 41 11 M 4 gt N GP EE no niter IM Yd Test object Version XYZ RCO1 E amp 3 Detailed description of the required g EHN 3 4 Required functions of the prodi juowetion Requirements History attributes TR Previous Resutts Plan Execution History 3 4 1 File Administration General Attributes Test Steps B a 3 4 1 1 New fl 3 41 11 New file ope EE
74. manually reopening the test structure test suite F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x e Test Structure Notepad RTF Import with TCs System Test 13 AL Notepad RTF N he whole tree EE 1 Introduction H Ea 2 General description of the product E amp 3 Detailed description of the required prod 3 1 Scope of delivery a 3 2 Sequences scenarios of interact E 3 3 User goals E 3 4 Required functions of the product ae 43 4 1 File Administration a 3 4411 New ee Tek 64 1 Mew file opened Error E 344 1 1 2 New file opened BB 3 4 1 1 3 New Test Packac 3 44 2 Open Requirements History Plan Execution History General Attributes Test Steps Fy Automation Inherit attributes Priority Medium state lin Work a Attribute Wales Regular Validation f Verification Additional Test Levels i H 3 4 1 3 Save o e 34A Exit 3 4 2 Edt Functions A 3 4 3 Print Functions m 3 4 4 Search Functions a 93 4 5 Help System E aa 3 5 External interfaces of the product E as 3 6 Other kama features soca 1 dimn b E Milestone M1 EP Platform windows 7 64 bit EP Regressiontest yes EF Test location Offshore Lock Applir Djecand T Acceptance Test x Figure 166 Button Reload for reloading the whole tree 3 2 2 1 2Refreshing recursively You ca
75. ne ccc Fr Instruction Expected O Baa Find i 5 i Mase 4 Find up Enter search phrase Hugo a T TE Mis 44444 Cas 5 Specify search up bs ah cE 3 444 122 QuickTe direction db J Required functions of the product Search Functions file testikt opened Ea Find find dialog open Find up ECursor at EQF M Case sensitive L 3 4 4 2 Replace Fress Search Search phrase tound and marked Pb e345 Help System lay Bae Ss 3 5 External MIERE of the produ i o eS a 3 51 2 Search Dialog A i E 3 5 2 System interfaces E 3 6 Other product features requirec 1 Performance 2 Resource a Security 4 Safety Path Postcondition 5 Portability 5 Detailed description of the required product featu eee Z Required functions of the product A Maintenance 5 Reuse i 5 Usability i ea 4 Specifications for project managemerr Find up L 5 Obligations of the client Meee eal 6 Literature Ea E T Annex O B 5441 2 Find down DE Press Search Search phrase found and marked E file test tst clased Figure 48 Test Case Preconditions and Postconditions 3 1 3 1 2Test Steps The test step editor provides functions for 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
76. parent test packages are listed Page 29 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad 2 i 7 ioj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test vit n j E xX E a S BB ho fter ALI Notepad RTF Import with TCs Fb 1 Introduction Locked hy Testmanagel J 2 General description of the product General Attributes Details Requirements History Pian j a 3 Detailed description of the required prods F 3 1 Scope of delivery Document CtempiPfichtenheft_Notepad_withTC rtf 3 2 Sequences cenarios of interactic a 3 3 User goals Mame ERT 3 4 Required functions of the product OO BP 3 4 1 File Administration Chapter 3 4 2 Edit Functions o E 34 3 Print Functions Eb 3 44 Search Functions SEER Precondition a a A J Search Functions file test xt opened Bo SEH 4 5 Help System Fy 3 5 External interfaces of the product a a i H E 3 6 Other product features required E 2a 4 Specifications for project management ei Ea 5 Obligations of the client C 6 Literature Postcondition H 7 Annex Precondition Postconditian L Detailed description of the revi _ Required functions of the product Search Functions tile testtt closed n z Find Lack Apply Discard Si Figure 27 P
77. passe TEMPPO V6 1 Description of Use Figure 272 Scheduler Protocol 3 3 19Task 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 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 Page 209 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Project Test Structure Edit Test lt 3 Task lists JADIS Phase 1 V10 Ela ADIS requirements Advanced Driving Info HW New Requirement New route require aiii ge TAERA pees ee ee LE CALE dispered roUe Contains E 1041716 Blue displayed route contains i T to41717 Blue displayed route contai Type Test Case ID tc41002 Requirement ID 7450 Requirement Name Hue dispayed route contains white arrows after each mancever Description Te will be marked as obsolete OF since version Reason of Creation Deleted Requirement il 2 Current position E 2 4 Current car position red User defined ID te41717 ca ia 3 Destination Name Current car position drive roundabout Ee 4 Along the route Owner Schiosser Dietmar Updato
78. structure does not cause that a task list is created a task list 3 3 18 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 P i 1 There are no newer checked in 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 input 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
79. test The test 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 iol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure JUnit System Test 41 Wo d amp WH amp E No filter A JUnit ai Framework Tests a ill 1 junit tests extensions Extension Test General Attributes Test Steps EJ Automation Requirements History Plan Execution History DE 1 11 test Running Errorlin Test Setup uri t sagi 42 test Setup Error In Test Setup junit tes User defedi here I 1 2 junit tests extensions Active Test Test Gy 1 241 test ctiveTest unt tests extension Name ftestRunningErrorinTestSetup unittests extensions ExtensionTest ahg 1 2 2 testActive Repeated Test0 junit tests ois 1 3 junit tests extensions Repeated Test Test Owner Testmanager Updator Testmanager y 1 3 1 test Repeated Once junit tests exten ay 1 3 2 test Repeated More Than Once junit t aly 1 3 3 test Repeated ero junit tests extens Type Manual f Atomated Test Case why 1 3 4 test Repeated Negative junit tests ex Created 20 02 2012 15 57 27 Updated 20 02 2012 15 67 26 Test Goal Lock Apply Discard Figure 360 Step 5 Names of test cases JUnit test methods Basically you are free to edit and change the automatically created struct
80. test package is selected It can be activated by the menu or a right mouse click A new child node Mi 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 38 User Manual TEMPPO V6 1 Edition January 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 by with TEMPPO s find feature F TEMPPO Testmanager Demo Notepad J ia oy xi Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test w1 Mo titer al 3 1 Scope of delivery 5 2 3 2 Sequences scenarios of interactions Spee Ueto EEE Pv 3 3 User goals fl Automation Requirements History
81. 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 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 8 User Manual TEMPPO V6 1 Edition January 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 b
82. 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 268 User Manual TEMPPO V6 1 Edition January 2014 JUnit Fi TEMPPO Testmanager Demo Notepad f Project Test Structure Edt Test Execution Evaluation Tools Windows Help D TEMPPO Designer IDATG Update O x Figure 350 Starting the import procedure x Steps Introduction 1 Introduction 2 Select a JUnit test class ae i f ae eee ere eee This wizard guides you through the steps necessary to import JUnit test cases into a TEMPPO test structure Cdees 4 Set package default values Anew test case will be crested for each imported JUnt test case Anew test package will be created for each JUnit test suite reflecting the hierarchical structure of the imported JUnit test class 5 Set test case default values G Summary Mote Updating i based on name matching The generated names of the test cases and test packages should be preserved to maintain their relation to the JUnit classes TEMPRFO Extension JUnit zz Frew Ment Finish Cancel Figure 351 General description of the following steps In the next step the JUnit test class can be selected All classes with names that start wit
83. 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 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 134 User Manual TEMPPO V6 1 Edition January 2014 Description of Use ser Interface Test Automation IY Switches on off a database chooser window on TEMPPO startup H Commands Change Management fi O Timeout in seconds displaying OSM choo
84. up Apply Discard amp Be amp amp amp Figure 181 Attributes TR 3 3 1 4 2Filter in multi selection mode If there is a multi selection and a filter is set only those items that match are considered If the items of the multi selection are still shown they are selected again see Figure 182 and Figure 183 The Show Details menu item has to be activated again because the selection has changed Page 152 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad a i 5 x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Motepad ATF Import with TCs A 1 Introduction r nenny your TSS SIECHO tate a 1 1 Purpose of the document General Test Packages Test Case nE 1 2 validity of the document i ti ee 1 3 Definitions of terms and abbreviati 414 Relationship with other documents Total number of selected TPs 28 445 Overview of the document a 2 General description of the product Total number of selected TCs 7 iais Fee 2 1 Relationship with existing projects Siete a 2 2 Relationship with earlier and follow Siete 29 23 Purpose of the product ings T 24 Delimitation and embedding of the tices 2 5 Overview of the required function iai T 26 General restrictions tags T 27 Hardware and software specificat i fe Z 2 8 Product users Zl 3 Detailed description of the required proc ae E 3 ery ee Scenarios of interac
85. v Test Results o 1 2 Sort alphabetical ascending descending Values All Only zero values No zero values ose Figure 122 Test Suite Requirement Analysis Fi Requirement Analysis x Requirement Structures Module 14 v Requirement attributes MEE Aandi Filter Calculate g Chart Ea Data Sort Test Results alphabetical ascending descending Values All Only zero values No zero values oe 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 101 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ei anatysis ee x Load S Analyse Uselt Load comma a bug IDs Bug IDs
86. where it was created During the opening process the adequate version of the test structure is loaded automatically x A Notepad RTF Import with TCs p ee ule chev versions only hw 1 Test Suites for V1 1 2012 02 16 cr EMEP v1 1 4 editable version pean Test object Version v2 RCO 16 02 2012 Versions and Labels Test object Version lt Y2 RCO2 16 02 2012 a Test object Version v2 RCOS 16 02 2012 AS Test object Version Ye RCOS COPY 16 02 2012 YW editable version ClearCase style m Order i ascending 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 85 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fnd and Replace F3 Edit test case Sao Details Saleck All Chrl 4 tf Tee a b Run auto
87. you will get the following dialog see Figure 164 after pressing the Finish button on the test Suite wizard LIM j x i j There are locks in test 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 137 TEMPPO V6 1 Description of Use User Manual Edition January 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 E xj Warning Found locks 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 E5 on top of the tree see Figure 166 This has the same effect as
88. 0 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Fi TEMPPO Administrator Testmanager IOl x Database Roles E Users a Metadata LA Projects Locke License TEMPP Editor schema Owner 13 02 2012 13 04 02 TEMPPO 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 TEMPFO Tester Schema Owner 13 02 2012 13 04 05 Figure 310 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 Page 241 User Manual TEMPPO V6 1 Bicle properties ES General Details S TEMPPO Key Tester Created 13 02 2012 13 04 04 Creator Schema Owner Type Role Change icon 16x16 Pixel Description eres Fi Role properties i X General Details Update Test package El Assign test categories Edit 4 aad 4 Link requirements Merge Test case Assign test case attributes Assign test levels Edit 101001 nan aa OOooOogd Link requirements Cancel Figure 311 Role properties General Details The functions are predefined and cover the whole functionality of TEMPPO Administrator and TEMPPO Lev
89. 1 Filter name already used After saving the new filter Figure 242is 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 Personal Fiter Project Fiter O Haa bilkin re be ac 1 Pal h gt n state in review tesi cases Ay MA 48 state_in work test cases i E AT Market in v laus 4 i Market IN fal US Aide Empty Subtrees Figure 242 Selected filter 3 3 13 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 Page 190 TEMPPO V6 1 User Manual Edition January 2014 Description of Use Filter ESE m i T a Personal Filter Project Filter E Pad Hti Testmanager Testmanager Testmanager E Testmanager Testmanager 29 04 2013 13 00 33 a7 Testmanager canca _ Figure 243 Edit filter Depending on the selected filter the conditions are displayed Filter name is read only filter conditions can be changed See Figure 240 3 3 13 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 191 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LA Filter b Mim i Personal Fiter Pr
90. 1 1 Editor Pane ff 3 51 2 Search Diak 93 5 2 System interfaces SR i nrar it 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 f Ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help gt Test Structure Notepad RTF Import with TCs System Test 4 E O xj M d gt b H o E mor AL Notepad RTF Import with TCs 1 Introduction 2 General description of the prc General Attributes Details Requirements History Plan 3 Detailed description of the rec eo 3 1 Scope of delivery Bees J 3 2 Sequences scenarios Requirement ID Requirement Mame Requirement Structure 0 al m m a 3 3 User goals O aane eel H E 342 Edit Functions functions of the implemented o E S 3 4 3 Print Functions product eee 3 44 Search Functions Func_rege Mew Notepad w1 All Poi og Implemented requirements iFuncreq e Sawe Notepad W1 Al implemented er 3 4 4 4 Find requirements Delete requirement ee 3344 2 Replace 3 4 5 Help System Seo 3 5 External interfaces of th 5 8 3 5 1 User interfaces ce fi 3 5 1 1 Editor Pane fi 3 5 4 2 Search Diak 5 5 2 System rere 4 F
91. 1 tc536 New Test Suite V6 1 1 i T T ji T T T Func_req27 Notepad V2 IF tc536 New Test Suite l H Func_req2s iNotepad 1 ltc703 Ne tc702 New Test Suite V6 1 1 L ee Se eee 4 adi lie TOn Tm E 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 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 Ifa test 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
92. 2 2012 10 56 56 i Changed since last login 20 02 2012 h o0 24 lo min 0 59 lo Apply Motepad RTF Import with TCs W3 General o e w Named e w oe Changed Test Package File Administration 20 02 2012 10 25 59 Testmanager Testeri Changed Test Package New 20 02 2012 10 46 56 Testmanager Testeri Changed Test Case Mew file opened no changes 20 02 2012 103018 Testmanager E Testeri Changed Test Case Mew file opened changes 20 02 2012 10 53 04 amp Testmanager Testeri Changed Test Package General description of the product 16 02 2012 18 00 46 FF Testeri Testmanager Changed Test Package Windows Login 20 02 2012 102613 Testmanager E Testmanager Changed Test Case Login 20 02 2012 10 56 57 Testmanager E Testmanager Changed Test Case Case sensitive 20 02 2012 10 53 05 amp Testmanager E Testmanager Changed Test Package Find up 20 02 2012 10 53 05 Testmanager E Testmanager Test Package Windows Login 20 02 2012 10 25 59 amp Testmanager E Testmanager Test Case Login 20 02 2012 10 2612 Testmanager E Testmanager Page 181 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad 7 EE oj xi Project Test Structure Edit Test Execution Evaluation Tools Windows Help a Newsboard Notepad RTE Import ith Tes Eval 5 x Updated 20 02 2012 10 56 55 Refresh Changed Since flest login T 20 02 AoT w h 00 24
93. 3 4 4 Search Functions ob BA S441 Find oo ER 3 3 4 4141 Find up yi b 3441141 Case RET Mo fiter General Attributes Test Steps Ei tematic Requirements History Pian Execution History Ne instruction Aetion image Expected File New pick I Unbenannt Editor Editor Pane cleared te Bearbeiten Format Ansicht 7 Strg N Seite einrichten Drucken Strg F li 344112 Quic DP Untitled Notepad in title bar r 3 4 4 1 2 Find down 3 4 4 2 Replace af Pa E 34 5 Help System Bs t 1 35 External interfaces of the pri F a5 User interfaces F i E lock AHI Biecang 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 automatically 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
94. 3 Main Menu 28 14 2002 15 07 59 bff 4_3 Main Menu I A 2 Destination Entry Ej A 2 Destination Entry I 24 2 4 GeneralPrinciples Eb La 21 GeneralPrinciples E 2A 244 Destination Entry via speller l E Al 2 1 41 Destination Entry via speller B 7 421 14 Speller usage 2353 n 4 Ee 41 Speler usage 2353 s H M 11 1 Speller_ Usage Town 28 11 2002 15 08 02 Pb fo opoo ope oe Il 2 1 1 1_1 Speller Usage Town 26 11 2002 15 27 17 p W E 24 14_2 Speller_Usage Street 25 11 2002 15 08 04 ey ffi 2 1 1 1_2 Speller Usage Street 26 11 2002 13 27 21 ae M P pop He O BB 2i 4 Speller_Usage_Zip_codes 28 11 2002 15 08 EOP io Go ef 2 1 1 4_4 Speller_Usage_Zip_codes 28 11 2002 15 27 28 be O E 2 1 1 4_5 Speller_Usage_house_numbers 28 11 2002 1 oi do befi 2411_5 Speller_Usage_house_numbers 28 11 2002 15 E O Sa 2411 2 Best match line E A a 244 2 Best match line ee LI Gil 244 21 Best_Match_Line_Town 2607 2 efi 214 21 Best_Match_Line_Town 2607 O Gil 211 2_2 Best_Match_Line_Street fl 2 11 22 Best_Match_Line_street O Gil 2142 3 Best_Match_Line_Housenuriber SH 2 1 1 2_3 Best _Match_Line_Housenurmber O Gil 2 14 2_4 Best_Match_Line_Intersection 2608 oo pi 2114 24 Best_Match_Line_Intersection 2608 oo de O Gil 2441 2_5 Best_Match_Line_Special_Destination 2609 eff 2141 25 Best_Match_Line_Special_Destination 2609 H O a 24 14 Auto Expand and Auto Delete function 2355 ae i D 5 2 1 1 4 Auto Expand and A
95. 336 you can select between a text and image column for test structure or suite Page 257 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Fi Properties of New Entry X General gi Pe Entry Created 13 10 2010 11 13 29 Owner Testmanager Type Additional Test Step Column Usage Test Structure Type f Text t Image f Test suite Figure 336 Additional test step column 5 5 Projects A TEMPPO Administrator Testmanager ii ik ee Database Roles users metadata LA Projects 9 Locks License HELETE SE E Demo Notepad Ee Example for versioning ae Notepad generated cae Link test cases to requirements C E Notepad RTF Import with TCs B Notepad RTF Import l BA Notepad System amp Acceptance Test S A New Project BE New Test Structure Figure 337 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 and copy 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 338 is displayed The user specifies a unique name and a description TEMPPO automatical
96. 4 Description of Use DOORS p TEMPPO Baseline Requirement Test anager Manager DEV1 1 0 _ DEV1 1 0 Test Structure Req1 Req1 V3 1 1 PLM1 1 0 Req2 import Lupaa Req2 elo Sales 1 0 Reqt Req3 Req3 TC1 Req1 TC2 Req2 TC3 Req2 Req3 Req3 n Reqd DEV2 2 0 DEV2 2 0 bet Req1 Req1 te Reqd i TC6 Req2 import update Req2 Req3 Req3 opy of DEV1 Req1 y Req2 Test Suite T2 X TC3 of opy of DEV2 Tc4 X Reqi TCS of Reqs 3 Figure 254 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 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
97. 4 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 62 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard 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 RCO1 expression a Remove test cases manually Created 16 02 2012 13 39 43 Owner Testmanager Type Test Suite Description Whole 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 constructed using test package categories test levels and test case attributes Specifying a logical connector in the last line can extend the
98. 441 Find a 3 4 4 1 1 Find up Type Test Suite fi 3 441 414 Cases B H E 34 41412 winPur Description hole structure H E 34 41 415 QuickT Release canidate 01 H E 34 4114 Test Pe ff 344115 UA no Created 16 02 2012 13 47 29 Updated 16 02 2012 13 47 29 IncludedTPs Mew Find Excluded TEE 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 Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 272 ROO v1 1 1 MH d b H h EE No iter EEPE object version Xz Ren amp 3 Detailed description of the required g El 3 4 Required functions of the prodi General Details Export Info Attributes Predecessor Plan Et sr 3 4 1 File Administration Attribute EE EM 3411 New 3 4111 New file ope i an an a PA i 3411 2 New file ope r 5 3 4 4 Search Functions l 4 3 441 Find j a 3 4444 Find up fi 3 441 414 Case s AT 34 4442 WinPur H E 3 4 4113 QuickT H E 34 41 14 Test Pe ff 3 4 4445 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 report Only attributes can be chosen that are indic
99. 50942636 1262636672962 13 Screenshot_1305604035020619001_ 1365004036346 13 Telematics xm UserManual pdf Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Figure 329 Metadata Uploads If you activate Delete all non referenced uploads a confirmation window see Figure 330 is arae before deleting all non referenced uploads Delete unreferenced uploads E x A Figure 330 Confirmation window 7 Do you really want to delete all unreferenced uploads 22At a 08 122013 1T 09 12 2013 17 22 11 2013 13 12 09 2012 14 09 12 2013 1T 2214 2013 13 2 171 2013 13 22 11 2093 Sa Ea 4 11 2013 13 22 14 2093 ia 09 12 2013 1T 09 12 2013 17 TEMPPO V6 1 TEMPPO Administrator 57 04 kB 492 64 k 435k 34 29 kB 2 40 kByte 4 97 MB 15 15 kB 26 13 kB 26 13 kB 26 13 kB 6 49 kByte 7 70 KByte 6 47 MB T 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 331 You can create new requirement structures with TEMPPO Requirement Manager Page 254 User Manual Edition January 2014 Fi TEMPPO Administrator Testmanager Database bo Roles E Users Metadata LA Projecta Lacks License TEMPPO V6
100. 51 2691632_ 13293520751 398 png Testmanager 15 02 2012 16 55 06 6 31 kByte Afirnport_1 329320751 2691632_ 13293520751 398 png Testmanager 15 02 2012 16 45 51 6 31 kByte uninstall joc Testmanager 14 02 2012 14 02 51 2 67 k Byte Cancel Figure 203 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 Of course you can upload files that exceed that limit and or change this value in admin properties TEMPPO Note l X You are about to upload a file which exceeds the limit of 466 265 kByte gt r Do you want to continue Figure 204 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 20 2 10 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 163 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Pi Hyperlink e iweb File Database E Command EJ Manual Test Case command UniversalFile T File iTemp TestCase_0 cmd S Additional Arguments
101. 6 1 Edition January 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 M j l x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test V1 M 4 gt b OW GP EE No fiter M 243 4 Required functions of the product EH 3 4 1 File Administration ad 3 4 1 1 New General Attributes Test Steps BJ oforeticn Requirements History Plan Execution History OE 3 411 1 New file opened no 3 4 1 4 2 New file opened ch 2 3 4 1 2 Open a H i Requirement ID Requirement Name Requirement Structure 4 1 4 EX H E 3 4 2 Edit Functions iNew re BBE ComponentA R2 Components 1 IV Inherit E 3 4 3 Print Functions L File Administration req684 ComponentA R1 HHE 3 4 4 Search Functions Required functions of the product req683 ComponentA R3
102. A 3 41 2 New bi fl 3 4 1 2 1 Mew file opened no H 3 4 4 2 2 New file opened ch fl 5 41 23 Mew Test Package c E 3 4 1 3 Open y General Attributes Test Steps Ei iteration Requirements History Plan Execution History Enter accountin test domain Expected Login successtul and password 34414 Save SEa LA 3 4 2 Edit Functions 3 4 3 Print Functions a 3 4 4 Search Functions 583 46 Help System A E 3 5 External interfaces of the product m 3 6 Other product features required Et 4 Speciications for project management a 5 Obligations of the client i a 6 Literature Loe dF Anney 4 Figure 210 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 200 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 a
103. CTRL gt pressed the suites to be displayed sees Test Suites Attribute Value IN 683 req684 req65 Components IN reag683 rec6e4 req635 Notepad RTF Import with TCs Tree style i V7 D Versions oniy i V1 1 Test Suites for V1 1 2012 02 16 i ae Labels oniy Versions and Labels ClearCase style Order 2 4 Test Suites for V2 1 2012 02 16 ascending Eb V2 41 editable version g Version 2 of Test object RCO1 16 02 2012 E V2 2 descending W21 D 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 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 Results the chart can be customized By pressing the button Save As the chart can be saved as jpg or png file Page 108 User Manual TEMPPO V6 1 Edition January 2014 Description of Use A Test
104. Case tab Attributes The tab Attributes contains 3 tabs Direct linked Attributes Inherited Attributes and Inheritance Tab Direct linked Attributes displays the attributes which are directly linked to a test case Type and Situation radio buttons 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 selection is empty Direct linked Attributes inherited Attributes Inheritance Regular Error Venhcaton State 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 ia Assign to al test cases red color Tab Inherited Attributes displays common state of TCs which have inherited attributes from a TP Radio buttons If all selected test cases with 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 am
105. 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 302 User Manual TEMPPO V6 1 Edition January 2014 Appendix 13 6 1Functions to be applied to a role An X means that it can be de activated for a role icat TEMPPO Administrator Administrate locks Administrate projects Administrate roles Administrate test structures Administrate test suites Assign Requirements Assign Test category Assign Test level Assign UDA Assign Uploads Assign User Fields Consistency checker Freeze Test Structure Freeze Test Suite Move ownership Unfreeze Test Structure Unfreeze Test Suite Unlock test suites Change includes assignment of roles to users Administrator Metadata Requirements Test categories me TELE me LETT TL RRR RRR pete me LETTE RRR pene me pian me TRE TT eoniterasr gt jea O 5 Page 303 User Manual TEMPPO V6 1 Edition January 2014 Appendix Test levels po plots XL XX XK x O erted ana eeeh S Po User User defined attributes attributes e Fe a structure Apply requirement updates O i i de L T eee Edit main LATEST oo export XT SSS po Unit Interface XT pd lock items X X Test structure root TP TC TEMPPO Test package Assign requirements X x D TP Assign test categories X ehete o Edit xj xix x x moe eee
106. Command Line Preview DATempiTtest Case O cmd lt lt ResultFile gt gt 2 gt lt lt ErrorFile gt gt res Figure 205 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 x iweb File EA Database EA Command EJ Manual Test Case Command Path CAProgram Files SiTEMPPO 5 8yreibinyava exe Arguments Jar D tempimeinjar jar arga argi Additional Arguments Cancel Figure 206 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 164 User Manual TEMPPO V6 1 Edition January 2014 Description of Use a TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Help lest Structure Notepad RTF Import with TEs System Test r3 H d P H ah E notiter v EAI Notepad RTF Import with TCs Fl 1 Introduction nge 2 General description of the product B 3 Detailed description of the required product E Sm 3 1 Scope of delivery jia A 3 2
107. Designer IDATG is saved in TEMPPO for each test structure version 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 automated 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 289 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Designer IDATG Ei TEMPPO Schlosser Dietmar Notepad B O x Project Test Structure Edt Test Execution Evaluation Tools windows Helg Lil Test Structure System amp Acceptance Test System Test V2 Wo d P W GP E no titer ALI System amp Acceptance Test Gl IDATG Tasks oa Use case File Mewn Sub use case Mew already opened sub use Case Mew Ve rev SUbUsecase Mewmcompletelynevy 1 fi SUBUSe Case eae 2 ia Use case File gt Open Enter name FT data Mew file E a 3 Detailed description of the required product feature name Lock Applir Discard tbd Figure 380 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
108. ESULT INNSrLE TeguLrements CELUS Tarse talee r lt ATTLIST 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 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 1if it does not exist it will be automatically created gt Page 300 User Manual Edition January 2014 lt ELEMENT USER DEFINED ATTRIBUTE EMPTY gt lt AT
109. Edit Functions HE 3 4 3 Print Functions Created 15 02 2012 16 46 57 Updated 16 02 2012 08 55 28 3 4 4 Search Functions E 3 4 44 Find 3 4 4 2 Replace Number of TCs 0 ts 34 5 Help System fA T 3 5 External interfaces of the product Test Category Performance Test zi t a 3 6 Other product features required Do 6 1 Performance This section describes the features which determine 2 Resource the speed of the product required values Standard 3 Security formulations such as rapid response times are 4 Safety required are to be avoided Exactvalues should best 6 Portability he used 6 Reliability A number of examples of speed features include Z Maintenance Real time time sharing batch 5 Reuse Response times 4 Usability Startup times e al 4 Specifications for project management Throughput rate ao 5 Obligations of the client a lt a oo C B Literature 7 Annex NNN Owner Testmanager Updator Testmanager Type Test Package Description Figure 29 Complete Test Structure with Test 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 documen
110. FF Al JUnit Tests test cases 5 Set package default values with the JUnit test class 5 Setter care default values junit samples AllTests 7 Summar TEMPPO test cases 2 new test cases will be added 1 obsolete test cases will be permanently removed TEMPP Extension Panama a Ta Lo Page 279 User Manual TEMPPO V6 1 Edition January 2014 JUnit Figure 368 Step 5 The summary of the update wizard Fi TEMPPO atw108s2 JUnit extension tests FW B xJ Project Test Structure Edt Test Execution Evaluation Tools Windows Help lt Test Structure Sample JUnit tests Module Test z v1 M4b gt H E At Jura Tests B junit samples VectorTest Jy testCapacity junt samples VectorTest Jy testContains junit samples VectorTest General Jy testElementAtQunt samples VectorTest Bancas Semple JUnit tests Jy lesihiemoveblement und samples VectorTest Owner abt O8s Jy testClone jiunt samples VectorTest Jy testRemovealgunt samples VectorTest Created 10 12 2002 13 41 07 QB junit samples money MoneyTest Tyan Teel Sucks Jy textBagiulioty und samples money Money Te Jy tesiBeagNegate und samples money Money Te Test Levet Tes m J tesiBaghotEquals junt samples money Money Jy testBagSimple Add iund samples money Mone Description Jy testBagSubtract jund samples money MoneyT Jy testBagSumAddQund samples money MoneyTs Jy testis Zera jurdt samples money MoneyTest Jy testMixedSimpleAdd
111. Help System an 3 5 External interfaces of the prod Postcondition H 3 6 Other product features require Fal 4 Specifications for project managemel Postcondition A 5 Obligations of the client 6 Literature i 7 Annex Precondition Figure 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 speci
112. INSTRUCTION INPUT EXPECTED USK FIELD gt lt ELEMENT USR FIELD VALUE gt lt ATTLIST USR FIELD name CDATA REQUIRED gt lt lATTLIST USR FIELD type text amage 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 1if 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 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 I
113. Inherited 3 3 1 3 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 A set the same value the value is displayed If Testcase o there are test packages with different test 7r EEE categories an entry with Several Categories is selected If there is no selection an empty entry is selected Page 148 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 3 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 common state of all selected TPs that have cenere 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
114. Login m 23456 Login TYPE F automatic C manual Last Mame Mustermann First Marne mend Comments M SUperuser OK Cancel Figure 305 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 l X General Login Testmanager Login Type automatic manual Password pe o Retype Password fees Last Name Mustermann O First Mame Mx comments iCal Superuser OK Cancel Figure 306 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 237 User Manual TEMPPO V6 1 Edition January 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 Manager At least one TEMPPO Superuser has to be defined 4 3 Database migration Fi TEMPPO Manager system O F Database Users OY
115. MPPO 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 class isPublic amp amp class nasPublicConstructor Page 267 User Manual TEMPPO V6 1 Edition January 2014 JUnit Sr x JUnit l User Interface Tree Test Collector at sch panama junittool Loading Test Collector bw Test Step Cells Analysis Arguments cp O Temp_PvAiTeststellung_PVA unita 7 H Newsboard he Test Suite El Test Automation be Silk Test Hin Runner Universal File H Universal Soc
116. MPPO can 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 52 User Manual TEMPPO V6 1 Edition January 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 a R oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test Mr bo MHO BE No titer _ 2 General description of the product 3 Detailed description of the required product features ee erae nee 34 Scope of delivery Gen
117. Migration Database Version 5 5 Build 46 Application version 6 0 Build 0 Database must be migrated Attention You may need administration privileges for migration Index Tablespace temppoot Data Tablespace sitemppoindex Save Migrate Migration Log Figure 307 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 238 User Manual TEMPPO V6 1 Edition January 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 effect You may start more than one TEMPPO Administrator application However take into account that all Administrator applications write to the same a
118. NSTRUCTION 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 lt ATTLIST TS version CDATA IMPLIED gt Page 299 TEMPPO V6 1 Appendix User Manual Edition January 2014 lt ATTLIST TS A Wide bas lastupdate CDATA IMPLIED gt 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 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 IATTLIST TP name CDATA REQUIRED gt lt if zero length then name New Testpackage generated gt lt if it already exists add 1 2 aa lt ATTLIST TP test category ODATA FIMPLIED gt lt l gt af 2b does not Exist Autom Create it for the test l
119. 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 202 User Manual TEMPPO V6 1 Edition January 2014 Description of Use E DOORS Database Test Results 3 1 1 A Sample DOORS Sel File Edit View Favorites Tools Help Hea amp e e Favorites Location fT est A esus 3 1 1 4 Sample ML pr DEW Copy Formal SITEMPFO gy Test Results E 3 1 1 A Sample DOORS Database Description Usemame Administrator User type Administrator Figure 261 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 E Formal module Test Results 3 1 1 Sample DE 1_ Copy Sel File Edit View Insert Link Analysis Table Tools Sa sma y z Results All levels Br ae i DEV Copy 1 Regl 2 Req passed 3 Reg User Help P failed 4 Regd P filed AJ Username Administrator Exclusive edit mode Figure 262 Results for requirements Page 203 U
120. New Test Package 3 41 2 Open Number of TCs 0 3 4 43 Save hl 3414 Exit Test Category 3 4 2 Edit Functions 3 4 3 Print Functions H 3 4 4 Search Functions o bl 3 4 5 Help System H 3 5 External interfaces of the product H 3 6 Other product features required m 4 Specifications for project management 5 Obligations of the client a G Literature i OF Annex Menge Lock Apply Discard B 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 Merge advice x The test package was modified in this branch wersion Would you like to apply the changes alao 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 8 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 89 User Manual
121. 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 VY e g Component 3 No blank is allowed commas has to be escaped with a A Build In Clause Find Selected values Available values M12 M13 r LA Filter Properties Name New Fiter rConditions Ww Yv Milestone IN M1 2 M1 3 M3 AND Miestne v O IN Y M1 2 M13 M3 a ao v X S Value v hA x Hide Empty Subtrees Attribute S 1 Yes if operators IN NOT IN are selected Yes if a set of values can be selected Yes if editable is Yes Fixed I Situation Test Case Type Additional Test Level Type Fixed II Test Level Test Category Requirement Fixed III Priority State Valu Value Wild e j card set allowed 3 Page 193 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Yo Test Y result Created Updated Require ment Table 2 Attributes meanings The user can write free text that may also contain wildcards like x any number of characters any single character Lal Filter Properties Name New Filter gt Conditions Attribute Value G Miestone M1 2 M1 3 M3 leas Agdibonal test level Acceptance Test w Fianned tester mi af Req_State Implemented Tes
122. O Test Manager automatically checks in your current Page 58 User Manual TEMPPO V6 1 Edition January 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 version 1 on the main line In TEMPPO every last version gets the label latest sig
123. Personal Settings Test Structure Settings Name Description E Several test suites withattinbute fiter 5 chars Testmanager 25 06 2013 12 5 Tms report seth 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 Page 124 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e to select Result current and Result current and history for a test case Name _NewReportSetting Owner Testmanager Fiter Created 25 06 2013 12 53 22 Updator Testmanager Updated 25 06 2013 12 56 14 Description This report setting is used for evaluating more test suites Figure 146 Report of several test suites Settings Notepad RTF Import with TCs B V4 1 Test Suites for V1 1 2012 02 16 v1 1 1 Test object Version XYZ RCO3 v1 1 1 editable version A Test object Version XYZ RCO1 Test object Version XYZ RCO2 1 Test object Version XYZ RCO3 Test object Version XYZ RCO3 CO eve V2 1 Test Suites for V2 1 2012 02 16 ES v2 1 1 editable version pa Version 2 of Test object RCO1 16 V3 Checked in by XML Update i Ud editable version Figure 147 Report of several test sui
124. Phase 8 Import Characters from other fonts 199 from Excel 22 33 J JUnit 266 Test execution 280 Update 275 K Keyboard Quick navigation 49 L LDAP 244 License Server See Administration License Server Connection Locks 263 Find 135 Login with password 237 Main Window 13 Merge Multi selection of changed TPs and TCs 150 Multi selection of unchanged TPs and TCs 145 Metadata 247 Attributes 250 copy 177 Page 310 User Manual Edition January 2014 Requirement Structure 254 Test Categories See Metadata Test Categories Test Levels 248 Uploads 253 User Field 257 Migration See Administration Database Migration Move ownership 176 Multi selection Delete 158 Move ownership 157 Multi selection mode 139 Multi user ability 134 N Newsboard 180 P Plug ins 293 Progress charts 102 Creation 102 Execution 104 Requirement analysis based on several test suites 110 Project 11 copy 260 create 11 258 open 12 properties 12 Test case template 169 Projects 258 Assign metadata 260 delete 260 Freeze unfreeze 262 Move ownership 261 Test Result template 173 R Refresh 138 recursively 138 Reload whole tree 138 Report Export to XML 133 Import from XML trp file 134 Import Templates 133 New 114 Several test suites 124 Templates 133 Reports 113 Chart Settings 128 General Settings 115 preview 129 samples 131 save 129 Textual Settings 117 Requirement Analysis 97 delete 36 Test pac
125. Plan Execution History HAN 3 4 Required functions of the product General Attributes Test Steps A 341 File Administration l Ce sd 3 4 2 Edit Functions erdei IE set i 93 4 3 Print Functions a 34 4 Search Functions Mame case senstie HAH 3 4 41 Find ce 3 4 4 1 1 Find up Daner Testmanager Updetor Testmanager TERR jo Case sensitive l ll 344112 QuickTestPra 7 o EM 3441 2 Find down Toe C ena inition Ten Care o 3 4 4 2 Replace ee E i 3 4 5 Help System Test Goal The test goal of this test case is to test search function with case Ela 3 5 External interfaces of the product sensitive search strings 5 3 6 1 User interfaces fl 3 5 1 1 Editor Pane fl 5 5 1 2 Search Dialog ae TE 3 6 2 System interfaces io 3 6 Other product features required m 3 6 1 Peformance m 3 6 2 Resource m 3 6 3 Security m MO oe a Look Apply Discard Created 16 02 2012 11 03 55 Updated 16 02 201211 Figure 37 Manual Test Case General It is also possible to design automated test cases without having any script Attributes Page 39 User Manual TEMPPO V6 1 Edition January 2014 Description of Use lolx F TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools windows Help Test Structure Notepad RTF Import with Tes System Test w1 He4hkh WH E No fitter r Eb es 3 4 Required functions of the product OO EL 3 41 File
126. Print Functions EL 3 44 Search Functions BAJ 3 4 44 Find o 3 4 441 1 Find up Dien TEMPP OTE MPP Osourcesispriv bat A gt lt lt ResultFiles gt 2 gt lt lt Error File gt gt Command Line Preview fil 3 4 4 1 1 1 Case sensitive 3 4 4 1 1 2 WinRunner Check Stat Tij 34 4445 QuickTestPro Test case 3 4 4 1 1 4 Test Partner Test case 3 44415 U4 Lock Apply Discard Figure 60 Test case settings for Universal Automation Interface Results of test cases Page 56 User Manual TEMPPO V6 1 Edition January 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 start and end line in its data base Getting the output By default TEMPPO Test M
127. Priority major Environment a xi Description a bug ocurred a x Attachment Add Test Report M Custom Fields Unknown 1 0 Backport to Version 20 DE Release Note oes Figure 96 JIRA LA Testmanager Demo Notepad R Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 71 11 S a DW 6 EE No titer Bion XYZ RCO1 description of the required product features yuired functions of the product File Administration General attributes Test Steps EE Aronson Requirements History Attributes TR Previous Resuits Plan Execution History File New pick Editor Pane cleared fl 3 4 Search Functions P Unbenannt Ed Datei Bearbeiten ffnen Speichern Speichern unter Seite einrichten Drucken o Beenden Untitled Notepad 5626 in titla bav http Watinzp10qa 2849 bugs_sitemppo_internalshow_bug cgi id 5626 Lock pl Discard al tf se Pe 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 a
128. RIA 15 Obermueller Peter abl 2S peter obermuell PSE SES MEC L Linz AUSTRIA id Import Close Figure 315 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 User cancelled the search Page 245 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Figure 316 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 x a 1 User cancelled importing users From LOAF Figure 317 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
129. Seguences scenarios of interactions Pee ae 3 3 User goals SE 3 4 Required functions of the product E EE 3 4 1 File Sdministration o B ass 4 Windows Login 2E ile New pi Editor Pane cleared efi 341 11 Login 33 Untitled Notepad in title bar Eh 3 4 4 2 New Expected EE 341 22 Wew ae npenied crt Lf 3 41 25 New Test Package c pe BY 3 4 1 3 Open 3 4 14 Save ob A sacs ext 3 4 2 Edit Functions 3 4 3 Print Functions E a 3 4 4 Search Functions haas Help System ee ae sais Figure 207 Source test case Then click right mouse button for context menu select Hyperlink and select the test case Ae xi web Si Fie Database EJ command BI Manual Test Case a User goals El Required functions of the product oo Ee a File Administration o amp 2a windows Login Figure 208 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 165 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO he saa ae Demo Notepad loj x Project Test Structure Edit Test Execution Evaluation Tools Windows Helg Test Structure Notepad RTF Import with Tes System Test MS H arug Mo filter S I Notepad RTF Import with TCs Bl 4 Introduction Et 2 General description of the product 8 3 Detailed description of the required produc
130. System a 3 5 External interfaces of the product E 3 6 Other sas daa secre a rare A ue m i TEMPPO V6 1 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 141 User Manual Edition January 2014 Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution e Test Structure Notepad RTF Import with TCs M4 W GP EE No ite Motepad RTF Import with Tos E1 Introduction E 2 General description of the product m 3 Detailed description of the required product 34 scope of delivery i Ea 3 2 Sequences scenarios of interaction S ca 3 3 User goals So 3 4 Required functions of the product Soap 13 41 File Administration MERR Ee BEE BAE 42 Edit Functions H 3 4 3 Print Functions e 3 4 4 Search Functions 3 4 5 Help System E 3 5 External interfaces of the product H 3 6 Other product features required 4 Specifications for project management 5 Obligations of the client 6 Literature T ANNES fi 3 4 1 1 1 Mew file opened ri
131. T 41 1 2 New fie ope pa fre sme fh cacao auton _ i soy P a 24 3 4 4 Search Functions File New pickO Message gt A Unbenannt Edit EHEN 3 4 4 1 Find Save changes rar Bearbelten 3 4 4 1 1 Find up fi 3 4 4111 Cases E 3 4 4 4 4 2 WinRur ff 3 4 4 1 1 3 QuickT ffnen Speichern B 344114 Test Pe speichern unter E 3 4 4 1 1 5 UAI no i Sate worchken Drucken Messagebox No Editor Pane click cleared Untitled Notepad in title Figure 83 Manual Test Execution Test Step Results Test case results are calculated by accumulating test step results So a test case S W not executed if all test steps are not executed initial result ll 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 l 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 74 User Manual Edition January 2014 TEMPPO V6 1 Description of Use B TEMPPO Testmanager Demo Notepad E 10l x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 v1 1 1 A 3 Detailed d
132. TA gt PASSWORD PCDATA gt PROJECT PCDATA gt LOGIN USER PASSWORD PROJECT gt PCDATA SUMMARY lt ELEMENT lt ELEMENT SUMMARY RESULT lt ATTLIST RESULT testsuiteid CDATA REQUIRED testcaseid CDATA REQUIRED value CDATA REQUIRED gt gt gt lt ELEMENT RESULTS RESULT gt 13 4 DTD Schema for XML Export User Profile with CLI Page 301 User Manual TEMPPO V6 1 Edition January 2014 Appendix 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 PCDATA 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
133. TLIST 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 name it will value it will lt ELEMENT USER DEFINED ATTRIBUTE TRESULT EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE TRESULT 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 DEFINED 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 CDATA REQUIRED gt lt be automatically created CDATA REQUIRED gt lt be automatically created name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically TEMPPO V6 1 Appendix cannot be zero gt cannot be zero gt lt cannot created gt lt cannot created gt l cannot created gt lt l 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 PCDA
134. Test Structure Auto Test Structure Auto Test Structure Auto Test Structure Auto Test Structure Auto Test Structure Auto E Record test Test Stricture Auto Lok canca Figure 264 New Scheduler 3 3 18 2 Delete Scheduler For deleting a scheduler press the Delete button The button is enabled if at 5 1 New Test Package AY 1 1 New Test Case not executed Updator Figure 265 Delete Scheduler Page 205 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 18 3 Import Scheduler Instead of creating a scheduler from the scratch importing schedulers from other test suites is possible If you press the Import button a new window opens with the whole version tree After selecting the scheduler which has to be imported OK has to be pressed A Select Test Suites BE g New Test Structure Tree style Ek VI V1 1 Test Suites for V1 1 2012 05 03 G v1 1 1 editable version z Q New Test Suite 03 05 2012 Versions and Labeis Bt oc C Versions only 2 Labels only est V2 editable version C ClearCase style Order ascending descending Figure 266 Import Scheduler After clicking OK the scheduler is displayed in table at register Scheduler Only existing test cases in current test suite can be applied to new scheduler 3 3 18 4 Run Scheduler For running a sched
135. V1 4 3 4 5 Help System Al New file opened no changes req6s Componente R3 Components 3 5 External interfaces of the product 5 5 3 5 1 User interfaces Qa 3 5 1 1 Editor Pane 8 3 6 1 2 Search Dialog i 3 5 2 System interfaces ne a gt 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 deleted 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 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 42 User Manual TEMPPO V6 1 Edition January 2014 De
136. WinRunner 3 Arguments 4 lt lt TestFiles gt batch on qun create_text_report on speed fast Universal File fun_minimized H Universal socket QuickTest Pra Test Partner JUnit HTEMPFO Designer DATS i Ranorex El Commands News Command i Javas El Change Management H Bugzilla Clear Quest Telelogic Change i JIRA delete temporary test automation files Restore Defaults OK 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 54 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad TS olx Project Test Structure Edit Test Execution Evaluation Toole Windows Help o Test Structure Notepad RTF Import with TCs System Test V1 B x 43 Mo fitter E 2 General description of the product 3 Detailed description of the r
137. 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 structures in the needed version TEMPPO Requirement Manager Page 26 User Manual TEMPPO V6 1 Edition January 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
138. You ll close TEMPPO and unplug your notebook from the central database LAN Unplugged from the central database you first start the TEMPPO 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 A You are connected to an esport database TEMIPPO willbe started in a restiched manner The exported test suite will be opened automatically now 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
139. ad RTF Import with TCs E 3 4 Introduction LOGE SST anage na pi ee e ad General a riputes Details Requirements History Pian Se i cript 1 EO PP OAL E stope of aeivery ID tpS29 i 2 hoy ZE 3 2 Sequences cenarios of interactic 3 3 User goals Detailed description ofthe required product features 5 a 3 4 Required functions of the product Mame Detailed description of the required product features ni 33 4 1 File Administration 3 4 2 Edit Functions H 3 4 3 Print Functions Created 15 02 2012 16 45 48 Updated 16 02 2012 08 40 22 3 44 Search Functions PoP eo Type Test Pack 3 4 44 Find icles Owner Testmanager Updator Testmanager 3 4 4 2 Replace Number of TCs 2 Po be 3 4 5 Help System 0 3 5 External interfaces of the product Test Category SEES Tei mics a 3 6 Other product features required 4 Specifications for project management This section of the software requirements Js Obligations of the client specification must define the product features pe a 5 Literature requested prescribed by the client and agreed to by LF Annex the development department These features contain all functions interfaces and other product features A number of points should be taken into accountin describing the features Description Every required feature should be Uniquely identified be oti ol ab ee ee a ey oe able ed din Figure 28 Assigning a test category Wh
140. age S E New Test C Find and Replace F3 F Mew Test Show Details a Mew Test Packe Select All E Tree b b Run automated Set Resultts fey Edit OS Refresh recursively 3 Move Ownership gl Analyse selected b ey Report selected Figure 195 Context menu Set Result s Page 159 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Set Result s X Set Resultis to Failed f passed not executed blocked not implemented f on hold Figure 196 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 197 If a test case contains no test steps it remains not executed TEMPPO X l Humber of test cases with new resutt 5 Humber of locked test cases 0 Figure 197 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 Descriptio
141. ager Page 4 User Manual TEMPPO V6 1 Edition January 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 new 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 5 TEMPPO V6 1 Introduction User Manual Edition January 2014 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 Engineering Baseline View EE Design a Test structure Engineering al eee rr Analysis i Eno oe A age EMPPO AUC TENMPPO TEMPPO ___ Requirement Analysis amp Test Manag
142. al u s F u E oA a Else vs Cn E U U U UO With view latest baseline 4 Owner Test Goal check the update with view together with a latest version and not a baseline Path Systemtest Introduction Purpose of the document With view latest baseline 4 Created 10 06 2008 15 33 49 ID tc54636 RPreview doc C DOCUME 1 atw10905 L0 CALS 1 Temp RPreview doc 6 of 1 SITEMPPO Report 11 06 2008 Priority High Situation Regular Test Case Type Verification State In Work Type manual Updator nt Updated 10 06 2006 15 33 49 Precondition Offline true Test levels Acceptance Test Test Steps in DOORS new attribute onnect to Screen with view DOORS server selection is available 3 Press Finish to New start update requirements are process updated Validity of the document R l B So HD MAK ERS ERW B e Figure 152 Report Word EJ Microsoft Excel RPreview xls lal xi a Datei Bearbeiten Ansicht Einf gen Format Extras Daten Fenster Livelink Frage hier eingeben ey BAS OSA RBSIGRIF OH 4 aA FIGO Bi avs 0 F KU F SSH Bnl Fo o A B u G ua a o gt BH H A Ye Bearbeitung zur cksenden Bearbeitung beenden p A1 f a a a E E NT j aml Systemtest 3 Name of Test Structure Systemtest 4 Owner nni 5 Description 6 Updator Updated Details A New Test Package 10 Owner
143. anager 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 the command line parameters o myResults res e myErrors err Additionally each scrip
144. anch 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 wersion Do you want to apply the changes also inthe maini latest wersion Remark This test case was alzo updated in main latest version by Testmanager Figure 235 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 IW Test Steps Jw Automation M Requirements W Plan Figure 236 Merge selection If nothing is selected test case is latest version remains unchanged 3 3 12Compare Version management also includes comparing a test case with a another one If you select a test case in the current version of a test structure and activate the menu item Compare Page 186 User Manual TEMPPO V6 1 Edition January 2014 Description of Use i Tree EJ Compare 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 Compar
145. art 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 cases The test cases linked to the requirements are displayed as e Chart e Numbers Page 97 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Test case IDs Page 98 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Requirement Analysis x Requirement Structures EAAS Requirement attributes v Fitter Calculate chart E Data E Detailed Data lest Cases Chart stacked Horizontal Bar Chart o 1 2 3 4 5 6 7 Sort GEN FN 0010 C alphabetical GEN FN 0030 C ascending descending GEN FN 0020 GEN FN 0030 032 Values C Al GEN FN 0030 031 Only zero values GEN FN 0030 020 No zero values GEN DB Coverage Average number of TC s per requirement 1 41 TC s GEN CD 0030 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 4 l aese Figure 118 Planned coverage Fi Requirement Analysis ie xj Requirement Structures Me aee ALAE a a Requirement attributes Filter Chart E Data E Detailed Data Calculate Chart Stacked Ho
146. ase by itself 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 o returm surte public void testSomethingRight assertTrue true Page 284 User Manual TEMPPO V6 1 Edition January 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 genera
147. ase 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 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 9 User Manual TEMPPO V6 1 Edition January 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
148. ase manually created La Mile stone Testmanager 22 11 2013 13 46 47 Test Case manuaay created I New Entry Testmanager 12 09 2012 14 21 01 Test Case manually created mo New Entry Tesimanager 12 09 2012 14 22 11 Test Suite manually created Regressiontest Testmanager 22 11 2013 13 46 46 Test Case manually created Sample Testmanager 27 11 2013 13 46 42 Test Case manually created i ia Treiber Testmanager 22 17 2013 13 46 41 Test Case manually created Figure 325 Metadata Attributes Here you can add delete view and fiter 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 251 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator x General Details Browser Created 20 02 2012 15 18 12 For Useot v Test Case Quwiner Testmanager tl resi Rer Type Attribute T Test Suite ia Test
149. ase sensitive blocke R 3 44442 WinRunner Check Ste 3 4 4 1 1 5 Quick TestProa Test ca eal 4 4 1 1 4 Test Partner Test ca E 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 78 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad S 5 x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO3 v1 1 1 ALJ Test object Version XYZ RCO3 a 3 Detailed description of the required g EA 3 4 Required functions of the prodi General attributes Test Steps IE tore Requirements History Attributes TR Previous Resutts Plan Execution History EH 3 4 1 File Administration ia aa ae a Test Suite version Resut Bug ID D 341 4 y New a me Test object Version XYZ RCO1 1 1 1 editable version failed Testmanager 16 02 2012 1 os a 3 4 4 Search Functions g Test object Version XYZ RCO2 1 1 1 editable version not executed g Test object Version XYZ RCOS 1 1 1 editable version passed Lock Apply Discard Figure 91 Previous Results 3 1 4 1 9Enter new bug entry An actual behavior and in case of errors a bug ID can be recorded for each test step and for ea
150. ask packages only can be created below the folder TEMPPO Designer IDATG Tasks by activating the menu item New gt Task Package or New gt Task Package before Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test V3 H d gt H No fter J Notepad RTF Import with TCs E Task Package Ctrl A T i 3 Ger a Test Package before ceil 4 Det Find and Replace F3 z ea E EE A Dl Test Case Ctri Alt E ty 5 Spe EE Obli show Details fi Test Case before Select All Owner Testmanager Up A task package contains all properties of a test case ID fixed name owner created updator updated test category optional description F TEMPPO Testmanager Demo Notepad joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Motepad RTF Import with TCs System Test Wa E x H o d gt b WM E No fiter Abd Motepad RTF Import with TCs Se 1 TEMPPO Designer DATS Tasks 11 New Task Package General attributes Details Requirements History Pian Introduction General description of the product ID bert Detailed description of the required product teal Specifications for project management _ Obligations of the client Mame Juse cate File New Literature Owner Testmanager Updator Testma
151. ated as test suite attributes in the Meta Data Editor see 5 3 Page 66 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad lolx Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version v2 ROOT 41 1 1 M d b H h EE No nter El ik Test object Version V2 REDI 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 Test suite name e Logical expression e Remove tes
152. 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 212 User Manual Edition January 2014 TEMPPO V6 1 Description of Use should be configured On the right side all single settings can be edited see Figure 277 Tree rw Test Step Cells Analysis en Mewsboard i Teast Suite El Test Automation Silk Test Hin Runner Universal File gt QuickTest Pro Test Partner es Unit H Ranorex El Commands zi Mew Command i Javaa p Bugzilla gt Clear Quest gt Uniwersal Socket TEMPPO Designer IDATG Fl Change Management Telelogic Change User Interface Expand the tree to edit settings Figure 277 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 O O O Tree Test Step Cells Analysis Newsboard Test suite e Database settings e Test automation O O O O 0 30 30 O Silk Test WinRunner Universal File Universal Socket QuickTest Pro Test Partner JUnit TEMPPO Designer IDATG Ranorex e Commands e Change Management o Bugzilla o IBM Telelogic Change o IBM Rational Clearquest o JIRA Page 213
153. base TestPartner Configure ee crcl Figure 290 TestPartner Login 3 3 20 2 8 JUnit For Junit see chapter 6 Page 226 User Manual TEMPPO V6 1 Edition January 2014 Description of Use l User Interface Tree Test Collector at sch panama junittool Loading Test Collector Test Step Cells Analysis Argumenta cp B Temp PvalTeststellung PVayunita 7 H Newsboard Test Suite Database El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test TEMPPO Designer DATS i Ranorex El Commands New Command VEZ El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Tallow duplicate names in same hierarchical level Figure 291 Junit configuration 3 3 20 2 9 TEMPPO Designer IDATG TEMPPO Designer IDATG el User Interface p Tree Application Fath Je pragram flesidaty binvdaty exe 4 Test Step Cells Analysis Connection time out le Sec He Mewsboard Le Test Suite Communication time out feo ZEC ptabace Ping wating time fa ZEC Cl Test Automation Silk Test Ping repeats f Hin Runner i Uniwersal File Universal Socket T Check In before Updating with data of TEMPPO Designer QuickTest Pro Test Partner i i Ranorex El Commands New Command SSE El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 292 Set
154. ble when changing column widths or table bounds Multiline height 52 Sets the minimum height of the edited row in pixels in a multi line table Page 214 User Manual TEMPPO V6 1 Edition January 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 Image column image Maximum width of thumbnail of a user width defined image field If it s 1 its ignored Maximum height thumbnail of a user defined image field If it s 1 its ignored il User Interface Mutiline table Tree O TRELAR LER I Onoff for refreshing the cell content when changing the column wicth gt Analysis H Mewshoard s2 Height of muiline rows during editing defaut is 52 Test Suite aa Database Image columna TI peeomenen la Maximum width of thumbnail of a user defined image field tf t s 1 it s ignored H Silk Test in Runner i Maximum height of thumbnail of a user defined image field f it s 1 it s ignrored Universal File H Universal Socket Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands lew Command SE El Change Management Bugzilla Clear Quest Telelogic Change Ean JIRA Restore Defaults Cancel Figure 279 Settings Test Step Cells 3 3 20 2 3 Analysis You can change the settings for analysis Property Description value different colors Label length for progress 100 Limi
155. c13544 tc13545 tc13546 tc13548 tc13550 tc13552 Requirement name 11 tc13574 tc13575 tc13576 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 Requirement name 31 Dam iramank mama 27 Figure 121 Test Structure Requirement Analysis Detailed Data tc13578 tc13868 tc13869 tc13581 tc13582 tc13583 tc13586 tc13611 tc13612 tc13592 tc13593 tc13596 tc13598 tc13600 tc13615 tc13618 tc13620 tc13622 tc13624 tc13630 tc13631 tc13633 tc13634 tc13635 tc13636 tc13449 tc13450 tc13451 tc13452 tc13453 tc13868 tc13869 tc13638 tc13639 tc13640 tc13641 tc13644 tc13645 tc13648 tc13661 tc13662 tc13663 tc13664 tc13665 tc13666 tc13667 tc13684 tc13685 tc13686 tc13688 tc13690 tc13693 tc13695 tc13696 tc13698 tc13699 tc13972 tc13973 tc13974 tc13976 tc13977 tc13978 tc13979 tc13972 tc13973 tc13974 tc13976 tc13977 tc13978 tc13979 tc13455 tc13456 tc13457 tc13458 tc13459 tc13988 tc13990 tc13993 tc13994 tc13995 tc13996 tc13997 be 1 202 bet 2082 be 1 OI be 1 VW be 1 WOW be 1 22 Fe 1 2aAN Page 100 User Manual TEMPPO V6 1 x Requirement Structures yma MEAE Requirement attributes Filter Calculate g Chart EA Data T Chart Stacked Horizontal Bar Chart 3D
156. ce 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 test 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 90 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Zuletzt ver rmendete Piel s es sud Deskto aj Eigene Dateien PE Arbeitzplatz a File name temppo_exp
157. cel Figure 322 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 Page 249 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 5 4 3 Test Categories Test categories are used to denote test packages that contain only test cases of a ee pele type S noes Users ur perro _ EB Test Leves MB Test Categories 4 Attributes Upioads Requirement Structures User Fies C r Pai fa Fiter Lo rl Hame Caner Created E GCul Layout Test admin 21 02 2001 00 00 00 a Maintenance Test admin 21 02 2001 00 00 00 1 Performance Test admin 2102 2001 00 00 00 Portabaity Test admin 21 02 2001 00 00 00 WB Rekshaity Test admin 24 02 2001 00 00 00 Resource Test a
158. ch 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 nn x PO Change Management A gla Active Change Management Tool Test Step Cells Bugzilla Analysis Telelogic Change Newsboard Test Suite C Clear Quest Database JIRA El Test Automation H Silk Test Win Runner gt Universal File Universal Socket gt QuickTest Pro Test Partner gt JUnit gt SITEMPPO Designer IDATG Ranorex Commands New Command H Java32 Cha nG e Managemen NA anagemer H Bugzilla H Clear Quest Telelogic Change So JIRA Restore Defaults o 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 79 User Manual TEMPPO V6 1 Edition January 2014 Description of Use General Attributes Test steps Ei Actometion Requirements History Attributes TR Previous Results Plan Precondition Select the User define attribute in the combobox Attribute TT Gelectthe E SS T e ES 462 NOT IM operator Push the A NEw button wirid o right comes up beside the where a wale selection field for the
159. ch will automatically be activated and can be edited like the latest version in the main line usually Page 184 User Manual TEMPPO V6 1 Edition January 2014 Description of Use called main latest One version can have several branches which can be created in the same manner Notepad RTF Import with TCs Edit RA Test Suites for W1 1 2012 02 16 C Check In LW 44 editable version z Ewe 48 Activate V2 4 Test Suites for V21 204202416 here b YBt editable version fet ge w r Tree style 2 aol V2 2 4 versions only MT edas versa Labels only i YWersions and Labels ClearCase style r Order fe ascending 2 descending Close Figure 232 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 possibility of recovering the test structure of the main line When pressing the merge button the following question will appear warning eee xl The merge will first check in the latest version in your main line and afterward
160. color If you want to assign such an attribute to all TPs select it right mouse click and activate a ee EE Such attributes or new assigned attributes are displayed in red color Direct inked Attributes inherited Attributes Inheritance Priority Top State Designed Attribute Values io TP Type User case F xDD Tab Inherited Attributes displays common i ro 4 state of TPs which have inherited attributes z General Atnbutes Requirements MON Te Direct inea atroutes Innentea Atrbutes innertance Radio buttons If all selected TPs with activated inherit flag have set the same value aaam the value is selected otherwise there is ld aera NN 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 am F E F xu The tab Inheritance displays the COMMON birectinked Attributes inherited Attributes Inheritance state of the inheritance flag of the selected TPs If the checkbox is not activated i e a Netinherted X all selected TPs do not inherit any F inherited partially attributes If the checkbox is activated FT kriherited Witnherted all selected TPs in
161. cuted 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 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 84 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fj Set Result s q X Set Result s to c passed not executed blocked not implemented on hold D 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
162. d V not completed V not implemented V on hold Fiter Attribute f Components Components IN req683 req684 req685 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 LA Select Test Suites Notepad RTF Import with TCs a Eb Vi Versions only V4 1 Test Suites for V1 4 2012 02 16 Eb VTT editable version Test object Version XYZ RCO1 16 02 2012 Versions and Labels ER E E een Test object Version AYA RCO M6022017 E Labels oniy Test object Version XYZ RECOS 1602202 ici Test object Version XYZ RCO3 COPY 16 02 2017 ES aw G21 Test Suites for V2 1 2012 02 16 ascending Pod GALT editable versi F KES T descending Version 2 of Fest object HOOT H VI Checked in by XML Update fe Vf editable version Page 110 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Figure 133 Select test suites Additionally you have to select the requirement structures by pressing th
163. d manualy created manuaay created manually created manuaay created manually created manually created manually created manuaay created mania created Rename the attribute by changing the name of the attribute see Figure 328 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 l j A Copy and rename only the attribute is cop Created 0912 2013 17 43 31 Owner Tesimanager Type Attribute M Copy values 5 4 5 Uploads If you activate the tab Uploads Figure 329 you can Figure 328 Copy and Rename ied not the values Upload new files without any reference View uploads properties Delete uploads from the database Delete all non referenced uploads Page 253 User Manual Edition January 2014 E Database Roles Roles Users Users ewe ron tocks amp Sj g 1 Test D Test Levels BT Test Categories ll A Attributes upicaas K cy Requirement Requirement Structures 7 El user Fields Ty ey Pai ta tv g Fitter Name 3e36d25bbb 1265268210525 1365124395679 jpg ADIS Phase 1 xmi Auto mmi coverage 1273655456963 13351243961 12 jpg launcher properties Navigation Denson result coverage _ 1265200203 103_ 7305124394534 jpg ecreenshot_126263057 250942636 1262636672962 13 ecreenshot_12626305 7250942630 _ 1262050572962 13 ecreenshot_126263057 2
164. d description of the required prod 3 4 Scope of delivery ID tp535 3 2 Sequences scenarios of interacti ew 3 3 User goals ca 3 4 Required functions of the product E8344 File Administration ES EEE Marne Mer Owner Testmanager Updator Testmanager il 3 441 141 New file opened Created 18 02 2012 16 45 50 Updated 16 02 2012 17 08 21 fi 3411 2 New file opened BB 3411 3 New Test Packac co 3 44 2 Open Number of TCs 2 C 3 41 3 Save E 3 4 1 4 Exit Test Category 3 4 2 Edt Functions 3 4 3 Print Functions Description E 3 4 4 Search Functions 2 fe 3 4 5 Help System H 3 5 External interfaces of the product E36 of i her product features required mo T Ae ee eee E E A R aasa Lock Applir Discard Type Test Package Figure 162 Lock button 3 2 1 3 Creating a version 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 F 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
165. 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 A TEMPPO Administrator Testmanager l C A Pi Ea Ba Al 7 Fitter Name Owner Created Attribute Type Creaton Type is Browser Testmanager 22 11 2013 13 46 46 Test Case manuaay created P demo Testmanager 12 08 2012 1421 37 Test Package manusi created Demonst Testmanager 22 17 2013 13 46 45 Test Case mantay created a Developer Testmanager 22 11 2013 13 46 43 Test Case manually created I pa Ist Schon Te Tesimanager 22 17 2013 13 46 44 Test Case manuaay created _ Medenstein Testmanager 22 11 2013 13 46 45 Test C
166. ding 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 CI 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 139 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Setting test results in 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 r
167. dmin 21 02 2001 00 00 00 Reuse Test admin 2102 2001 00 00 00 Safety Test admin 21 02 2001 00 00 00 I Security Test admin 24 02 2004 00 00 00 W State Based Test 21 02 2001 00 00 00 Figure 323 Metadata Test Categories Here you can add delete view and filter test categories When pressing 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 EI for editing the test category properties Fi Properties of New Entry xj General j New Entry Created 20 027 2012 15 16 46 Owner Testmanager Type Test Category Description eres Figure 324 Test Category Properties 5 4 4 Attributes Attributes are applied to test cases test results and test suites They can be applied in addition 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 Page 250 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 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 How is the progress of test case
168. dmin properties file 5 1 Database Connection Fi TEMPPO Administrator t O x Ee grates Users a Bi rroects torte ticense DSN User documentation C Pas Database Oracle SID fJaktx Schema temppo_um Host Jatinzpt a Fort h 521 User jatw112h9 M Login manually Connect Database Mame Database Version Figure 308 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 239 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator using the 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 o x Database Roles Users gf Metadata Projects g Lock 5 License ats Wotihication me SiTEMPPO 5 7 Users Guide i a Database Access
169. dows Help Test Structure Notepad RTF Import with TCs System Test m1171 ag ajx M4 PH of B Nofite m Notepad RTF Import with TCs JTM EMAL LI cic CUO MOGE al 1 Introduction After finishing your rulti ce Z 1 14 Purpose of the document 1 2 Validity of the document egy 1 3 Definitions of terms and abbreviati 44 Relationship with other documents Total number of selected TPs 9 eal 1 5 Overview of the document a 2 General description of the product Total number of selected TCs 2 Fee 2 1 Relationship with existing projects l Ea 2 2 Relationship with earlier and follow ea 2 3 Purpose of the product Ee 2 4 Delimitation and embedding of the aa 2 5 Overview of the required functions eal 2 6 General restrictions ze 2 7 Hardware and software specificat eal 2 8 Product users m 3 Detailed description of the required proc Ea 3 1 Scope of delivery General Test Packages Test Case Merge Apply Discard S 8 o oF amp B Figure 176 After Show Details content is shown 3 3 1 2 Multi selection merge of unchanged TPs and TCs A so called Multi selection merge is done based on the current selection of unchanged TPs and TCs Please do not mix this feature with the merge of all changed items If you press the button Merge all items are merged to the latest version after pressing the Yes in Figure 176 Merge Waming Appiying the function of merging the sel
170. e Description 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 fitter or attributes values and logical operators 2 Choose creation mode 3 Select an existing Test Suite Fitter E No filter v Apply 4 Select nodes or subtrees Attribut Val 5 Enter test suite name eee wale 6 Determine the logical Regressiontest esS hal x expression 7 Remove test cases manually Regressiortest yes TEMPPO Test Suite Generator lt lt Prey Next gt gt Cancel Figure 77 Logical Expression 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 69 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard 5 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 an existing Test Suite Test object Version XYZ RCO2 16 02 2012 Detailed description of the required product features E E Required functions of the product File Administration Fl New D New file opened no changes not executed J Search Functi
171. e gets enabled F Yersions X ee Notepad RTF Import with TCs E Display MV Test Suites for W14 2012 02416 Tree style i oid editable version Versions only Er v2 EbW24 Test Suites for V2 1 2042 02 16 Labels only Vet editable version versions and Labels Ee oe V221 ClearCase style iy editable version e ie ascending t descending Figure 237 Compare selecting a version When pressing the button Compare Figure 238 is shown The two versions of the test case are displayed with their differences in red color Page 187 User Manual TEMPPO V6 1 Edition January 2014 Description of Use x W224 VI Fl Mew file opened no changes Fl Mew file opened no changes El General General beLser defined ID tc636 be User defined ID te636 Mame Mew file opened no changes Mame Mew file opened no changes i Owner Tester bener Testeri Updated 2012 02 20 Updated 201 2402 16 i Type manual oe Type manual The test case pursues the aim of testing the function Mey The test case pursues the aim of testing the function Attributes Attributes Test Steps Test Steps ee Nev step is added on branch Ch Requirements bereqGs EH Plan Figure 238 Compare differences 3 3 13Filter Users can see their test structures and test suites in a filtered way by creating and selecting filters i e for the p
172. e FM F Text Test Case A Test Step i Requirement E Chart Layout Continuous Format HTML Microsoft Word O Microsoft Excel 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 customize 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 116 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LA TEMPPO report setting in project New Project Name NewReportSetting To add a page number date time or fle insert positon the cursor in the edit box and then cick the desired button E Centinuous Report Test Package Name NewReportSetting El Settings E General eee ie Page EFTE Projectie Continuous Report Test Package i Test Fackag Test Case E Test Case 4 Test Step i Requirement amp Charts Projectname Projectstate Fi
173. e Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs Systerm Test PyS HWH 4b OW g Nofiter oF Notepad RTF Import with TCs i A 1 Introduction fey 1 14 Purpose of the document 941 2 Validity of the document e a 1 3 Definitions of terms and abbreviati miia Requirements Plan ZR 4 Relationship with other documents eee 94 5 Overview of the document Inherit attributes a 2 General description of the product Fee 2 1 Relationship with existing projects L 2 2 Relationship with earlier and follow f Regular Validation BA 2 3 Purpose of the product Fe 2 4 Delimitation and embedding of the 2 6 Overview of the required functions 3 i TAE anaie specificat i o Hiibtevees O i over sBRGC ER LISGES CO Acceptance Test Device type CAR G 002 nf i Detailed description of the required proc HE System Test O E Milestone mit 31 50 AE fery General Test Packages Test Case Error T verification E Platform Windows 7 64 bit E Regressiontest yes Test location Offshore 3441 2 LE 3 4 1 3 Save 3 444 Exit 3 Apply Discard Bt YY amp amp Figure 185 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 186
174. e 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 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 88 User Manual TEMPPO V6 1 Edition January 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 gt H GP E no ter QI Notepad RTF Import with TCs 2 Gb 1 Introduction HH 2 General description of the product General Attributes Details Requirements History Flan H 3 Detailed description of the required product 1 e031 Scope of delivery ID tpF24 Ea 3 2 Sequences cenarios of interactions i ga 3 3 User goals l hew Test Package on the branch Se 34 Required functions of the product Mame Mew Test Package on the branch EL 3 4 1 File Administration O BA 3411 New 5 41 44 Mew fle opened no Created 16 02 2012 15 50 36 Updated 16 02 2012 15 50 37 3 4 1 1 2 New file opened ch i fe 3 4 1 1 5
175. e button Select Structures LA Select Requirement Structure Created Components Testmana 2012 19 2 Mania s Learning Project UseC Testmana 14 02 2012 14 5 IBM Requisit t Link test cases to require Testimana 14 02 2012 11 1 Manual Notepad Tesimana 13 0 17 0 Manwal 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 SHect Test Sunes Mew Test Suite V61 1 Regressiontest Test Obeject 1 123 beta V amp t1 Requirement Structures Select Structures Components Notepad Requirement attnbutes sort Fune reg22 Fune req23 i Func req26 _ ascending Funes req2r Fung reg2e Te Func reg2o Fung reg30 Values Fung reg31 E Func reg32 i Al Fung reqa3 Fung reqa4 Funes reg35 Fune regq45 reqeies re gaa regs reqoey E failed W passed E not executed M blocked Mnotcompleted Mnotimplemented Mon hold E Only zero values gi ak cc a a T E No zero values 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 cumulated together
176. e current 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 51 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Step Cells User Interface F io Mukiline table M Ono for refreshing the cell content when changing the column width i Mewsboard sz Height of muiline rows during editing defaut is 52 Teast Suite Database Image columns ra ioral Ja Maxirum width of thumbnail of a user defined image field if it s 1 it s ignored i cile Te Ain 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 QuickTest Pra Test Partner HTEMPFO Designer DATS i Ranorex El Commands Mew Command i Javas El Change Management H Bugzilla Clear Quest Telelogic Change Restore Defaults 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 sorol Scale iojxl Datei Bearbeiten Format Ansicht Strg h ffnen Strg o Speichern Strg 5 Speichern unter Seite einrichten Drucken Strg P Beenden Figure 55 External viewer 3 1 3 1 7 Automated test cases TE
177. e required product features El e 3 4 Required functions of the product E on 3 4 1 File Administration Eb a 3 4 1 4 New I PREFA a New file opened no changes failed iet 3 4 1 1 2 New file opened ea A 3 4 4 Search Functions EHI 3 4 4 1 Find t 3 4411 Find up esse i 3 4 4 11 1 Case sensitive blocked GB 3 4 4 4 4 2 WinRunner Check Stat on hold E 3 4 4113 QuickTestPro Test case not implemented f E 3 4 4 1 1 4 Test Partner Test case not executed AR 3 4 4 1 1 5 UAI not executed changes passed Figure 85 Test Execution 5 x M Attributes TR Previous Results Plan Execution History General Attributes Test Steps E Avtiomation Requirements History Pa save changes Y Z iS Test execution assistant y Messa gebox No Editor Pane 4 clickQ cleared Untitled Notepad in title har Look Apply Discard 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 75 User Manual TEMPPO V6 1 Edition January 2014 Description of Use x User defined ID tc537 Mame Mem file opened changes FE Details TANEET SE fr 1 Instruction File Mew pick Expected Message gt save changes 0 x Datei Bearbeiten Format aAnsicht 7
178. e 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 70 User Manual TEMPPO V6 1 Edition January 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 i x Steps Select Test Suite 4 Introduction Select an existing Test Suite 2 Choose creation mode 3 Select an existing Test Suite Notepad RTF Import with TCs Ww V1 1 Test Suites for V1 1 2012 02 16 f v1 1 1 editable version Ge Test object Version XYZ RCO1 16 02 2012 Se Test object Version XYZ RCO2 16 02 2012 Ge Test object Version XYZ RCOS 16 02 2012 V2 editable version TEMPPO Test Suite Generator lt lt Prey Next gt gt Finish Cancel Figure 80 Copy Select a test suite In the
179. e 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 46 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad REF Import with Tes Sistem Test y1 H 4 b WH w amp Nofiter oF J Notepad RTF Import with TCs M wadote SCII Et Bi Introduction icked by Testmanager 2 General description of the product General Attributes Test Steps E Autaniation Requirements Histor yl Pian San History ea 3 Detailed description of the required pr eT 13 1 Scope of delivery Path Precondition EY 3 2 Sequences cenarios of inter eee hay E 2 3 User goals een 3 4 Required functions of the produ IZ Oi EL 3441 File Administration Ooi AA a411 New ls fl 341141 New dile open I 3 4 441 2 New file open E 3 4 1 2 Open 3 4 1 3 Save Po Gil 4 tt Exit 3 4 2 Edit Functions 3 4 3 Print Functions 2 EP 3 44 Search Functions
180. e 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
181. e v Test Pac Find up tp650 export dat 20 02 201 A User documentation Demo Not Notepad W211 editable w Test Pac Finddown tp651 export dat 20 02 201 Demo Not Notepad W214 editable w Test Pac Relations tp521 export dat 20 02 201 J Figure 346 Unlock 5 7 License Server Connection Fi TEMPPO Administrator Testmanager Host Port fatinzpt Oga www 930 my t solutions net 2013 Disconnect Server info License usage Log Server Mame atinzp1 Oga MAC address O0 30 05 F 6 4 40 Started 08 02 2012 03 05 07 Version 5 5 Build 10 14 10 2010 11 33 Licensed for Department SIS SOL AD CTE AUT Mame Pichler Rainer Figure 347 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 Page 264 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator address and the port number usually 2000 where the license server is running When connected to it you can see information about it in the sub tabs Server info License usage Log 5 7 1 Using a lice
182. eating 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 l ked EF Mi 0 Milestone mna aia amp Offshore 4 Test location mo Device type C4R F 002 Device type CAR F 003 D Device type mL Device type windows 7 64 bit Platform E yes A Regressiontest Z Device type E car G o04 0 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 41 User Manual TEMPPO V
183. echart 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 NO automation UniversalFile adapter ext MyAdapter Page 309 User Manual Edition January 2014 14 Index A Administration Database Connection 234 239 Database Migration 238 User Management 235 243 Analysis 94 Bug ID project 101 Bug ID test suite 102 Previous test suites 96 Requirement analysis based on several test Suites 110 several test suites 105 Several test suites 104 Apply 180 Attribute 10 activation 174 customize See Metadata Attributes B Baseline 10 C Command Line 291 D Database connection See Administration Database Connection See Administration Database Connection Discard 180 E Evaluation 8 94 Excel import Test Cases 22 33 Execution progress Standard 105 Export test suite to DOORS 199 F Filter 188 change 190 criterion 192 delete 191 Edit filter criterion 194 export 195 import 195 Predefined 188 Find and Replace 177 Freeze unfreeze 262 TEMPPO V6 1 Index H Hyperlink Download an upload 167 Edit 167 existing upload 162 File 161 new upload 162 Remove 167 to description 160 to fields of test case in test suite 160 to instruction expected input 160 to precondition 160 to test goal 160 to to postcondition 160 Web 161 Hyperlinks and Uploads 160 Implementation
184. ected test packages test cases mull merge overwntes those tems in the iatest version Figure 177 Merge information After finishing merge a result summary is displayed to the user see Figure 178 It is not possible to merge an item if its father item doesn t exist in the latest version Page 145 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Dd New Test Case te117254 Success D New Test Case te117252 Success Gi New Test Case tc117256 Test cases Test Packages couki not be merge because its father test package does not exist in latest version Please select and merge it za New Test Package tp117253 Success B New Test Package tp117251 Success Figure 178 Merge summary 3 3 1 3 Display of assigned attributes and requirements 3 3 1 3 1Test 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 146 User Manual TEMPPO V6 1 Edition January 2014 3 3 1 3 1 1 Description of Use Test
185. ector 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 JUnit Inport Warning There are elements in the selected JUnit Suite with JAN duplicate names in the same hierarchical level The import of these elements will cause an automatic renaming in references to their JUnit counterpart will be lost TEMPPFO and the Figure 353 Warning of duplicate test suite names The related test suites are marked accordingly and can t be selected for importing Page 270 User Manual TEMPPO V6 1 Edition January 2014 JUnit Fi Import JUnit Tests x Steps Test Case Selection Introduction select all the JUnit test cases to be imported 2 Select a JUnit test class 3 Select a set of JUnit test cases Select test cases E Framework Tests Select ll 4 Set package default values Bo junit tests extensi
186. el 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 Page 242 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 5 3 User management olx Database Roes Users a Metadata LA Projecta Locke E License E x I LDAP Testeri tester testers tester4 tester testerB tester Testmanager temppo_um Figure 312 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 you 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 lo
187. en 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 31 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad ee a o xj Project Test Structure Edit Test Execution Evaluation Tools Windows Help a Test Structure Notepad RF Import with TCs Systen Test wt H q H gh Mo titer ALI Notepad RTF Import with TCs E Introduction eae tert EHL 2 General description of the product General Attributes Details Requirements History Plan a 8 3 Detailed description of the required prod l Ber 2 3 1 Scope of delivery ID tpS62 et ZE 3 2 Sequences cenarios of interactic at 433 User goals icone sid Es 3 4 Required functions of the product Hame ag Perrormance 93 41 File Administration H 3 4 2
188. endix 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 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 uses My Adapter uses MyResult R vin getResult ein aus returnFromAutoTool Reader IResult aan e ed Figure 381 Class diagram of an adapter implementation Interface temppo test tools adapters TAutoToolAdapter Page 306 User Manual TEMPPO V6 1 Edition January 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 te
189. ener ob bl 3 4 2 1 Undo ob pe 342 2 Cut 3 4 2 3 Copy 3 4 24 Paste 3 4 25 Delete 3 4 2 6 Select Al 3 4 2 7 TimeDate 3 4 2 8 Word Wrap bl 3 4 2 9 Set Font EMS 3 4 3 Print Functions 3 4 3 4 Page Setup pk 3 4 9 2 Print Fy 3 4 4 Search Functions EL 5 4 4 1 Find O EB 34411 Find up 16 4 4 114 Test Parin 344415 UA RB S 4 4 1 2 Find down 3 4 4 2 Replace bn 5 4 5 Help System H 3 5 External interfaces of the ama F Figure 172 Selection with lt Ctrl gt e Select contiguous 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 F TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Ew Test Structure Motepad RTF Import with TCs M4 W GP EE no iter M p J 3 3 User goals gt a 3 4 Required functions of the product fea e 13 41 File Scministration eee 1341 1 New 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 143 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Evaluat Test Suite Tes
190. ent 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 Func reqz2 Sequences scenarios of interac f es Func _reqes User goals i bt Func _reqz4 Required functions of the product 4 Func _req26 File Administration p eg Func req26 Mew ie Func_req Open i Func _req2o Save Ata Func reaz9 Exit Figure 31 Requirements Selection After pressing OK the requirement s are linked to the test package Page 35 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ki TEMPPO Testmanager Demo Notepad e jol x Project Test Structure Edt Test Execution Evaluation Tool windows Help Test Structure Notepad RTF Import with TCs System Test 11 AL Notepad RTF Import with TCs E E 1 Introduction H O 2 General description of the prc General attributes Details Requirements History Plan os 3 Detailed description of the rec Sa 3 1 Scope of delivery Inherit _J32 Sequences scenarios i 3 3 User goals ay ep aa ahead Func_reqe4 Required Notepad WA AI H E 34 2 Edt Functions functions ofthe MPEmENEN nE 93 43 Print Functions product requirements 5 aa 3 4 4 Search Functions P 3 4 4 1 Find a 3 4 4 2 Replace 3 4 5 Help System Seo 3 5 External interfaces of th 5r S 3 5 1 User interfaces fo 3 5
191. equired product features 3 1 Scope of delivery General Attributes Test Steps fi a 3 2 Sequences scenarios of interactions with the environmen G Automation E History TE a ea o 0 3 3 User goals et EJ 3 4 Required functions of the product Se a fr stPart 2 23 44 File Administration AS B i fo H4 3 444 N Gg 7 a Fite Tl 3 4 1 1 1 New file opened no changes fl 3 4 14 2 New file opened changes Serint Data 3 4 1 2 Open ak a 34414 Save Scriptname project P3444 Exit 3 42 Edit Functions 3 4 3 Print Functions El 3 4 4 Search Functions BAN 3 4 4 4 Find EB 3 4 4 1 4 Find up fil 344111 Case sensitive Mer 344 1 1 2 WinRunner Check Stat ls 3 4 44 41 3 QuickTestPro Test case 3 4 4 1 1 4 Test Partner Test case E 344115 UA Lock Pesta Bizcarg 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 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 can upda
192. er Manual TEMPPO V6 1 Edition January 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 O 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 296 User Manual Edition January 2014 TEMPPO V6 1 Abbreviations 12 Abbreviations DB HW TD GUI SW 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 297 User Manual TEMPPO V6 1 Edition January 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
193. er Pia a Manager oe i mR Elicitate Specify Implement Test cases A Ve d Engineering Import Update Execute Test results o Test cases Test cases equirements _ impor update ones Execute et LF Offline Test Offline Test Management Management ene amp fee are Automated TC external external external Figure 1 Test Process with TEMPPO Page 6 User Manual TEMPPO V6 1 Edition January 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 s
194. er 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 requirement If these conditions are not fulfilled the test case cannot be saved For details see chapter 95l 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 3 3 3 2 After pressing the button OK the user is asked if he wants to assign immediately meta data If the user presses Yes Figure 341 is shown Page 11 User Manual TEMPPO V6 1 Edition January 2014 Description of Use x General Roles Test Case template Test Result template E hew Project Created 15 02 2012 12 56 15 Mandatory history comment Owner Testmanager Type TEMPPO Project Description This project is used for user documentation ores Figure 2 Project Properties TEMPPO Administrator 3 1 2 1 2Opening an Existing Project x sea eee Gee Demo Notepad Testmanager 14 02 2012 10 50 01 User documentation Testmanager 14 02 2012 11 08 07 ores Figure 3 Open Project When activating the menu item Project
195. er 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 5 3 1 2 Importing users from LDAP xi Search Last Name FO First Mame FO Login FO Windows group FO Department PSESESMEC nn ss SSSSCisS Location ine Country Clear 1 Aigner Judith atw12083 judith aigner si PSE SES MEC L Linz AUSTRIA z Fuchs Clemens atw 10Ss2 clemens Fuchs PSE SES MECL Linz AUSTRIA 3 Hainzl Thomas atw10by1 thomas hain PSE SES MEC L Linz AUSTRIA 4 Hametner Andreas atwiQcl andreas hametn PSE SES MEC L Linz AUSTRIA 5 Hametner Andreas atwgf789 pse Ydo core te PSE SES MEC L Linz AUSTRIA 6 Hampel Michael ati 134 michael hampel PSE SES MECL Linz AUSTRIA 7 Hofmann Roland atwii4c5 hofriannroland PSE SES MEC L Linz AUSTRIA 3 Holzlechner Manfred atw zsz manfred holzlec PSE SES MEC L Linz AUSTRIA J Kronegger Martin akw 12903 martin kronegge PSE SES MECL Linz AUSTRIA 10 Mayrbaeurl Max atwl0sFS max mayrbaeurl PSE SES MECL Linz AUSTRIA 11 Moritsch Karin atwol426 psenllbespr1085 PSE SES MEC L Linz AUSTRIA lz Moritsch Karin abwoF3cl psekblbespr713 PSE SES MEC L Linz AUSTRIA 13 Moritsch Karin atwObme karin moritschia PSE SES MECL Linz AUSTRIA 14 Niederwieser Peter atwlOmce Peter Wiederwie PSE SES MEC L Linz AUST
196. eral Attributes Test Steps peo 3 2 Sequences scenarios of interactions with the environmen EI Automation Requirements History Plan Execution History a 3 3 User goals aal Win Au ha 3 E aaa File Administration fag eune 3 5j 4 at File CAPragram Filesitercury Interactivewiin Runner samples fighttestsichbxstat z g D 3 4 1 1 1 New file opened no changes E 3 4 1 1 2 New file opened changes Script Data ps T 3 4 1 2 Open os 2 341 3 Save ob Sa acest ng fa 3 4 2 Edit Functions E 3 4 3 Print Functions E 43 4 4 Search Functions Eb 3 4 4 1 Find ob ER a 3 4444 Find up E eck 3441 vt A a sensitive EF 3444 AL QuickTestPro Teste case 3 4 4 1 1 4 New Test Case AS 3 441415 New Test Case 1 gt lack yap 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 53 User Manual TEMPPO V6 1 Edition January 2014 Description of Use settings x WinRunner User Interface Tree Application Path CAProgram FilesiMercury Interactive Win Runnerarchwrun exe S Test Step Cells Analysis Temporary Path CAProgram FilesiMercury Interactive win Runnerttmp po Newshoard Test Suite a Database Resutt Path CAProgram FilesiMercury Interactive win Runnertmp S El Test Automation f Lou Test Result viewer c AProgram Files UtraEdituedits2 exe
197. ery 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 1 Consider the test structure displayed in Figure 227 Initially there exists just one version of the test structure version 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 Page 182 User Manual TEMPPO V6 1 Edition January 2014 Description of Use
198. es were planned 5 test cases were executed and 19 test cases were not executed Page 105 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ll Test Execution Progress Standard gl Chart E Data EH Detailed Data se mane 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 RCO3 Select Test Suites Ee Test Cases is Test Cases Result rt Vertical Bar Chart Show valises Onentation i horizontal vertical Representation absolute D relative Results V faled W passed V not executed V blocked not completed Da y Z not implemented F on hod Test Suites Han E planned O executed M failed E passed Mnot executed O blocked i V actual execution time E notcompleted M notimplemented E 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 106 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LA Fest ection oe chart E Data E Detaited Data a Test Suite Selection Test object Version XYZ
199. escription of the required product features E a 3 4 Required functions of the product EM 3 4 1 File Administration B 3 4 11 New 3 4 1 1 1 New file opened no changes failed i 3 4 1 1 2 New file opened changes passed G ya 3 4 4 Search Functions E 3 4 4 1 Find a 3 4 4 1 1 Find up fi 3 4 41 1 1 Case sensitive blocked R 3 4 4 1 1 2 WinRunner Check Stat on hold 3 4 41 1 3 QuickTestPro Test case not implemented aa 3 4 4 1 1 4 Test Partner Test case not executed EE 3 4 4115 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 35 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 Pi TEMPPO Etestmanageri Demo Notepad pe Bipi Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 41 11 M 4 gt 49 RE No fitter EAL Test object Version XYZ RCO1 3 Detailed description of th
200. ess Test case creation overview test structure Graphical settings Y axis X axis Value subdivision Display data Chart Selection Sum of test cases Test packages of first level State absolute 3D Stacked Bar Chart Page 131 User Manual Edition January 2014 Teast packages of first level iate Designed Min Wok MiReady W Ready foi Review TEMPPO V6 1 Description of Use Figure 155 Test case creation overview Test execution progress graph test suite Graphical settings Y axis X axis Value subdivision Date Unit Accumulate Data Display data Chart Selection Sum of test cases Tested Result 1 Day no absolute Line Chart Page 132 User Manual TEMPPO V6 1 Edition January 2014 Description of Use chert E cota x ais fected ooo T_T 40 r Group br Rezus Orientation E horizordal 2 i T aiic Representation shackle T retire Accumulate Tasl Gases 20 f Tine Settings j set paoa J ea forza U Unt OS Dania gt Tested 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
201. evel 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 Mnerit reguirements true Talse Tfalse t 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 te id CDATA REQUIRED gt lt IATTLEST TEST RESULT user defined rd CDATA IMPLIED gt lt leo If at already exists in containing test structure add 1 2 gt lt ATTLIST TEST RESULT 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 S Abp ee S 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 VATTLISI TESI RESULT Situation Error Regular TError 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 lt 1TATELLSI AESI R
202. ew 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 the 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 Page 40 User Manual TEMPPO V6 1 Edition January 2014 Description of Use You also
203. 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 fitter or attributes values and logical operators 2 Choose creation mode 3 Select nodes or subtrees Filter No filter v Apply 4 Enter test suite name Attribut Val 5 Determine the logical nue ae 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 63 User Manual TEMPPO V6 1 Edition January 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 x Steps Rework Test suite 1 Introduction Select obsolete test cases hold lt STRG gt and lt Shift gt for mutti select 2 Choose creation mode 3 Select nodes or subtrees A Entel testsuite name Test object Version XYZ RCO1 16 02 2012 5 Determine the logical Detailed
204. fication This happens if you don t have a test Page 19 User Manual TEMPPO V6 1 Edition January 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 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 Eh Pfichtenheft_Notepad_withTC rtf Microsoft Word iol x sha a Textk rper gt SA ih amp dle Ebenenan Bal A Inhaltsverzeichnis aktualisieren a 2 i a E 2 Datei Bearbeiten Ansicht Einf gen Format Extras Tabele Fenster 7 Livelink Frage hier eingeben X mea il jj III III Wk M nel ee A4 Tabellengittern Arial 411 2 oR i z eA v 34 1 1 24Nevr fle opened changes o hetestcase pursues the aim oftesting the lal function Sew with changes E i Message ax A ida a Bearbeiten Format Ansicht 7 i changes 2 J Sstro h ae Ger ffnen Strg oO Speichern Strg 5 v aby Speichern unter a i Seite einrichten Ti Drucken Strg P al Beenden a Zz a clicks clea
205. 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 71 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard o x Steps Determine the test suite 4 Introduction Enter test suite name 2 Choose creation mode 3 Select sting Test Suit 4 Select nodes or subtrees 5 Enter test suite name Test object Version XYZ RCOS COPY 6 Determine the logical pression 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 ld field f TEMPPO Test Suite Generator lt lt Prey 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 to copy a certain test suite with the restriction of test results
206. 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 Building the Test Structure Extending the Test Structure adding more test packages Designing Test Cases test case design Page 10 User Manual TEMPPO V6 1 Edition January 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 manag
207. ge 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 118 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 2 za Page 119 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Case Attributes Selected Attributes Milestone E l Name NewReportSetting General aas es Add columns with popup menu in table header or hide columns Define the sequence and sire of columns by dragging in table header Page 120 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LA TEMPPO report setting in project New Project Name NewreportSeting Settings a Ganeral V Requirement Header Footer rar l i H V Requirement Structure E Version E Text El Continvous Report est Package i Teast Packag 3 Test Case v Requirement ID Requirement ID Requirement Requirement Path Test Case A Requirement Name p Test Step Charts Requirement Description Define the sequence and size of columns by drag Requirement Short Description In
208. ge 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 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 224 with the number of replaced test case and number of test case package which couldn t be replaced because of locks etc Page 179 User Manual TEMPPO V6 1 Edition January 2014 Description of Use TEMPPO i x Fi 1 Search ino test cases if completed and 7 replacements in 3 test cases were done Figure 224 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 9 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 message The buttons are only enabled if the selected node has been changed since it was loaded 15 x Fi TEMPPO Testmanager Demo Notepad Project Test Str
209. 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 Bj TEMPPO Administrator Testmanager loj x z Database e Roles f Users Metadata Projects amp Locks amp License A a J Exclude test suites Suppress export locks sa Example for versioning NS Link test cases to requirements Notepad generated Notepad RTF Import 1 editable version Notepad RTF Import with TCs E 2 1 Test Suites for V2 1 20124 E 141 editable version ge Version 2 of T H 2 Branch 3 editable version ie Notepad System amp Acceptance T Fi User documentation
210. gins 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 Fi User properties x General Roles amp Rights M TEMPRO SUPETUSET Choose project User documentation sr TEMPPO Editor MW TEMPPO Reporter TEMPPO Guest I TEMPPO Requirement Editor I TEMPPO Tester TEMPPO key User OK Cancel Page 243 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Figure 313 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 checkbox 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 wh
211. gned to all selected test cases are Requiremen parti displayed as usual in white background color Requirements assigned to not all test cases are jo displayed in a special color grey background color mess ee 1 1 req686 ComponentB R1 If you want to assign such a requirement to all se a selected TCs select it and activate the context menu mle It is displayed in red color as well as new linked requirements The tab Inherited Requirements displays the Inherited Requirements aman requirements which are inherited from test Legend packages Requirements assigned to all selected test Requireme parti cases are displayed as usual in white background color Requirements assigned to not all test cases AS ma are displayed in a special color grey background req683 ComponentAR3 TE req684 ComponentaRt a Of course it is not possible to edit anything e ere The tab Inheritance displays the COMMON rectinkedRegurements innentes Requirements inherlance state of the inheritance flag of the selected S TCs If the checkbox is not activated MW inherit Legend E Not inherted 1Notinnerted all selected TCs do not have any ee inherited requirements If the checkbox is activated Wiinherted all selected TCs have at least one inherited requirement If the checkbox looks like M nhertedpartaty the common state is mixed TCs with and without inherited requirements
212. gular 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 cases 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 102 User Manual TEMPPO V6 1 Edition January 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 cha
213. gure 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 117 User Manual TEMPPO V6 1 Edition January 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 Poe to Generate heading numbers in your report L TEMPPO report setting in project Demo Notepad p gt o gt ocan CE aa Name NewReportSetting E Settings General Title Page 5 E Continuous Report V Generate Heading Numbers Test Package Test Packag Format Options E Limit depth of report Summary Options spay Number of Representation E Test Case absolute Test Steps 1 by percentage eee Figure 142 Report General Textual Settings Continuous Report Test Packa
214. h 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 269 User Manual Edition January 2014 Fi Import JUnit Tests Steps 1 Introduction 2 Select a JUnit test class 3 Select a set of JUnit test cases 4 Set package default values 5 Set test case default values G Summary TEMPPFO Extension JUnit Test Class Selection select the JUnit test class to be imported Select the test class TEMPPO V6 1 JUnit 2 AlTests U AiTests Tests a AllTests AliTests O AllTests JUnit Classpath Class lt C ActiweTestTest C AllMembers Supplier Test junit tests extensions Bl org junit tests experimental theories junit tests extensions org junit tests junit tests junit tests runner junit samples junit tests framework fo ATemp_PwAtTeststellung PY Ayunita Note Only classes that are inthe JUnit classpath can be selected lt lt Prev Mesh Finish ii Figure 352 Step 2 A JUnit test class can be selected by which a JUnit test suite is defined After clicking next the test coll
215. hamer No user with the name not exists Import Masterpiant Incremental Import Mastenptant Incremental Cramer Mo user with the name noni exists Import Masterpiant Incremental Import Mastenptant Incremental Priority Normal is an invalid value for this field so the default value was used Figure 20 CSV Import Result Build manually XML Import Page 34 User Manual TEMPPO V6 1 Edition January 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 requirement 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 requirem
216. 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 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 cr
217. he batch file TEMPPO bat in the installation directory for running TEMPPO with command line options TEMPPO bau exporl testes eructure my pro secu the Lest structure Viz export xml Page 292 User Manual TEMPPO V6 1 Edition January 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 ArrectCoy 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 Version 1 0 Plugin Name My First Plugin PIUGin Version O1 Plugin Author Muster Max Pr gin 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
218. he criteria defined in the Page 64 User Manual TEMPPO V6 1 Edition January 2014 Description of Use logical expression Furthermore test packages where no test cases are selected at all are not displayed Bi TEMPPO Testmanager DemoNotepad lols Sep Test Structure Edit Test Execution Evaluation Tools Windows Help Teast Suite Test object Version Sra Aco 1 41 val H 4b H cy No filter ALI Test object Version v2 REDI 3 Detailed description of the required g E T 3 4 Required functions of the proc Et er 3 4 1 File Administration E3411 New E 344141 New fle ope i 3441 2 New file ope TS 3 4 4 Search Functions 3 4 4 1 Find a 3 4444 Find up En efi 344111 Case s bu E 3 4 4 1 4 2 WinRur bs E 344141 3 QuickT pi E 344114 Test Pe El EERE eon Requirements History Attributes TR Previous Results Pian Execution History General Attributes Test Steps E Automation Ea eT Test Structure Motepad RTF Import with Teal System Test t 1 1 H gt H Ea BE ho fitter Ep ode oD 344 4 Exi 3 4 2 Edt Functions E 9 343 Print Functions l y 3 4 4 Search Functions O BMG 3441 Find Et a 4 4 1 1 Find up Ir instructi Action image Expected opo pe fd 34 41 4141 Case sensitive Bob be 3 44442 WinRunner Check Stat be 3 44443 QuickTestPro Test case er 344 1 1 4 Test Partner Test
219. hented Requirement attributes Select Requirement Structure ka Avalabe Atinibutes Selected Attributes mike type Req State 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 121 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Package Attributes Test Package Attributes Selected Attributes Lo gt 4 a Name NewReportSeting amp Settings General bisa Test Package Attributes a Test Package Attributes Selected Attributes Page 122 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Case Attributes Test Case Attributes Available Attributes Selected Attributes
220. herit their attributes If the checkbox looks like W nherted partaly the common state is mixed TPs with and without attribute inheritance Page 149 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 3 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 Direct inked Requirements requirements which are directly linked to a TP Requirements assigned to all selected TPs are parti displayed as usual in white background color Requirements assigned to not all TPs are displayed a Requirement ID Requirement Name ant in a special color grey background color New 20685 a requirements are displayed in red color If you want req686 ComponentB R1 x req687 Componente R3 ia to assign such a requirement to all selected TPs select it and activate the context menu Mb ices eetnetens Such requirements or new linked requirements are displayed in red color The tab Inherited Requirements displays the TEn e ra ae common state of selected TPs which inherit their Legend requirements Requirements assigned to all selected Requireme part TPs are displayed as usual in white background color Requirements assigned to not all TPs are 1 F Requirement ID Requirement Name b displayed in a special color grey background color A ee mais oa i
221. 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 case 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 SiITEMPPO 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
222. ich the user was imported If a user was created manually the value in the column LDAP server is not set 5 3 1 1 LDAP Connection iojxi Database Roes Users a Metadata LA Projecta Locke License k X F LDAP OOo danme Franee gin S E Tester E tester E testers E tester4 E testers tester Connect to LOAF serwer DSM Jatos C Pai Host scdldap atas net Port ss Base User Domainilsery waat 129 Password Connect SE Synchronize users H Import users Figure 314 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 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 4 button For each DSN Page 244 TEMPPO V6 1 TEMPPO Administrator User Manual Edition January 2014 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 server 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 serv
223. ields 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 196 User Manual TEMPPO V6 1 Edition January 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 1L6Test 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 TEMPPO and after executing them outside of TEMPPO the results are imported 3 3 16 1 Export The export XML feature can either be used to execute automated TCs somewhere off
224. if a postcondition is entered and the corresponding checkbox in TCT see Figure 214 Test Case Template Test Step is ticked e if a test goal is entered and the corresponding checkbox in TCT see Figure 212 is ticked e if at least one requirement is linked and the corresponding checkbox in TCT see Figure 215 is ticked e if an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 213 is ticked Page 172 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 3 1 2Unlock save existing test case An existing test case can be unlocked saved without message if a precondition is entered and the corresponding checkbox in TCT see Figure 214 is ticked if a postcondition is entered and the corresponding checkbox in TCT see Figure 214 is ticked if a test goal is entered and the corresponding checkbox in TCT see Figure 212 is ticked if checkbox Inherit in tab Requirement is activated and the corresponding checkbox in TCT see Figure 215 is ticked if at least one requirement is linked and the corresponding checkbox in TCT see Figure 215 is ticked if checkbox Inherit in tab Attributes is activated and the corresponding checkbox in TCT see Figure 213 is ticked If an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 213 is ticked If a TCT is activated and a test case with missing e g default attribute values is edited those are not added automatical
225. ight 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 New Find and Replace F3 Show Details Select All E Tree b A Cut Ctrl Copy Ctrl C Ea Paste Ctrl Delete Delete Order M Refresh recursively Ta Move Ownership g Analyse selected b 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 140 User Manual Edition January 2014 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluatior Test Structure Notepad RTF Import with TCs Systen M4 W GP E monter AL Notepad RTF Import with TCs F241 troduction E 2 General description of the product 5j 8 3 Detailed description of the required prod L341 Scope of delivery Z 3 2 SBQUENces Scenarios of interacti mp a User goals seen 0 4 Required functions of the product Eta 3 4 1 File Administration Ls i 3 4 2 Edit Functions 3 4 3 Print Functions m 3 4 4 Search Functions 84 5 Help
226. ignore PROJECT TS 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 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 lt currently IGNORED gt lt ATTLIST PROJECT name CDATA REQUIRED gt lt the TEMPPO project must already exist DL 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 IE 2 lt ATTLIST TS version CDATA IMPLIED gt lt Added 31 5 2004 gt lt ELEMENT TP DESCRIPTION PRECONDITION POSTCONDITION REQUIREMENT TP TC gt SUAS cee name CDATA REQUIRED gt lt if zero length then name New Testpackage generated gt lt if it already exists add 1 2 gt lt TATTLISTE TP test category CDATA IMPLIED gt gt lt 1 28 at 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 req
227. ile Administration eco 3 444 New fi 3 4 1 1 1 Mev file opened no change A 3 441412 New file opened changes Planned test execution time f h 30 min 0 65 Eb 8 3 4 4 Search Functions a 3 4 4 1 Find Actual test execution time lo h 45 min 0 59 ag a 4444 Find up iol 3 4 4 1 1 1 Case sensitive blocke R 4 414 2 WinRunner Check Ste 34 41 15 GuickTestPro Test ca ma 3 441 414 Test Partner Test ca on 3 4 4 1 1 5 UAI not executed gt Lock Appl Discard 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 3 i E oj xj Project Test Structure Edt Test Execution Ewalustion Toole windows Help Test Suite Test object Version XYZ RCO W11 l laj xj H d b WH no fter gt Test object Version 2 RCO a 3 Detailed description of the required product features 3 4 Required functions of the product General Attributes Test Steps Ei Automation Et 3 4 1 File Administration Requirements History Attributes TR Previous Results Plan Execution History l a 3 l 1 Mew FE 344 12 Neus otis aoe ET 5 EE 3 4 4 Search Functions Fl 3 4 44 Find i i Ei t 34 4 11 Find up oe H 3 4 4 1 1 1 C
228. iled 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 112 TEMPPO V6 1 Description of Use User Manual Edition January 2014 eS a Test Suites Select Test Surtes New Test Suite V6 1 1 New Test Suite V8 1 1 Requirement Structures Select Structures Components Notepad Requirement attributes X Chart E Data Esl Detailed Data v Requirement Requirement Structu faled passed not executed 8 8 not on Chart Horizontai Bar Chart v _Func_req2 Sort LF unc_req2t a d E alphabetical Func_req22 Notepad V1 te536 New Test Surte V6 1 1 l 5 ascending Func_req22 Notepad V2 tc536 New Test Suite mintir a ee descending Func_req23 iNotepad 1 tc742_1 New Test Suite V6 Ti i T T T Func_req23_ Notepad V2 te742_1 New Test Suit l Values Func_regq24 A j_Func_req25 i O Only zero values Func_req26 Notepad 1 tc537 New Test Suite V6 1 1 if f 7 a ae No zero values Func_req26__ Notepad V2 tc637 New Test Suite Func_req27 Notepad V
229. ing 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 d 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 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 136 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Oo x Project Test Structure Edt Test Execution Evaluation Tools Windows Help e rest Structure Notepad RTF Import with TCs System Test v3 a E x AL Notepad RTF Import with TCs Fb 1 Introduction J 2 General description of the product General Attributes Details Requirements History Plan 5 3 Detaile
230. ion coen 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 Fi TEMPPO Testmanager E loj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help 5 Mev ER Euplicate E Open Reopen 1 Notepad System amp Acceptance Test Demo Notepad wi 4 Close 2 Notepad Demo Motepad generated v4 D al 3 Notepad Demo Notepad generated w 1 1 El Import Structure a 4 Notepad System amp Acceptance Test Demo Notepad V4 Update F Export Structure Apply regurement updates q Task lists Mewshoard E Versions 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
231. iption 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 file Fi TEMPPO Testmanager Demo Notepad Ioj x Project Test Structure Edt Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test 31 q E x Fe 4 Introduction Pt 2 General description of the product General Plan Requirements H al 3 Detailed description of the required g Ce 4 Specifications for project managemel Mame Notepad RTF Import with TCs cl 5 Obligations of the client i 6 Literature Owner Testmanager Updator Testmanager 7 Annex Fb S Introduction 1 na 9 General description of the product 1 Type Test Structure H al 10 Detailed description of the required Gt 141 Specifications for project managem TEMPPO Designer IDATG D A 12 Obligations of the client 1 He 43 Literature 1 Test level System Test H 14 Annex 1 Created 15 02 2012 16 36 29 Updated 15 02 2012 16 44 37 Description Lock Appl Discard Figure 23 name of test package already exists 3 1 2 2 7 3 Transfer data via
232. 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 and 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 Page 262 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator only be
233. 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 aborts 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 290 User Manual Edition January 2014 TEMPPO V6 1 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 copy_testsuite lt project test structure version existing test Suite new test suite name flag actual result flag bugid gt profile lt user password gt file lt file gt separated list of values where the names for pro
234. ivided 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 Page 247 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 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 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 ent
235. ject 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 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 names for project test structure version existing test suite new test suite name and flag actual result and bug id must be specified with true or false A new test suite is created with settings of existing test suite Optionally you can configure if you want to get actual result and bug ID of source test Suite for retesting bug fix more efficiently separated list of val
236. junt samples money Mon Jy testoneyBagEquals unit sarples money Mor Jy testMoneyBagHashQund samples money Mone Jy testMoneyEquals jund samples money Money w gt Figure 369 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 280 User Manual TEMPPO V6 1 Edition January 2014 JUnit TEMPPO atw108s2 Unit extension tests Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Sample JUnit execution V1 1 1 eat lank Sarees vector est Owner atwi Os Created 10 12 2002 14 21 01 OE junit samples money Money Test Type Test Package Test Category z Figure 370 Executing JUnit test cases Running a JUnit test case involves three levels of execution 1 TEMPPO where the JUnit test case class is instantiated and the corresp
237. kage 35 37 Requirement Structure TEMPPO V6 1 Index activation 175 Requirements Import 10 Roles 240 Predefined 302 S Settings 211 Bugzilla 230 Change 232 Change Management 229 Clearquest 231 Global 211 JUnit 226 QuickTestPro 224 Ranorex 228 TEMPPO Designer 227 TEMPPO Test Manager 212 Test Automation settings 220 TestPartner 225 UAI 222 T Task lists 209 TEMPPO Administrator 239 LDAP 244 License Server Connection 264 Locks 263 Metadata 247 Projects 258 Requirement structures 254 Roles 240 Uploads 253 TEMPPO Designer Restore designed test cases 290 TEMPPO Manager 234 Test Automation Ranorex 55 Universal Automation Interface UAI 56 WinRunner Quicktest Professional SilkTest TestPartner 53 Test Automation settings 220 Test case Additional test levels 41 Attributes TR 78 Execution History 45 Link Requirements 35 Set test results 159 Tab History 42 Tab Plan 44 Unlink requirement 36 Test Case 5 77 78 Adding more columns 49 attribute 5 Compare 186 design 38 Import from Word 19 Merge 87 Postconditions 46 Preconditions 46 results 74 tab Attributes 39 tab Automated 52 Page 311 User Manual Edition January 2014 tab General 39 Tab Requirement 42 tab Test Steps 47 Test Case Execution 8 58 Test Case Implementation 46 Test case template 169 Filter 173 Test Categories See Test Package categorize customize See Metadata Test Categories Test Creation Assistant 48 Test Design 7 10 Test exec
238. ket H Quick Test Pro Test Partner ttn be TEMPPO Designer IDATG i Ranorex El Commands New Command SE El Change Management Bugzilla Clear Quest Telelogic Change Tallow duplicate names in same hierarchical level Restore Defaults OK Cancel Figure 349 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 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
239. l Test Levels E Attribute values Inherit attributes Figure 374 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 ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Jy JUnit 5 Z Ej x Id d H gh E Mo filter T TEMPPO Designer DAT Design Test Cases Restore designed Test Cases AL Notepad RTF Import with TCs re TEMPFO Designer DATO Tasks B 01 1 New Task Package General Altribubes Details Requirements History Plan J D 2 Introduction a 3 General description of the product ae A 4 Detailed description of the required product fesl ni 2a 5 Specifications for project management A 6 Obligations of the client Regular Ch Pieter Priority Top 7 Literature Ge ANNEX Error Verification State Designed Additional Test Levels Attribute values E TP Type User case x Inherit attributes Lock Apply Discard Figure 375 Design Test cases After activating the menu item Design Test Cases the window Connection Status Figure 376 and TEMPPO Designer IDATG itself are displayed Page 287 User
240. lasspath can be selected lt 2 Frew Nest Finish Cancel Figure 364 Step 2 The correct JUnit test class is automatically selected TEMPPFO 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 Fj Update JUnit Tests k xj Steps Add New Test Cases 1 Introduction Select the nev JUnit test cases to add 2 Select a JUnit test elass g 3 Select new JUnit test tases Sacchi eae 4 Select obsoltete TEMPPo EHEN junit samples VectorTest Select All test cases 6 Set package default values El testClone junit samples vector Test 5 Settert case default values E testRemove Ali junit_samples vector Test Dessiect Al T Summan Xj a i TEMPPO Extension Panama oo Prey Next gt Finish Cancel Figure 365 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 VectorTest Page 278 User Manual TEMPPO V6 1 Edition January 2014 JUnit Fi Update JUnit Tests Steps Remove Obsolete Test Cases 1 Intreduethon Select the obsolete TEMPPO te
241. 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 1 User cancelled the synchronization Figure 318 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 Page 246 User Manual Edition January 2014 Fi Synchronize with LDAP The Following users could mot be Found in the LDAP server Thomas Andreas Andreas Michael Roland Holzlechner Manfred kKronegger Martin Mayrbaeurl Max Moritsch Karin Moritsch Karin yz 1Oby1 xyzl ci xyzgf7ag xyzZllav4 xyzll4c5 xy2lZose xyz212903 yz lOsh xyzgf3ci xyzgf4z6 atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa TEMPPO V6 1 TEMPPO Administrator Figure 319 Result of the synchronization with LDAP 5 4 Metadata You can customize Metadata 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 5 The tab Metadata is d
242. le 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 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 20 2 7 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 Page 222 User Edition January 2014 Manual TEMPPO V6 1 Description of Use 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 U
243. line 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 x Should the test sute be locked after export The file can only be imported if a lock is set W Lock Test Suite Figure 250 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 197 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x Test Suite Version 2 of Test abject ROOT vW2 1 1 H d gt b WH E Mo filter BR Version 2 of Test object REDI a 3 Detailed description of the require Sea 3 4 Required functions of the pi BHA 3 4 1 File Administration ELA 341 1 New H D 3 41 11 New tile i 3 4 1 4 2 New file i l Bay 3 4 4 Search Functions j Testmanager 20 02 2012 13 22 51 xML File EHA 3 4 4 1 Find G 3 4444 Find up E 3 444114 Cas Lock Apply Discard Figure 251 Exp
244. lities 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 222 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 222 Find and Replace Xx P T Mo more occurrences Found Figure 222 No more occurrences found e List occurrences With the button List occurrences the searching result is shown in a list see Figure 223 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 Mew file opened changes Tester 15 02 2012 16 45 51 Figure 223 List occurrences 3 3 8 1 2Replace Test Case Test Package There are also two possibilities for replacing e Replace 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 packa
245. loaded Check Locks in Test Suite activated Switches on off check of locks in test 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 recommended 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 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 Page 218 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 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 s
246. lues G Summary Mame Chapter Precondition TEMPRPO Extension JUnit lt e Prey Finish Cancel Page 271 User Manual TEMPPO V6 1 Edition January 2014 JUnit Figure 355 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 Ei Import JUnit Tests X Steps Test Case Default Values 1 Introduction Enter default values for the new test cases in TEMPPO 2 Select a JUnit test class 3 Select a set of JUnit test General attributes PE ditions Cdtes 4 Set package default values ic rae Regular Priority To 5 Settes case default values 4 y P 6 Summary Error State Designed Additional Test Levels Attribute Values fa System Test x TEMPFO Extension JUnit Ei Import JUnit Tests i x Steps Summary 1 Introduction Review your settings zZ Select a JUnit test class gt Select aset of JUnit test You choose to impor the JU
247. ly 3 3 3 1 3Test case template and filter If a TCT is activated and a filter is set and a new TC should be created and 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 3 3 3 2 Test result templates A test result template supports you in test case execution You can define a test result as mandatory or set a default value if a result is recorded Page 173 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Structure 1 Manua fi 2 Auto General Pian Requirements Tempiste Attributes Test Case template Test Result template 7 Test Result template activated Remark Test result template is oniy applied in case of result recording Test case viewing is not concerned Attributes Attribute Mandatory TRI TR2 Figure 217 Test result template In Figure 217 test result attributes are defined If you record a test result TR1 Releasel1 is assigned automatically and you have to specify a value for TR2 Otherwise the test case cannot be saved 3 3 4 Attribute activation In some cases attributes shouldn t be assigned to test cases anymore because they are invalid in future In TEMPPO available attributes can be restricted for assignments but assignments from past are still visible a
248. ly supplies the creation date and owner which is taken from the Windows account Page 258 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator AA ome Owner Strasser Johanna Type TEMPPO Project Description Demo Project Figure 338 Project Properties New Project A Project Properties Editor Guest Key Key Rep Reg Test A A IS Figure 339 Project Properties Roles In the tab Roles roles can be assigned to users see Figure 339 By pressing OK the project is created Then the project can be edited and worked on in TEMPPO Page 259 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 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 338 is displayed Copy project r So Do you realy want to copy the project Demo Notepad Oniy the assigned meta data except requirement structures and user roles are copied Figure 340 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
249. manager Updator Testmanager e Test Package ii Order Test automated test case i Refresh recursively fa Move Ownership gt Lock Apply Discard T 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 27 User Manual TEMPPO V6 1 Edition January 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 colored yellow lo x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Motepad RTF Import System Test pu H gt b Hyg EE Mo fter M AL Notepad RTF Import HHL 1 Introduction H 2 General description of the product General attributes Details Requirements History Plan EF A 3 Detailed description of the required prod 0 3 41 Scope of delivery ry fps g a Sequences scenarios of interactions with the environment i 3 3 User goals lsearchFuncions 5 3 4 Required functions of the product Mame search Functions E 3 44 File Administration Owner Testmanager Updator Testmanager E D 34 2 Edit Functions E l 3 4 3 Print Functions Created 15 02 2012 16 28 59 Updated 16 02 2012 08 37 12 E ag 4 4 Search Functions E E 34A Search up
250. mated Sst Resultis eer Edt M Refresh recursively ta Kove Ownership g Analyse selected 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 F TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version v Roo ies H ab H 69 EE hofter i Test object Version wY RCO 5 3 Detailed description of the required p Ela 3 4 Required functions of the prodi Requirements History Attributes TR Previous Resuts Plan Execution History O EH 34141 New i 34111 New i i 3 4712 Men Me ope L a a iemene aie 3 4 4 Search Functions File New pickt ae cave fA Unbenannt Ed Hi changes 4 SEN ISR 3 44414 ind up ip He E 344111 Cases as AGB 34 4112 WinPur Sn E 3 4 4113 QuickT Spade EE 34 44114 Test Pe Speichern unter oF 34 4445 UA no Seite einrichten b a RTF Import with TEs duction eral description of the product ied description of the required product features Scope of delivery sequences scenarios of interactions with thi _ User goals Required functions of the product 3 4 1 File Administration A 3 41 1 New D 3 4 1 1 1 New file opened no change
251. mporary files are stored e Result Path path where all the result runs are stored e Result viewer path to QTReport exe Page 224 User Manual TEMPPO V6 1 Edition January 2014 Description of Use el User Interface p Tree Application Fath D AProgram Files HPiauick Test ProfessionalibiniaTPro exe Test Step Cells Analysis Temporary Path Joey a MHewsbhoard Teast Suite cMempesut Dee Result Path Ctempiresult El Test Automation Silke Test Result viewer D Program Files HPiauickTest ProfessionalibiniaT Report exe S Hin Runner Universal File Arguments wecript lt lt Test File gt gt be Universal Socket aeouick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands New Command i Javaza2 Fl Change Management Bugzilla Clear Quest Telelagic Change Restore Defaults OK Cancel IY delete temporary test automation files Figure 287 Settings QuickTest Pro TEMPPO uses the data table iterations from the QTP test case Run Data Table iterations Run one iteration only Run on all rows f Run from row 2 to roy E Recovery Local System Monitor Log Tracking When emor occurs during run session pop Up message box Object synchronization timeout 20 seconds T Disable Smart Identification during the run session Save image of desktop when error occurs if test is run by the HP Business Process Monitor OF Cancel Ap
252. n 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 160 User Manual TEMPPO V6 1 Edition January 2014 Description of Use EB Bolg X talic U Underline gt Hyperlink S Remise ty Breniitit Ey Downoad Figure 198 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 198 which opens the Hyperlink window see Figure 199 E web S Fie EB Database URL Jrttp tenn Figure 199 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 200 m B web File Database File C AProgram FilesiTEMPPO 6 0uqunicher properties OK Cancel Figure 200 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 161 User Ma
253. n 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 43 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F History Comment 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 executes 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 Fi TEMPPO Testmanager Demo Notepad l 2 iol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Motepad RTF Import with TCs System Test 41 Wo dd amp WH E Mo filter BAJ 3 4 Required functions of the product EP 3 41 File Administration ER 3411 New General aliribyes ear A 3 4 1 1 1 New file opened no fy Automation Requirements History Plan Execution History fi 3411 2 New file opened che
254. n 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 Import CSV eee Mime You can assign Excel atinbutes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by Selecting an item from the combobox Remark New attnbute values of UDAs wal be automaticaly created in TEMPPO s meta data Test Case Namet Title User defined ID ID V TestGoat Path V Owner Created By wW Planned tester F Planned test execution time ValitationVerification W Regular Error F Input Figure 19 Assign Excel to TEMPPO attributes After pressing OK the user is informed about errors of the import F i 4 Tin We Or All test cases were importert For the folowing test cases a probem was detected and a default value was used Test Case TEMPPO Attnbute Error Example Testcase Document Properties Example Testcase Document Properties Chwner Mo user with the name noni exists Create Devroom for Product Create Gevroom for Product Chwirer No user with the name nnd exists Assign Members to Gevroom Assign Members to Gevroom Cranmer Mo user with the name nn1 exists Assign Group to DeyvRioom Assign Group to beyRioom C
255. n 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 138 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F TEMPPO Testmanager Demo Notepad 7 Project Test Structure Edt Test Execution Evaluation Toole Windows Help 5 tL CI Mev an 3 N d gt b H i Find and Replace F3 HBl i Motepad ATF Ir O x show Details HE Introductior 71 Select All Ctri 4 a1 2 General de Attributes Details Requirements History Plan G 3 Detailed de Ci 7 e ree pl S41 Scop ID p535 3 2 Sequl KA Compare fii 3 3 User i M S34 Requ d Cut Cire Mame Mew Po F 4 a8 Copy Ctr Owner Testmanager Updator Tester a at Paste Ctrl TEE r Created 16 02 2012 16 45 50 Updated 16 02 2012 17 12 24 Po aR Paste before a olf Type Test Package ia rder bema bode o ooo r of TCs 2 Ma E i 3 7 Delete Heki ategory H te Test automated test tase scription H 34 3 eee E344 Edit Fitter Ctrl F 2 4 5 H 3 5 Exter Fl 3 6 he _ o Eaa eia Ga Move Ownership Lock prli 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 inclu
256. nager Created 20 02 2012 16 43 56 Updated 20 02 2012 16 43 57 Type Task Package Number of TEs 0 Test Category sr Description Lock Apply Discard Figure 373 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 286 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Designer IDATG Fi TEMPPO Testmanager Demo Notepad ol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help a Test Structure Notepad RTF Import with TCs System Test W3 l j E x H d b H oF E Mo filter ALY Notepad RTF Import with TCs re TEMPFO Designer DATO Tasks 1 1 New Task Package General Attributes Details Requirements History Plan J J 2 Introduction a 3 General description of the product E i 4 Detailed description of the required product fesl Ea 5 Specifications for project management m EB Spigen of the client fe Regular fe eTieeiian Priority Top i Ea 7 Literature E a Annex Error Verification State Designed Additiona
257. naling 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 J Just For Demonstration a Edit ME V1 editable version check In Activate Tree style i Versions only Latest test structure version in the main line This version is checked out for editing Labels only is Versions and Labels ClearCase style Order f ascending descending 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 59 User Manual TEMPPO V6 1 Edition January 2014 Description of Use A new Test Suite is created by activating Test Execution gt New This will cause
258. nd activate the context sensitive menu mouse over hyperlink and choose the menu Download Figure 211 is shown to select a directory for the file download Page 167 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F Select a destination directory x Look in B Eigene Bilder we F O Media Go Desktop ini Zuletzt GD Sample Pictures aah TPrr JPS Reena mer Geb a96efS76a_8454626 3 jog GU untitled bmp Pieler ramanta Gab e96afS76a_8454626_s4 3 jpg E Gd cut jpg Desktop File name Jexpected image jpg Download Files of type fan Files F Cancel Figure 211 Destination selection 3 3 3 Test Case Templates Templates can be defined for test structures and test suites For each test structure exactly 1 test case template can be defined For test suites belonging to a test structure a template can be configured as well In the tab Test Case Template the test manager 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 requirement If these conditions are not fulfilled the test case cannot be saved For details see chapter 3 3 3 1 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 values for the mandatory attributes For details see chapter 3 3 3 2
259. nd can be used e g for filtering Attribute activation can be defined for each test structure in tab Attributes see also Figure 218 If the check box for an attribute is greyed the attribute is set in template Only Superusers and TEMPPO Key Users are allowed to deactivate attributes Page 174 User Manual Edition January 2014 Fg a eal ee Test Structure Notepad RTF Import with TCs System Test 14 MH d b H ga BE No filter RTF import with TES Introduction RS General description of the product a Fa Detaled description of the required pr E Speciications for proyect management m E Obligations of the cient A Literature s E wd amp Mame Hi Browser A Developer E Device type Firmware version 2 Ist Schon Testbar Mefienstein 0 Mile stone Milestone 2 New Entry mJ Plationm Regressiontest A Sample 2 Test location 9 Test_ININ_ IN m TP Type 4 Treiber 2 Window 7 client Fl i i i Ei Ei Ei TEMPPO V6 1 Description of Use H E TEMPPO Designer IDATG Tasks i ae Generat Pian Requirement structure Atirbutes Attribute activation Select attributes which can be assigned Attribute Type Test Case Test Case Test Case Test Case Test Result Test Suite Test Case Test Case Test Case Test Case Test Resuit Test Case Test Case Test Case Test Case Test Case Test Package Test Case Test Result Test S
260. nd fetch the result obtained by the tool after the automated run Page 83 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Before running automated tests the automation settings in TEMPPO s administration tool see 4 must be configured IO x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Help Test Sute Test object Versi Li Mew Ca Open M APAS Reopen M Test object version ae cy ees a 3 Detailed descripti EHA 3 4 Required ful Run automated l Attributes Details Requirements History Plan Set Resut s ID peso F Export Test Suite F EY 3 4 4 Searc Import Test Suite gt Hama Fina sl E3441 5 90 0 ig BRR Find locks fi 344111 Cases Created 15 02 2012 17 0 Updated 16 02 2012 13 2 EE 3 4 4 1 4 2 WinRur 3 4 4 1 QuickT fi 3 441 414 Test Pe Number of TCs 5 EJ 3 4 4 1 1 5 UA no Test Category Description Lock Apply Discard Caner 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 exe
261. ndow opens for set the properties for creating a report see Figure 139 Page 114 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LF TEMPPO report setting in project Demo Notepad 9 F vug oe lt pn i Name NewRPeporntsetting SB Settings Daner Testmanager EP General ce A Created 07 05 2013 11 44 09 Updator Updated Description j Test Case Attributes Test Step cee Requirement Figure 139 Report settings overview The reporting functionality 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 115 User Manual TEMPPO V6 1 Edition January 2014 Description of Use H TEMPPO report setting in project New Project Name NewReportsetting Components E Title Page Ie Continuous Report ae Test Package General Information of Test Structur
262. neral 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 20 2 7 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 xi Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Motepad RTF Import with TCs System Test pu M4 MH g E Mo fitter 2 General description of the product 3 Detailed description of the required product features zm 3 1 scope of delivery General Attributes Test Steps 3 2 Sequences scenarios of interactions with the environmen EJ Automation Seaton E History Plan LL 3 3 User goals UniversalFile i oo he Oni IFil EPL 3 4 1 File Administration ie niverse ie gt o File evni TEMPPOTEMPPOtsourcesilspriv bat S Ea fd 3 4 1 1 1 Mew file opened no changes i 3 4 44 2 Mew file opened changes i 3 4 1 2 Open 0 3 41 5 Save i 3 4 1 4 Exit Execution History Additional Arguments 3 4 2 Edt Functions 3 4 3
263. ng test cases a probem was detected and a default value was used Test Case TEMPPO Attribute Error Example Testcase Document Properties Example Testcase Document Properties Chamer Mo user with the name noni exists Create Devroom for Product Create Gevroom for Product Chaner No user with the name nn exists Assign Members to Gevroom Assign Members to Geyroom Chamer Mo user with the name noni exists Assign Group to DevRioom Assign Group to beyRioom ewer No user with the name not exists Import Masterpiant Incremental Import Masternptant Incremental Chamer Mo user with the name nnd exists Import Masterpiant Incremental Import Mastenptant Incremental Prony 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 Tes
264. nge Management Tool C Telelogic Change Database JIPA El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands Mew Command Be Change w Bugzill Clear Quest Telelogic Change Restore Defaults OK Cancel e Manage EE Figure 296 Settings Change Management 3 3 20 2 12 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 230 User Manual TEMPPO V6 1 Edition January 2014 Description of Use l User Interface Tree Test Step Cells Analysis Basic Authentication activate E gt Mewshoard User linterna Test Suite REREEREEEREEREEEREEEEERELERAEEEREEAEEEREEREEEREEREERELEEREERELEREEREEEEEEEEEREEEEREREEEREEEREES Database Password ssssssesnnanannanannazsnnanannansnaaninnatinnstinaatinaatinantinantinanQQnnsQnnanQnnA sana Fl Test Automation H Silk Test Hetin Runner Universal File URL nttp ftatinzpt Oga 24S bugs temppo_internal He Universal Socket QuickTest Fro User testmanger atos net Test Partner P fee 2 JUnit assword TEMPPO Designer DATS i Ranorex El Commands New Command JSD Bugzilla
265. nit test class cases junit tests extensions All Tests 4 Set package default values 5 Settes case default values into the TEMPPO test package 6 Summary JUnit tems to import 6 new testcases willbe added 4 pew test packages will be added TEMPPO Extension JUnit lt a Prev bert 2 Page 272 User Manual TEMPPO V6 1 Edition January 2014 JUnit Figure 357 Step 5 The summary of the import wizard F TEMPPO Testmanager Demo Notepad oO x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure JUnit System Test w O x I a 1 Framework Tests El w 1 junit tests extensions ExtensionTest General Plan Requirements a hy 1 11 test Running Error In Test Setup junit t Mame lint Bhan kg 1 1 2 test Setup Error In Test Setup junit tes El w 2 junit tests extensions ActiveTestTest Owner Testmanager Updator _ ay 2 1 testActive Test unit tests extension Crested 12 2012 15 48 24 Updated poo he ahg 1 22 testactive Repeated Testi junit tests 2i kal 3 junit tests extensions Repeated Test Test Type Test structure hg 1 3 1 test Repeated Once junit tests exten hy 1 3 2 test Repeated More Than Once junit t hy 1 3 3 testRepesatedZero junit tests extens wel System Test hig test Repeated Negative junit tests extensions RepeatedTest Test tc793 Lock Apply Discard TEMPPS Designer IDATS E Figure 358 Step 5 The res
266. niversal Socket Universal Socket l User Interface Tree rw Test Step Cells Analysis H Newsboard s Teast Suite El Test Automation be Silk Test Hin Runner Universal File QuickTest Pro Test Partner JUnit be TEMPPO Designer IDATG i Ranorex El Commands E Change Management Bugzilla Clear Quest Telelogic Change i JIRA Drive Letter Ica S Application Path C AProgram Files TEMPPO 5 5 4uto Tools Proprietary tester bat IF Address 127 0 0 1 Port Humber 1492 Connection delay 5 seconds Adapter temppo test tools adapters C Defautt uto Tool dapter sr Argument argi arg tcid filet i E Upload resut files to database Result Viewer c winntinotepad exe Mew Command aves Restore Defaults OK Cancel Figure 286 Settings Universal Socket 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 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 applicati
267. nn i 11 Description i i 12 Test Category H j 13 Path Systemtest New Test Package 14 Created 10 06 2008 15 33 49 i i 15 Document Name i 16 Document Chapter i Updator nn1 18 Updated 10 06 2008 15 33 49 19 Precondition i i New Test Case 21 Test Goal i i 22 Path Systemtest New Test Package New Test Case 23 Created 10 06 2008 15 33 49 i i ID tc12383 25 Priority Top i i 26 Situation Regular Test Case Type Validation i i 28 State Designed i i 29 Type manual i 30 Updator nni 31 Updated 10 06 2008 15 33 49 32 Precondition i i 3A Tact Stane j 4 4 gt Hh Temppo_Reporting IKI gt Bereit NF Figure 153 Report Excel Page 130 User Manual Edition January 2014 TEMPPO V6 1 Description of Use 3 1 5 6 5Sample Charts Test case creation progress test structure Graphical settings Y axis X axis Group by Date Unit Accumulate Data Display data Chart Selection E cran E data SURE lel oe Test Cases 2003 apri f 2007 Mey M Son J J001 Jour b 2002 Mach i i 2501 Daoembei B Created Siate E Designed Bin Wel BReady BB Re aiy tai Review Sum of test cases Created State 1 Month yes absolute 3D Stacked Bar Chart Ceo absolute redatives Accumulate E Tne Sets A swt ooizz007 Figure 154 Test case creation progr
268. nnot 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 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 A Import CSV You can assign Excel atinbutes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by Selecting an item from the combobox Remark New attnbute values of UDAs wal be automaticaly created in TEMPPO s meta data Test Case Name Tite User defined D ID W TestGoal Path W Owner Created By E Precondition Planned tester F Postcondition ia Planned test execution time V Priority Priority Validation Verification i State Regular Error Test Step i al Instruction Expected Attributes Pa Version Figure 19 Assign Excel to TEMPPO attributes After pressing OK the user is informed about errors of the import Page 23 User Manual TEMPPO V6 1 Edition January 2014 Description of Use All test cases were importert For the followi
269. nse 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 fx Netzwerkkarten und Bindungen Reihenfolge der Anbieter Die Verbindungen werden in der Reihenfolge aufgefuhrt in der Netzwerkdienste darauf zugreifen Verbindungerr MAN Verbindu ng ae VMware Network Adapter VMnetl A Local Area Connection A wireless Network Connection Bindungen tur LAN erbindung 5 File and Printer Sharing for Microsoft Networks Internet Protocol TCPYIP Client for Microsoft Metworks Internet Protocol TCP IP Figure 348 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 DentityExpansionLimit 1000000 Djava rmi hostname 158 226 235 13 Page 265 User Manual Edition January 2014 6 JUnit TEMPPO V6 1 JUnit Since TEMPPO V3 0 it is possible to manage and execute JUnit test methods with TEMPPO
270. nt Structure Activation 3 3 6 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 6 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 Page 176 User Manual TEMPPO V6 1 Edition January 2014 Description of Use A list of all TEMPPO users is presented to the current user see Figure 320 on page 248 A new owner of the selected item can be chosen see also 5 5 6 3 3 7 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 220 f Copy with Meta Data ie only those assigned to opened project all used in selected subtree Mote Insensitive tems are not used in selected subtree J Test Level IY Test Category IY Attribute lv Upload Additional Test Step Column Figure 220 Copy Meta Data There you can choose from three possibilities to paste e Cop
271. nual TEMPPO V6 1 Edition January 2014 Description of Use F Upload Properties of launcher properties x General launcher properties a fe ia Origin CAProgram Files TEMPPO 6 0launcher properties Size 2 10 kByte Created 16 02 2012 17 56 04 Owner Testert References 0 Type Upload Description Figure 201 Upload properties Upload a new file You have to activate the Upload button to open Figure 201 for specifying a special name and description Additionally owner creation date size the number of references and the type are displayed x iweb File EA Database EI Command EJ Manual Test Case Reference z res Figure 202 Hyperlink database Use an existing upload You have to activate tab database and press button create reference to uploaded file to open Figure 203 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 203 and Figure 202 Page 162 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi Uploads X Find Oooo OoOo O e a d e launcher properties Testmanager 14 02 2012 14 02 33 2 10 kByte logging properties Testmanager 14 02 2012 14 03 06 1 95 k Byte timpo 13293207502261 631 1329320750320 png Testmanager 15 02 2012 16 55 05 6 31 kByte timpo 13293207502261 631 1329520750320 png Testmanager 15 02 2012 16 45 50 6 31 kByte Mfirnport_1 3293207
272. o 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 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 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 Page 178 User Manual TEMPPO V6 1 Edition January 2014 Description of Use A searching direction can be chosen too The searching algorithm starts from the selected node in the tree Is the tree root selected the whole tree is searched whatever direction is selected 3 3 8 1 1Find Test Case Test Package There are three possibi
273. o 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 18 User Manual TEMPPO V6 1 Edition January 2014 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 F TEMPPO Testmanager Demo Notepad g ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import System Test 1 A Notepad RTF Import EE 1 Introduction HH 2 General description of the product General Attributes Details Requirements History Plan EF a 3 Detailed description of the required g a 5 1 Scope of delivery Document C temp Pfichtenheft_Notepad rtf S 3 2 Sequences scenarios of intel 3 3 User goals Mame Ala 3 4 Required functions of the prod eee 13 4 1 File Administration Chapter S411 Mew El 3 4 1 2 Open 0 3441 3 Save O 4 4 Exit Precondition 3 4 2 Edit Functions J Detailed description of al 4 4 4 Print Functions L Required functions oft 3 44 Search Functions o gt L 345
274. oduct E 3 1 scope of delivery Mame Fie Administration Ea 3 2 Sequences scenarios of interactions 2a 3 5 User goals Owner Tester Updator Testmanager 2 BAH 3 4 Required functions of the product Set 134 1 File Administration Created 16 02 2012 16 46 49 Updated 16 02 2012 11 28 57 EM S411 New E p 3 4 1 1 1 Mew file opened no i 3 4 41 2 New file opened ch Mumber of TOs 2 3 4 1 1 3 Mew Test Package c o M i Test Category my 3 44 2 Open hf R444 Save a Merge Lock Apply Dicar ey Type Test Package Figure 230 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 ws The only possibilty to make changes is to create a branch Do you want TEMPPO to create a branch for you Figure 231 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 bran
275. of interactions with the environment m User goals a Required functions of the product J File Administration Ea New Ti New file opened no changes El New file opened changes 2A Open Ea Save L Exit 4 J Edit Functions Print Functions Z Search Functions E E Find za Find up Dd Case sensitive sf TEMPPO Test Suite Generator lt lt Prev Next gt gt Cancel Figure 64 New Test structure pre selection whole test structure _ 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 nodes or subtrees 4 5 Enter test suite name l i Notepad RTF Import with TCs Determine the logical E Introduction a E General description of the product 6 Remove test cases manually P Detailed description of the required product features Z Scope of delivery fs Sequences scenarios of interactions with the environmert a User goals a Required functions of the product J File Administration Sioa New New file opened no changes D New file opened changes ga Open Ea Save Z Ext Edit Functions Print Functions a Search Functions SER Fino E By Find up Dd Case sensitive sf TEMPPO Test Suite Generator lt lt Prev Next gt gt Cancel Figure 65 New Test structure pre selection test packages Figure 6
276. oject Fiter C aner i sonia 2 ew Testmanager Testmanager H Al state ready te Testmanager i A Ad updated test ca Testmanager Testmanager 29 04 2013 13 00 33 F af f Testmanager Cancel _ Figure 244 Delete Filter After activating the Delete filter button the reconfirmation window comes up Do you reamy want to delete the selected fitter Figure 245 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 246 Filter deleted After deleting a filter the No filter is highlighted in the list box 3 3 13 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 192 User Manual Edition January 2014 TEMPPO V6 1 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 text 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 247 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
277. ol TEMPPO Test case Assign requirements eee o o allowed if user is TC editor ason test level_ __ test level X Px xL ff a tt TOE OPEREER rr Edit XXX _ XX Consider User concerns only the deleting _ _ Merge o if user is editor of e ee eet version TEMPPO Test suite Assign test suite attributes at SS IE EO is only allowed if test suite has no test Edit _ X xee merno h e es o S Import x S Remove from export database lock o O po lock items XX TEMPPO Test result Assign test result attributes xX X PP po eit XX implies Run automated and Set results multi Page 304 User Manual TEMPPO V6 1 Edition January 2014 Appendix Merge actual execution MERRET time X _TEMPPO Evaluation Analyse O OIX C TTS o o o o AnalysebybugiD SX FT ooo Creation progress SX T T T O o Execution progress X C T TS gt pi Personal report setting X XI x x x S O pi Project report setting X x x x x S O ert n Requirement analysis X J TEHPPO REKENEN Requirement e Export to XML xe ee po Import from XML po OpenX __ Requirement __ xX x pi Requirement Structure X_ po Spit dt E V Po Versions OX TEMPPO Others MultiSelection X po Copy XY poopy XY po EXport Import filter X po iter XX X xX XY New implies applying a filter __ po Order KY po Task ist XX XK po ersions XL XX Page 305 User Manual TEMPPO V6 1 Edition January 2014 App
278. oly Help Figure 288 QTP Run Settings 3 3 20 2 7 5 TestPartner TestPartner requires NET Framework 2 0 For Compuware TestPartner you have to activate the automation tab and select TestPartner Page 225 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Partner el User Interface gt Tree User name tamin Test Step Cell j E Password pe gt Analysis p Newsboard Database TestPartner_Oracle Test Suite Database Temporary Fath c tmp S El Test Automation i Silk Test Arqumerts Hin Runner Universal File H Universal Socket TEMPPO Designer DATS i Ranorex El Commands New Command VEZ El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults OK Cancel Figure 289 Settings TestPartner The meanings of the parameters are as follows 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 289 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 g Thi TestPartner from Compuware User Mame Admin Password SEE Data
279. on enough time to startup before retrying to open the socket connection This delay is 5 seconds per default 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 that it is not possible to launch an application on a remote computer without any additional software At port number the socket connection for automation will be opened 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 Page 223 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Arguments are the command line arguments for the automation application In the arguments parameters can be used for the configuration user defined id of test case Example Administrator configuration Arguments tc dbtcid ts dbtsid f file args 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 20 2 7 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 te
280. onding 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 jJunit swingui TestRunner TEMPPO Test Runner Return test result Call JUnit test method JUnit Framework Return calculated value Call method to test 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 281 User M Edition anual January 2014 TEMPPO V6 1 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 B a B BLOCKED 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 prog
281. ons Find Find up E Case sensitive not executed 4 2 3 4 Select nodes or subtrees 5 Enter test 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 Fi TEMPPO Testmanager Demo Notepad a ol x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version 72 REOS v1 1 1 Test object Version XYZ RCO W1 1 1 editable version 2 Test object Version XYZ ATOZ 1 1 1 editable version 3 ee Test abject 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 With the change of predecessors the settings of the current test suite can t be changed in common Now all results of on
282. ons Extension Test 5 Set test case default values 6 Summary a EJ test Running ErrorinTest Setup Deselect All u ae O test RunningErrors InTest Setup ioe O test Setup Error Dort Tear Down El test Setup Error InTest Setup eam junit tests extensions Active Test Test 3 3 E testActive Test O testActiveRepeatedTest vn E testActive Repeated Test0 2 O testActiveRepeatedTestt H E juni tests extensions Repested Test Test test ctive Repeated Testi junit tests extensions Active Test Test TEMFFO Extension JUnit zz Prev Ment gt Finizh Cancel Figure 354 Step 3 All or a subset of JUnit test cases can be selected Fi Import JUnit Tests X Steps Package Default Values Introduction Enter default values for the new test packages in TEMPPO 2 Select a JUnit test class 3 Select a set of JUnit test ener Details Cates 4 Set package default values Hame nenerated 5 Settes case default values 6 Summar Creator Testmanager Created generated Type Test Package Test Category a Description I Acted to description TEMPPO Extension JUnit lt e Prey Finish Cancel Fi Import JUnit Tests x Steps Package Default Values Introduction Enter default values for the new test packages in TEMPPO 2 Select a JUnit test class 3 Select a set of JUnit test ea Details Cates 4 Set package default values Document 5 Set test case default va
283. or 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 187 Fj Locked Items l x Locked Items Da tc57 Mew Test Case bcesos Mew Test Case 1 Figure 187 Locked Items If the button Discard is pressed all changes in all tabs will be discarded Page 156 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 1 6 Move Ownership Now the function move ownership can be applied for any number of selected test cases and test packages but the right has to be considered test New Test Package ff New Test Case Oi E D new b New Test p Find and Replace FS i Show Details Select All gre db Cut Ctrl X Copy Ctrl C amp Paste Ctrl X Delete Delete li Order gt ge Edit OS Refresh recursively ta Move Ownership orea Figure 189 Move ownership After the process moving the ownership a summary is shown see Figure 190 x 1 Mumber of tema with new owner 9 JJ Humber of locked tems 0 Humber of tems with identical owner 0 Figure 190 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 191 These items aren t changed Page 15 7 User Manual TEMPPO V6 1 Edition Janua
284. ork 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 S 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 By TEMPPO Manager temppo_um 5 Ioj x E Dasbase amp Users Ai migration O Wi X i Schema femppoum fatinz pr Ona Port ha n User fatwi12hg B Login manually hal Test User jtemppo_um Password ge Disconnect Database Mame Oracle Database Version Oracle Database 10g Enterprise Edition Release 10 2 0 3 0 Production With the Partitioning OLAP Data Mining and Real Application Testing options Figure 304 DB connect to create MS Window Login When pressing the button Connect Figure 303 is displayed A new super user can be created by clicking the button Create new user The input fields are explained in chapter 4 2 3 Page 236 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Manager Fj User properties x General
285. ort XML information TEMPPO identifies an XML file by a unique ID 3 3 16 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 S Import all test resus Figure 252 XML Import e Manually choose test results to import When activating this option Figure 253 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 Page 198 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Import only newe
286. ort ma Save Peers Files of type Microsc access Database mdi sA Cancel tf Figure 106 Save dialog If the export database already exists you get the following message Figure 107 Fileexists S we The file already exists Do you want ko overwrite it Figure 107 Overwrite file After successful export the test suite with activated root node looks as follows Project Test Structure Edit Test Execution Evaluation Took Windows Help Test Suite Version 2 of Test obeject RCO1 v2 1 1 l laj xj H d b H 4 E Mo fiter El 1 Mersion 2 of Test obeject REDI E 3 Detailed description of the required g General Details Export nfo Attributes Predecessor Plan Mame version 2 of Test obeject RCO Owner Testmanager Updator Testmanager Created 16 02 2012 15 53 31 Updated 16 02 2012 15 53 31 Type InclidedTPs 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 91 User Manual
287. orts all parameters 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 Page 221 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 20 2 7 2 Universal File Automation Interface For UFAI Universal File Automation Interface you have to activate the automation tab and select Universal File Settings X Universal File l User Interface Tree Drive Letter Ba S pw Test Step Cells 2 Analysis Error Path P pe p Newshoard S he Tast Suite l e R Databaze Result Fath C tmp S st Automation E Te 2 pe Silk Test Avi Faun ag niverse S H Universal Socket Quick Test Pro Test Danker ee Unit TEMPPO Designer IDATG H Ranorex F Commands 2 Mew Command Jeers El Change Management Bugzilla Clear Guest Telelogic Charge i JIRA M Upload result files to database Result Wiewer c iwinntinotepad exe Adapter temppo test tools adapters CDefautt uto ToolAdapter Arguments gt lt lt ResuitFiles gt 2 gt lt lt ErrorFiles gt her cal File D3 Restore Defaults OK Cancel Figure 285 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 possib
288. overed 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 201 User Manual TEMPPO V6 1 Edition January 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 2 Test suite successfully exported to Doors Figure 258 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 AT Cancel Figure 259 DOORS Export progress monitor The User is asked for confirmation then and if he confirms the export is stopped neel LY Do you really want to cancel the import process Figure 260 Doors Export confirm cancel 3 3 17 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
289. pad System Acceptance Test Owner Testmanager Updator Created 19 05 2010 14 03 04 Updated Type Test Structure SITEMPPO Designer DATS E Test level System Test a Description This test structure Figure 5 Test Structure Properties By clicking 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 13 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad i oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad System amp Acceptance Test System Test m pu E E x H gt b H Mo fiter oF aiNotepad System amp Acceptance Test General Plan Requirements Mame Notepad system amp Acceptance Test Daner Testmanager Updator Created 16 02 2012 13 26 40 Updated Type Test Structure TEMPPO Designer IDATG E Test level system Test hal Description This test 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
290. pened _ 1O SubusecaseNewaleadyopened H E Sub use case New completely new KD Subusecasel eweompletelynevy Use case File gt Open ie O UsecaseFileO pen CERIEL LESIE AGTasks Figure 377 Design Test Cases For Help press F1 Page 288 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Designer IDATG Mame Delay mSec Priority Ente names ss SCS eooo Poo Conditions Event Achone User Defined Fields Start window Destination window Browee Designators Commands for Test Script Description Input data New file name Enter name Expected Result Name entered Cancel Figure 378 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 Send or Save x Ph The data can now be transmitted to SITEMPPO Proceed Qn ae Yes Send data to SITEMPPO No Save data as XML File i Nein Abbrechen Figure 379 Save dialog It can be configured in settings for TEMPPO Designer If test structure is checked in with data of TEMPPO Designer The file used by TEMPPO
291. ported Page 255 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Fi Meta Data Editor ry xi Attributes Requirement Selected values 7 Attribute Find l Available values Figure 333 Requirement attributes With a double click on an attribute tab attributes the properties of the attribute are shown see Figure 334 It s not possible to change the requirement attribute because it s imported from DOORS or RequisitePro Page 256 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator Fi Properties of Property x General Details Property Created 14 02 2012 14 54 30 For Use of 7 Test Case Cuaner Testmanager Test Package Type Attribute T Test Suite Test Result m Requirement Description orea Figure 334 Properties of attribute 5 4 7 User Fields Fi TEMPPO Administrator Testmanager IOl x Database Roles E Users Metadata LA Projects B Locke License Test Levels By Test Categories od Attributes Uploads if 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 335 Metadata User Fields For test steps new columns can be defined for test structures and test suites When pressing the button New see Figure
292. 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 Pr 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 P 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 47 User Manual TEMPPO V6 1 Edition January 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 amp General Attributes Test Steps E Automation Requirements History Plan Execution History up Press Search Search phrase found and marked Search phrase found and marked Message Hugo not found 4 ES Press Search Figure 49 Test Case Test Step Editor With cut copy paste you copy or move one or more test steps via multi
293. 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 Page 261 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 5 5 7 Freeze Unfreeze ioi x Database G Roles E Users G Metadata LA Projects Lacks License DEX eo aAa H Demo Notepad Ee Example for versioning E Link test cases to requirements Ee Notepad generated o E notepad RTF Import O EM Notepad RTF Import with TCs R EM Test Suites for W1 1 2012 02 16 Fl editable version z Test object Version XYZ R001 16 02 2012 z Test object Version xY RCO2 16 02 2012 A Test object Version v2 RCOS 16 02 2012 i Test object Version V2 RCOS COPY 16 02 2012 O beg edabe version Ee Notepad System amp Acceptance Test A User documentation e Mew Test Structure Figure 343 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 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
294. r Created 27 06 2010 14 24 14 Updated 15 06 2071 09 26 16 Type G Manual Automated Test Case Test Goal lt Figure 273 Task due to deleted requirement Task lists can 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 210 User Manual TEMPPO V6 1 Edition January 2014 Description of Use DA TEMPPO Schlosser Dietmar ADIS Advanced Driving Information System Project Test Structure Edit Test Execution Evaluation Tools Windows Help Sy oS Sr SSO 7 5 Ss jon z r 7 A ZER a Task ists ADIS P ase 1 0 E oro eP gt aS ADIS reg gt V 2 New Requirement New route requirement x Delete task list Delete tc41002 Blue displayed route contains white arrows after ez ti tc41716 Blue displayed route contains white arrows after e lt Export tc41717 Blue displayed route contains white arrows after each manoever General Name ADIS requirements Advanced Driving Information System V1 gt V2 Created 27 08 2010 Version update V1 gt V2 Figure 274 Task List 3 3 20Settings TEMPPO differs between global and application specific settings
295. r each priority grouped by the state x Gi Chart E pata Test Cases M Axis State Group by WAE Chart vertical Bar Chart ag 20 r 60 50 30 20 10 Designed In Work Ready Ready for Review state Meilenstein 11 Bi Bis wos Bie none coe Figure 114 Test Structure Analysis x Test Results M AXIS Resut 50 Group by Result 70 hart vertical Bar Chart 60 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 not implemented Son hold E passed oss 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 95 User Manual TEMPPO V6 1 Edition January 2014 Description of Use E Analysis j E E i F FEH a a Resut Coverage kd Teaca o stacked vertical Bar chart GD 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 96 User Manual TEMPPO V6 1 r z C art E pata EI Group by
296. r 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 i x Test Suite in XML File Test Suite in Master Database v New Test Suite New Test Suite E M A Detailed description of the required product features L Detailed description of the required product features E M Required functions of the product He Required functions of the product E M lt 4 File Administration FJ File Administration E O Sa New EN New O Gd new file opened no changes E New file opened no changes O BB new file opened changes 31 01 2004 13 27 10 W New file opened changes 27 01 2004 13 27 10 Fuchs Clemens lt 4 Open 4 Open E Open normal 26 01 2004 13 27 14 E Open normal 27 01 2004 13 27 14 Fuchs Clemens f l j Open file opened changes 27 01 2004 13 27 18 lt a Save v Dd Save fil Save Save as 27 01 2004 13 27 25 f Save as 27 01 2004 13 27 25 Fuchs Clemens SM Ext Crea
297. ram 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 282 User Manual TEMPPO V6 1 Edition January 2014 JUnit Table 4 Possible test execution results Ei TEMPPO atwi08s2 JUnit extension tests ojx Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Sample JUnit execution 1 1 1 rar ALD Sarpe Jind execution Ar unt Tests ard samples Vector Test GB testCapactyjurt samples VectorTest OB testCortanciurd samples Vector Test E testElementatiuna samples Vector Test WB tectRemcvellemert urd samples Vecto E testCioneQund samples VectorTest pa User Defined E teig A lesRemove Aju sampes VectorTest athe cerol juni tampia mongey Morey esi taedd SE pri sompies MoneyTest Owner aby OGs2 E testBaghutipty unt samples money Mor Crested 10 12 2002 14 71 01 BB
298. raphical way It is possible to add more charts to your report by right zE Add new chart mouse click on chart and activate Add new chart By ie gt R selecting a Chart right mouse click and activating Remove E 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 Bar 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
299. rate test cases Iw Import test goal Fixed test step columns Atest case is identified by a table with following headers Iv Instruction Jinstruction m Input Input m Expected Expected r Ignore empty table rows do not create empty test steps User defined test step columns Comment E Expected image DK 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 t
300. recondition 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 amp 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 details 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 30 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad oo IE Project Test Structure Edit Test Execution Evaluation Tools Windows Help lest Structure Notepad RTF Import with Teel System Test vi i d p H g E Mo titer ALI Notep
301. red o oleneda a title bare A 34 1 2 0penf FE ao 34 1 54S5ave a a 34 1 45 Exit a t 2 4 2 Edit Functions 342 1 Undof a a 342 24Cut a 342 54Copy4 a 34 2 44Pastel e 34 2 5 Deletef a 34 2 6 Select Al 34 2 74Time Datef a 34 2 84VVord Vyrap G a 3429 5etFonti ee ee gt Zeichnen Le AutoFormen t Ne 7 O E a As E a lt P Oa prne Lal ae Seite 11 ab 3 11 19 Bei 35 7pi Ze 17 Sp MAK AND ERW B Ended us G 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 20 User Manual TEMPPO V6 1 xi Document JC ctemp Piichtenhet_Motepad withT Cott 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 W Generate test cases r Import test goal Fixed test step columna Atest case is identified by a table with following headers M Instruction Jaction E Input input r Expected Output m Ignore empty table rows do not create empty test steps User defined test step columna T Comment IY Action image Jaction image DK 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 ca
302. red functions of the pre E341 File Administration E 5 3 4 1 1 New General Attributes Test Steps EE iometon Requirements History Plan Execution History pats diii a Datei Bearbeiten Format Ansicht t Ve Strg h ffnen Strg 0 Speichern Strg 5 E Speichern unter Seite einrichten 5 Drucken Strg F ni fs 3 4112 New w fleo ol 3 4 1 2 Open 3 4 1 3 Save Do blll 3414 Exit E 3 4 2 Edit Functions o E 3 4 3 Print Functions Eb 3 4 4 Search Functions AAN 3 4 4 1 Find ee amp 3 4 4141 Find up fi 3441141 Case lf 3 4 4 1 41 2 Quicl pa rs 3 4 4 1 2 Find down 3 4 4 2 Replace 3 4 6 Help System BAN 3 5 External interfaces of the pri ii IP Beenden a x 4 Untitled Notepad in title bar Upload X Delete B 3 6 1 User interfaces rat ae _ Bs Fa BB Cor paste mage ooe ary ocea Reference R 5 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 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 th
303. ress export locks amp Unlock selected elements H Demo Notepad e Example for versioning Demo Not Notepad v2 44 editable v Test Pac Performa tp562 export dat 20 02 201 a in gt voll aa Demo Not Notepad W244 editable v Test Pac Resource tp563 export dat 20 02 201 Notepad RTF Import Demo Not Notepad V2 1 1 editable v Test Pac Systemin tp560 export dat 20 02 201 Demo Not Notepad V2 1 editable v Test Pac Other pro tp561 export dat 20 02 201 Demo Not Notepad W211 editable w Test Pac Externali tp558 export dat 20 02 201 Demo Not Notepad v2 1 1 editable v Test Pac User inter tp559 export dat 20 02 201 Demo Not Notepad W211 editable v Test Case Test Part tc702 export dat 20 02 201 Demo Not Notepad Version ae ed editable v Test Suite Version 2 export dat 20 02 201 Demo Not Notepad W2 1 1 editable v Test Case UAI tc7O3 export dat 20 02 201 Demo Not Notepad W211 editable v Test Case WinRunn tc701 export dat 20 02 201 J 1 editable version I Notepad RTF Import with TCs 1 E 2 41 Test Suites for V2 1 20124 El editable version i g Version 2 of T 2 Branch J editable version ee Notepad System amp Acceptance T Demo Not Notepad W211 editabl
304. ries 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 Bmore ownership to X atw112h9 Tester tester testers tester4 testers testerB tester Testmanager temppo_um Figure 320 Move Ownership The new owner of the metadata can be chosen 5 4 2 Test Levels Here you can add delete view and filter test levels In Figure 321 all test levels are displayed with name owner and creation date Page 248 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 21 02 2001 00 00 00 21 02 2001 00 00 00 21 02 2001 00 00 00 IFC Regression Test i 21 02 2001 00 00 00 System Test 21 02 2001 00 00 00 Figure 321 Metadata Test Levels A new test level can be added by pressing the button New in the tab Test levels and Figure 322 is displayed Fi Properties of New Entry 4 8 Fi Properties of New Entry X General Details General Details _ Sub system test Created 20 02 2012 15 14 46 Owner Testmanager Type Test Level Description Cancel Can
305. rizontal Bar Chart bd Test Cases Sort Requirement name 1 alphabetical Requirement name 10 ascending descending Requirement name 11 Requirement name 12 Values Requirement name 13 C all C Only zero values Requirement name 14 No zero values Requirement name 17 Coverage Average number of TC s per requirement 8 00 TC s Requirement name 18 Requirement name 19 Percentage of requirements covered by TC s 100 00 Requirement name 2 Requirement name 20 Requirement name 21 cu Figure 119 Test Structure Requirement Analysis Page 99 TEMPPO V6 1 Description of Use User Manual Edition January 2014 B Requirement Analysis Demo Requirement structure Stacked Horizontal Bar Chart 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 Requirement name 31 Donitiramant mama 27 Figure 120 Test Structure Requirement Analysis Data Fi Requirement Analysis Demo Requirement structure Stacked Horizontal Bar Chart v Requirement name 1 tc13442 tc13443 tc13444 Requirement name 10 tc13543 t
306. rt 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 customized By pressing the button Save As the chart can be saved as jpg or png file Page 103 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi Test Creation Progress _ x chert E Data Select Test Structures Chart Line Chart x Orientation horizontal e vertical Test Gases absolute relative States IY Designed IY In work 1 1 v7 Me ike S x IY Ready tor Review Test Structures V Ready States E pesigned E in Wok Ready for Review C Ready Approvect Representation o Figure 126 Test Creation Progress Fi Select Test Structures 4 E x H5 Tests Linz reviewed i Tree style L igtest Hest _igtest Bg nl ee JG 2 VOTO 002 0007 HG Tests Linz fatest cM wWilestone 16 Wien Testcases latest a Branch ascendin EhHhleilenstein IE Wien fate st Saved by Opala H NWavilap post l6 tests fate st Branch ost IE _Igtest ranch Versions only Labels only Versions and Labels ClearCase style Order C descending Branch EHO Tests Linz latest Branch EHO Wien _jate st Figure 127 Select Test Structures 3 1 5 5 2Execution Progress There are 3
307. ry 2014 Description of Use Fi Locked Items x Locked Items kaSr Mew Test Case bceos Mew Test Case 1 Figure 191 Locked Items 3 3 1 7 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 ha ai js r Li i New Test Package Gl i cea H He C Mew ETN f F Dal fe Find and Replace F3 a Show Details j Select All B Tree at Cue Ctrl Copy Ctrl C Paste Ctrl V Order Edit Refresh recursively fa Move Ownership Analvse selected b E Report selected Figure 192 Context menu delete x YD Do you really want to delete these tems Figure 193 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 194 Page 158 User Manual TEMPPO V6 1 Edition January 2014 Description of Use x kaSr Mew Test Case bceos Mew Test Case 1 Figure 194 Locked Items 3 3 1 8 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 195 and afterwards Figure 196 is shown 4 4 rF A y Jes No riter eal e New Test Suite Tamu cm New Test Pack
308. s create a new latest version that is identical with your branch wersion Do you want to proceed Figure 233 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 185 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test W2 2 7 x WW b amp b HW E Mo fitter ALI Notepad RTF Import with TCs FA 1 Introduction aa 2 General description of the product 3 Detailed description of the required product f T 3 1 Scope of delivery A _ 3 2 Sequences scenarios of interactions v Res 3 3 User goals Ba 3 4 Required functions of the product EL 34 1 File Administration A 3 4 1 1 New A 3 4 1 1 1 New file opened no c fi 3 4 1 1 2 Mew file opened char l os 3 4 1 1 3 New Test Package on PB bw E 2 411 341 New Test Case i belag Onen Ra Merge Lock Apply Discard bot Figure 234 Test case merge If working on a br
309. s updated Page 195 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Attributes E Attribute inheritance Requirements Requirement inheritance Test Steps Figure 249 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 15 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 reordered it keeps the new order but neither Updated nor Updator is written Changed TCs Detected changes Name test goal attributes planning attributes f
310. scription of Use 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 est St ad RT M 4 gt y xj iaia y Notepad RTF Import with TCs E E 1 Introduction e 2 TEMPPO Designer IDATG Tas fm 2 1 Use case File gt New General Attributes Test Steps EI st Requirements History Pian Execution History ra 3 General description of the produc A m 0 3 4 Relationship with existing pi 4 3 2 Relationship with earlier anc Date User Property Action C 3 3 Purpose of the product 20 02 2012 10 26 57 Testmanager General change _ E 3 4 Defimitation and embedding 20 02 2012 10 26 57 Testmanager Steps add 20 02 2012 10 53 04 Testmanager Steps change 20 02 2012 10 56 57 Testmanager penera change UDA E 3 5 Overview of the required fu i 3 C 3 6 General restrictions p ae 3 7 Hardware and software spe __ 013 8 Product users 07 03 2012 14 51 01 8 4 Detaled description of the require Windows 7 E 4 1 Scope of delivery 07 03 2012 14 51 01 Testmanager Test Level Acceptance Test add p oe A 4 2 Sequences scenarios of i 07 03 2012 14 51 01 Testmanager Test Level System Test add p 4 3
311. se template activated Test Case template vald only for new and updated test cases except viewed test cases Requirements eiaq E ne roguenent mite assed Figure 215 Test Case Template Requirement Page 171 User Manual TEMPPO V6 1 Edition January 2014 Description of Use General Plan Requirements Template Attributes Test Case template Test Resuit template V Test Case template activated V Test Case template valid only for new and updated test cases except viewed test cases General Attributes Test Steps Requirements Pian Plan Planned tester No Pianned tester Pianned test execution time 0 2S ee eee Figure 216 Test Case Template Plan 3 3 3 1 1Create new test case If a TCT is activated and a new test case is created the values of TCT are applied e fixed attributes are set automatically e UDAs with default values but without ticked checkbox Mandatory are assigned automatically e inheritance flag of requirements is de activated e inheritance flag of UDAs is de activated e 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 214 Test Case Template Test Step is ticked e
312. 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 Ctri gt C and lt Ctri 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 Input w Expected Figure 50 Context menu for column hiding displaying 3 1 3 1 3Test Creation Assistant When pressing Er 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 48 User Manual TEMPPO V6 1 Edition January 2014 Description of Use F Test creation assistant X Navigation main meni Instruction Input i st data Men points Destination memory Destination entry Last destination POls are offered Sk TMG Sk4 Mode SsKo Settings Bales Expected eres 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 stop 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
313. ser E Switches anvoff to lock the whole test structure betore 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 onioff to check if the entire test suite is unlocked before exporting Locking Made Locking mode in test structure and test suite i automatic C manual History f 0 Number of history records 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 x Unlock selected el t Locked by Detailed description of the required product features User Super 23 05 2006 16 13 33 Wt Exit Yes file open changes nna 23 05 2006 15 53 55 Mo New file opened changes nnz 23 05 2006 15 53 37 ai Nev file opened no changes nrn 23 05 2006 15 53 07 New 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 135 User Manual TEMPPO V6 1 Edition January 2014 Description of Use e Test structure When activat
314. ser Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 18Test Suite Scheduler Manual test cases are executed sequential but executing automated test cases it is insufficient to do it in a sequential way Therefore TEMPPO provides a feature to schedule automated test cases A scheduler includes general information a start time and an ordered selection of test cases which has to be executed For each test suite several schedulers can be defined The test suite has to be opened and tab Scheduler has to be activated SSS fo Le es Test Suite Tes M No fiter estsuite Scheduler E 2 1 Create Player not executed EJ 2 2 Create Player 1 not executed E 2 3 Edit Person not executed General Detais Export info Attributes Predecessor Plan Scheduler BJ i El 2 4 Record_test not executed Name Owner Created Updated Updator Host Scheduler Star EJ 2 5 Record_test 1 not executed EJ 2 6 Record_test 2 not executed Es E 2 7 Record_test 3 not executed x E 2 8 UniversalFile not executed i E 2 9 New Test Case not executed Figure 263 Test Suite Scheduler With the buttons on the right side you can manage and run schedulers e Create Edit a scheduler Define a scheduler with start time and a sequence of test cases see 3 3 18 1 e Delete a scheduler Remove a scheduler for a test suite see 3 3 18 2 e Import
315. ses 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 Additionally the paragraph after the heading which should become a test case must contain a test step table This table must contain columns which describe tnstruction 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 21 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Please consider that importing is applied on the selected test package 10 xi Project Test Structure Edit Test
316. sh button to get the latest news Page 180 User Manual TEMPPO V6 1 Edition January 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 f ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Mewsboard Notepad RTF Import with TCs 3 BE Updated 20 0
317. st cases to remote 2 Select a JUnit tect class 3 Select new JUnit test tases t test i 4 Select obsoltete TEMPPO test cases Set package default values Sel bert cone default values 7 Summar m h TEMPRO Extension Panama lt lt Prev Next gt Tr Figure 366 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 A Update JUnit Tests x 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 General Detaas 4 Select obsolete TEMPPO test cases Nar 5 Set package default values Set test case default values Owner jatw108s2 7 Summary Test Package Test Category Description is description applies to all new JUnit test suites V Add description Updated by TEMPPO from JUnit Suite TEMPPO Extension Panama lt lt Prev Next gt gt Fish Cancel Figure 367 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 tert class 1 Review your settings 2 3 Select new JUnit test cares fou choose to update the TEMPPFO test package 4 S Select obsolete TEM
318. st 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 implementation 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 JaK Implementation of adapter for universial automation interface ne 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 mee result IResult FAILED else if line egquals Result PASSED mee result IResult PASSED Page 307
319. structure dtd gt lt TEMPPO_EXCHANGE gt lt TP name HumanResources gt lt TC name Search_T1 test_goal Transition Test situation Error gt lt STEP instruction inout expected gt lt USR_FIELD name Actor value Sean 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 50 User Manual TEMPPO V6 1 Edition January 2014 Description of Use lt STEP instruction inout expected gt lt USR_FIELD name Actor value Sean 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 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 i i Ee ioj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test 1 E je x 44 gt WwW EE no fiter y gt Notepad RTF Import with TCs 31 Introduction E J 2 General description of the product a dz 3 Detailed description of the requiret E 3 1 Scope of delivery S 3 2 Sequences scenarios of in 3 3 User goals BAN 3 4 Requi
320. t be 34 Scope of delivery pe A 3 2 Sequences cenarios of interactions BE 03 3 User goals a a 3 4 Required functions of the product 3 4 1 File Administration E Ep a 3 4 44 Windows Login Newpi Editor Pane cleared in El 41141 Login Untitled Notepad in title bar gi 3 4 4 2 New Hi 344 22 Mew e obris am fl 3 41 23 New Test Package c asi 93 4413 Open pov a 3 4 1 4 Save 3 4 1 5 Exit 5 3 4 2 Edit Functions 3 4 3 Print Functions Bh EE 3 4 4 Search Functions Ea 3 4 6 neig E ai See mrn Figure 209 Referenced Test case ID If you click on the hyperlink the destination test cases is selected automatically Additionally a Back button see Figure 210 is shown to return to the source test case Page 166 User Manual Edition January 2014 F TEMPPO Testmanager Demo Notepad TEMPPO V6 1 Description of Use Project Test Structure Edit Test Execution Evaluation Tools Windows Help lest Structure Notepad RTF Import with TCs Systerm Test m3 H 4 P H 4h E Mo fitter E H Notepad RTF Import with TCs a Bl 1 Introduction Bt 2 General description of the product Bia 3 Detailed description of the required product ane E 3 1 Scope of delivery 3 2 Sequences scenarios of interactions g 3 3 User goala A a 3 4 Required functions of the product EDA 3 41 File Administration OO EBM S414 Windows Login Bin te 3 4 4 14 Login A
321. t Case Type Validation F Miesione IN IMT 2 MTN S MJ AND Additonal test level Acceptance Test AND Planned tester nni AND Reg State Implemented AND Test Case Type Vaidation _ Hide Empty Subtrees Figure 248 Filter criterion 3 3 13 6 Edit filter criterion You delete and add lines of filter criterion When pressing the button e the current line is deleted b3 a line is inserted before the current one Page 194 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 3 3 13 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 3 3 13 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 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 sho
322. t 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 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 k 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 24 User Manual TEMPPO V6 1 Edition January 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
323. t 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 67 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard E x Steps Select Test Suite Introduction Select an existing Test Suite Choose creation mode Select an existing Test Suite Notepad RTF Import with TCs Ew 4 2 3 4 Select nodes or subtrees 5 Entertest suite name 6 Determine the logical expression V11 Test Suites for V1 1 2012 02 16 f v1 1 1 editable version 7 Remove test cases manually Test object Version XYZ RC01 16 02 2012 V2 editable version TEMPPO Test Suite Generator lt lt Prey Next gt gt Figure 74 Select a test suite Cancel 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 i i x Steps Test structure pre selection Introduction Select test packages hold lt STRG gt and lt Shift gt for mutti select Choose creation mode Select an existing Test Suite Select nodes or subtrees Notepad RTF Import
324. t name chapter Page 32 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Help FRE e Test Structure Notepad RTF Import with TEs Sistem Test wt ALI Notepad RTF Import with TCs 31 Introduction E 2 General description of the product E 8 3 Detailed description of the required pr ee 3 1 Scope of delivery a al 3 2 Sequences scenarios of intere rS Ea 3 3 User goals 5i re 3 4 Required functions of the produ 3 4 4 File Administration 34 2 Edt Functions E 33 4 3 Print Functions 3 4 4 Search Functions Sop ni 134 44 Find General Attributes Details Requirements History Plan Document S Mame Chapter Precondition Precondition Detailed description ofthe requir 00 J External interfaces of the product User interfaces Editor Pane po be D 3 4 4 2 Replace me i 3 4 5 Help System So 3 5 External interfaces of the produ B i 3 6 1 User interfaces meee 8s 0 1 1 Editor Pane 3 6 1 2 Search Dialog ke de Be Z 35 2 System interfaces B 3 6 Other product features required 1 Performance 2 Resource 3 Security 4 Safety 5 Portability 6 Reliability Maintenance 6 8 Reuse fl 3 6 9 Usability FA HA 4 snecticatinns for orniert ae F
325. t object Version v2 REIS COPY pA H 4 e H of E Mo fiter i Test object Version v2 ROOS COPY 5 3 Detailed description of the required g ca 344 Required functions of the prod Ed 3 4 1 File Administration BA 3 4 1 1 New Et al 3 4 4 Search Functions Elid 3 4 4 1 Find EH 3 4 4 1 1 Find up mo ris441441 Cases 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 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 item Show Details is deactivated 4 eve Find and Replace F3 Show Details Select All t Tree Topy Ctrl He i Paste Etrit Toa Cadet Edit u 05 Refresh recursively Ta Move Ownership E Report selected Figure 175 Show Details Page 144 User Manual TEMPPO V6 1 Edition January 2014 Description of Use oi x Project Test Structure Edit Test Execution Evaluation Tools win
326. t 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 o myResults res e myErrors err Page 57 User Manual TEMPPO V6 1 Edition January 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 LE fA 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 which even allows you to copy or move around complete test structure sub trees By using
327. tarted 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 specific 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 20 2 9 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
328. te is lost and a later update won t work properly Page 273 User Manual TEMPPO V6 1 Edition January 2014 JUnit Fi TEMPPO Testmanager Demo Notepad i joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure JUnit System Test W1 S 1 Framework Tests a 1 1 junit tests extensions Extension Test General Attributes Details Requirements History Plan aly 1 1 1 test Running Error In Test Setup junit t hg 1 1 2 test Setup Error In Test Setup junit tes ID p783 El a 2 junt tests extensions Active Test Test ay 2 1 testActive Test junit tests extension soy 12 2 testActiveRepestedTest0 junit tests Mame junit tests extensions Extension Test 1 3 junit tests extensions Repeated Test Test why 1 3 1 test Repeated Once junit tests exten aly 1 3 2 test Repeated More Than Once junit t Created 20 02 2012 15 57 727 Updated 20 07 2012 15 57 728 ay 1 3 3 test RepestedZera junit tests extens iJ 1 3 4 test Repeated Negative junt tests ex Owner Testmanager Updator Testmanager Type Test Package Humber of TCs 2 Test Category ar Description pnported by TEMPPO from JUnit Suite junit tests extensions AllTests Lock Apply Pizcand Figure 359 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
329. te scripts for other 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 F TEMPPO Testmanager Demo Notepad 1 Project Test Structure Edt Test Execution Evaluation Toole Windows Help IO x e Test Structure Motepad RTF Import with TCs System Test 13 l z x E im Motepad RTF Import with TCs E 1 TEMFPO Designer DATO Tasks I 2 Introduction General Plan Requirements H 3 General description of the product i 4 Detailed description of the required product teat Hame Notepad RTF Import with TCs H 5 Specifications for project management 6 Obligations of the client Owner Testmanager Updaetor Testmanager 7 Literature Lal 8 Annexe Created 16 02 2012 16 36 29 Updated 20 02 2012 16 40 10 Type Test Structure TEMPPO Designer CATG m Test lewel System Test of Description Lock Apply Discard Figure 372 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 285 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Designer IDATG 7 1 Creating Task Packages T
330. te 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 55 User Manual TEMPPO V6 1 Edition January 2014 Description of Use EE jj x Should the following attributes of the existing test structure be retained during the update process E Attribute inhertance C 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 have to set some ge
331. tes suite selection Page 125 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Test Result IN faled passed not implemented blocked AND Req_Type Header AND Priority High ok _ canos W Figure 148 Report of several test suites Filter Page 126 User Manual TEMPPO V6 1 Edition January 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 RCO V2 1 1 Figure 149 Reported information ate Bs i aa ee ee 2 TN LA TEMPPO report setting in project Demo Notepad i x J Name NewReportSetting Select Test Suites Companeras a SEneral es E Text V General Information of Report Tabular Report F General Information of Test Suites E Charts I E Charts Layout Continuous Tabular Format HTML Microsoft Word C Microsoft Excel Co cancel 7 E Figure 150 Report of several test suites General Page 127 User Manual TEMPPO V6 1 Edition January 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 g
332. tes are expected 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 283 User Manual TEMPPO V6 1 Edition January 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 c
333. 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 also Figure 7 F Select Requirement Structure l A New Requirement Str E 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 14 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi Test Structure Properties xj General Mame New Requirement Structure added Owner Testmanager Updator Created 19 05 2010 14 06 10 Updated Type Test Structure SITEMPPO Designer DAT E Test lewel MGE Description ore 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 d Joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Motepad generated System Test v1
334. test packages 3 1 2 3 1Adding 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 Therefore 2 sub test packages are necessary that refer to these requirements Ei TEMPPO Testmanager Demo Notepad 2 Oj x Project Test Structure Edit Test Execution Evaluation Toole Windows Help e Test Structure Notep Test Package Ctrl Alt T H d b Wt Find and Replace 8 Test Package before H Test Case Ctrl 4h C 2 Notepad RTF Irr s ile show Details Gl Test Case before F241 Introductior Select All Ctrl 4 4 General de es Details Requirements History Plan EHIH 3 Detailed de i H i LS Scopi nee i ipts Compare a 332 Segu oo bel 3 3 User ey 3 4 Requ dh Cut Ctra E Search Functions o H 3 4 1 ES copy Ctrl c oa 34 2 E Faste irit oOo B aa N 15 02 2012 16 28 59 Updated 16 02 2012 08 12 20 it SE a Faste betore aas GG 3 5 Exter BO AL 3 6 Other o E al 4 Specificatia E 5 Obligations l a 6 Literature 7 Annex i Edit Fitter gt Test
335. testBaghegate und samples money Mor E testBagSimpleAddiunt samples money pim oa i ak Tester atwiO s E testBegSumAdajund samples money Wi Type Test Result _ Fe ta Rest MccedtSimnple Add jund camples Resut Guipa junit framework AssectionFailedErccoc E testMoneyGagtquals junt samples mors E tectnoneySagHash pind samples more E tesiMoneyEquals und samples money W A tesiMoneyHashiuni samples money Mo A bestNormnealne Ajun samples money Mor tA lesihormakre Njuna samples money Mor BD te sthcematzes pund snenpdes money Mor Oo testPrintijund samples money MoneyTes Test Goat E te stSunpieAdajund samples money Mon E testSirnpieBagAddjund samples money BB testSinplemutpty jund samples money A E testSimpietegate junt samples money I BD test SirpieSuttract und samples money GB testSrrpityQund samples money Money at junit samples money HoneyTest testIa zero MoneyTest java 54 brt sun reflect NativeMethodAccessorInpl invoke Native Method at sun reflect NativelethodAccessorInpl invoke NativeNethodAcces at sun reflect DelegatingMethodAccessorInpl invoke DelegatingMeti Gt t scch panana junittool TestRumn er dokun Unknown Source of b Figure 371 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 sui
336. th E s 3 5 ik iii laea bFer 3 54 2 ah Diak on 3 6 2 System interfaces w b Lock Apply Discard I 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 easy 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 full
337. the export database Page 92 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Ei Open Test Suites X Notepad ATF Import with TCs Tree style Bea Versions only El Test Suites for v1 1 2012 02 16 Fl editable version bn Test object Version XYZ RCO 16 02 2012 Versions and Labels Labels only Test object Version lt 2 RCO 16 02 2012 ClearCase style A Test object Version XYZ COS 16 02 2042 a e Test object Version 2 RCOS COPY 16 02 2012 Order Bez EM Test Suites for V2 1 2012 02 16 ascending EHE 1 editable version A Version 2 of Test sbeject ACO 18 07 2092 2 descending 9 editable version 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 Randle conflicting test results during import Aye cm ek 18 ea sn e Eg oh eT A Import all test results Manually choose test results to import cmos
338. the prior versions items are not available of course see Figure 230 You can see the active version of your test structure in the title bar of the test structure explorer Page 183 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad E jol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test u3 92 8 Product users M a 3 Detailed description of the required product Ld 3 1 Scope of delivery General Attributes Test Steps E automotion Requirements History Plan Execution History 3 2 Sequences scenarios _ SS Ea 3 3 User goals oa Expected Enter accountin test domain and Login successtul E l f matt wi password i E 3 4 1 2 1 New file opened no fi 3 4 1 2 2 New file opened ch of BY E 3 4 1 2 3 Mew Test Package c i 3 4 1 3 Open cl dd A Sawe aE Lock Apply Discard Figure 229 New items in latest structure version Fi TEMPPO Testmanager Demo Notepad io xj Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test Puz d Notepad RTF Import with TCs EHL 1 Introduction EHL 2 General description of the product General Attributes Details Requirements History Plan a 3 Detailed description of the required pr
339. tings TEMPPO Designer IDATG e Application path Path to IDATG exe e Connection time out Time for connecting successfully with TEMPPO Designer IDATG Page 227 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 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 wait for an answer on a ping heart beat e Ping repeats Number of pings heart beats sent to TEMPPO Designer IDATG 3 3 20 2 10 Ranorex e Result path Path to directory of the result file s e Result viewer Application to open result file s El User Interface Tree Test Step Cells Analysis H Newsboard Test Suite Result Path Ctmp S Resu viewer C Program Files WhtraEdmwedits2 exe El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H QuickTest Pro Test Partner JUnit be TEMPPO Designer IDATG SOP ex Fl Commands Men Command MSE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults OK Cancel Figure 293 Settings Ranorex 3 3 20 2 11 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 294 Then a new tree node is created with the new command see Figure 295 A
340. tioning 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 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
341. 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 Doors requirements could be found in the active test suite Figure 255 Information Message If there are linked requirements the user is guided through the wizard Page 200 User Manual TEMPPO V6 1 Edition January 2014 Description of Use LA Export of Testsuite Sheps Export requirement data to a RM tool 1 Introduction This wizard assists you to export requirement data to 4 provided RM tool 2 Export of Testsuite affected modules baselines Crees rh Ceara Figure 256 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 m E 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 corresponding requirements will not be exported importer 4 0 Figure 257 Export Wizard step 2 Results for found modules will be exported results for not found modules will be skipped If a requirement is c
342. to requirement relation is evident every time This enables the test responsible to easily verify which requirements are covered by test cases Page 16 User Manual TEMPPO V6 1 Edition January 2014 Description of Use 1 II iii ik E e gt La Pi m ll iil Iil e product Seitenwechsel ee0 DRD 34 1 14Ne 34 1 240pe 14 1 4d 5ave 4 1 44Exit 3 4 24Edit Functions 34 2 14Undoj 3 4 27 24Cut 14 2 d4Copy i 14 2 44Paste 3 4 2 64Delete 3 4 2 6aSelect AI 3 4 2 7 lime Daten 34 2 84VVord VVrap 3 4 2 945et Font 3 4 34Print Functions o 34 9 14Page Setup a 34 39 24Print 3 4 44Search Functions o 344 1 FReplace oa 344 24Find 7 AE Ca De he ee Figure 12 Sample Software Requirements Specification for MS Notepad Sin i 4 Mo ooo 2 4 co co m m SASENATESS 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 17 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi Import Settings X Document tempi Pichtenhet_MNotepad rtf V Generate document path Heading Mask Heading Limit test structure depth to f Generate numbers and start with f V Generate test packages Jw Import description IW Gene
343. 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 bere act Demo Not Notepad W2 1 1 editable v Test Pac Delete tp546 export dat 20 02 201 g Notepad System amp Acceptance T Demo Not Notepad W211 editable v Test Pac Word Wrap tp549 export dat 20 02 201 A User documentation bd Demo Not Notepad W211 editable v Test Pac Time Date tp546 export dat 20 02 201 gt Demo Not Notepad W211 editable w Test Pac Cut tn543 export dat 20 02 201 E Figure 345 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 Page 263 User Manual TEMPPO V6 1 Edition January 2014 TEMPPO Administrator 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 Bj TEMPPO Administrator Testmanager i Oj x z Database e Roles f Users Metadata Al Projects By Locks Ea License A ey I Exclude test suites J Supp
344. tructure 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 219 User Manual TEMPPO V6 1 Edition January 2014 Description of Use el User Interface H Tree Test Step Cells Analysis H Newsboard Test Suite Database El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H QuickTest Pro Test Partner TEMPPO Designer IDATG i Ranorex Fl Commands ElChange Management Figure 283 Settings Database 3 3 20 2 7 Test Automation 3 3 20 2 7 1 WinRunner and SilkTest Page 220 User Manual TEMPPO V6 1 Edition January 2014 Description of Use settings eee x Silk Test l User Interface E Tree Application Fath cAProgram Files Seque Silk Testipartner exe Test Step Cells analysis Temporary Path C ADocuments and Settings H Newsboard he Test Suite Resut Path CADocuments and Settings Result viewer C nctepad exe Argues q resexport lt lt TestFile gt gt Universal File H Universal Socket H Quick Test Pro Test Partner bs TEMPPO Designer IDATG i Ranorex El Commands New Command SE El Change Management Bugzilla Clear Quest Telelogic Change delete temporary test automation files Restore Defaults OK Cancel Figure 284 Test Automation SilkTest WinRunner If you plan to manage automated test cases in TEMPPO
345. ts 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 215 User Manual TEMPPO V6 1 Edition January 2014 Description of Use el User Interface p Tree Test Step Cells be MHewsboard Test Suite Database El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H QuickTest Pro Test Partner TEMPPO Designer IDATG i Ranorex El Commands ee New Command fe dawad2 El Change Management Bugzilla Clear Quest Telelagic Change Figure 280 Settings Analysis 3 3 20 2 4 Newsboard You can configure if Newsboard window is automatically opened if a test structure is opened Page 216 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Newsboard User Interface start automatic Test step Cells Display Newsboard automatically when opening a test structure Analysis 3 ae ew sboarcd Test Suite Database El Test Automation Silk Test WinRunner H Universal File Universal Socket QuickTest Pra Test Partner JUnit TEMPPO Designer DATS i RAnorex E Commands Mew Command L Javaz2 El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Figure 281 Settings
346. uct EL 3 41 File Administration EMS 3 4 11 New o fi 3 4 1 1 1 New file opened no fil 3 4 1 41 2 New file opened che E 3 4 1 2 Open 3344 3 Save L414 Exit 3 4 2 Edit Functions Bg i i EH 3 4 3 Print Functions ka H pone DE 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 N z z z z Schlosser Dietmar Planned tester Figure 45 Chart Planned Tester Planned test execution time and Planned Tester can also be used for test structure 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 45 User Manual TEMPPO V6 1 Edition January 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
347. ucture Edit Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test 43 x H o d b amp b Ng E Mo filter QL Notepad RTF Import with TCs E Introduction ng L 2 General description of the product General Attributes Test Steps Ei Automation Requirements History Plan Execution History a s 3 Detailed description of the required product 0 341 Scope of delivery User defined ID torae 3 min om 3 2 Sequences scenarios of interactions a 13 3 User goals Name log zE 3 4 Required functions of the product Eb 4 3 4 1 File Administration Owner Testmanager Updator Testmanager a ai a 3 4 1 1 Windows Login Created 20 02 2012 10 26 12 Updated 20 02 2012 10 53 04 aj D 341 2 New Type Manual Automated Test Case 3 4 1 3 Open i 3 414 Save 4 3415 Ext 3 4 2 Edit Functions 3 4 3 Print Functions Ee E 3 4 4 Search Functions 9 3 4 5 Help System H A S05 Peternal interfaces of the nrod irt n Lack Apply Discard Test Goal tesst goall Figure 225 Apply Discard 3 3 10 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 Settings 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 Refre
348. ues where the user and password must be specified The user profile is exported to standard out Page 291 User Manual Edition January 2014 results lt xml file gt report lt project test structure version test suite filter report setting file gt file lt file gt exit help hide license TEMPPO V6 1 Command Line 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 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 based 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 t
349. uired functions of the product E 33 44 File Administration 3 4 2 Edt Functions G Ek 3 4 3 Print Functions Al 2 4 4 Search Functions Boi ni 3 4 41 Find oo h 33442 Replace Be ei 29 3 4 5 Help System E E 3 5 External interfaces of the product H 43 6 Other product features required E H E 4 Specifications for project management zi Ea 5 Obligations of the client pe a 6 Literature a fe 7 Annex System Test Vi General Attributes Detaile Requirements History Plan Document CtempiPfichtenheft_Notepad_withTC rtf S Mame Chapter EE Precondition Precondition L Detailed description of the requir L Required functions of the product L Search Functions file testikt opened Postcondition Postcondition J Detailed description of the regui _ Required functions of the product Ea Search Functions tile testtxt clased y Lock Apply Discard Si 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
350. uirements true false false gt lt ELEMENT TC TESTGOAL PRECONDITION POSTCONDITION REQUIREMENT STEP AUTOMATION ADD TEST LEVEL USER DEFINED ATTRIBUTE gt STATENS FC user defined Id CDATA IMPLIED gt lt ls gt at 2t already exists in containing test structure add T Ly T 21y ses See 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 2l zey ae lt ATTLIST TC situation Error Regular Error gt lt ATTLIST TC val ver Validation Verification Validation gt lt IATTLIST 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 inherit requirements true false false gt Page 298 User Manual TEMPPO V6 1 Edition January 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
351. uite Figure 218 Attribute activation 3 3 5 Requirement Structure activation In some cases requirements shouldn t be assigned to test cases anymore because they are invalid in future In TEMPPO available requirement structures can be restricted for assignments but assignments from past are still visible and can be used e g for filtering Requirement Structure activation can be defined for each test structure in tab Requirement Structure gt De Activation see also Figure 218 If the check box for a requirement structure is greyed the attribute is set in template Only Superusers and TEMPPO Key Users are allowed to deactivate requirement structures Page 175 User Manual Edition January 2014 A face ei eer ag rear nc gr E re ee Ee tans Se Test Structure Not ATF import wath TCs epad i Notepad RTF import with TES H Introduction HH TEMPPO Designer IDATG Tasks EE E General description of the product Detaled description of the required pro El a Specifications for project management 3 Obligations of the client al Literature TEMPPO V6 1 Description of Use General Requirement Structure Template Atiriputes Info DelActvaton Requirement Structure actvaton Select Requirement Structures which can be assigned e Components Manual Leaming Project Use Cases 1 IBM RequisitePro i Link test cases to requirement Manual g User requirements Figure 219 Requireme
352. uler press Execute button A new window opens where scheduler can be started in two different modes e Run at start time The scheduler is locked and waits until start date The scheduler starts working at defined start date Locked by Scheduler Start Time 31 12 2012 13 00 Oj E Execute Scheduler At Start Time Current State 0 4 Test Cases Figure 267 Execute Scheduler at Start Date e Execute scheduler manually The scheduler is locked and starts executing test cases immediately Page 206 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Se Ret ie 4 Scheduler Mame Locked by Scheduler Start Time 30 06 2012 13 55 n Execute Scheduler mow Current State O 12 Test Cases A running scheduler can be paused or stopped e Pause When pressing Pause current test case execution is finished the scheduler stops executing test cases and running mode is pause If the scheduler is paused scheduler remains locked and user can continue or stop the scheduler Name 1 Locked by Strasser Johanna Scheduler Start Tame 30 06 2012 13 55 u a Pause Scheduler Current State 0 12 Test Cases Figure 269 Pause Scheduler e Stop When pressing Stop current test case execution is finished and running mode is stopped If a scheduler is stopped the scheduler is unlocked and user cannot continue Page 207
353. ult of 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 sui
354. unctions of the product General Attributes Test Steps aeoe iR Plan Eb 3 4 1 File Administration Requirements History Attributes TR Previous Results H ight News 3 4 1 1 1 Mew file opened no change E 3 4 1 1 2 Mew ile opened changes Planned tester Testert E a 3 4 4 Search Functions Execution History El 3 4 41 Find k 3 4444 Find up Planned test execution time fo h 30 min 0 55 iol 3 4 4 1 1 1 Case sensitive blocke R 3 4 4 1 1 2 WinRunner Check Ste Actual test execution time fo h js min 0 59 ig Merge 3 4 4 1 1 3 Quick TestPro Test ca mA 3 4 4 14 4 Test Partner Test ca ou A 3 4 4 1 1 5 UAI not executed i 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 77 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad 3 P ojx Project Test Structure Edt Test Execution Ewalustion Toole windows Help Test Suite Test abject Version swa RCO 11 1 1 l AEE 8 3 Detailed d BAT aquired product features od Locked b Tea er B d a4 Re i General Details Export Into Attributes Predecessor Plan I 3 4 1 F
355. ure and the names of test packages and test cases However the update function see below relies on the names to maintain the relationship to the JUnit test classes Page 274 User Manual TEMPPO V6 1 Edition January 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 o Test Structure JUnit System Test V1 x H d t H of E Mo filter AL JUnit a EO 1 Framework Tests a m 1 junit tests extensions aeaea General Attributes Test Steps E Automation Requirements History Plan Execution History 1 11 test Running Errorin Tests oy 1 12 fest SaunErrorhvTestSetuptunt tes on Junta Jy 2i a 1 2 junit tests extensions Active TestTest ahg 1 2 1 testActive Test unit tests extension File junittests extensions ExtensionTest S ai 22 testActive Repeated TestO qunit tests k 1 3 juni tests extensions Repeated Test Test Script Data aly 3 1 test Repeated Once junit tests exten dy 1 3 2 test Repeated More Than Once junit t aly 1 3 3 test Repeated ero unit tests extent hy 1 3 4 test Repeated Negative junit tests ex
356. ures FE User Fields Find l Gui Layouk Test Maintenance Test Performance Test Portability Test Reliability Test s Resource Test s Reuse Test Bs Safety Test s Security Test State Based Test a Task Based Test Usability Test 7 Figure 341 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 6 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 The button Move Ownership in the project tab see Figure 337 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 E atw112h9 Testeri E tester E Testmanager ores Figure 342 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 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
357. urpose 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 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 filters can be copied to project ones and vice versa 3 3 13 1 Predefined filters There are a lot of predefined filter which are useful for each user Page 188 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Figure 239 Predefined filters 3 3 13 2 Create filter You can create a new filter when pressing the button New filter in Figure 239 Name EE Condtons Hide Empty Subtrees Figure 240 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 Page 189 User Manual TEMPPO V6 1 Edition January 2014 Description of Use TEMPPO Note e S ma A Fiter name already used Please enter a different name Remark Due to missing meta data assignments some Mers might not be usable in the opened project and therefore not visible Figure 24
358. ution add test package 88 Test Execution 75 add test case 88 automated 83 continue 85 89 finish 90 manual 73 start 59 Test Level 7 customize See Metadata Test Levels Test Package 7 categorize 30 create 27 Test Plan 7 Test Planning 7 9 Test Result template 173 Test step Copy Upload 51 Delete Upload 51 Paste Upload 51 Pictures in columns 51 Reference to Upload 51 Upload 51 Uploads 51 Test Step See Test Case tab Test Steps results 73 Test structure delete 260 TEMPPO V6 1 Index Extend 27 Freeze unfreeze 262 Transfer 26 Transfer to other database 26 Version 15 XML export 195 XML update 195 Test Structure 7 13 create 13 generate test cases 19 generate test packages 16 import RTF document 16 24 open 15 properties 13 15 reopen 16 Test suite based on a predescessor 67 Based on previous results 72 copy 71 delete 260 Export 197 Freeze unfreeze 262 Import 92 198 tab Attributes 66 tab Details 66 Test Suite 8 78 create 59 Tools TEMPPO Designer IDATG 285 U User Management See Administration User Management See Administration User Management V Versioning 182 Page 312
359. uto Delete function 2355 ae 4 i 4 d Cancel 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 4 3 1 5 Evaluation In this phase 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 10 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 94 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Figure 115 and Figure 115 show an analysis from a test structure and a test Suite displaying the number of test cases fo
360. 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 293 User Manual TEMPPO V6 1 Edition January 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 294 User Manual TEMPPO V6 1 Edition January 2014 Terms 11 Terms Administration unit This term denotes any object data that is managed in a configuration management tool Typical administration 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
361. with TCs J Introduction H E General description of the product Detailed description of the required product features a Scope of delivery Sequences scenarios of interactions with the environment Z User goals a Required functions of the product J File Administration EE 2 Open Z Save Exit J Edit Functions ey Print Functions aA Search Functions ER Find a Replace 7 fe Help System ed External interfaces of the product Ea Other product features required x TEMPPO Test Suite Generator lt lt Prey i Cancel Figure 75 Test structure pre selection test packages Enter test suite name oA PWN Determine the logical expression 7 Remove test cases manually E 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 68 User Manual TEMPPO V6 1 Edition January 2014 Description of Use Bj Test Suite Wizard a 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 Enter testsuite 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 Suit
362. wn 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 14Test 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 15Test 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 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 i
363. y 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 37 User Manual TEMPPO V6 1 Edition January 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 Select the requirement structures when the assignments should be updated By clicking Apply the test structure is checked in and then propagation is executed F 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
364. y 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 Al 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 8 Find and Replace TEMPPO offers a find and replace mechanism By pressing F3 or activating the menu item Edit gt Find and Replace Figure 221 is shown Page 177 User Manual TEMPPO V6 1 Edition January 2014 Description of Use DA Find a Test case Test package Requirement Search in User defined ID a Direction for J Up B Down Case sensitive Find Next Find Next TestCase List Occurrences Figure 221 Find and Replace The find replace dialog includes two tabs whereas the first one is for searching in test cases test packages and for requirements Both tabs provide the same features the only different between this tw
365. you define the automation settings here First of all you have to choose the automation tool which will run your test cases 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 supp

User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents