Home

User Manual

Contents

1. Edition July 2014 Description of Use DOORS r TEMPPO Baseline Requirement Test anager Manager DEV1 1 0 DEV1 1 0 Test Structure Req1 3 Req1 V3 1 1 PLM1 1 0 Req2 import update Rea2 let a Sales 1 0 Req r Req3 Req3 TC2 Req1 s aa Y lt i Req2 Req3 OR Req3 FE Reni ine DEV2 2 0 DEV2 2 0 1A S TC5 Req5 OSes Req1 Req1 s Req2 import update Req2 Req3 Req3 Sopy of DEV1 Reqi a Req2 Req3 lt Test Suite TC1 TC2 TC3 Copy of DEV2 TC4 Reqi 5 TC5 Req2 of TC6 Req3 t KK AKA Figure 258 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 f
2. Figure 43 History tab Within current test structure version the number of history entries loaded x can be configured in settings see 3 3 21 2 4 If there are more history entries the button Search next is still enabled und the next x lines could be loaded It also possible to view all history entries of all test structure versions by pressing the button Display all entries and save them to CSV file The additional comment Info can be configured to be mandatory in TEMPPO Administrator gt Project properties For each project this mandatory flag can be set If the mandatory flag is set on a history comment is popped up on apply Figure 44 Page 52 User Manual TEMPPO V6 1 Edition July 2014 Description of Use AIC x Figure 44 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 F TEMPPO Testmanager Demo
3. F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x Test Structure Notepad RTF Import System Test pu Q Notepad RTF Import EHE 1 Introduction H General description of the product General Attributes Details Requirements History Plan EF H 3 Detailed description of the required g a 31 Scope of delivery Document C temp Pfichtenheft_Notepad rif 7 3 2 Sequences scenarios of intel Ea 3 3 User goals Mame Foy 3 4 Required functions of the prodi Ea 34 1 File Administration Chapter Precondition 3 Precondition ce 3 4 2 Edit Functions Detailed description of A 3 4 3 Print Functions Fea Required functions of t 3 4 4 Search Functions fe 3 4 5 Help System H 3 5 External interfaces of the prodi Postcondition 3 6 Other product features require c aal 4 Specifications for project managemel Postcondition LU 5 Obligations of the client Detailed description of u 5 Literature J Required functions of me OF Annex 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 di
4. O a Tester tester a tester3 E tester4 testers E testerB Connect ta LOAF server DSM Jatos C Pi Host scdldap atas net Port fes Base User bomainilsery wga 129 Password E Gonhnect JE Synchronize Users HE Import users Figure 318 Connection to the LDAP server You can define various LDAP connection configurations where each is identified by a DSN Data Source Name A new DSN can be created using the L button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the tt button For each DSN Page 254 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator 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 server was successful the buttons Import users and Synchronize users are enabled You can import users by clicking the button Import users By clicking the button Synchronize users you can synchronize the existing TEMPPO users with the LDAP server 5 3 1 2 Importing users from LDAP x
5. L Test object Version Wz RCOS COPY ii 3 Detailed description of the required g l 3 4 Required functions of the prodi attributes TR Plan Eb 3 4 1 File Administration EF a 3 44 41 New 2 Attribute values ih i Yew file ope Seas ay as 3 4 4 Search Functions B 3 4 4 1 Find a E Wasa 4 Find up ie n ajr Apply Discard amp fio amp amp amp Figure 185 Attributes TR 3 3 2 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 186 and Figure 187 The Show Details menu item has to be activated again because the selection has changed Page 162 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad ol x Project Test Structure Edt Test Execution Evaluation Tools Windows Help EE v4 1 1 Li Notepad RTF Import with Tos 1 Introduction i z 1 1 Purpose of the document General Test Packages Test Caze 211 2 Validity of the document A 1 3 Definitions of terms and abbreviati 1 4 Relationship with other documente Total number of selected TPE 26 215 Overview of the document Total number of selected TCs 7 Relationship with existing projects Relationship with earlier and follow Purpose of the product Delimitation and embedding of the Overv
6. Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Testmanager Figure 333 Metadata Uploads If you activate Delete all non referenced uploads a confirmation window see Figure 334 is displayed before deleting all non referenced uploads Delete unreferenced uploads a x in 2 Do you really wank to delete all unreferenced uploads Figure 334 Confirmation window Created 22 11 2013 13 09 12 2013 17 09 12 2013 17 22 11 2013 15 12 09 2012 14 09 12 2013 17 22 11 2013 13 22 11 2013 13 22 11 2013 13 22 11 2013 13 22 11 2013 13 09 12 2013 1T 09 12 2013 17 TEMPPO V6 1 TEMPPO Administrator Size 57 01 kB 432 64 k 443 45 k 84 29 kB 2 10 kByte 4 97 MB 15 15 kB 26 13 kB 26 13 kB 26 13 kB 6 49 kByte 7 70 kByte 8 47 ME Y 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 335 You can create new requirement structures with TEMPPO Requirement Manager Page 264 User Manual Edition July 2014 Fi TEMPPO Administrator Testmanager Database bo Roles E Users Metadata LA Projects Lacks License TEMPPO V6 1 TEMPPO Administrator O x Test Levels Test Categories attributes GB Uploads Requirement Structures C Use
7. 3 4 Required functions of the product and password EP 3 4 1 File Administration oF a7 3 4 4 1 Windows Login General Attributes Test Steps Ei Automation Requirements History Plan Execution History Expected Enter account in test domain Login successtul d 34 2 New Po be fi 341 24 New file opened no os 3 4 1 2 2 New file opened ch BB 3 41 23 New Test Package c been 3 4 1 3 Open LU 3 41 4 Save pli 3 4 1 5 Exit 3 4 2 Edit Functions 3 4 3 Print Functions 33 44 Search Functions 2 9 3 4 5 Help System E E 3 5 External interfaces of the product H E 3 6 Other product features required Et al 4 Specifications for project management a 5 Obligations of the client En 6 Literature Ea F 7T Annes ad 4 F Figure 214 Referenced test case with Back button 3 3 3 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 204 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 3 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
8. Find E Find up Di Case sensitive x Determine the logical expression 6 Remove test cases manually TEMPPO Test Suite Generator lt lt Prey Next gt gt Finish Cancel Figure 66 New Test structure pre selection whole test structure Bj Test Suite Wizard Steps Test structure pre selection Introduction Select test packages hold lt STRG gt and lt Shift gt for mutti select Choose creation mode Enter test suite name 4 2 3 Select nodes or subtrees 4 5 Notepad RTF Import with TCs SJ Introduction gA General description of the product 5j Detailed description of the required product features Z Scope of delivery E Sequences scenarios of interactions with the environment ey User goals Required functions of the product File Administration a New New file opened no changes Fl New file opened changes el Open Save L exit J Edit Functions h J Print Functions J Search Functions moe fr inc EH Find up Di Case sensitive x Determine the logical expression 6 Remove test cases manually TEMPPO Test Suite Generator lt lt Prey Next gt gt Figure 67 New Test structure pre selection test packages Finish Cancel Figure 66 shows the first step for creating a test suite It shows the whole test structure pre selected If you want to consider a whole te
9. To remove obsolete uploads see chapter 5 4 5 3 3 3 4 Download an upload If you select a hyperlink upload and activate the context sensitive menu mouse over hyperlink and choose the menu Download Figure 215 is shown to select a directory for the file download Page 177 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F Select a destination directory Look in B Eigene Bilder ar Ti Jm E re im Media o a Desktop ini GD Sample Pictures Faj TPnr JPG Zuletzt nde lah s96ef376a_9464628 3jo9 GL untitled bmp Piel wena Gah a96af37Sa_8454626_s4 3 jpg E Gh cut jpg Desktop File name expected image jpg Download i Files of type fan Files Cancel Figure 215 Destination selection 3 3 4 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 4 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 resu
10. e If atest structure is opened reporting for more test suites is opened via Evaluation gt Report selected gt Several Test Suites Different report settings can be defined for user level and for projects In tab Personal settings the user sees its own defined settings and in tab Project settings all settings defined for this project are visible Page 122 User Manual TEMPPO V6 1 Edition July 2014 Description of Use default Setting TEMPPO default setting NewReportSetting_Report depth 07 03 2013 15 22 06 Report Template 16 02 2012 16 36 07 TC Review Template Y Test creation report Excel tight Continuous text Amost all test package attributes Almost all of test case att Test creation report Word tight Continuous text Test packages with description Test with preconditi Figure 140 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 repo
11. ALA JUnit B S 1 Framework Tests a b 1 junit tests extensions Extension Test General Attributes Test Steps B Automation Requirements History Plan Execution History 0 1 1 test Running Error in Tests i salgi 1 2 testSetupError InTest Setup funit tee Tadi JUnit Jy Eh a 1 2 junit tests extensions Active Test Test yt 2 1 testActive Test junit tests extension File junit tests extensions Extension Test S hg 1 2 2 testActive Repeated TestO junit tests ae 5 1 3 junit tests extensions Repeated Test Test Script Data why 3 1 testRepeated Once junit tests exten dy 1 3 2 test Repeated More Than Once qunit t oy 1 3 3 test RepeatedZera junit tests extens why 1 3 4 test Repeated Negative junit tests x est RunningErrorlin Test Setup Lack Epply Figure 365 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 evo
12. Demo Notepad Project Test Structure Edit Test Execution Evaluation Toole Windows Helg Test Sute Test object Versi Li Mew Ca Open K 4 gt mM 8 Reopen M Test onec version ae ay nies a 3 Detailed descripti EHA 3 4 Required ful Run automated Al Attributes Details Requirements History Plan Set Pesut ID ipsso F Export Test Suite F 2 3 Import Test Suite Mame Fina up Ela 3 4 4 1 BRE Find locks fi 344144 Cases Created 15 02 201217 0 Updated 16 02 2012 13 2 EE 3 4 4 1 4 2 WinRur BD 3 4 4 1 1 3 QuickT of 3 4 4 1 14 Test Pe Number of TCs 46 EJ 3 4 4 1 1 5 UA no Test Category Description Lock Apply Discard Cwner Testmanager Updator Testmanager Type Test Package Figure 100 Automated Test Execution 3 1 4 1 11 Mixed Test Execution A mixed test suite contains both manual and automated test cases The test execution doesn t differ from the one described above but is just a mixture of them If a test package contains both manual and automated test cases and Run automated is invoked on it only the automated test cases will be executed All manual test cases in this test package must be carried out afterwards 3 1 4 1 12 Setting several results For regression testing it is often convenient to set results for several test cases at once e g if you already know the results of the test cases First you have to select a
13. Figure 108 Save dialog If the export database already exists you get the following message Figure 109 Fileexists S LY The file already exists Do you want to overwrite it Figure 109 Overwrite file After successful export the test suite with activated root node looks as follows Fi TEMPPO Testmanager Demo Notepad a _ ojx Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Version 2 of Test obeject ROOI V211 ey x MH d b H GP EE No mter eee obeject RCO i 3 Detailed description of the required g General Details Expor Into Attributes Predecessor Plan Mame version 2 of Test obeject Rci Owner Testmanager Updator Testmanager Created 16 02 2012 15 53 31 Updated 16 02 2012 15 53 31 Type IncludedTPs Whole test structure ExcludedT Cs Lock Apply Discard Figure 110 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 111 shows that also test cases are marked read only The only possible change is to add test results Page 100 User Manual TEMPPO V6 1 Edition July 2014 Description of Use
14. General New Entry Created 20 02 2012 15 16 45 Owner Testmanager Type Test Category Description eres Figure 328 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 260 User Manual TEMPPO V6 1 Edition July 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 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
15. Requirement Selected values h Attribut Find I Available values Figure 337 Requirement attributes With a double click on an attribute tab attributes the properties of the attribute are shown see Figure 338 It s not possible to change the requirement attribute because it s imported from DOORS or RequisitePro Page 266 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Fi Properties of Property x General Details Property Created 14 02 2012 14 54 30 For Use of 7 Test Case Owner Testmanager in Test Package Type Attribute Test Suite D Test Resutt m Reguiremert Description eres Figure 338 Properties of attribute 5 4 7 User Fields Fi TEMPPO Administrator Testmanager _ Oo x Database ka Roles E Users Metadata LA Projects B Locke E License Test Levels By Test Categories ot Attributes ES Uploads tf Requirement Structures CT User Fields Action image Testmanager 15 02 2012 16 14 56 Image Test Structure Actual screen shot Testmanager 20 02 2012 15 28 06 Image Test suite Comment Testmanager 15 02 2012 16 15 13 Text Test Structure Figure 339 Metadata User Fields For test steps new columns can be defined for test structures and test suites When pressing the button New see Figure 340 you can select between a text and image column for test structure or suite Page 267 User Manual TEMPPO V6 1 x
16. V 2 1 Test Suites for V2 1 2012 02 16 ascending V2 1 1 editable version descending K Version 2 of Test object RC01 16 02 2012 V2 2 V221 V3 editable version Figure 132 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 Page 117 User Manual Edition July 2014 TEMPPO V6 1 Description of Use 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 RC01 RC02 Test Results RCO1 Test Suites E failed Mpassed Mnotexecuted O blocked Mnot completed notimplemented E on hold Favountes z Dy tal x Favourite RCO1 RCO2 Test Suite Selection Test suite analysis depending on filter settings Press Select Test Suites for choosing test suites and setting filter Sele
17. gi 2 3 2 Sequences Scenarios oe 13 3 User goals AML 34 Required functions of th Requirement ID Requirement Mame Requirement Structure Func reqz4 Required Motepad WH All functions of the product implemented Func req 6 BENY Motepad WH All _ 2 Pas Delete requirement requirements See 3 44 Search Functions AL 3 4 41 Find 3 4 4 2 Replace implemented requirements Fune_reqes Notepad WA AlI implemented requirements a 3 5 1 User interfaces eee 511 Editor Pane El Lock Apply Discard Bs 3 5 1 2 Search Diak 3 6 2 System rere 4 F Figure 35 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 you have children test packages Therefore TEMPPO offers you to inherit requirements from parent test packages Page 45 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 5 x Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test 41 H b H o Enor L Notepad RTF Import with TCs E E 1 Introduction HHL 2 General description of the
18. 3 4 2 8 Word Wrap 5 4 2 9 Set Fort oe 4 3 4 3 Print Functions eu 3 4 34 Page Setup pS 3 4 3 2 Print 2 P 3 4 4 Search Functions EA 34 41 Find o B 3 4 4 1 Find up A 444142 WinRunner Bev E 3 4 4 1 1 3 QuickTest o 344145 UA ff 3 4 4 1 2 Find down Fi 34 4 2 Replace 93 45 Help System H a 3 5 External interfaces of the product j Other product features required Figure 176 Selection with lt Ctrl gt e Select contiguous TEMPPO V6 1 Description of Use First select a test package or test case then press lt Shift gt and select a test package or test case The items from the first selected item to the last item are selected but only the visible items are selected see Figure 177 Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution Ew e Test Structure Notepad RTF Import with TCs M4 H E Mo fiter E 3 3 User goals a E 3 4 Required functions of the product a a 3 4 1 File Administration oe 2497 Tire Pate Figure 177 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 178 Page 153 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Evaluat Test Suite Test abject Version Ye REOS CO
19. 3 41 3 Save ob blll 3 4414 Exit 3 4 2 Edit Functions 3 4 3 Print Functions H 3 4 4 Search Functions a 93 4 5 Help System E E 3 5 External interfaces of the product H os 3 6 oe noe kai amaramen p 1 hi m x E Milestone M1 E Platform windows 7 64 bit E Regressiortest yes EP Test location Offshore ma Acceptance Test x Figure 168 Button Reload for reloading the whole tree 3 2 2 1 2Refreshing recursively You can refresh an item including all sub items by selecting the refresh recursive function in the context menu see Figure 169 Attention The selected item with all sub items will be completely re loaded from the database so it may take a long time Page 147 User Manual TEMPPO V6 1 xl Project Test Structure Edt Test Execution Evaluation Tool Windows Help 5 tL LY Mew We Fi H d b We Find and Replace F3 E AJ Motepad RTF Ir show Detaile EE 1 Introductior Select All Ctri A 2 General de Attributes Details Requirements History Plan EH 3 Detailed de z A S 2 oa 20 i Tree E o ID hipsa6 o p 3 2 Sequi E compare 2 ew 33 User By 3 4 Regu at Cut Ctr Hame New i Ee Ep ra a a8 Copy Ctrl Owner Testmanager Updator Tester BE i Paste Ctrl 4 E Created 16 02 2012 16 45 50 Updated 16 02 2012 17 12 24 fe eas aste before a h Type Test Package ia d F gas M O OOOO P ets 2 Gs ge Delete Delete bat
20. 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 249 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator using theL button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the button If you delete all DSNs TEMPPO will not be able to connect to a database For each DSN you have to specify several connection parameters which are explained in the following TEMPPO supports two database management systems selectable in the field database Depending on the chosen one you must specify several connection parameters Access For Access you just simply have to specify the path to Access mdb TEMPPO automatically creates an ODBC entry Fi SiTEMPPO Administrator i Ioj x Database Roles E Users a Metadata Projects locks fea License a Notification MB ISITEMPPO 5 7 Users Guide E a Database Access File E Documents and Settings atw 1 12h9 DesktoplsitemppolsersGuidev57 mdb_ Wa Connect Database Name Database Version Figure 313 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 data
21. 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 308 User Manual TEMPPO V6 1 Edition July 2014 Appendix lt ELEMENT REQUIREMENT DESCRIPTION REQUIREMENTSTRUCTURE gt lt ATTLIST REQUIREMENT id CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt lt ELEMENT REQUIREMENTSTRUCTURE DESCRIPTION gt lt ATTLIST REQUIREMENTSTRUCTURE name CDATA REQUIRED gt lt cannot be zero length string gt lt ATTLIST REQUIREMENTSTRUCTURE version CDATA REQUIRED gt lt cannot be zero length string gt lt ELEMENT STEP INSTRUCTION INPUT EXPECTED USR FIELD gt lt ELEMENT USR FIELD VALUE gt lt ATTLIST USR FIELD name CDATA REQUIRED gt lt IATTLIST USR FIELD type text image text gt lt ELEMENT AUTOMATION EMPTY gt lt ATTLIST AUTOMATION tool SilkTest WinRunner UniversalFile UniversalSocket JUnit QuickTestPro TestPartner UniversalFile gt lt ATTLIST AUTOMATION file CDATA IMPLIED gt lt ATTLIST AUTOMATION data CDATA IMPLIED gt lt ELEMENT ADD TEST LEVEL EMPTY gt lt ATTLIST ADD TEST LEVEL name CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt l
22. Requirement name 31 Donitiramant mama 27 r z Stacked Horizontal Bar Chart v Requirement name 1 tc13442 tc13443 tc13444 Al Requirement name 10 tc13543 tc13544 tc13545 tc13546 tc13548 tc13550 tc13552 Requirement name 11 tc13574 tc13575 tc13576 Requirement name 12 _ tc13578 tc13868 tc13869 Requirement name 13 tc13581 tc13582 tc13583 Requirement name 14 tc13586 Requirement name 17 tc13611 tc13612 tc135992 tc13593 tc13596 tc13598 tc13600 Requirement name 18 tc13615 tc13618 tc13620 tc13622 tc13624 Requirement name 19 tc13630 tc13631 tc13633 tc13634 tc13635 tc1 3636 Requirement name 2 tc13449 tc13450 tc13451 tc13452 te13453 tc 3868 tc13869 tc13638 tc13639 tc13640 tc13641 tc13644 tc13645 tc13648 tc13661 tc13662 tc13663 tc13664 tc13665 tc13666 tc13667 Requirement name 22 _ tc13684 tc13685 tc13686 Requirement name 23 tc 13688 tc13690 tc13693 tc13695 tc13696 tcl 3698 tc13699 Requirement name 24 tc13972 tc13973 tc13974 te13976 tc13977 tc13978 tc13979 Requirement name 29 _ tc13972 tc13973 tc13974 tc13976 tc13977 tc13978 tc13979 Requirement name 3 tc13455 tc13456 tc13457 tc13458 tc13459 Requirement name 31 c13988 tc13990 tc13993 tc13994 tc13995 tc13996 tc13997 Donitirermnant mama 27 he 1 20297 be 12022 kei ROR be 1 IARA be 1 RARR be 1 2020 kei aaan Figure 123 Test Structure Requirement Analysis Detailed Data Page 109 User Manual
23. Test Execution fagina z l Planning and rePorting Organizer User Manual Edition July 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 1 OVGEVICW cona a a suveseuesiasmnnnenues 9 2 Iptrod cti N siisiiirri saena aariaa raian 10 TAE TESEPrOcCESS ianei enna EA AEEA AEAN 11 3 DESCHDUON OF USC einna 14 Suk Tne FESE Process PHASES serne erdan etiawesaaue nd ETNE 14 Sht FES PiShiMinG ssienatwaietaesoacivuas iain aiateieialeeesebrwnirealiaanniasesuieselin 14 Sadak Writing the est Plalinsessaenssstersaiianswenss xraiiaseton series a 14 3 14 12 Writing the Project Plan waviissscecsaiennseiastasoniadi ase womiatersguesaenens 14 3 1 1 3 Defining Test Case AttributeS ssssessssssrsrnnenssnrsnrrrrernrenens 15 3 1 1 4 Baseline Import REquireMeNts cece eeeeeeeeeeeeeeees 15 JAA Tet DESIN erer E E 15 I2 WOrKNG WIENSPFOlCCUS riepen in iana EN TEAN 16 Sled k Ereatng ar PrOJe CE sinia a ra E E ESA 16 3ed Al2 OPeniIng an EXISHNG PFOJECT oabarii e E teet eee soass 17 3 1 2 2 Building the Tes
24. User Manual TEMPPO V6 1 x Notepad RTF Import with TCs Tree style 4 Yersions only EM Test Suites for W1 1 2012 02 16 Fl editable version om oe Test object Version lt 2 REOT 16 02 2012 Versions and Labels Labels only A Test object Version XYZ RCOZ 16 02 2012 E Test object Version XYZ RECOS 16 02 2012 ius Test object Version WYA RCOS COPY 16 02 2012 Order ClearCase style EHZ o A Test Suites for W21 2012 02 16 ascending Ete 7 editable version E Version 2 of Test obeject RCD 16 02 2012 J editable version D descending eres Figure 113 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 114 Then an open dialog is shown where the export database has to be selected Fi Test Suite Import Settings How should SITEMPPO handle conflicting test results during import C impart all test results Manually choose test results to import oasi Figure 114 Test Suite Import Settings Import only newer test results If a user already imported a test result for a test case a
25. gt Arial sis Newsboard Path ta HTTPS Certificate Test Suite 2 Database Connections Cl Test Automation Sill Test User repository Hin Runner i Universal File er H Universal Socket a Quick Test Pro jeer admin H Test Partner TEMPPO Designer DATS i Ranorex El Commands New Command i Javas El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults Cancel File Edit view Favorites Tools Help a Back gt x x a A 4 Search SY Favorites al oF Address http 192 168 146 7 cqweb login Go Please enter your User Name and Password User Name ir ClearQuest Web Password Schema Repository cq_aktx Database tpo user database is mov Login p es a ER ed Local intranet Figure 303 Login to Clearquest 3 3 21 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 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 242 User Manual TEMPPO V6 1 Edition July 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 Tel
26. 1 editable version Demo Not Notepad W211 editable w Test Pac Other pro tp561 export dat 20 02 201 EH Notepad RTF Import with TCs Demo Not Notepad v2 44 editable v Test Pac Externali tp558 export dat 20 02 201 i Demo Not Notepad W214 editable w Test Pac User inter tp559 export dat 20 02 201 Poe 1 Test Suites for V2 1 20124 Demo Not Notepad W214 editable v Test Case Test Part tc702 export dat 20 02 201 editable version Demo Not Notepad Version 2 V2 1 1 editable v Test Suite Version 2 export dat 20 02 201 Version 2 of T Demo Not Notepad W244 editable v Test Case UAI tc703 export dat 20 02 201 EE Demo Not Notepad Y24141 editable v Test Case WinRunn tc701 export dat 20 02 201 Notepad System amp Acceptance T Demo Not Notepad W214 editable v Test Pac Find up tp650 export dat 20 02 201 A User documentation Demo Not Notepad v2 44 editable v Test Pac Finddown tp651 export dat 20 02 201 gt Demo Not Notepad W214 editable v Test Pac Relations tp521 export dat 20 02 201 a Figure 350 Unlock 5 7 License Server Connection Fj TEMPPO Administrator Testmanager 1 ae Host Port fatinzpt Oya wwyS30 ry t solution net 3 2013 Disconnect Server into License usage Log Server Mame atlizp 0ga MAC
27. 127 0 0 1 Port Humber 1492 Connection delay 5 seconds Adapter temppo test tools adapters C Defautt uto Tool dapter s Argument argi arg Mtcid filet i E Upload resutt files to database Result Viewer c winntinotepad exe Mew Command aves Restore Defaults OK Cancel Figure 290 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 application 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
28. 3 3 21 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 221 User Manual TEMPPO V6 1 Edition July 2014 Description of Use me ser Interface zs ay Fell tele User Interface esses opgang General f Font size For multi line Fields Examples description instruction 1 Language Fa ie English a German Look amp Feel f Metal i CDEMotiF f Windows Windows Classic Restore Defaults Cancel Apply Figure 279 Global Settings User Interface 3 3 2 1 1 2 Logging You can also change the location of TEMPPO s log directory Default value is the user s profile Directory to store log files E Documents and Settings fuchscl temppoilog S Restore Defaults Cancel Apply Figure 280 Global Settings Logging 3 3 21 2 TEMPPO Test Manager Settings Specific settings e g tree display automation tools etc can be configured in the settings dialog in TEMPPO This dialog is opened via Windows gt Settings On the left side there is a tree where the user can select the setting group which Page 222 User Manual Edition July 2014 TEMPPO V6 1 Description of Use Should be configured On the right side all single settings can be edited see Figure 281 settings ee PP Tree pw Test Step Cells Analysis Mewsboard Teast Su
29. A task package contains all properties of a test case ID fixed name owner created updator updated test category optional description Fi TEMPPO Testmanager Demo Notepad i joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test 15 H d gt WH E No filter Abd Motepad ATF Import with TCs oe 1 TEMPPS Designer DATS Tasks 11 New Task Package General tributes Details Requirements History Plan Introduction General description of the product ID pras Detailed description of the required product fea Specifications for project management usecase FiesNew O _ Obligations of the client Name UIse case File gt New Literature Owner Testmanager Updetor Testmanager Crested 20 02 2012 16 43 56 Updated 20 02 2012 16 43 57 Type Task Package Number of TCs 0 Test Category i Description Lock Apply Discard Figure 377 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 store
30. 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 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 312 User Manual TEMPPO V6 1 Edition July 2014 Appendix 13 6 1 Functions to be applied to a role An X means that it can be de activated for a role Rig o U 5 r o Y z Bi U U o oye Z A K S TEMPPO Aaminstrator administrates xa o o O Administrate projects X X x x PF O Administrate roles X X X X X _ Change includes assignment of roles to users id Administrate test structures XK P ti CCC Administratetes
31. 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 191 Fi Locked Items x Locked Items kaSr Mew Test Case bees Mew Test Case 1 Figure 191 Locked Items If the button Discard is pressed all changes in all tabs will be discarded Page 166 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 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 im Bee gt Brew Teste AfindandReplace Fs ae MENew Te Show Details Di New Te Select All ol New Te JCC B ree d y Git Ctrl x Copy Ctrl C A Paste Ctrl X Delete Delete T Order ey Edit OS Refresh recursively ta Move Ownership g Analyse selecter Ei Report selected Figure 192 Context menu Move Ownership eres Figure 193 Move ownership After the process moving the ownership a summary is shown see Figure 194 x Humber of tems with new owner 9 DD Number of locked tems 0 Humber of tems with identical owner 0 Figure 194 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 displa
32. Figure 228 with the number of replaced test case and number of test case package which couldn t be replaced because of locks etc TEMPPO i x Fi 1 Search ino test cases if completed and 7 replacements in 3 test cases were done Figure 228 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 10Apply 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 loj x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test 3 l al E x H d P H g E Mo fiter A Notepad RTF Import with TCs Fb 4 Introduction Cet Ea 2 General description of the product General Attributes Test Steps Ei atomation Requirements History Plan Execution History Ej 8 3 Detailed description of the required product lL 3 1 Scope of delivery User defined ID ftc7a2 m 3 2 Sequences scenarios of interactions 3 3 User goals erie log 3 3 4 Required functions of the product EP a 3 4 1 File Administration Owner
33. Page 61 User Manual TEMPPO V6 1 Edition July 2014 Description of Use http www microfocus com Ranorex http www ranorex com and on the other hand there is a Universal Automation Interface UAI With the context menu item Test automated test case or Edit gt Test automated test case the test case can be started on trial i e the result of test case isn t saved The result is shown in a message box 3 1 3 1 7 1 WinRunner QuickTest Professional SilkTest TestPartner For specifying an automated test case it is necessary to enter the tool WinRunner QuickTest Professional SilkTest TestPartner the file name of the script plus path a file selection dialog is opened The text field Script Data is used for passing parameters to the automation script Currently only SilkTest uses this feature Fi TEMPPO Testmanager Demo Notepad E l Joj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test v1 2 General description of the product 3 Detailed description of the required product features LL 31 Scope of delivery General Attributes Test Steps E 3 2 Sequences scenarios of interactions with the environmen EJ automation Requirements History Plan Execution History D33 User goals a 3 4 Required functions of the product wi Ru Et 43 4 1 File Administration ee nunner S Er a oe File C
34. Save o be 3414 Ext 3 4 2 Edt Functions Ei 33 4 3 Print Functions l E ar 3 4 4 Search Functions Ed 3 4 4 1 Find Eb a 3 4 41 4 Find up FF 344142 TT r 344 4 1 2 Find down General Attributes Test Steps Ei Actomeation Requirements History Plan Execution History Precondition file testixt opened find dialog open M Case sensitive Cursor at EOF 1 Enter search phrase Specity search direction 7 a 3 4 4 2 Replace A tn EY 3 45 Help System Sia 3 5 External interfaces of the produ a dee 3 5 1 User interfaces B 3 5 1 4 Editor Pane iy 3 5 1 2 Search Dialog i E 3 5 2 System interfaces ei 3 6 Other product features requirec 3 6 1 Performance m 3 6 2 Resource m 3 6 3 Security fi 384 Safety fi 3 65 Portability fi 3 6 6 Reliability m 3 6 7 Maintenance fi 3 6 8 Reuse i i Postcondition file test tkt closed Wi Case sensitive fli 3 6 9 Usability H 4 Specifications for project managemery A 5 Obligations of the cliert B Literature i 7 ANNEX El Figure 50 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
35. 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 58 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad a joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test 01 H P H gt E Mo fiter lA Notepad RTF Import with TCs gt E 1 introduction c 2 General description of the product EF 8 3 Detailed description of the requires pope A 3 41 Scope of delivery pen a 3 2 Sequences scenarios of in a 23 3 User goals 5 ra 3 4 Required functions of the pri E 3 4 1 File Administration EL 3411 New o B New file opened no changes Locked by Testmanager tc536 General Attributes Test steps Ei utometion Requirements History Plan Execution History ee instruction Actionimage EERE l i A Unbenannt Editor Editor Pane cleared Bearbeiten Format Ansicht 7 Stro h Strg o peichern Strg
36. Y k 4 000000 0 0 0 SA SmwANe e 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 22 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Import Settings Document C Users atwl 12no Documents Sample_Nach RTF Himport rif cae F Generate document path Heading Mask Heading Limit test structure depth to 4 Generate numbers and start wath 1 F Generate test packages V import description Fj Generate test cases Fixed test step columns A test case is identified by a table with following headers Instruction My_Instruction W Input My_Input I Expected My Fj Ignore empty table rows do not create empty test steps User defined test step columns F Erwarteter Screenshot Expected Screenshot Attributes Another UDA Another UDA E upa UDA Requirement Structure Functional requirements Functional requirements Non functional requirements Non functional requirements canca Figure 13 Import Settings for generating a basic test structure For the generation of a basic test structure following settings can be applied e Generate document path The path of the imported document is set for each test package in tab Details e Heading mask Specify the name o
37. 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 script should take some individual parameters Assume test_case bat corresponds to a TEMPPO test case and should be started with individual parameters f i like this test case bat
38. heart beat e Ping repeats Number of pings heart beats sent to TEMPPO Designer IDATG 3 3 21 2 10 Ranorex e Result path Path to directory of the result file s e Result viewer Application to open result file s l User Interface Tree rw Test Step Cells Analysis H Newsboard i Teast Suite Result Path C itmp S Ressut viewer C Program Files WWtraEdtwedits2 exe El Test Automation Silk Test Hin Runner Universal File H Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS Ber anon ex El Commands lew Command SE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults OK Cancel Figure 297 Settings Ranorex 3 3 21 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 298 Then a new tree node is created with the new command see Figure 299 A command is defined by its name path and arguments The name has to be unique Page 238 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Settings OOOO x Commands l User Interface Tree New Command ew Test Step Cells Analysis H Mewsboard Test Suite Database El Test Automation pe Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test Partner JUnit b TEMPPO Designer IDATG i Ranorex o mmands
39. in documents e Referring to requirement numbers or names 3 1 2 2 1Creating a test structure TEMPPO allows opening only one test structure at a time which means that a test structure can only be created if no other one is already open Furthermore test structures are related to projects so the project which shall own the test structure to be created must be open too 3 1 2 2 1 1 Creating an empty test structure When activating Test Structure gt New gt Empty Test Structure the window shown in Figure 5 is displayed You may enter a name and a description Also a test level has to be related to the new test structure Fi Test Structure Properties x General Mame Notepad System Acceptance Test Owner Testmanager Updator Created 19 05 2010 14 03 04 Updater Type Test Structure SITEMPPO Designer D473 T Test level System Test a Description This test structure Figure 5 Test Structure Properties By 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 18 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F TEMPPO Testmanager Demo Notepad 7 me x Project Test Structure Edt Test Execution Ewaluation Tools windows Help Test Struc
40. that won t be executed e Based on a predecessor new test suite is chained with an existing test Suite chain e Copy Based on an existing test suite only copying test suite selections to the new one e Special Based on an existing test suite defining restrictions on certain test results Bj Test Suite Wizard xl Steps Introduction 1 Introduction This wizard guides you through the steps necessary to create atest suite There are three possibilities to create a test suite 2 Choose creation mode 1 Based on test structure preselection applying a condition and finally removing some test cases that won t be executed Test structure preselection De Select nodes test packages or sub trees The default selection is the whole tree Enter test suite name Determine the logical expression based on that preselection Removing test cases that do not match the test suite 2 Based on an existing test suite only copying test suite selections to the new one Selecting an existing test suite Enter test suite name 3 Based on an existing test suite defining restrictions to certain test results Selecting an existing test suite Selecting test results to be considered Enter test suite name TEMPPO Test Suite Generator Figure 64 Test Suite wizard Introduction When pressing Next Figure 65 is shown where you can select one mode Page 69 User Manual TEMPPO V6 1 Edition J
41. the requirement management application e TEMPPO Designer the application for test case and test data generation e TEMPPO Administrator the application for meta data maintenance e TEMPPO Manager the application for database migration The main parts of TEMPPO Test Manager are Editing and administrating automated and manual test cases including version control Integration of automated test case execution with WinRunner SilkTest TestPartner QuickTest Professional Ranorex or any other tool that supports a command line interface Flexible manual test case execution even with unplugged notebooks Professional analysis statistics and reporting This manual described the way of working with TEMPPO Test Manager Page 9 User Manual TEMPPO V6 1 Edition July 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 priorit
42. you have to configure the corresponding settings in TEMPPO settings Change Management El User Interface Tree Test Step Cells Bugzilla gt Analysis gt Newsboard Test Suite Clear Quest Database JIRA Test Automation Silk Test gt in Runner Universal File Universal Socket Active Change Management Tool Telelogic Change QuickTest Pro gt Test Partner JUnit gt SITEMPPO Designer IDATG Ranorex Commands New Command Java32 Change Managemen _ ar anagemerit H Bugzilla Clear Quest Telelogic Change JIRA Restore Defaults oo Cancel Figure 94 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 95 Page 88 TEMPPO V6 1 User Manual Description of Use Edition July 2014 General Attributes Test steps Ei Actometion Requirements History Attributes TR Previous Results Plan Precondition Select the Lser detine attribute in the combobox Attribute select the 222 NOT IM operator Push the button right beside the wale field selection for the Figure 95 Create a new bug entry Now a dialog for creating a bug or change request opens see Figure 96 Fill in the data of the bug and may activate the combo box Add test report In the end you press Submit T
43. 02 2012 13 47 29 Updated 16 02 2012 13 47 29 Ihcluded TPs Mew Find ExcludedT CE Lock Apply Discard Figure 73 Information about included TPs and excluded TCs The tab Details displays the logical criterion of the test suite It can be changed Since there aren t any results yet recorded Fi TEMPPO Testmanager Demo Notepad E lel Es Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version lt 2 RCO1 41 1 1 M d b H GP E no tter A Test object RERA RCO Efa 3 Detailed description of the required g Fad 3 4 Required functions of the prodi General Details Export Info Attributes Predecessor Flan EHA 3 4 1 File Administration Attribute Value EAA 3 411 New 2 34444 new gieope Jf J x iE 3 4 1 1 2 New file ope ey 8 3 4 4 Search Functions El 3 4 41 Find a 34 41 41 Find up il 344444 Cases fF 3 44 14 2 WirRur fF 3 4 4 1 4 3 QuickT LEE 3 44 14 4 Test Pe EV 3 4 4 145 UA no Lock Apply Discard Figure 74 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 indicated as test suite attributes in the Meta Data Editor see 5 3 Page 75 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad ioj x Project Test Structure Edt T
44. 1 1 New file opened no changes failed i 3 4 1 4 2 New file opened changes passed Owner Testmanager Updator Testmanager 3 4 4 Search Functions B A 3 4 4 1 Find 3 4 4 1 Find up Type Test Suite fi 3 4 4111 Case sensitive blocked BB 3 4 4 1 1 2 WinRunner Check Stat on hold Description Whole structure i 3 4 4 1 1 3 QuickTestPro Test case not implemented Release canidate 01 EJ 3 4 4 1 1 4 Test Partner Test case not executed EJ 3 4 4 1 1 5 UAI not executed Created 16 02 2012 13 47 29 Updated 16 02 2012 14 36 01 IncludedTPs New Find ExcludedTCs Lock Apply Discard Figure 86 Test Execution Test Case Results 3 1 4 1 5 1 Test execution assistant Test execution assistant supports you in executing each step by displaying each step in an own window It can be called by selecting a step and pressing the button Test Execution Assistant Fi TEMPPO Testmanager Demo Notepad o E ol xj Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 41 1 1 M 4 gt N B No nter QA Test object Version XYZ RCO1 M 3 Detailed description of the required product features 3 4 Required functions of the product Attributes TR Previous Results Plan Execution History FS 3 4 1 File Administration General Attributes Test Steps FX Atomation Requirements History B3411 New ai aaMMM
45. 156 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 3 1 1 Test Case tab Attributes The tab Attributes contains 3 tabs Direct linked Attributes Inherited Attributes and Inheritance e a eas Tab Direct linked Attributes displays the Direct inked Attributes inherited Attributes Inheritance attributes which are directly linked to a test case Regular Validation Priority Error Verification State d Type and Situation radio buttons If all selected test cases have set the same CO 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 a 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 Se Such attributes or new assigned attributes are displayed in red color XO Tab Inherited Attributes displays common aa Ais state of TCs which have inherited attributes fro m a TP Regular 2 Validation Priority Top Radio buttons If all selected test cases with ani Venfica
46. 16 55 05 6 31 kByte timpo 13293207502261 631 1329320750320 png Testmanager 15 02 2012 16 45 50 6 31 kByte Mfirnport_1 329320751 2691 632_1329320761 395 png Testmanager 15 02 2012 16 55 06 6 31 kByte Mfirnport_1 329320751 2691632 _1329320751398 prg Testmanager 15 02 2012 16 45 51 6 31 kByte uninstall joc Testmanager 14 02 2012 14 02 51 2 67 kByte Cancel Figure 207 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 X You are about to upload a file which exceeds the limit of 466 25 kByte v Do you want to continue Figure 208 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 21 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 173 User Manual TEMPPO V6 1 Edition July 2014 Description of Use x web Si Fie E Database E Command EA manual Tes
47. 2 test cases but the plan value was 3 Therefore the requirement is displayed red means Coverage false The following chart types for displaying the data are possible e Horizontal bar chart e Horizontal bar chart 3D e Stacked horizontal bar chart e Stacked horizontal bar chart 3D There is also the possibility to save the chart as jpg or png file by pressing the button Save As Figure 121 Figure 124 and Figure 123 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 107 User Manual Edition July 2014 e Test case IDs Bj Requirement Analysis Requirement Structures AIEE Requirement attributes hd Fitter Calculate chart Data H Detailed Data GEN FN 0010 GEN FN 0030 GEN FN 0020 GEN FN 0030 032 GEN FN 0030 031 GEN FN 0030 020 GEN DB GEN CD 0030 GEN DI 0010 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 lest Cases 4 TEMPPO V6 1 Description of Use aj Chart stacked Horizontal Bar Chart v aap a ey Sort alphabetical C ascending descending Values C All C Only zero values No zero values M Coverage Average number of TC s per requirement 1 41 TC s Percentage
48. 3 1 5 6 2Report of several test suites When selecting the menu item Evaluation gt Report selected gt Several Test Suites Figure 147 is displayed Reports for several test suites are test structure wide Therefore such a personal report setting can only be provided to other test structure users Fi TEMPPO reporting settings Personal Settings Test Structure Settings E Several test suites with attribute fiter 5 charts Testmanager 25 06 2013 12 5 This report setti Figure 147 Report setting test structure wide When creating or editing a report setting Figure 148 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 133 User Manual TEMPPO V6 1 Edition July 2014 Description of Use e to select Result current and Result current and history for a test case Fireman OT Owner Testmanager Filter Created 25 06 2013 12 53 22 wate Updator Testmanager Updated 25 06 2013 12 56 14 Description This report setting is used for evaluating more test suites ox Figure 148 Report of several test suites Settings z x eva Demoen tenon E Notepad RTF Import with TCs ag V1 1 Test Suites for V1 1 2012 02 16 V1 1 1 editable version Test object Version XYZ RCO1 BV _ a
49. 3 3 9 Find and Replace TEMPPO offers a find and replace mechanism By pressing F3 or activating the menu item Edit gt Find and Replace Figure 225 is shown Page 187 User Manual TEMPPO V6 1 Edition July 2014 Description of Use DA Find a Test case Test package Requirement Search in User defined ID Direction for Up B Down Replace with F C o iti Find NextTestCase List Occurrences Replace A lepiace Al Replace n Test Case Repla Figure 225 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 two tabs is the different search content A test case in a test structure can be found via searching for e user defined ID e name e test goal e precondition e postcondition e test step columns instruction input expected e user defined fields A test case in a test suite can be found additionally by its tester s comment actual result and bug ID Only the text fields tester s comment actual result and bug ID can be replaced in test suites A test package in a test structure can be found via searching for e 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
50. 60 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Test Step Cells Mukiline table M Ono for refreshing the cell content when changing the column width i Newsboardl sz Height of muiline rows during editing defaut is 52 ko Test Suite Database mage columns fae ia Ja Waximum width of thumbnail of a user defined image field if it s 1 it s ignored i cile Te in Runner Ja Maximum height of thumbnail of a user defined image field i it s 1 it s ignrored H Universal File H Universal socket gt QuickTest Pra Test Partner HTEMPFO Designer DATS i Ranorex El Commands p Men Command i Javas El Change Management H Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Cancel Figure 56 TEMPPO Test Manager settings For very large images a viewer is integrated which can be started by double clicking the image See Figure 57 x serol Scale iol Datei Bearbeiten Format Ansicht 7 Strg h ffnen Strg c Speichern Strg 5 Speichern unter Seite einrichten Drucken Strg P Beenden Figure 57 External viewer 3 1 3 1 7 Automated test cases TEMPPO 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
51. 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 233 User Manual TEMPPO V6 1 Edition July 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 Y 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 21 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 temporary files are stored e Result Path path where all the result runs are stored e Result viewer path to QTReport exe Page 234 User Manual TEMPPO V6 1 Edition July 2014 Description of Use User Interface p Tree Application Fath DAProgram Files HPiauick Test ProfessionalbinwaTPro exe Test Step Cells Analysis Temporary Path Citemp MHewsboard Test Suite cMempvesut pasha Result Path Ctempiresult I Test Automation i Silke Test Result viewer D vPr
52. Cancel After clicking Finish the new test suite is created based on the settings of the predecessor test suite Now that you have a test suite with all desired test cases you are ready to start for the test execution and recording of results The predecessor information will be displayed if the root node of test suite is selected and tab Predecessor is activated o x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test object Version lt 2 Reis 1 1 1 l za x H d gt b HW E Mo fitter Aa est object Version Xv2 RCO3 a 3 Detailed description of the required g General Details Export Info Attributes Predecessor pian ca Test Suite Test object Version 72 RCO W1 1 1 editable version 2 Test object Version XYZ RCOZ W1 1 1 editable version 3 g Test object Version v2 RCOS 1 1 1 editable version Figure 81 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 one test case are displayed in the new tab Previous Results see 3 1 4 1 8 All results can be analyzed see 3 1 5 1 1 and written to report see Figure 155
53. E Color yellow Figure 188 Assignment dialog Page 164 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad E oj Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test w5 H db WH no fter Notepad RTF Import with TCs i 21 Introduction 5 1 1 Purpose of the document General Test Packages Test Case cE 1 2 Validity of the document 2E 1 3 Definitions of terms and abbreviati HEPES Requirements Plan ZE 1 4 Relationship with other documents oo 418 Overview of the document Inherit attributes a 2 General description of the product Lon Relationship with existing projects m Purpose of the product f Error Werfication State Po Delimitation and embedding of the 5 Overview of the required function Delete TE nets Additional Test Levels Attribute Values Hardware and software specificat amp Device type CAR G 002 Milestone M1 Product users TA Acceptance Test M 3 Detailed description of the required prac TI System Test x i 3 1 Scope of delivery iha 2 Platform Windows 7 64 bit i nces scenarios of interac EI Regressiontest yes ED Test location Offshore 3 4 1 2 Open 3 4 1 3 Save J 3 4 1 4 Exit Apraly Discard G Bu G amp amp amp Figure 189 New common values Not common values displa
54. Edit Buttons all the preconditions from the test case and the test packages above are displayed see Figure 51 If the first test steps of a test case are implemented the preconditions can be hidden by pressing P When pressing P show preconditions beneath the Test steps Edit Buttons all the postconditions from the test case and the test packages beneath are displayed see Figure 51 If the first test steps of a test case are implemented the postconditions can be hided by pressing F When pressing L a new line for Instruction Input and Expected result is inserted The cell height is always 3 lines during editing When pressing Apply the cell height is adapted to the whole line The default cell height can be Page 56 User Manual TEMPPO V6 1 Edition July 2014 Description of Use configured in TEMPPO settings The test step number is created automatically With the two arrows 1 T you can reorder steps by selecting a step and pressing the proper button The test step numbers are updated automatically Test steps can be deleted by selecting them and pressing a General Attributes Test Steps E Automation Requirements History Plan Execution History Figure 51 Test Case Test Step Editor With cut copy paste you copy or move one or more test steps via multi select either within a test case or to other test cases in the test structure By selecting a test step and pressing the corresponding button you
55. Figure 162 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 144 User Manual TEMPPO V6 1 Edition July 2014 Description of Use e Test structure When activating the menu item Find locks menu test structure Figure 162 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 162 is displayed By selecting one or more locks and pressing the button Unlock selected elements locks can be removed If the corresponding user that still believes in his locked items presses the button Save he will get the following message that the lock have be removed in the meantime Lock Exception x fA Saving not possible because the lock was suspended by the administrator Figure 163 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 suit
56. Figure 18 Menu Import Test Cases from Excel When activating the menu Test Structure gt Import Structure gt From CSV Figure 20 is displayed In that dialog you can assign Excel columns to TEMPPO attributes They are automatically selected if their names match Mandatory attributes Name and User Defined 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 40 User Manual Edition July 2014 TEMPPO V6 1 Description of Use Test step The 3 attributes Instruction Expected Input can be assigned with exactly 1 step User Defined Attributes Any UDAs can be assigned with Excel attributes If a value to be assigned doesn t exist it will be created automatically If 2 or more values have to be assigned to an attribute separate it in Excel with Wa If an user defined attribute is deactivated for the test structure it is not displayed as a TEMPPO attribute Requirements Since requirements are arranged in requirement structures they can also be imported as well For each requirement structure a column can be defined A test case can be linked to more requirement IDs separated by Limitations Dea
57. Figure 180 Merge Warning A Applying the function of merging the selected test packages test cases multi merge overwrites SS these items in the latest version Figure 181 Merge information After finishing merge a result summary is displayed to the user see Figure 182 It is not possible to merge an item if its father item doesn t exist in the latest version Page 155 User Manual Edition July 2014 TEMPPO V6 1 Description of Use Gd New Test Case Gd New Test Case Gi New Test Case A New Test Package A New Test Package tce117254 te117252 tc117256 tp117253 tp117251 Success Success Test cases Test Packages could not be merge because its father test package does not exist in latest version Please select and merge it Success Success Figure 182 Merge summary 3 3 2 3 Display of assigned attributes and requirements 3 3 2 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
58. Figure 220 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 179 User Manual TEMPPO V6 1 Edition July 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 FA TEMPPO Testma Project Test Structure Edit Test Execution Evaluation Tools Windows Help e General Pan Requrenents Tense Test Case tempate V Test Case template activated Test Case template valid only for new and updated test cases except viewed test cases V Inherit attributes Attribute New Entry os Lock Apply Discard Figure 217 Test Case Template Attribute Page 180 User Manual TEMPPO V6 1 Edition July 2014 Description of Use AA TEMPPO Tes p S Project Test Structure Edit Test Execution Evaluation Tools Windows Help HM lt gt M oh Beno titer Test Case template Test Result template V Test Case template activated V Test Case template valid only for new and updated test
59. Import wth Tes c 5 Specifications for project management m 6 Obligations of the client Owner Testmanager Updator Testmanager bn 7 Literature E g Apek Created 15 02 2012 16 36 29 Updated 20 02 2012 16 40 10 Type Test Structure TEMPPO Designer DATS T Test level System Test 7 Description Lock Epply Figure 376 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 295 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG 7 1 Creating Task Packages Task 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 F TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test u3 H d gt WH E Mo filter dJ Notepad RTF Import with TCs fam Task Package Ctri At T a 3 Ger Ga Test Package before sil 4 Det Find and Replace F3 2 e SS fi Test Case Ctrl Alt th 5 Spe Bal 6 Obli show Details Dl Test Case before Select ll Owner Testmanager Up
60. 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 290 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fi TEMPPO atw108s2 Unit extension tests n Bio a Project Test Structure Edt Test Execution Evaluation Took Windows Help Test Suite Sample JUnit execution V1 1 1 Uni Samnpes Vector lest Owner atwi lis Createct 10 12 2002 14 21 01 Be unt samples money Money Test Type Test Package Test Category z Descriptio Figure 374 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 corresponding method is called 2 JUnit where the actual result is compared to the expected result in the test method and 3 the classes of the program under test that is executed during the test To run the tests TEMPPO provides its own TestRunner that calls the JUnit test methods and collects their results Thus for executing JUnit tests TEMPPO can be used interchangeably with other JUnit test runners like Junit swingui TestRunner TEMPPO Test Runner Call JUnit test method Return test result JUnit Framework Call method to test Return calculated value Program Under Test Note To execute the JUnit tests the classpath has to contain not only contain the JUnit test classes but also the
61. Key Rep Req Test Figure 343 Project Properties Roles In the tab Roles roles can be assigned to users see Figure 343 By pressing OK the project is created Then the project can be edited and worked on in TEMPPO Page 269 User Manual TEMPPO V6 1 Edition July 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 342 is displayed Copy project peeve So gt Do you really want to copy the project Demo Notepad Only the assigned meta data except requirement structures and user roles are copied Figure 344 Copy project confirmation The user is asked whether he wants to copy the current selected project including all assigned meta data except requirement structures If the user presses Yes the project including assigned users plus meta data except requirement structures is copied 5 5 3 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
62. Men Command SSE El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 298 Settings Command Hew Command User Interface Tree Mame New Command Test Step Cells Analysis Path CAorfice exe H Newsboard Test Suite Arguments Hest doc Database El Test Automation pe Silk Test Hin Runner Universal File Delete gt Universal Socket H Quick Test Pro Test Partner JUnit gt TEMPPO Designer DATS i Ranorex El Commands iD Command SE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Figure 299 New Command 3 3 21 2 12 Change Management Select the change management tool which is used in TEMPPO for adding bugs to test steps Page 239 User Manual TEMPPO V6 1 Edition July 2014 Description of Use fo Change Management l User Interface i Tree Test Step Cells Bugzilla Analysis H Mewsboard ee Test Suite Clear Quest Database El Test Automation pe Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands Active Change Management Tool Cc Telelogic Change JIRA e Nlew Command Se Change Management 3 Bugzill Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 300 Settings Change Management 3 3 21 2 12 1 Bugzilla The following parameters have to be specif
63. Program Files Mercury Interactive win Runner samples dighttests chbxstat o D 3 4 1 1 1 New file opened no changes aM 3 4 1 1 2 New file opened changes or 3 4 1 2 Open oo 3 4 1 3 Save ob bl 3414 Exit 3 4 2 Edit Functions 3 4 3 Print Functions fe 3 4 4 Search Functions ERAN 34 4 1 Find 2 dee a 3 4444 Find up E i dii 4 L eee Script Data 3 4 4 1 1 4 Hew Test Case FP 344 145 New Test Case 1 z lock Apply Discard Figure 58 Automated WinRunner test case The paths to the WinRunner QuickTest Professional SilkTest TestPartner executables are specified in TEMPPO settings see Figure 59 Page 62 User Manual TEMPPO V6 1 Edition July 2014 Description of Use settings O OOOO x WinRunner fl User Interface p Tree Application Path CaProgram Files Mercury Interactive win RunnenarchWwirun exe S Test Step Cells Analysis Temporary Path c AProgram Files Mercury Interactive Win Runner tmp S p Newshoard aTi st Suit Baran oon Result Path CAProgram FilesiMercury Interactiven Runnertmg I Test Automation Silk Test Result viewer CAProgram Files Utra Editwedits2 exe niwersal File H Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex El Commeands Mews Command i SVE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Arguments 2 lt TestFiles gt batch on run create_text_repor
64. QuickT Speichern 3 4 4 1 41 4 Test Pe Speichern unter E 3 4 4 1 1 5 UAI no A Seite einrichten Drucken Beenden Messagebox Nd Editor Pane 2 click cleared Untitled Notepad in title S Look Apply Discard oF Figure 85 Manual Test Execution Test Step Results Test case results are calculated by accumulating test step results So a test case iS fil not executed if all test steps are not executed initial result lil passed if all test steps are passed W failed if at least one test step failed fil blocked if no test step failed and at least one is blocked W not completed if no test step failed or is blocked and at least one is passed not implemented if at least one test step is not implemented stronger than on hold Gi on hold if at least one test step is on hold Test case results are displayed within square brackets following the test case name Page 83 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad ol x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 v1 1 1 3 Detailed description of the required product features El 3 4 Required functions of the product General Details Export Info Attributes Predecessor Plan EH 3 4 1 File Administration 3 4414 New Name Test object Version xyz Rc E 3 4 1
65. Resource m 3 6 3 Security a an lack Apply Discard Figure 39 Manual Test Case General It is also possible to design automated test cases without having any script Attributes Page 48 User Manual TEMPPO V6 1 iol x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test 11 H 4b Woof RE ofiter E A 3 4 Required functions of the product Eb 43 4 1 File Administration sj 3 4 4 1 Mew Ee Recuirements History Plan Execution History eee i5 4 1 1 1 Mew file opened no General Attributes Test Steps E 3 4 1 1 2 New file opened che 3 4 4 2 Open 3 4 1 3 Save oo 3 44 4 Exit EF 1342 Poi puneuens Regular E validation Priority Medium ki o EHE 3 4 3 Print Functions ce 3 4 4 Search Functions Error ie verification State Jin work 3 4 5 Help System Ela 35 External interfaces of the product rA rs 4 User interfaces Additional Test Levels C Attribute Values C 3 5 1 1 Editor Pane 7 T Ta Acceptance Test EP Milestone M1 3 5 1 2 Search Dialog i bas a oe i 3 6 2 System interfaces E Platform Windows 7 64 bit oe a 3 6 Other product features required EP Regressiontest yes a 3 6 1 Performance EP Test location Offshore 3 6 2 Resource fll 3 6 3 Security fll 3 64 Safety b Figure 40 Attributes You have to specify whether the test
66. Roles sersrsriseriis rer eridi nauk EEEE E E 312 13 6 1 Functions to be applied to a role cccccccssssceessseneeneeneeeeeeenssegs 313 Lo UArAdapLEr S aapna O E E E a 316 13 7 1 CDefaultAutoToolAdapter saisenstcncncsse taavontesawmiaihcsatonstanwntaaicnasen 316 13 742 CAPOXIAGGDCCR F ens E EEEE 316 13 7 3 How to implement an adapter cc cccecccceeeeeeeeseeeeeeeeeeeeeeeeeeeeeas 316 eT aot TEIASS OS atc tacia ao aemasctnansens as aan ae ean EA S cans AA 316 ES e7 4922 COGS SNDPP eorr raora 317 13 7 3 3 Implementation and integration StEPS ccceceee cece eee ees 318 User Manual TEMPPO V6 1 Edition July 2014 Overview 1 Overview Managing the test process involves a large number of engineering disciplines like project management risk management high and low level design development and metrics collection Normally testers manage their test cases with Word tables or Excel sheets The main disadvantages are that test cases cannot be maintained easily 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
67. Step 3 All or a subset of JUnit test cases can be selected F Import JUnit Tests x Steps Package Default Values Introduction Enter default values for the new test packages in TEMPPO Select a JUnit test class 3 Select a set of JUnit test enor Details C JSES 4 Set package default values Hame lt generatect 5 Set test case default values 6 Summary Creator Testmanager Created generatedt Twpe Test Package Test Category Description Jv Add to description TEMPPO Extension JUnit co Prey Finish Cancel Fi Import JUnit Tests x Steps Package Default Values Introduction Enter defaut values for the new test packages in TEMPFO Select a JUnit test class 3 Select a set of JUnit test ae Details Cafes 4 Set package default values Document 5 Settest case default values amp Summary Mame Chapter Precondition Page 281 User Manual TEMPPO V6 1 Edition July 2014 JUnit Figure 359 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 individ
68. Sub tree in the test suite and then activate the context menu Set result s and afterwards Figure 101 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 93 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Set Result s E x Set Resut s to Cc passed not executed blocked C not implemented on holed O Overwrite existing results Apply Close Figure 101 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 102 will be displayed This dialog also shows the version tree extended by the test suite beneath the version where it was created During the opening process the adequate version of the test structure is loaded automatically Fi Open Test Suites E x Notepad RTF Import with TCs Tree style ra Wersions only EAA A Test Suites for W11 2012 02 16 le v1 1 1 editable version A Test
69. Suite You can retest bug fix more efficiently Page 80 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Bj Test Suite Wizard E Steps Determine the test suite Introduction Enter test suite name T 2 3 4 Select nodes or subtrees 5 6 Test object Version XYZ RCOS COPY 7 Remove test cases manually Created 16 02 2012 14 52 33 Owner Testmanager Type Test Suite Description Assume the actual result field Assume the bug Id field f TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 83 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 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
70. T 1 3 junit tests extensions Repeated Test Test dy 1 3 1 test Repeated Once funit tests exten why 1 3 2 testRepeated More Than Once funit t Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 28 oy 1 3 3 test RepeatedZero funt tests extens Why 1 3 4 test Repeated Negative unit tests ex Owner Testmanager Updator Testmanager Type Test Package Humber of TCs 2 Test Category a Description parted by TEMPPO tror JUnit Suite jUnittests extensions AllTests Lock Apply Discard Figure 363 Step 5 Names of test packages JUnit test suites Naming of test cases A JUnit test case is implemented as a method of a sub class of TestCase and usually has a name starting with test The test cases in TEMPPO will be named according to the JUnit method name followed by the class name in parentheses testWethod SubClassOfTestCase Fi TEMPPO Testmanager Demo Notepad joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help a Test Structure JUnit System Test V1 lal x Wod b Hg E No filter M AL JUnit E Ea 1 Framework Tests El S 1 junit tests extensions Extension Test General Attributes Test Steps EI Automation Requirements History Plan Execution History o Jul 1 1 test Running Errorin Test Setup qunit t ade 4 2 test Setup Errorin Test Setup junit tes eer aered in tore I a 1 2 junit tests extensions Active Test Test Gy 1 2 1 test ct
71. T Create Playe 17 12 2012 144 17 12 2012 14 17 12 2012 14 17 12 2012 14 17 12 2012 14 17 12 2012 14 Figure 275 Finished Scheduler In Details information about executed test cases are shown 3 3 19 5 Protocol of Scheduler All test case executions of a scheduler can be shown by pressing Show Scheduler Protocol Page 218 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Started T Finished Result Comment EJ New Test Ei New Test Es New Test Ei New Test F New Test New Test New Test Ei New Test New Test Es New Test Ei New Test Hs New Test Ei New Test Ei New Test 15 06 2012 16 06 2072 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 15 06 2012 15 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 01 06 2012 Figure 276 Scheduler Protocol 3 3 20Task 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 T
72. TEMPPO V6 1 Edition July 2014 Description of Use F Requirement Analysis x Requirement Structures m meee Requirement attributes v Filter Calculate G chart E pata r Chart stacked Horizontal Bar Chart 3D v Test Results o 1 2 Sort alphabetical ascending descending Values All C Only zero values No zero values ose Figure 124 Test Suite Requirement Analysis Fi Requirement Analysis i x Requirement Structures Module 14 v Requirement attributes MEE Aand ni e Filter Calculate gl Chart i Data Sort Test Results alphabetical ascending C descending Values All C Only zero values C No zero values cee Figure 125 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 127 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 Te
73. Test Manager 222 Test Automation settings 230 TestPartner 235 UAI 232 T Task lists 219 TEMPPO Administrator 249 LDAP 254 License Server Connection 274 Locks 273 Metadata 257 Projects 268 Requirement structures 264 Roles 250 Uploads 263 TEMPPO Designer Restore designed test cases 300 TEMPPO Manager 244 Test Automation Ranorex 64 Universal Automation Interface UAI 65 WinRunner Quicktest Professional SilkTest TestPartner 62 Test Automation settings 230 Test case Additional test levels 50 Attributes TR 87 Execution History 54 Link Requirements 44 Set test results 169 Tab History 51 Tab Plan 53 Unlink requirement 45 Test Case 10 86 87 Adding more columns 58 attribute 10 Compare 196 design 47 Import from Word 25 Merge 96 Postconditions 55 Preconditions 55 results 83 Page 321 User Manual Edition July 2014 tab Attributes 48 tab Automated 61 tab General 48 Tab Requirement 51 tab Test Steps 56 Test Case Execution 13 67 Test Case Implementation 55 Test case template 179 Filter 183 Test Categories See Test Package categorize customize See Metadata Test Categories Test Creation Assistant 57 Test Design 12 15 Test execution add test package 97 Test Execution 84 add test case 97 automated 92 continue 94 98 finish 99 manual 82 start 68 Test Level 12 customize See Metadata Test Levels Test Package 12 categorize 37 create 34 Test Plan 12 Test Planning 12 14 Test Result template 183 Test step
74. Use l User Interface Tree Test Step Cells Nemsboard Test Suite Database El Test Automation Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro Test Partner TEMPPO Designer IDATG i Ranorex Commands ee Nlew Command leaves El Change Management Bugzilla Clear Quest Telelagic Change Figure 284 Settings Analysis 3 3 21 2 4 Newsboard You can configure if Newsboard window is automatically opened if a test structure is opened Page 226 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Newsboard User Interface Start automatic Test Step Cells Display Newsboard automatically when opening a test structure Analysis aaewshoard Test Suite Database ElTest Automation Silk Test WinRunner Universal File gt lt Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex El Commarnds New Command EES El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Detauks Figure 285 Settings Newsboard 3 3 21 2 5 Test suite You specify if test suites are sorted by name or date in the open dialog User Interface gt Tree Test Step Cells Specifies the sort criteria for test suite inthe open dialog of test suites Analysis Mame Date Newshoard hase El Test Automation be Silk Test Hin Runner Universal File H Universal Socket H Quick Test Pro T
75. User Manual TEMPPO V6 1 Edition July 2014 Description of Use Gh RPreview doc Microsoft Word lel es Datei Bearbeiten Ansicht Einf gen Format Extras Tabele Fenster Livelink Frage hier eingeben x OBE RBIEGRIFG 4aBJ 9 SEE RewB Ad x P standard Arial u F Z U B B oA a scr vs Ges ian Re 1 14 15 With view latest baseline 4 Owner nni Test Goal check the update with view together with a latest version and not a baseline Path Systemtest Introduction Purp ose of the document With view latest baseline 4 Created 10 06 2008 15 33 49 ID tc54636 RPreview doc C DOCUME 1 atw10905 LO CALS 1 Temp RPreview doc SITEMPPO Report 11 06 2008 08 41 Priority High Situation Regular Test Case Type Verification State In Work Type manual Updator nni Updated 10 06 2008 15 33 49 Precondition Offline true Test levels Acceptance Test Test Steps Nr Instruction Input_ _ Expected_ Comment TN ooo Connect to Screen with my available Press Finish to New process updated Validity of the document SHS R ol P B So te Dl i MAK AND ERW UB Englisch US Figure 154 Report Word Ej Microsoft Excel RPreview xls olx G2 Datei Bearbeiten Ansicht Einf gen Format Extras Daten Fenster Livelink Frage hier eingeben 4 e 28 OSA RBSIGRIF OH A aA FIGO Bira 0 F Z usaman FA B a OE PEA HES F
76. Verbindungen werden in der Reihenfolge autgefuhrt in der Netzwerkdienste darauf zugreifen Yerbindungeri LAN verbindung VMware Network Adapter Mnett st Local Area Connection at Wireless Network Connection Bindungen fur LAN Yerbindung im File and Printer Sharing for Microsoft Networks 3 Internet Protocol TCP IP El Client for Microsoft Metworks 3 Internet Protocol TCP IP Figure 352 Order of network interface cards 2 Add TEMPPO start option Open lt Installation Directory gt launcher properties with a text editor Add Djava rmi hostname lt IP address gt to TEMPPO vmargs g TEMPPO vmargs Xms128m Xmx256m DentityExpansionbLimit 1000000 Djava rmi hostname 158 226 235 13 Page 275 User Manual Edition July 2014 6 JUnit TEMPPO V6 1 JUnit Since TEMPPO V3 0 it is possible to manage and execute JUnit test methods with TEMPPO The following paragraphs describe the scope of the JUnit extension 6 1 Terms Testing terms are used differently in the JUnit community and in TEMPPO In order to clarify the meanings the following table serves as a reference Test The entire tree of test structure packages and test cases A hierarchy of test packages test suite Test package and test cases test suite A subset of test cases from the test structure intended for execution in a certain results test Contains recorded test test case A set of test inputs execution conditions an
77. a TEMPPO Editor MW TEMPPO Reporter TEMPPO Guest V TEMPPO Requirement Editor W TEMPPO Tester TEMPPO key User OK Cancel Page 253 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Figure 317 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 which 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 ioi Database Roes Users 3 Metadata Fi Projects Locke E License L X F oe Oooo tastname O Firstname O tog o
78. a gt N GP EE No fiter M 243 4 Required functions of the product 3 4 1 File Administration aa rate 1 New General Attributes Test Steps IE outonstion Requirements History Plan Execution History fe 8 403 4 1 1 1 New file opened no 2 E 3 4 1 1 2 New file opened ch V Inherit 1 3 4 1 2 Open gh M OO Ph OE Requirement ID Requirement Name Requirement Structure 4 1 4 CX d 3 4 2 Edit Functions ma req685 ComponentA R2 Components v1 H E 3 4 3 Print Functions v1 3 4 4 Search Functions __ Required functions of the product req683 ComponentA R3 V1 1 3 4 5 Help System ll New file opened no changes req6s Componente R3 Components 24 3 5 External interfaces of the product 5 5 3 5 1 User interfaces 8 3 5 1 1 Editor Pane A 2 51 2 Search Dialog 0 3 5 2 System interfaces oe pees Figure 42 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
79. address 00 30 05 F BH 40 Started 03 02 2012 03 05 07 Version 5 5 Build 10 14 10 2010 11 33 Licensed for Deparment S15 SOL AD CTE AUT Mame Pichler Rainer Figure 351 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 274 User Manual TEMPPO V6 1 Edition July 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 license server ona computer with several network interface cards When working on a computer with several NICs network interface cards the connection to the license server might cause problems because the wrong IP address is sent to the license server This problem can be solved in two ways 1 Reorder your network cards Open Control Panel Network Connections Menu Extended Extended Settings The NIC connected to LAN must be the first in the list see screenshot Erweitert Netzwerkkarten und Bindungen Reihenfolge der Anbieter Die
80. advanced user you can skip this step and directly choose a previously opened test structure in the Test Structure menu see 3 1 2 2 3 3 1 2 1 1Creating a Project A new project can only be created in TEMPPO Administrator Log on to TEMPPO Administrator and choose the tab Projects Then press the button New Figure 2 is displayed Project properties contains 4 tabs General Roles Test Case Template Test Result Template In the tab General user specifies a unique name description and the possibility to determine if the testers have to add a mandatory comment for each Save operation of a test case In the tab Roles the test manager configures the roles for each tester If a user has no role in a project he won t see it In the tab Test Case Template the test manager appoints defines a basic test case He can configure standard attributes define mandatory attributes or determines if a test case has to be at least one link to a requirement If these conditions are not fulfilled the test case cannot be saved For details see chapter Deus 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 4 2 After pressing the button OK the user is asked if he wants to assign immediately meta data If the user presses
81. 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 173 or the menu item Edit gt Select All C Mew Find and Replace F3 Show Details Select All E Tree b ab Cut Chrl x Copy Ctrl C ey Paste Ctrl gt Delete Delete Order M Refresh recursively Ta Move Ownership gl Analyse selected E Report selected Figure 173 context menu Select All The whole sub tree of the selected test structure or test package s can be selected see Figure 174 Page 150 User Manual Edition July 2014 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluatior Test Structure Motepad RTF Import with TCs Systen M4 gt W o5 E monter AL Notepad RTF Import with TCs F241 troduction E 2 General description of the product a 78 3 Detailed description of the required prod L341 Scope of delivery 2 at E EENET scenarios of interacti i 3 4 2 Edit Functions 3 4 3 Print Functions m 3 4 4 Search Functions 3 4 5 Help System i E 3 5 External interfaces of the product BATEA 3 6 Bua ours ERU iaia F T
82. 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 is updated Page 205 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Figure 253 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 16 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
83. as 27 01 2004 13 27 25 Exit O A Ext file open no changes O Gd Ext cancel file open changes O Gd exit No file open changes Gd Exit Yes file open changes lt 4 Open Open E Open normal 27 01 2004 13 27 14 Fuchs Clemens Open file opened changes 27 01 2004 13 27 18 Fuchs Clemens JEN Save aM Save ME Save as 27 01 2004 13 27 25 Fuchs Clemens Cred Exit fi Exit file open no changes fi Exit Cancel file open changes fi Exit No file open changes fil Exit Yes file open changes Figure 257 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 17 2 1 Import characters of other fonts If you want to import Chinese or Arabic characters the xml header has to be lt xml version 1 0 encoding UTF 8 gt For more information see 8 com 3 3 18Export Test Suite to DOORS This feature allows exporting Test Suite Results of test cases where requirements from DOORS Requirement Structures are linked to DOORS http de wikipedia or wiki UTF 8 and http www utf Page 209 User Manual TEMPPO V6 1
84. automation tab and select Universal File Settings l x Universal File User Interface Tree Drive Letter Jos ew Test Step Cells Analysis Error Path pe Alewsboard a diols Result Path C itmp M Upload resut files to database Result Wiewer c wwinntinotepad exe Adapter temppo test tools adapters CDefautt uto Tooldapter Arguments gt lt lt ResuitFiles gt 2 gt lt lt ErrorFile gt gt amp e B El Test Automation be Silk Test bitin Runner TEES H Universal Socket H Quick Test Pro Test Partner be TEMPPO Designer IDATG i Ranorex El Commands p Men Command SE El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 289 Settings Universal File The meanings of the parameters are as follows e Drive Letter is that letter where path of all test executables start For each test case a path has to be added without a letter drive In this way it is possible to support scenarios where test executables have to be started from varying drive letters You only have to change the Drive Letter setting in the Administrator e Result Path mandatory This is the directory where all the result files are stored e 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 e Error Path mandatory The directory where all error output files a
85. ca Ea 3 4 4 1 4 4 Test Partner Test ca EY 3 4 4 1 1 5 UAI not executed Lock Apply Discard General Details Export Into Attributes Predecessor Plan Figure 91 Test suite Plan 3 1 4 1 7Test Result Attributes There is the possibility to assign attributes to test cases for execution in tab Attributes TR of a test case result Only attributes can be chosen that are indicated as test result attributes in the Meta Data Editor see 5 3 Fi TEMPPO Testmanager Demo Notepad P Ioj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 72 RCO 41 1 1 MH d b H GP EE no tter s Test object Version rZ AEO Eim 3 Detailed description of the required product features Flo 3 4 Required functions of the product Ceneral ES Test Steps E Automation a 5 4 1 File Administration Requirements History Attributes TR Previous Rezuits Flan Execution History m G 85 41 14 New file opened no change ag MH 34 1412 New fie opene changes trite vets O O OSO O Attribute wal ay 3 4 4 Search Functions T ee 3 4 44 Find E t 34 411 Find up BH 3 4 4 1 1 1 Case sensitive blocke R 34 4 1 412 WinRunner Check Ste 3 4 4 1 1 3 Quick TestPro Test ca E 34 44 14 Test Partner Test ca B Al 3 4 4 1 1 5 UAI not executed Figure 92 Test Case Result Attributes 3 1 4 1 8 Previous Results With
86. 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 2 joj x Project Test Structure Edt Test Execution Evaluation Tools windows Help _ Test Structure Notepad RTF Import with TCs System Test w1 lej x H da gt b H GD E no titer Ea 3 1 Scope of delivery 2 3 2 Sequences scenarios of interactions o 4 3 User goals EP Aitomation Requirements History Plan Execution History HAJ 3 4 Required functions of the product General tributes Test Steps oO EE 344 File Administration GHE 3 4 2 Edt Functions User defined ID tcee1 3 4 3 Print Functions aa 3 4 4 Search Functions Rae Case senstie 0 oO BA 3 4 41 Find oo oi 3 4 4 1 1 Find up Owner Testmanager Updator Testmanager ad 3444412 QuickTestPro Created 16 02 2072 11 03 55 Updated 16 02 2012 11 l i 3 4 4 1 2 Find down Type Manual Automated Test Case 5 4 4 2 Replace a 3 4 5 Help System Test Goal The test goal of this test case is to test search function with case ce 3 5 External interfaces of the product sensitive search strings a 3 5 1 User interfaces fl 35141 Edtor Pane ff 3 51 2 Search Dialog _ i 3 5 2 System interfaces ce 3 6 Other product features required 3 6 1 Performance fi 3 6 2
87. 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 view It is important to note that risk oriented testing is no substitute for a complete run of all test cases However it should be taken as a guideline telling which tests have to be performed prior to shipment even when time is short After shipment the remaining tests still have to be carried out Suggestion for the definition of test case priority attributes usually they should be defined in the test plan Top test case whose main concern is testing functionality If this functionality is not implemented properly the customer may be disgruntled Interrelationship to other functionality is very strong such that system behavior may be concerned High test case whose main concern is testing an often used functionality Therefore misbehavior would be immediately evident Strong interrelationship to other functionality or complex algorithm involved Medium test cas
88. cases except viewed test cases General Attributes Test Steps Requirements Pian Mandatory fields Precondition is mandatory V Postcondition is mandatory Lock Apply Discard j Figure 218 Test Case Template Test Step A TEMPPO Tes Project Test Structure Edit Test Execution Evaluation Tools Windows Help M 4 gt Mo E nofiter V Test Case template activated Test Case template valid only for new and updated test cases except viewed test cases General Attributes Test Steps Requirements Pran V At least one requirement must be assigned Lock apy _ Discara Figure 219 Test Case Template Requirement Page 181 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure e5 Structure Syste Tes l V2 General Pian Requirements Template 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 General Attributes Test Steps Requirements Pian Plan Planned tester _No Planned tester Planned test execution time 0 Figure 220 Test Case Template Plan 3 3 4 1 1
89. classes of the program under test Page 291 User Manual Edition July 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 o m n l i The test case was executed and the actual result returned by the program under test matched the expected result as specified in the JUnit test case The test case was executed and the actual result returned by the program 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 292 User Manual TEMPPO V6 1 Edition July 2014 JUnit Table 4 Possible test execution results Fi TEM
90. connection parameters to connect to a database Using button Test you can verify your settings A message will inform about the result of the verification By clicking Connect the TEMPPO Manager will establish a connection to the database user and password are required for Oracle This will cause the tabs Users and Migration getting enabled Information about the database will be displayed on the bottom of the tab 4 2 User management Fi TEMPPO Manager temppo_um l Z ioj x Database 2 Users AW migration __ lastname Firstname Login E Tester E tester2 E Testmanager temppo_um Figure 307 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 245 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Manager User management in TEMPPO Manager is used to create the first super user who has afterwards the rights to do all the administrative work in TEMPPO Administrator without any database password SQLSERVER if a superuser is created the following procedure has to be executed via a console or EnterpriseManager by an sysadmin exec sp_addsrvrolemember N 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 no
91. 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 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 278 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fi TEMPPO Testmanager Demo Notepad f Project Test Structure Edt Test Execution Evaluation Tools Windows Help B TEMPPRO Designer CATG Uedate O x Figure 354 Starting the im
92. defined image field If it s 1 its ignored Image column image Maximum height thumbnail of a user defined image field If it s 1 its ignored Test Step Cells User Interface T Boog Mutiline table E o I Onvoff for refreshing the cell content when changing the column width gt Analysis H Mewshoard s2 Height of muiline rows during editing defaut is 52 Test Suite a Database Image columna u Maroro E Maximum width of thumbnail of a user defined image field tf it s 1 t s ignored H Silk Test Ain Runner E Maximum height of thumbnail of a user defined image field f it s 1 t s ignrored Universal File H Universal Socket H Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands H Men Command SE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Cancel Figure 283 Settings Test Step Cells 3 3 21 2 3 Analysis You can change the settings for analysis Property Description value different colors Label length for progress 100 Limits the label length of the chart requirement names in order to keep the chart readable Creation Progress Label Version Specifies the text to be displayed on creation progress chart labels Execution Progress Label Date Specifies the text to be displayed on execution progress chart labels Page 225 User Manual TEMPPO V6 1 Edition July 2014 Description of
93. designed Test Cases i Motepad RTF Import with TCs Eb re TEMPFO Designer DATO Tasks 11 New Task Package General Attributes Details Requirements History Plan 7 L 2 Introduction Sa 3 General description of the product Inherit attributes i A 4 Detailed description of the required product teal n E 5 Specifications for project management A 6 Obligations of the client Regular Validation Priority Top r i 7 Literature 8 Annex Error Verification State Designed Additional Test Levels Attribute values i E TP Type User case x Lock Apply Discard Figure 379 Design Test cases After activating the menu item Design Test Cases the window Connection Status Figure 380 and TEMPPO Designer IDATG itself are displayed Page 297 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG F Connection status E X Locking structures OK Prepare data ating for TEMPPO Designer IDATGI to connect Figure 380 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 i
94. 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 wv WW when Property is All name is Version of merged Item e Action possible values add change delete merge e Info additional comment for changing reason Page 51 User Manual Edition July 2014 e Version of history entry With button Display all entries all history entries of all test structures can be loaded Action is depending on Property possible values e Requirement add delete e UDA add delete e Test Level add delete e Steps add change delete e General change Info Name User defined ID or Test goal e All merge M aby 72 Eome QD Notepad RTF Import with TCs H E 1 Introduction 5 Ge 2 TEMPPO Designer IDATG Tas 2 1 Use case File gt New e io General description of the produc E 3 1 Relationship with existing pi E 3 2 Relationship with earlier anc E 3 3 Purpose of the product _ Jil 3 4 Delimitation and embedding ii 3 5 Overview of the required fu 2 3 6 General restrictions E 3 7 Hardware and software spe E 3 8 Product users T 4 Detaled description of th
95. in Containing t st Structure aqd 1Y ue aw gt lt ATTLIST TEST RESULT name CDATA REQUIRED gt lt if zero length then name New Testcase generated gt lt if it already exists in containing test package add 1 2 gt lt ATTLIST TEST RESULT type Manual Automated Manual gt lt ATTLIST TEST RESULT tester CDATA REQUIRED gt lt ATTLIST TEST RESULT tested CDATA REQUIRED gt lt ATTLIST TEST RESULT situation Error Regular Error gt lt ATTLIST TEST RESULT val ver Validation Verification Validation gt lt ATTLIST TEST RESULT priority Top High Medium Low Top gt lt ATTLIST TEST RESULT state Designed In Work Ready for Review Ready Approved Designed gt SITATILIOT TEST RESULT Inher Pequirements true Talse Tialsen gt lt LATTLIST TEST RESULT result Failed Passed Not executed Blocked Not completed Not implemented On hold Not executed gt lt ATTLIST TEST RESULT lastupdate CDATA IMPLIED gt lt ATTLIST TEST RESULT lastupdateby CDATA IMPLIED gt lt ELEMENT REQUIREMENT DESCRIPTION gt lt ATTLIST REQUIREMENT REQUIREMENTID CDATA REQUIRED gt lt cannot be zero length string gt lt if it does not exist it will be automatically created gt lt ELEMENT TEST STEP RESULT INSTRUCTION INPUT EXPECTED ACTUALRESULT BUGID USR FIELD gt lt ATTLIST TEST STEP RESULT test step id CDATA REQUIR
96. in prior versions You can restore the version of a test structure by activating it in the versions dialog with button 2 Activate selected version You cannot change a test structure in a version which is not latest However you can create a branch of a structure version and apply changes to that latest version in the branch When you activate version 2 V2 and try to insert a new test package you will get the following message You are trying to change atest structure that is already checked in 1 The only possibilty to make changes is to create a branch Do you want TEMPPO to create a branch for yout Figure 235 New branch confirmation Pressing No will abort the action Pressing Yes will create a new V2 2 branch a branch latest version of the test structure and the test package in this branch latest version The latest version in the branch will automatically be activated and can be edited like the latest version in the main line usually Page 194 User Manual TEMPPO V6 1 Edition July 2014 Description of Use called main latest One version can have several branches which can be created in the same manner Motepad RTF Import with Tos oN Edit ERI Test Suites for W1 1 2012 02 16 Cy Check In Wl 44 editable version Eales Activate O A Test Suites for W21 2012 02 16 iF Merce i FE Menge O ke W2 44 editable version eae i B23 gt Tree style ie VE Versions only WT eciteab
97. interactions ae E 3 3 User goals 3 4 Required functions of the product O B 3 4 1 File Administration EGR S411 windows Login gt il 1 1 1 Login o B E 3 4 1 2 New General Attributes Test stepa E Automation Requirements History Plan Execution History User defined ID teraz Mame fLogin Owner Testmanager Updator Testmanager Created 20 02 2012 10 26 12 Updated 1 02 2012 10 56 57 Automated Test Case Lock Appl Discard ey of hanual fie L 3 4 1 3 Open Pes O 3 4 1 4 Save Figure 230 Newsboard 3 3 12Versioning 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 very powerful but expensive one like ClearCase to a cheap one with restricted functionality would be a challenge For example ClearCase offers attributes for each administration unit VSS does not have such commands Therefore the developers of TEMPPO decided to implement an own solution for maintaining versions of test structures with test cases In TEMPPO it is only possible to check in an entire test structure baseline where whole means the hierarchical order of all test packages and test cases as well as their data In contrast to other CM tools where check in and check out are separate steps checki
98. 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 222 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 185 User Manual TEMPPO V6 1 Edition July 2014 Description of Use E4 G TEMPPO Designer IDATG Tasks H General description of the product Figure 223 Requirement Structure Activation 3 3 7 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 186 User Manual TEMPPO V6 1 Edition July 2014 Description of Use A list of all TEMPPO users is presented to the current user see Figure 324 on page 258 A new owner of
99. is no element anymore a message is shown see Figure 226 Find and Replace Xx P n LI Mo more occurrences Found Figure 226 No more occurrences found e List occurrences With the button List occurrences the searching result is shown in a list see Figure 227 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 227 List occurrences 3 3 9 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 package is locked the test case package isn t changed e g the next one is searched e Replace All in Test Case package To use this feature a test case package have to be selected first otherwise the button is disabled At first a test case is searched and selected The user has to click again for replacing all occurrences in this test case package If the test case package is locked the test case package isn t changed Page 189 User Manual TEMPPO V6 1 Edition July 2014 Description of Use e Replace All The selected field of all test cases packages is changed which contains the text After replacing all a message is shown see
100. of requirements covered by TC s 70 59 4 gt aee Figure 120 Planned coverage Requirement Structures MA La a Requirement attributes e a ae Chart Stacked Horizontal Bar Chart z chart E Data E Detailed Data 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 D Test Cases 16 20 x Sort alphabetical ascending descending Values C all Only zero values No zero values Coverage Average number of TC s per requirement 8 00 TC s Percentage of requirements covered by TC s 100 00 oe Figure 121 Test Structure Requirement Analysis Page 108 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Requirement Analysis Demo Requirement structure 7 Stacked Horizontal Bar Chart v Requirement name 1 Requirement name 10 Requirement name 11 Requirement name 12 Requirement name 13 Requirement name 14 Requirement name 17 Requirement name 18 Requirement name 19 Requirement name 2 Requirement name 20 Requirement name 21 Requirement name 22 Requirement name 23 Requirement name 24 Requirement name 29 Requirement name 3 a tis ian a tis H
101. 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 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 15 User Manual TEMPPO V6 1 Edition July 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
102. scheduler with start time and a sequence of test cases see 3 3 19 1 e Delete a scheduler Remove a scheduler for a test suite see 3 3 19 2 e Import a scheduler Import an existing scheduler from other test suites see 3 3 19 3 e Run a scheduler Execute all test cases selected for scheduler now or at Start time see 3 3 19 4 e Protocol of a scheduler Visit all results set by scheduler see 3 3 19 5 3 3 19 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 214 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 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 5 Scheduler Start Time 17 12 2012 00 00 Ei Create Player E Create Player 1 Ei Edit Person D 0O ppa Figure 268 New Scheduler 3 3 19 2 Delete Scheduler F
103. so that all results of a test case in a sequence of test suites can be shown Page 79 User Manual TEMPPO V6 1 Edition July 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 82 where you can select an existing test suite that will be copied to a new branch Bj Test Suite Wizard f Steps Select Test Suite x 1 Introduction Select an existing Test Suite 2 Choose creation mode 3 Select an existing Test Suite Notepad RTF Import with TCs V4 441 1 Test Suites for V1 1 2012 02 16 Ef V1 1 1 editable version Test object Version XYZ RCO1 16 02 2012 Test object Version XYZ RCO2 16 02 2012 Test object Version XYZ RCOS 16 02 2012 V2 editable version TEMPPO Test Suite Generator lt lt Prey Next gt gt Finish Cancel Figure 82 Copy Select a test suite In the final step test suite name and comment are to be specified Additionally you can configure if you want to get Actual Result and Bug ID of source test
104. 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 106 and use them also in the latest version later on Page 97 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad iol x Project Test Structure Edt Test Execution Evaluation Toole windows Help e Test Structure Notepad RTF Import with TCs System Test 111 1 M d4 b H GP E no ter l QU Notepad RTF Import with TCs 2 HE 1 Introduction i L 2 General description of the product General Attributes Details Requirements History Plan 2 8 3 Detailed description of the required product 1 A 3 1 Scope of delivery ID ltp721 a 3 2 Sequences scenarios of interactions m 3 3 User goals l INew Test Package onthebranen OOOO O 2 Se 3 4 Required functions of the product Mame Mew Test Package on the branch 24 H 3 4 1 File Administration Sr 293 444 New lf 3414141 New fle opened no Created 16 02 2012 15 50 36 Updated 16 02 2012 15 60 37 3 4 1 4 2 New file opened ch Z 13 414 3 New Test Package E 3 4 1 2 Open Number of TCs 0 a 3 4 1 3 Save o m 3444 Exit Test Category 3 4 2 Edit Functions 3 4 3 Print Fu
105. 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 fields for automated TCs new attribute assignments deleted attribute assignments new requirement assignments and deleted requirement assignments If a change in test steps is detected all steps of XML file are applied Changed TPs Detected changes Name description test category change new delete change document path document name document chapter new attribute assignments deleted attribute assignments new requirement assignments and deleted requirement assignments Page 206 User Manual TEMPPO V6 1 Edition July 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 17Test 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 TE
106. 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 shown The imported test suite filter is shown the first time when a test suite is opened and the filter dialog is called or the filter combo box is clicked 3 3 15Test 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 1L6Test 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
107. 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 The data can now be transmitted to SITEMPPO Proceed Qxsxxx i Yes Send data to SiITEMPPO No Save data as XML File Nein Abbrechen Figure 383 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 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 299 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG Ei TEMPPO Schlosser Dietmar Notepad i l O x Project Test Str
108. the selected item can be chosen see also 5 5 6 3 3 8 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 224 Copy with Meta Data is only those assigned to opened project all used in selected subtree Mote Insensitive tems are not used in selected subtree V Test Level J Test Category I Attribute M Upload Additional Test Step Column oren Figure 224 Copy Meta Data There you can choose from three possibilities to paste e Copy without Meta Data Only the selected part of the structure is copied but not the metadata e Copy with Meta Data o Only those assigned to opened project The selected part are copied only with those metadata which are already assigned to the target project o All used in selected sub tree The selected part with all assigned metadata is pasted to the project B Metadata which is not yet assigned to the target project are implicitly assigned to it The third possibility is disabled if the user has not the right Copy All After opening the window the metadata types checkboxes are selected which are used in the copied sub tree You can also un select each metadata which should be pasted By clicking OK the items are added to the test structure
109. the test suite Only the selected ones will be in the new test suite Page 81 User Manual TEMPPO V6 1 Edition July 2014 Description of Use UU x Steps Choose test cases included with following test result 1 Introduction 2 3 4 Enter test suite name 5 Test suite should include test cases with following results NV failed Slee j herp passed V not completed V not executed V not implemented TEMPPO Test Suite Generator lt lt Prev Next gt Finish Cancel Figure 84 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 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 f
110. type J ED yes a Regressiontest EF CAR F A002 Device type al EF CAR F A003 Device type 4 Device type Device type car G oo4 aE Device type Figure 41 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 50 User Manual TEMPPO V6 1 Edition July 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 42 shows the test case 3 4 1 1 1 New file opened no changes which inherits from the test package 3 4 Required functions of the product the requirements ComponentA R3 inherits from the test package 3 4 1 1 New the requirement ComponentA R2 has a link to the requirement ComponentC R3 Fi TEMPPO Testmanager Demo Notepad l loj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help z Test Structure Notepad RTF Import with TCs System Test v1 M
111. 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 293 User Manual TEMPPO V6 1 Edition July 2014 JUnit If the classpath contains two class files with the same fully qualified name the file with the newest build date will be loaded Anonymous inner classes By statically creating the tests using anonymous inner classes that are not public the tests from this suite will not be executeable by TEMPPO With a JUnit TestRunner this construction works because there JUnit suites are executed as a whole whereas TEMPPO tries to instantiate and execute each test case by itself Sample code public class MyTestPkgWithStatSuite extends TestCase public MyTestPkgWithStatSuite String name super name public static Test suite TestSuite suite new TestSuite MyTestPkgWithStatSuite suite addTest new MyTestPkgWithStatSuite testSomethingRight protected void runTest testSomethingRight FE tet rn SuLte public void testSomethingRight assertTrue true Page 294 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG 7 TEMPPO Designer IDATG TEMPPO Designer IDATG is your gateway to professional and cost efficient test aut
112. 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 305 User Manual TEMPPO V6 1 Edition July 2014 Terms Test Structure The entire tree of test packages and test cases Test Suite A subset of test cases from the test structure intended for execution in a certain test their recorded test results Version A version denotes a certain state of an administration unit at a certain time There are two kinds of versions i checked in version which can t be changed any more and ii checked out versions Usually versions follow a decimal notation scheme starting with 0 or 1 For each new version the version number is incremented Version Tree A tree representation of all versions including all branc
113. 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 12 User Manual TEMPPO V6 1 Edition July 2014 Introduction names test goals and the links to the requirements are fixed This is useful because you will quickly get an overview of the number of test cases and their distribution to test packages And it is still early enough to set corrective measures if e g the number of planned test cases turns out to be way too high or even too low For a high rate of error finding it s suggested to make use of well tried test case design methods like Equivalence Class Partitioning or Boundary Value Analysis for details refer to 2 Test Case Implementation In this phase three main tasks have to be accomplished i writing manual test cases test step definition ii writing automated test cases test script programming iii implementing test frameworks Only the first 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 wor
114. 0 end 09122008 oo Figure 158 Test execution progress graph within one Test Suite 3 1 5 6 6Report Templates Some report templates are provided in your TEMPPO installation directory These are mainly templates for Test plan and Test execution report 3 1 5 7 Import from another projects You can import report settings from another project You have to press the button Import report setting from another project then the following window opens x El Demo Notepad ana a Eeport Template Figure 159 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 142 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 1 5 9 Import from XML TRP file For importing report settings press the button Import report setting from XML or TRP file and then the following file dialog opens x Look in Ee Eigene Dateien gl ii E E KA 5 Aktien 5 Media Go TE 9 Artikel 9 My Meetings B Audi Eigene Musik CC_TestFactory 2 Eigene Bilder fm Downloads io hy Podcasts 4P Eigene Datenquellen oo My Received Files ca rrorReport20d 21 3021 30732 Eigene Wi
115. 00 Sia TEMPPO Reporter Schema Owner 13 02 2012 13 04 01 Sf TEMPPO Requirement Editor schema Owner 13 02 2012 13 04 03 Ss TEMPPO Superuser schema Owner 13 02 2012 13 03 59 TEMPPO Tester schema Owner 13 02 2012 13 04 05 Figure 314 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 251 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Fi Role properties x General Details amp 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 4 Test package Assign test categories Edit 4 ad 5 4 Link requirements Merge Test case Assign test case attributes Assign test levels Edit EA at Link requirements T r r r r r r r Cancel Figure 315 Role properties General Details The functions are predefined and cover the whole functionality of TEMPPO Administrator and TEMPPO Level of access of the function e New or execute e Edit e Delete e Read e Move Ownership e Consider User objects can only be deleted if the user is the owner of the object In the dialog only the possible checkboxes are shown E g report It only makes sense and is only possible to execute a report Therefore only the
116. 014 Description of Use x W224 VI Fl Mew file opened no changes El General be User defined ID tc636 fa Mame Mew tile opened no changes i Owner Testeri Updated 2012 02 20 i Type manual The test caze purses the aim of testing the function Mev Fl Mew file opened no changes Et General beUser defined ID tc636 ee Mame Mew file opened no changes i Owner Testeri Updated 2012 02 16 Type manual The test case purses the aim of testing the function H Attributes Attributes Fi Test Steps Test Steps HS gt Eee Es Bg New atep is added on brancho o o gt E Automation Automation Et Requirements E Requirements beregbe bereqhe reqees a ie reqhed pane oe reqees dese Plan Plan 4 4 Cancel Figure 242 Compare differences 3 35 14Filter Users can see their test structures and test suites in a filtered way by creating and selecting filters i e for the purpose of hiding test cases that are not of interest All fixed and user defined attributes can be used to define a filter criterion Test structure filters are available for test suites Test Suite filters which are including result or tester are not available for test structures 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
117. 183 Page 160 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Merge Warning eS Appling the function of merging the selected test packages test cases mull merge overamites SS those tems in the latest version Figure 183 Merge information After finishing merge a result summary is displayed to the user It is not possible to merge an item if its father item doesn t exist in the latest version D New Test Case tc117254 Success D New Test Case tc117252 Success E 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 QA New Test Package tp117253 Success By New Test Package tp117251 Success Figure 184 Merge summary Page 161 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 4 1 Test Suite After activating the menu Edit gt Show Details the tab Attributes TR is displayed e tab Attributes TR see Figure 185 The attribute values that are assigned to all selected test cases are displayed as usual The attribute values assigned to not all test cases are displayed in a special color grey background color New added attributes are displayed in red color Fi TEMPPO Tester1 Demo Notepad iol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Test object Version lt 2 ARCOS COP 41 1 1 Wo d b WH E Mo fitter
118. 2 16 Fl editable version A Test object Version XvZ RCO 16 02 2012 oA Test object Version XYZ RCO2 16 02 2012 E Test object Version XYZ RCO3 16 02 2042 A Test object Version XYZ RECOS COPY 16 02 2012 az o EA Test Suites for W241 2012 02 16 Fite 1 editable version A version 2 of Test obeject RCO1 16 02 2012 J editable version Tree style Yersions only Labels only i Yersions and Labels ClearCase style Order fe ascending D descending Cancel Figure 107 An extra branch for each test execution Typically each test execution has its own branch which is directly beneath the main line and contains just one test suite This is because faults in test cases are usually corrected in the main line of the version tree versions 1 2 3 4 in the example If every new test execution branches directly off the main line it will always have the most up to date definitions of test cases Grouping test executions within a common branch is possible yet not recommended due to the suggested procedure described above Only highly experienced users should consider departing from this approach 3 1 4 7 Test case execution with an exported test suite In projects for certain domains tests can t be executed in the office on the desktop PC but must be executed offline e g in a test car for the automotive domain For this purpose TEMPPO provides features which enable e to export a test suite into an
119. 3 3 3 4 2 Test result templateS ssnessssssnsrsnsunsnrunsnrnnrnrnnennrnrsnrnrnnne 183 I ADUTE ACE V QUI ON ai aa A a 184 3 3 6 Requirement Structure activation ssssssssssessnsnsnsunsnsnnnsennas 185 S MOVE OWIMEONSIN Dis cetiatas conics aeaa a 186 3 3 8 Map of Meta Data project wide COPY c ccc ece cece ee eeeeeeeeeeeeneees 187 3 5 9 FING ang REDI ICE uieii wade usta NE r ton dewlereweduint 187 3 3 9 1 1 Find Test Case Test Package ccecesseeeeeeceeeeeeeeseees 189 3 3 9 1 2 Replace Test Case Test Package ccceecccceeeeeeeeeseees 189 Soak AD DIY F DISCaN aee teases ceuteaceeeadicade E 190 3 3 11 INGW SD Cal Cur sastenscsncinst E nen oe aan enataneetaai owed 190 Seek VEFSN Orori S aE AE E Peete cece meatier mee emcee 192 3 3 13 COMP ai Gsan5 aemradecseeraccaaserise EE 196 Bone TENOR eara er aro eider ia 198 FLAL PFEGENNEG CES airos N TE AAN Eini 198 rL Create E aere A O ENAA Aani 199 FAAS Change MtO arosine aa a a N 200 2AA Delete TILER crrr aaan 201 3 3 14 5 Defining the filter criterion sssssssssussnnunsnnnnrnrnnensrnennrrrnens 202 LAG JEGIE TIECI ChICEFION sinicsccasvnithindnatsanewepeitecaumisananereiticanntonwexe 204 S264 EXPO TILER iseuninectiescccseiaihinanatasetweneiuecaenaieseeeiiieawneceeiniks 205 ILAS PDO TICS i aiea naa ENEE E AAEE 205 JL MESC SERUCTUTEC XML EXPO E crara a EE 205 3 3 16 Test structure XML Update ssssesssssnssrsrrnrrrenrrrrsrerrrrrnrrrenr
120. 3 3 2 Multi selection Mode sssssesssnnsnssnsnsnnnnnnernesnnnrnnnnennrunrnrnnsnrenne 149 Seok MuU Selectors aana E E AEA 150 3 3 2 2 Multi selection merge of unchanged TPs and TCs 155 3 3 2 3 Display of assigned attributes and requirements eeeeee 156 Deos AL TOSE OUUTE erde clea aetanccdatsanse settee sai nascent kesdauianccn 156 3 3 2 4 Multi selection merge of changed TPs and TCsS 000000s 160 JoL dL WES SUNG ceirar ena rneer orr Eer 162 3 3 2 4 2 Filter in multi selection mode sssssssssssssnssrensrrsrrrrrrrsnse 162 32A Sew NEW ASSIGQNINGINS cessera nn se a EA EUER 164 LAO MOVE sOWMEESIID ascenics sie enina i Niani 167 551257 DEEE a A ee 168 33 2 0 SETCSE FSS UES ain eaa a a a 169 3 3 3 Hyperlinks and UploadS ossosnesesnssnnsnnnussnnsnsnennnnrnnrunrnrsnsnrenne 170 Jdal CREATING NYDEFIINKS seicsetsnenisvadonieacerebcasscamniagiaanenievcaonteesevens 170 JsJ EdE NYDEnINKS Setorani ENEA 177 S101 REMOVE NY DETINKS errre sininn nena sents 177 S154 DOWNIOAG AN upload caseveunssacensy iea E EAE 177 3 3 4 Test Case TemplateS cicccsccscscecsvessaoanasvedetarssoaranansaaecaaacenerseden 178 3 3 4 1 Test case template iivirirrisrrinricieiririciii anini aidaa 179 J21 Create New test CaSe uiia i EE E O EENE EEY 182 3 3 4 1 2 Unlock save existing test CaSe sesessrrerererrrrrrnrerrrrrrue 183 3 3 4 1 3 Test case template and filter sssossesssrensrrersrrerrnrrrrsnne 18
121. 3 4 Required functions of the pre Datei Bearbeiten Format Ansicht EP 3 4 1 File Administration TE Stra N B moti H E ffnen Strg 0 Speichern Strg 5 3 441 12 Net le o 0 i w s fie l Speichern unter 0 3 4 1 2 Open l 3 4 13 Save Seite einrichten 3 4 1 4 Exit Drucken Strg P 1 3 4 2 Edit Functions _ o EE 3 4 3 Print Functions Beenden EH 3 4 4 Search Functions 3 4 4 1 Find 3 4 4 1 Find up i fi 3 4 4111 Case EJ 3 4 41 1 2 Quicl B 5 4 4 1 2 Find down 2 Upload 3 4 4 2 Replace i 3 4 5 Help System X Delete BAN 3 5 External interfaces of the pri aste Ctrl i B 3 5 1 User interfaces PER i B E n paste mage Reference R Figure 55 Upload new picture e Upload If you activate the menu Upload a file open dialog opens where you can select a file jpg png gif which is uploaded to the database e Delete If you activate the menu Delete the image is deleted e Paste If you activate the menu Paste the screen shot which is currently in the clipboard is pasted to the cell and also uploaded to the database The menu is disabled if the clipboard is empty e Copy If you activate the menu Copy the 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
122. 4 1 1 1 New file opened ne 3 4 1 1 2 New ffile openec 3 4 1 1 5 New Test Package 6 Select All ma 3 4 2 7 Time Date ee a Word Wrap set Font ome 1 2 WinRunne 3 4 3 Print Functions 13 QuickTest HL 3 4 4 Search Functions a A544114 Test Parin l m 3 4 5 Help System l sie gt 344715 UA Hl 3 5 External interfaces of the product eee J i412 Find down 43 6 Other product features required E E E 4 Specifications for project management Pk System L 5 Obligations of the client i Ea 3 5 aA PENS of the product h 6 Literature 0 7 Annex E a b Figure 175 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 176 Page 152 User Manual Edition July 2014 F TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution E Test Structure Notepad RTF Import with TCs H 4b H E Mo filter ote E 3 3 User goals a a 3 4 Required functions of the product Er a 3 4 1 File Administration o Ee a 3 4 44 New a fl 3 4 4 1 4 Mew file openec 3 4 1 1 2 New file openec fH 3 4113 New Test Packe E i 3 4 2 1 Undo i 3 4 2 2 Cut 3 4 2 3 Copy Zi 3 4 2 4 Paste 3 4 25 Delete E 3 4 26 Select Al T 3 4 2 7 Time Date ae
123. 5 Speichern unter E 3 4 1 1 2 Mew file o pen n 3 4 1 2 Open a 3 4 1 3 Save 3 4 1 4 Exit 3 4 2 Edt Functions cae 33 4 3 Print Functions E a 3 4 4 Search Functions EMG 3 4 4 1 Find o gt EF 3 4 4 11 Find up fi 344111 Case fl 344141 2 Quicl 7 3 4 4 41 2 Find down _ ol 3 4 4 2 Replace aE Pe bn 345 Help System i I 4 3 6 External interfaces of the pre a 351 User interfaces z lock Apply Discard Seite einrichten Drucken Strg P Beenden Untitled Notepad in tithe bar Figure 54 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 structure dtd gt lt TEMPPO EXCHANGE gt lt TP name HumanResources gt lt TC name Search_1T1 test_goal
124. 6 Literature EJ automation Requirements History Plan Execution History General Attributes Test Steps Expected Merge Lock Apply Discard bo Figure 72 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 73 Page 74 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F TEMPPO Testmanager Demo Notepad lel xj Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Suite Test abject Version swe ROO v1 1 1 H d gt b WH ho fter A EEA 3 Detailed description of the required g Ell 3 4 Required functions of the prodi General Details Export Into Attributes Predecessor Pian Eh 3 4 1 File Administration 3 444 New Mame Test object Version v2 RCO g 3 44144 New file ope i 3 4 1 41 2 New file ope Owner Testmanager Updetor Testmanager 7 3 4 4 Search Functions El 3 4 4 1 Find a 3 4 4 414 Find up Type Test Suite fi 344111 Cases a HEE 3 4 4 1 4 2 WinRur Description wwihole structure fF 3 4 4 143 QuickT Release canidate 01 LEE 344114 Test Pe H E 344411 5 UAI no Created 16
125. 6 45 46 Updated 16 02 2012 08 50 22 Ela 3 4 4 Search Functions o H D34441 Find 3 4 4 2 Replace Mumber of TEs 2 i i E 3 4 5 Help System E 9 3 5 External interfaces of the product Test Category MERSE E E 3 6 Other product features required a Fal 4 Specifications for project management Description This section of the software requirements Ee 5 Obligations of the client specification must define the product features a 5 Literature requested prescribed by the client and agreed to by H UO 7 Annex the development department These features contain all functions interfaces and other product features A number of points should be taken into account in describing the features Owner Testmanager Updator Testmanager Type Test Package Every required feature should be Uniquely identified be eee see ls eee oe es ee ee ths ee eel be Figure 30 Assigning a test category When creating test packages you may determine appropriate test categories Normally you start test case design with the chapter Required functions of the product that should cover all task based tests In further steps of test case design you identify GUI layout tests in chapter External interfaces User interface Such test packages should be given the test category GUI layout test They pursue the aim to cover tests for input syntax check completeness of GUI masks etc Furthermore you categorize the test packages below Other p
126. Copy Upload 60 Delete Upload 60 Paste Upload 60 Pictures in columns 60 Reference to Upload 60 Upload 60 Uploads 60 Test Step See Test Case tab Test Steps results 82 Test structure TEMPPO V6 1 Index delete 270 Extend 33 Freeze unfreeze 272 Transfer 33 Transfer to other database 33 Version 20 XML export 205 XML update 205 Test Structure 12 18 create 18 generate test cases 25 generate test packages 21 import RTF document 21 31 open 20 properties 18 20 reopen 21 Test suite based on a predescessor 76 Based on previous results 81 copy 80 delete 270 Export 207 Freeze unfreeze 272 Import 101 208 tab Attributes 75 tab Details 75 Test Suite 13 87 create 68 Tools TEMPPO Designer IDATG 295 U User Management See Administration User Management See Administration User Management V Versioning 192 Page 322
127. Create 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 218 Test Case Template Test Step is ticked e if a postcondition is entered and the corresponding checkbox in TCT see Figure 218 Test Case Template Test Step is ticked e if a test goal is entered and the corresponding checkbox in TCT see Figure 216 is ticked e if at least one requirement is linked and the corresponding checkbox in TCT see Figure 219 is ticked e if an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 217 is ticked Page 182 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 4 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 218 is ticked if a postcondition is entered and the corresponding checkbox in TCT see Figure 218 is ticked if a
128. ED 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 if it does not exist it will be automatically created gt Page 310 User Manual Edition July 2014 lt ELEMENT USER DEFINED ATTRIBUTE EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE length string gt lt if it does not exist lt ATTLIST USER DEFINED ATTRIBUTE length string gt lt if it does not exist TEMPPO V6 1 Appendix name cannot be zero it will value it will CDATA REQUIRED gt 5 be automatically created gt CDATA REQUIRED gt lt be automatically created gt cannot be zero lt ELEMENT USER DEFINED ATTRIBUTE TRESULT EMPTY gt lt ATTLIST USER DEFINED ATTRIBUTE TRESULT name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically lt l l cannot created gt Ss cannot created gt be zero length string gt lt i
129. EH E 3 4 2 Edit Functions AL 3 4 3 Print Functions 3 4 4 Search Functions BRL 344A Find 3 44 2 Replace i i 3 4 5 Help System Fy 3 5 External interfaces of the produi E A 3 5 1 User interfaces ft 3 6 1 2 Search Dialog 3 5 2 System interfaces TEMPPO V6 1 Description of Use O x x General Attributes Details Requirements History Plan Document P O E Mame Chapter Precondition Precondition Detailed description of the requir External interfaces of the product User interfaces Editor Pane Postcondition a 3 6 Other product features required 1 Performance 2 Resource Security 4 Safety 5 Portability 6 Reliability 4 Maintenance 6 Reuse 4 Usability H S 4 snecficatiaons for oroiect oneik F Postcondition User interfaces Editor Pane Figure 32 Test package without reference to a document name or chapter First of all you create a new test structure or open an existing one After this the test structure can be filled in the following ways Importing an RTF formatted document Import Test Cases from Excel TEMPPO is able to import test cases from an Excel list First you have to save your Excel file as csv and select a test package El Import Structure From RTF Document Update b l From XML Document a Export Structure From Ranorex Document Apply requirement updates From CSV
130. EMPPO 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 167 Locks found in the database on starting quitting TEMPPO 3 2 2 Refreshing 3 2 2 1 Refreshing manually 3 2 2 1 1 Reloading the whole test structure test suite You can reload the whole test structure test suite by pressing the reload button ES on top of the tree see Figure 168 This has the same effect as manually reopening the test structure test suite Ei TEMPPO Testmanager Demo Notepad E Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x a Test Structure Notepad RTF Import with TCs System Test W5 b i A Notepad RTF menej whole tree H 1 Introduction 2 General description of the product i 5 3 Detailed description of the required prod 3 1 Scope of delivery a 3 2 Sequences scenarios of interacti 3 3 User goals i 3 4 Required functions of the product EL 3 41 File Administration ob Eb a 3 4 1 1 Mew o B a411 Mew file opened Error Hi 3 41 12 New file opened E 3 41 1 3 Mew Test Packac 3 44 2 Open Requirements History Flan Execution History General Attributes Test Steps Fy Automation Inherit attributes Priority Medium State lin Work se Attribute values L f Regular i validation it Verification Additional Test Levels E
131. EMPPO V6 1 Description of Use Figure 174 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 176 or with lt Shift gt see Figure 177 After pressing Select all sub trees of the test packages and the selected test cases are marked see example at Figure 175 Page 151 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad Project Test Structure Edt Test Execution Er Test Structure Notepad RTF Import with TCs H d b H gh RE Mo fiter ae ooo 3 3 User goals E dE 4 Required functions of the product I dE 4 1 File Administration SET 3 4 14 Mew fi 3 4 1 1 1 Mew file opener D k 3 4 1 1 2 New file openec me 13 4 14 3 New Test Packa Her ai 4 1 2 Open F TEMPPO Tester1 Demo Notepad Project Test Structure Edit Test Execution e Test Structure Notepad RTF Import with TCs M4 W GP EE No iter Motepad RTF Import with TES E1 Introduction E 2 General description of the product m 3 Detailed description of the required product a E 31 Scope of delivery T 3 2 Sequences Scenarios of interaction g 3 3 User goals TE E a 3 4 Required functions of the product i 3 4 1 File Administration oF 3 4 41 New oOo 3
132. 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 WA WM a amp HW No fitter ALA Notepad RTF Import with TCs EFLA 1 Introduction ft aa 4 parietal Geecinien of the procie Requirements History Flarn Execution History Sim 3 Detailed description of the required prod General Attributes Test Steps E Automation ee 3 1 Scope of delivery as 3 2 Sequences scenarios of interactir Inherit attributes E IA 3 3 User goals Sie 3 4 Required functions of the product Ea 3 44 File Administration e Medium a O T om Regular E validation Priority Mediun Z o B3411 New i a mA 344 1 1 1 Mew file opened D Error f Verification State in Tene ee 442 d LB 3 4 1 1 3 New Test Packac La 3 4 1 2 Open Additional Test Levels Attribute values d a saue ma Acceptance Test E Milestone Mit ool 3 44 4 Exit bai 54 3 4 2 Edit Functions amp Platform Windows 7 64 bit a TA 3 4 21 Undo E Regressiontest yes fae 42 2 E Test location Offshore La 3 4 2 3 Copy La 3 4 24 Paste DA 3 4 25 Delete ee ee ee ee fo Merge Lock Apply Discard os Figure 111 Locked test structure 3 1 4 7 2Test case execution with an exported test suite Let s continue the example of offline test case execution You ll close TEMPPO a
133. F Import with TCs B04 Introduction E 2 General description of the product 5 rA 3 Detailed BESCHElOn of the required product m 3 2 Sequences scenarios of interactions Pr 93 3 User goals Login a ra 3 4 Required functions of the product 21 H 3 41 File Administration H a 3 4 1 1 Windows Login 2 File Mew pick Editor Pane cleared hi 3414141 Login Se 3 Untitled Notepad in title bar aasa New a 344 22 Mew aE aene gh BA 3 4 1 2 3 New Test Package c 3413 Open i 3 4 14 Save 3 4 4 5 Ext E E 3 4 2 Edit Functions EH E 3 4 3 Print Functions i E 3 4 4 Search Functions bw 34 5 Help System Figure 213 Referenced Test case ID If you click on the hyperlink the destination test cases is selected automatically Additionally a Back button see Figure 214 is shown to return to the source test case Page 176 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F TEMPPO Testmanager Demo Notepad z joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test W5 ajx Wod b H E No fitter El tll Notepad RTF Import with TCs a M H1 troduction c 2 General description of the product Et 8 3 Detailed description of the required product ee 341 Scope of delivery pn A 3 2 SEQUENCES cenarios of interactions 3 3 User goals a
134. General gii hew Entry Crested 13 10 2010 11 13 29 Owner Testmanager Type Additional Test Step Column Type Usage 0 Text Test Structure Image L Test suite L Figure 340 Additional test step column 5 5 Projects A Projects TESLI ETE uE B Example for versioning B Notepad generated B Link test cases to requirements B Notepad RTF Import with TCs o E Notepad RTF Import O E Notepad System amp Acceptance Test dA New Project BE New Test Structure Figure 341 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 342 is displayed The user specifies a unique name and a description TEMPPO automatically supplies the creation date and owner which is taken from the Windows account Page 268 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator General Roles LA om Created 11 10 2012 12 38 50 Owner Strasser Johanna Type TEMPPO Project ion Demo Project Editor Guest Key
135. General tributes Test Steps Automation Requirements History Plan Execution History zi rS 3 Detailed description of the required product aE oe Expected 3 2 Sequences scenarios of interactions i 3 3 User goals E a 3 4 Required functions of the product a E a 3 4 1 File Administration E 3 4 14 windows Login 32 File Mew pick Editar Pane cleared fi 34111 Login PE 3 Untitled Notepad in title bar EY ra 3 4 1 2 Nem EE 34122 Wew a TERE E sf 541 23 New Test Package c 3 4 1 3 Open 3 4 1 4 Save 0b bef 341 5 Exit 3 4 2 Edit Functions 3 4 3 Print Functions Fp E 3 4 4 Search Functions a 3 4 5 Help System Figure 211 Source test case Then click right mouse button for context menu select Hyperlink and select the test case AA x web S Fie Database E Commana EA Manual Test Case o User goals Ea Required functions of the product O EE File Administration o i ad Windows Login fil Login i New Cancel Figure 212 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 175 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test is H 4 WH E No fitter d Notepad RT
136. H Universal Socket H QuickTest Pro Test Partner HTEMPFO Designer IDATG i Ranorex Fl Commands ElChange Management Figure 287 Settings Database 3 3 21 2 7 Test Automation 3 3 21 2 7 1 WinRunner and SilkTest Page 230 User Manual TEMPPO V6 1 Edition July 2014 Description of Use settings eee x Silk Test l User Interface Tree Application Path cAProgram Files Seque lik Testipartner exe i ew Test Step Cells analysis Temporary Path C ADocuments and Settings H Newsboard he Test Suite Resutt Path C ADocuments and Settings Result viewer C nctepad exe ATOUMEMS q resexport lt lt TestFile gt gt Universal File H Universal Socket H Quick Test Pro Test Partner be TEMPPO Designer IDATG i Ranorex Fl Commands New Command SE El Change Management Bugzilla Clear Quest Telelogic Change delete temporary test automation files Restore Defaults OK Cancel Figure 288 Test Automation SilkTest WinRunner If you plan to manage automated test cases in TEMPPO you define the automation settings here First of all you have to choose the automation tool 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
137. M IMIMM 3 4 1 44 New file opened no changes failed M 3 4 1 1 2 New ile opened changes passed Nr Instruction Expected _ Pel earch Functions File New pickQ Message gt B E 3 4 4 1 Find save changes M E 3 4 4 1 1 Find up T E 3 4 4111 Case sensitive blocked E 3 4 41 1 2 WinRunner CheckStat on hold 3 4 4 1 1 3 QuickTestPro Test case not implemented E 3 4 41 1 4 Test Partner Test case not executed Speiche AY 3 4 4115 UAI not executed j one Drucker Neu ffnen Speiche Beende Messagebox No Editor Pane click cleared Untitled Notepad in title bar Lock Epply Figure 87 Test Execution 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 84 User Manual TEMPPO V6 1 Edition July 2014 Description of Use x User defined ID tc537 Mame Mew fle opened changes FE Details TANEET SE fr 1 Instruction File Mew pick Expected Message gt save changes ioii Datei Bearbeiten Format amp nsicht 7 Strg h ffnen Strg Speichern Strg 5 Speichern unter Action image 000 Seite einrichten Drucken Strg P Beenden Baa El Create a new bug Close Figure 88 Test Execution Test Execution Assistant 3 1 4 1 5 2 Set result s With c
138. MPPO Therefore those test cases are administrated in TEMPPO and after executing them outside of TEMPPO the results are imported 3 3 17 1 Export The export XML feature can either be used to execute automated TCs somewhere offline and export results later or export the test suite to an XML file for other matters In this case the test suite shouldn t be locked A test suite can be exported if a test suite is already opened any node test suite root or TP is selected and the menu item Export test suite gt to XML is activated Test suite export to AML xX 3 Should the test suite be locked after export The file can only be imported if a lock j set M Lock Test Suite Figure 254 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 207 User Manual TEMPPO V6 1 ioj xi Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Version 2 of Test abject ROOT 12 1 1 MH d b H GP E No titer SE version 2 of Test object REO Eimi 3 Detailed description of the require Ea 3 4 Required functions of the pi Eb La 3 4 1 File Administration BA 3 4 1 1 New E 3 41141 New gile r i 3 4 1 41 2 New file EHSA 3 4 4 Search Functio
139. Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help ll x Test Structure Notepad RTF Import with TCs System Test pu Wo d p H GP EE monter Et a 3 4 Required functions of the product EP 3 4 1 File Administration a a 3 4 1 1 Mew General Attributes Test Steps 4111 New file opened no Ei Automation Requirements History Plan Execution History E 3 4 1 1 2 Mew file opened ch D 3 41 2 Open He 3 41 3 Save 3444 Exit Planned tester Tester 3 4 2 Edit Functions Et 3 4 3 Print Functions Planned test execution time o h T min 0 59 H D344 Search Functions bs 3 4 5 Help System a 3 5 External interfaces of the product Et S 3 5 1 User interfaces 3 51 1 Editor Pane 3 5 1 2 Search Dialog a a 3 6 2 System interfaces Lock Apply Discard Figure 45 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 46 Page 53 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad E olx Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Motepad
140. O Testmanager Demo Notepad p Oj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test W22 7 m Ej x SE S S E E Mo fitter ALI Notepad RTF Import with TCs E 1 Introduction m 2 General description of the product os 3 Detailed description of the required product f re 3 1 Scope of delivery ae a 3 2 Sequences scenarios of interactions v an ee Ea 3 3 User goals Ba 3 4 Required functions of the product ER 3 41 File Administration Ea 3 4 1 1 Mew o A 3 4 1 1 1 New file opened na c fi 3 4 1 1 2 Mew file opened char oe 3 4 1 1 3 Mew Test Package on Bb E 3 4 1 1 3 41 New Test Case i beag Onen of Merge Lock Apply Discard bot Figure 238 Test case merge If working on a branch an additional button Merge appears besides Lock Apply and Discard the current test case After pressing the button Apply the user is automatically asked if he wants to apply the changes on the latest version V3 Additionally the message shows the information if the same test case was also changed in the latest version Merge advice x The test case was modified in this branch version Do you want to apply the changes alao in the main latest version Remark This test case was also updated in main latest version by Testmanager Figure 239 Merge advice If the user presses Yes the following window appe
141. 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 11 can be selected if a non latest version should be loaded Page 20 User Manual TEMPPO V6 1 a a IBN ON x Test Level S Link test cases to requirem Testmanager 14 02 2012 11 14 46 System Test vA editable version Notepad generated Testmanager 16 02 2012 15 07 System Test V2 editable version Notepad System amp Accepta Testmanager 15 02 2012 13 26 40 System Test WI W111 editable version V2 editable wersion nen Figure 10 Open Test Structure 3 1 2 2 3Reopen a test structure A faster way to open a test structure and the according project as well is to use Test Structure gt Reopen which displays the 4 last opened test structures It will only be enabled if no project is open F TEMPPO Testmanager 5 x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Li Mer BS Duplicate i Open Reopen gt 1 Notepad System amp Acceptance Test Demo Notepad l a lose gt 2 Notepad Demo Notepad generated v4 o Te 3 Notepad Demo Notepad generated w1 1 1 we 4 Notepad System amp Acceptance Test Demo Notepad v4 El Import Structure Update 7 Export Structure Apply reguiremernt updates Task list
142. PPO atw108s2 JUnit extension tests Project Test Structure Edt Tes Execution Evaluation Took Windows Help Test Suite Sample JUnit execution 1 1 1 H 4b HW LJ Sample Und execution An ret Tests BB punt samples VectorTest 7 pansa aed General attributes Preconditions Test Steps EJ Automation OB testCortanciurd sampes vectorTest A este erol juni sampes money Morey lest taxied E testElemertatiyune samples Vector Test WB tectRencveBlemert purdt samples Vecto QO testCloneajuund samples Vector Test pa User Defined Er tci6 A lesRemove Ajumi samples Vecio Test prt sii MoneyTest Owner ebwilBe BBD testBagiutinty unt samples money Mor Created 10 12 2002 14 21 01 E textBaghegate pnt samples money Mor E testBagNotiquats jund samples money Tested 10 12 2002 14 53 48 E testBagSirpleAddijunt samples money E erGagSubtractiuni sampes money Mi ert A C E testBagSumAdajunit samples money Mi Type Test Resul a LA testMocedtSurnple Adini samples mir Resut Output junit framework AssertionFailedErrorc Bi testiMoneyBagE quals und samples mone St junit samples money MoneyTest testiszero MoneyTest java 54 Oo besiMone Bagtath jund samples mone br sun ceftlect WativemethodAccessoriInupl invokeO Native Method E tesiMioneryEquatn jund samples money W at sun ceflect WativenethodAccessorlapl invoke Nativetethodicces GB testmoneyHashijunt zampe money M
143. PY VA M4 W GP EE No nter i Test object Version sYa RCOS COPY Si 3 Detailed description of the reguired g 3 4 Required functions of the prod FI 4 3 4 1 File Administration 3 4 44 New 333 3 4 4 Search Functions Fy 3 4 4 1 Find bcs 34 444 Find up Figure 178 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 179 and the tabs with the content of the selected items is shown on the right side see Figure 180 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 Fi he 3 kind and Replace F3 Show Details Select All E Tree d Cue Chrl s Topy Ckrl 2 BA Paste Chrl gt Delete Delete Order Edit Refresh recursively fa Move gl Analyse selected b E Report selected Figure 179 Show Details Page 154 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad a Ioj Project Test Structure Ed
144. RTF Import with TCs System Test 41 HM d gt b W GP EE monter ake na 1 Introduction Locked by Testmanager H 2 General description of the product General Plan Requirements 3 Detailed description of the required product f 0 3 1 Scope of delivery Ea 3 2 Sequences Scenarios of interactions fea 3 3 User goals Planned test execution time 3 h 30 min 0 59 Sao 3 4 Required functions of the product EP 3 41 File Administration EM 3 444 New 2 3 fi 3 4 1 1 1 Mew ile opened no fi 3 4 1 4 2 Nev file opened ch Gd 3 4 1 2 Open LI 3 4 1 3 Save ob bli 414 Exit 3 4 2 Edt Functions AF i F HE 3 4 3 Print Functions ER seal D Figure 46 Planned execution time for whole test structure Additionally the designer enters a Planned tester for each test case who is planned to execute it For Analysis of test structure Planned Tester is available to view whereas the analysis of different Test execution efforts makes no sense Test Cases NN 1 NN Schlosser Dietmar Planned tester Figure 47 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
145. SAS NOSE Cede S inae Sass dectanbegseavabeseesseeeesds edar Ei 260 gadd ANOUCES sirri sn a E A a 260 5 4 4 1 Copy and rename of UDA nssassssussssnsssersnsnsnnrsnrnrnnsnrnnensrnrnn 262 SA5 Upad a array ig e A A 263 S470 Regurement StrUCtUrES aerer E ER 264 Sa USEF ld Sinaia a E AAE 267 DE SRO OCS a E meee eee 268 d Creanga Droe Tansini sageontianeusess sncesasianeedasi cages 268 I2 COPYING a iDEOJECE cprimirisos one OEE OE OSEO 270 SDr OC CLONS arerin Erea onaeiareeaengse nantes een eae 270 5 5 4 Test Suites check consistency unlock ccceeeee cece eee eeeeeeeeeeeas 270 5 5 5 JXASSION Metadata avacicirstaserbnaderararsntabieriiassierstiaasereiaunawanoediercees 270 5 5 6 Move Ownership vidceccamnshses eeuscieweaehiatertaavoteenttsicreuhutaeashaedentaes 271 Dice Freeze UMIFCCZS ceirirrnnoro un eE rT TAE TUTOE EA 272 O LOCK oeren r E 273 5 7 VHICCNSE Serv Gr COMME CUION 225i scareredoeerectsatoreceteseresaasnrecalerurectdatorece 2 4 5 7 1 Using a license server on a computer with several network interface cards 275 6 JUNI conania aaa Aa aA 276 o TERN a a e a 276 G2 CONMIUFACON orrian AEEA E AAIE 277 6 3 IMHO JUNIE test CASES eripe e a e a a 278 6 3 1 Description and STEDS orresriricii eraciren eA EART S 278 6 3 2 References to JUnit test CASES ssssssssssnnunrnrsernrnnenrrnrsnrnrenne 283 64 Update JUUNIT test Ca SES nerenin a a a e 285 6 4 1 Description And STEDS semeewciivinracatsennin sheeneeadenennan
146. 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 GD detnece 8 rates S 7 promats noc G tense cE Test Levels Test Categories 40 Attributes Uploads Requirement Structures D g X a Ba a Name y Atribute Type 22 11 2013 13 46 46 Test Case 12 09 2012 14 21 37 Test Package 22 11 2013 13 46 45 Test Case a r 22 11 2013 13 46 43 Test Case 22 11 2013 13 46 44 Test Case 22 11 2013 13 46 45 Test Case 22 11 2013 13 46 47 Test Case 12 09 2012 14 21 01 Test Case J New Entry3 12 08 2012 14 22 11 Test Suite J Regressiontest 22 11 2013 13 46 46 Test Case 22 11 2013 13 46 42 Test Case 22 11 2013 13 46 41 Test Case Figure 329 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 resul
147. Search Functions Execution History Elid 3 4 4 1 Find u 34411 Find up Planned test execution time i h 30 min 0 697 BH 3 4 4 1 1 1 Case sensitive blocke R 3 4 4 1 1 2 WinRunner Check Ste Actual test execution time f h 4 min 0 59 ig Merge 3444143 QuickTestPro Test ca E 3 444144 Test Partner Test ca B A 3 4 4 1 1 5 UAI not executed Lock Apply Discard Figure 90 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 86 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad S loj xi Project Test Structure Edt Test Execution Evaluation Tools windows Help Test Suite Test abject Version lt 2 RCO v1 1 1 Ss 3 Detailed d esr aquired product features I Ay 34 Rg locked by EET P 3 4 1 File Administration sl 3 4 4 1 New o 3 4 1 1 1 Mev file opened no change 3 4442 New file opened changes Planned test execution time 3 g fo min 0 59 ee a 3 4 4 Search Functions 2 3 4 4 1 Find Actual test execution time fo h 48 min 0 59 E t 34 441 Find up E 3 4 4 1 1 1 Case sensitive blocke R 34 41 12 WinRunner Check Ste 3 4 4 1 1 3 Quick TestPro Test
148. Suite Filter E No filter v Apply 4 Select nodes or subtrees Attribut Val 5 Enter testsuite name meee one 6 Determine the logical ie Regressiontest expression 7 Remove test cases manually I O ax Regressiontest yes TEMPPO Test Suite Generator lt lt Prey Next gt gt Figure 79 Logical Expression Cancel When pressing Next the user can remove test cases that should not be executed Figure 80 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 78 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Bj Test Suite Wizard 4 x Steps Rework Test suite Introduction Select obsolete test cases hold lt STRG gt and lt Shift gt for muti select Choose creation mode Select an existing Test Suite Test object Version XYZ RCO2 16 02 2012 Detailed description of the required product features Z Required functions of the product J File Administration B a New Fl New ile opened no changes not executed L Search Functions Find a Find up Li Case sensitive not executed 4 2 3 4 Select nodes or subtrees 5 Entertest suite name 6 Determine the logical expression 7 Remove test cases manually TEMPPO Test Suite Generator lt lt Prey Figure 80 Remove unwanted test cases Finish
149. TEMPPO Test result Assign test result attributes X X P E T E a Implies Run automated and Set results multi Page 314 User Manual TEMPPO V6 1 Edition July 2014 Appendix Merge actual execution time X _TEMPPO Evaluation Analyse O Z O X pt Aalysebybug IDOE X Pt reationprogress O X OS Execution progress xt T ST C Personal report setting XX XIX x O O Project report setting X x x x x Ret a e a PY Reg uirement Requirement analysis S S x o o oOo o o TEMPPO Requirement e 1 a to XML ps Tmportfrom CSV _ _ _ E EEEE a a po Import from xmMe EX po pen XY po Requirement X x x pi Requirement Structure X X po Split XY po Update XT po ersions XY TEMPPO Others Multi Selection X P po Copy XY poopy XY po EXport Import filter X FP po iter XX X X XT New implies applying a filter _ po Order XY po ask ist XX XK po ersions XE XE XY SO Page 315 User Manual TEMPPO V6 1 Edition July 2014 Appendix 13 7 UAI Adapters An adapter is used to convert the results returned from an automation tool into a format which can be processed by TEMPPO Currently 2 adapters are provided 13 7 1CDefaultAutoToolAdapter The result string returned after a test case has been executed must have following format line 1 result passed failed blocked not implemented on hold line 2 summary begin line n summary end 13 7 2CAPOXIAdapter Tak
150. TTLIST TS name CDATA REQUIRED gt lt ATTLIST TS test level CDATA IMPLIED gt lt if it does not exist autom create LE e lt ATTLIST TS version CDATA IMPLIED gt lt Added 31 5 2004 gt lt ELEMENT TP DESCRIPTION PRECONDITION POSTCONDITION REQUIREMENT TP TC gt lt ATTLIST TP name CDATA REQUIRED gt lt if zero length then name New Restpackage generated gt lt l at at already EGxusts add Iy My ae te Se lt ATTLIST TP test category CDATA IMPLIED gt lt la af it does not exist autom create it for the test level of the containing test structure gt lt ATTLIST TP document CDATA IMPLIED gt lt ATTLIST TP doc name CDATA IMPLIED gt lt ATTLIST TP chapter CDATA IMPLIED gt lt ATTLIST TP inherit requirements true false false gt lt ELEMENT TC TESTGOAL PRECONDITION POSTCONDITION REQUIREMENT STEP AUTOMATION ADD TEST LEVEL USER DEFINED ATTRIBUTE gt Aire on TG user defined id CDATA FiIMPLIED gt lt l af 10 already exists in containing test structure add 1 2 Se lt ATTLIST TC name CDATA REQUIRED gt lt if zero length then name New Testcase generated gt lt if it already exists in containing test package add 1 adh ts Si TE lt ATTLIST TC situation Error Regular Error gt lt ATTLIST TC val ver Validation Verification Validation gt lt ATTLIST TC priority Top High
151. Testmanager Updator Testmanager o a a 3 4 1 1 Windows Login i Created 20 02 2012 10 26 12 Updated 20 02 2012 10 53 04 2 oi 153 4 1 2 Mew Type Manual f Automated Test Case A 3 4 1 3 Open S414 Save aa tesst goal o bli 3415 Exit 3 4 2 Edit Functions RL 3 4 3 Print Functions pF E 3 4 4 Search Functions 3 4 5 Help System H A 76A Peternal intertares the nrn ict 5 a Lack Apply Discard Figure 229 Apply Discard 3 3 L1Newsboard 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 Refresh button to get the latest news Page 190 User Manual TEMPPO V6 1 Edition July 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
152. Transition bead situation Error gt lt STEP instruction input expected 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 59 User Manual TEMPPO V6 1 Edition July 2014 Description of Use lt STEP instruction input expected lt USR_FIELD name Actor ae err Connery gt lt USR_FIELD name ExecutionRequest value lt USR_FIELD name Data value line 1 line 2 gt line 3 gt lt STEP gt lt TC gt lt TP gt lt TEMPPO_EXCHANGE gt 3 1 3 1 6Upload paste reference images For adding pictures to such a column you have to select such a cell press the right mouse button and activate the menu Upload Delete Paste Copy or Reference Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help x Test Structure Notepad RTF Import with TCs System Test V1 q x M d b HW EE no fiter ALJ Notepad RTF Import with TCs 1 Introduction 2 General description of the product General Attributes Test Steps E Atomation Requirements History Plan Execution History E amp 3 Detailed description of the requirec i pened el Ne struction 3 2 Sequences scenarios of in n n i 3 3 User goals File New pick fA Unbenannt Editor Editor Pane cleared E
153. User goals Mame Aad 3 4 Required functions of the product BP 3 4 1 File Administration Chapter 3 4 4 A 342 Edit Functions E 0 3 4 3 Print Functions are naian Sao 3 4 4 Search Functions 3 4 44 Find Precondition 3 4 4 2 Replace 3 4 5 Help System Ee 3 5 External interfaces of the product J 3 6 Other product features required FA al 4 Specifications for project management A 5 Obligations of the client Al 6 Literature i 7 Annex file test tst opened Postoondition Postcondition file testixt closed Lock Apply Discard bot Figure 28 Adding new test packages without direct relations to document chapter You can add test packages that do or don t refer to requirements in random hierarchical order It is up to you if the structure remains comprehensible When activating the tab Details a special precondition and a special postcondition for this test package may be specified This is suggested if all contained test cases have a common setup phase In the table below all preconditions and postconditions of the parent test packages are listed Page 36 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 10 x Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test v4 q x H gt b Hyg Mo fitter AL Notepad RTF Import
154. Yes Figure 345 is shown Page 16 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Project Properties X General Roles Test Case template Test Result template mE New Project Created 15 02 2012 12 56 16 Mandatory history cormert Owner Testmanager Type TEMPPO Project Description This projectis used for user documentation eres Figure 2 Project Properties TEMPPO Administrator 3 1 2 1 2Opening an Existing Project F Open Project q X e mer rete Demo Motepact Testmanager 14 02 2012 10 50 01 User documentation Testmanager 14 02 2012 11 08 07 eres Figure 3 Open Project When activating the menu item Project gt Open the window Open Project Figure 3 with project name owner and creation date is displayed Exactly one project can be selected and is opened by clicking the OK button The name of the project is shown in the title bar of the main window see Figure 4 Cancel closes the window and no project is opened Page 17 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F TEMPPO Testmanager Demo Notepad z oj x Project Test Structure Edt Test Execution Evaluation Toole windows Help Figure 4 Main Window project opened 3 1 2 2 Building the Test Structure A test structure contains test packages and test cases which can refer to requirements This can be established in 2 ways and or e Referring to chapters
155. a F failed 4 Regd P failed m Username Administrator Exclusive edit mode Figure 266 Results for requirements Page 213 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 19Test 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 Test Suite Testsuite Scheduler V1 1 1 M 4 gt DW 6S BR No fiter X SK YJ restsuite Scheduler M 2 Auto E 2 1 Create Player not executed EJ 2 2 Create Player 1 not executed E 2 3 Edit Person not executed E 2 4 Record_test not executed Name Owner Created Updated Updator Host Scheduler Star iD E 2 5 Record_test 1 not executed E 2 6 Record_test 2 not executed E3 E 2 7 Record_test 3 not executed E 2 8 UniversalFie not executed E 2 9 New Test Case not executed General Detais Export Info Attributes Predecessor Pian Scheduler Figure 267 Test Suite Scheduler With the buttons on the right side you can manage and run schedulers e Create Edit a scheduler Define a
156. a country By clicking the button Clear you can delete the search preferences Clicking the Search button will perform the search and the result is shown in the table below The search can be cancelled at any time by clicking the button Cancel l User cancelled the search Page 255 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Figure 320 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 pP i 1 J User cancelled importing users From LOAP Figure 321 Cancel the import from LDAP 5 3 1 3 Synchronizing users with LDAP A LDAP search for all TEMPPO users is performed and if they were found the first name and the last name are updated The synchronization will be performed for each user from the current LDAP server or for manually created users If a manually created user was found the column LDAP server is set The synchronization can be cancelle
157. abase 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 248 User Manual TEMPPO V6 1 Edition July 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 admin properties file 5 1 Database Connection Fi TEMPPO Administrator O x TE Deicbase Foes Users meaa Bi rroiects B locke icense DSM User documentation C Pad Database oracle SID jaktx Schema temppo_um Host Jatin ga Fort f 521 User fatwi12h3 wf Login manually Connect Database Mame Database Version Figure 312 Administrator
158. action and the person are shown Newsboard consists of 2 tabs lt name of test structure plus version gt and General The first one shows all activities new change delete on test cases and test packages in the current selected test structure version On the other hand General displays all other information New attribute assigned to the project changed attribute new attribute value new test suite new user new version If an item of newsboard is selected the corresponding one is also highlighted in the test structure if possible A deleted item cannot be displayed of course F TEMPPO Testmanager Demo Notepad E ioj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Hewsboard Notepad RTF Import with Tes vWa i E x Updated 20 02 2012 10 56 58 Changed since last login 20 02 2012 E h 00 24 f min 00 59 fa Apply Notepad RTF Import with TCs v3 General Changed Test Package File Administration 20 02 2012 102659 Testmanager Testeri Changed Test Package Mew 20 02 202104656 amp Testmanager Testeri Changed Test Case Mew file opened no changes 20 02 202103018 amp Testmanager Testeri Changed Test Case New file opened changes 20 02 2012 105304 Testmanager Testeri Changed Test Package General description of the product 16 02 2012 18 00 46 Testeri E Testmanager Changed Test Pack
159. ad W211 editable w Test Pac Cut th543 export dat 20 02 201 Figure 349 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 273 User Manual TEMPPO V6 1 Edition July 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 o x z Database e Roles Users Metadata DH Projects By Locks Ea License A ey I Exclude test suites J Suppress export locks Ea Unlock selected elements Demo Notepad Test Sute version Label Type Name Test Case Locked by Locked by g gt Example for versioning Demo Not Notepad W244 editable v Test Pac Performa tp562 export dat 20 02 201 T Link test t i rit E ace pnt ii E Demo Not Notepad Y24141 editable v Test Pac Resource tp563 export dat 20 02 201 T gt Notepad RTF Import Demo Not Notepad W214 editable v Test Pac Systemin tp560 export dat 20 02 201
160. age Windows Login 20 02 202102613 FF Testmanager E Testmanager Changed Test Case Login 20 02 2012 10 56 57 amp Testmanager E Testmanager Changed Test Case Case sensitive 20 02 2012 1053 05 Testmanager E Testmanager Changed Test Package Find up 20 02 2012 10 53 05 amp Testmanager E Testmanager Test Package Windows Login 20 02 2012 10 25 59 FF Testmanager E Testmanager Test Case Login 20 02 2012 102612 Testmanager E Testmanager Page 191 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Ei TEMPPO Testmanager Demo Notepad i ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Helg v3 5 x d Mewsboard Notepad RTF Import with Tes Updated 20 02 2012 10 56 56 Refresh Changed since last login w 20 02 201 z E h 00 24 fo min 00 59 fo Apply Notepad RTF Import with TCs v3 General o etone o Tye ame version Dae Updator Changed 51 Test Structure Notepad RTF Import with TCs VW 20 02 2012 10 53 05 Testmanager Testmanager Mew 51 Test Structure Notepad ATF Import with Tos V3 16 02 2012 16 36 30 E Testmanager E Testmanager Test Structure Notepad RTF Import with TCs System Test v3 wo WH EE no iter d Notepad RTF Import with TCs gt FA 1 Introduction na 2 General description of the product m 3 Detailed description of the required product os Eg 3 1 Scope of delivery m 3 2 Sequences scenarios of
161. ailed failed Test Suite results can be exported if a test suite is open and active and the menu item Export test suite gt to DOORS is activated TEMPPO first verifies whether the test suite contains any test cases linked to requirements imported from DOORS If no linked requirements can be found the user is informed via a message and the process is aborted x 1 Export to Doors not possible because no test cases with links to LD Doors requirements could be found in the active test suite Figure 259 Information Message If there are linked requirements the user is guided through the wizard Page 210 User Manual TEMPPO V6 1 Edition July 2014 Description of Use A Export of Testsuite Sheps Export requirement data to a RM tool 1 Introduction This Wizard assists you to export requirement data to a provided RM tool 2 Export of Testsuite affected modules baselines Figure 260 Export Wizard step 1 TEMPPO starts the communication with DOORS and searches for the affected module s baseline s in the DOORS database Before starting the export TEMPPO gives an overview Export of Testsuite Steps Export of Testsuite 1 Introduction The Following DOORS modules will be copied and updated 2 Export of Testsuite affected with test results modules b aselines DEY 3 0 TEMPPO 5 2 Requirements The Following DOORS mudules could not be located the results of the corresponding requirements w
162. al interfaces of the product Test Category H 3 6 Other product features required a io Description H l 4 Specifications for project management ia 5 Obligations of the client i 6 Literature oo 7 Annex Lock Apply Discard bot Figure 27 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 35 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help 10 x Test Structure Notepad RTF Import with TCs System Test u i x MH WwW w E Mo fitter d Notepad RTF Import with TCs Fl 1 Introduction FA a 2 General description of the product Sao 3 Detailed description of the required prode 13 1 Scope of delivery Document C temp Pfichtenheft_Notepad_withTC rtf HO 3 2 Sequences scenarios of interactic General Attributes Details Requirements History Pian i Ea 3 3
163. al requirements Y Functional requirements Functional requirements Figure 21 Select non matching attributes After pressing OK the user is informed about errors of the import All test cases were importiert For the folowing test cases a problem was detected and a default value was used Test Case Error Example Testcase Document Properties Example Testcase Document Properties No user with the name nn1 exists Create Devroom for Product Create Devroom for Product No user with the name nn1 exists Assign Members to Gevroom Assign Members to Devroom No user with the name nn1 exists Assign Group to DevRoom Assign Group to DevRoom No user with the name nnd exists Import Masterptant Incremental Import Masterptant Incremental No user with the name nnd exists Import Masterplant Incremental Import Masterpiant Incremental Normal is an invalid value for this field so the default value was used Figure 22 CSV Import Result Build manually XML Import 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 Page 43 User Manual TEMPPO V6 1 Edition July 2014 Description of Use But before linking those to test packages it might be necessary to define and assign them for the project see chapt
164. 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 341 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 270 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator x Test Levels Test Categories _ Attributes ES Uploads ia Requirement structures E User Fields Find l a Gui Layoukt Test Maintenance Test Performance Test Portability Test Reliability Test 4 Resource Test s Reuse Test s Safety Test Ys Security Test State Based Test a Task Based Test Usability Test 4 7 F Figure 345 Metadata Editor Example On the left side all available test categories are listed By clicking the buttons gt
165. anual TEMPPO V6 1 Edition July 2014 Description of Use al Favountes Test Cases retatve Time Settings stat State End BiOS E Linu Enone Windows unt Refresh Designed Approved Figure 116 Test Structure Analysis Test Cases fan at vertical Representation aa absolute F relative a a a i x 4 5 E 4 Accumulate E a a z c mi a E e E o o a be B Time Settings e E o E si wman o wel Oats reren Result E passed E failed O blocked on hold Figure 117 Test Suite Analysis Favourite sine romedty 05 E t xm see Y Axis Page 105 User Manual TEMPPO V6 1 Edition July 2014 Description of Use A special analysis is the result coverage The following analysis compares or displays the planned tests and executed not executed tests LA Analysis Favourites Favourite Result coverage without grouping X Axis Result Coverage Y Axis Test Cases Group by Chart Vertical Bar Chart iS Show 0 values Test Cases mn Onentation horizontal bi oo oO vertical Representation absolute relative Accumulate Time Settings executed Start 29 11 2012 not executed Result Coverage End 01 04 2014 Figure 118 Test Suite Analysis Coverage 3 1 5 1 1 Analysis with previous test suites Now there is an analysis t
166. apply these functions Even the short cuts lt Ctrl gt X lt Ctrl gt C and lt Ctrl gt V are supported If the mouse cursor is located over the column headings a menu for hiding and displaying the columns is popped up when pressing the right mouse button w Input w Expected Figure 52 Context menu for column hiding displaying 3 1 3 1 3 Test Creation Assistant When pressing t or double clicking a test step Figure 53 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 57 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F Test creation assistant X Navigation main mend Instruction Input st data Ment points Destination memory Destination entry Last destination POls are offered Sk TMC sk4 Mode SKS Settings Bale Expected ores Figure 53 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 jump to next previous table cell only if not in edit mode LT move one test step down up lt Ctrl gt lt TAB gt leave test step table
167. ars where the user can select which parts of the test case will be merged x Select the content which has to be merged m Attributes M Test Steps W Automation r Requirements W Plan Figure 240 Merge selection If nothing is selected test case is latest version remains unchanged 3 3 13Compare 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 196 User Manual TEMPPO V6 1 Edition July 2014 Description of Use E Tree Compare a Cut Ctra a version window comes up where you can select the version of the test case to be compared The versions window does only show the versions in which the test case exists After selecting a version the button Compare gets enabled ee Notepad RTF Import with TCs Display E11 Test Suites for v1 1 2012 02 16 gt Tree style e 1 1 1 editable wersion E viehe only EF W2 o EW24 Test Suites for V2 1 2012 02 16 Labels only 2 W277 editable version f Versions and Labels a w221 Clear Case style L yT editable version PaE ie ascending Figure 241 Compare selecting a version When pressing the button Compare Figure 242 is shown The two versions of the test case are displayed with their differences in red color Page 197 User Manual TEMPPO V6 1 Edition July 2
168. assrursnsnsnrersnsrerrns 133 FEDO Chai CCU Co airaa EE 137 3 1 5 6 4 Previewing and Saving ssssssssssssssssnsnennnnrnnrnssnrnnrnrenne 138 3 457015 Sampe CHAS cciitcs te cccdeteusnaadinredaitarsseseserciouawanneeierceds 140 3 1 5 6 6 Report Templates ccccceccccceeeeeeensscccccnsenneecnreseeeenssegs 142 3 1 5 7 Import from another projects ccccssseeeeeeeeeeeeeeeseeeeeeusenns 142 FD EXPO LO AMI vadeccsakuadstencareesatenniecesanes sees EAE Oi 142 SLS IMPOFre trom AML 7 TRP Wie ssid eiceericseiuan aig ate sages 143 3 2 Multiuser ADINNCY sesuivdans ca chuetetdaa ie ides tases Lia teen ee aes 143 Bak HOCK MOG SS areri a A A A 143 Jela FING IOCKS UNOCK ania a a ane aaeegaanG 144 3 2Zelkse SNOWING JOCK SEAS cirie E ie aaa eehaaeee een 145 J2sl3 Creanga VERSION recccces inne cic Bie eet a a sie eeea ie tane 146 S i2 1c4 Creating a TeSt SUILG accor nsec iaeiccsuateusicmeeieciseprniescsaaieseuent 146 Jah FINGINGANVAIG JOCKS onirnserna ro eeeitieawnes ects 146 322 RENES MNO eaa aT E 147 322d Refreshing Manually rerien a a a tan vader 147 3 2 2 1 1 Reloading the whole test structure test suite sess 147 3 2 2 1 2 Refreshing recursively cccccceeeccccssccccccusenneneueeeeeeenssegs 147 3 2 2 1 3 Refreshing on certain user ACTIONS s sssssseressrsrrererrrrrrus 148 3 3 General principles and user prompting ss s ssssesssserenrsrenrsresrerrrrenas 148 ZJ IMIS MMO Cs areri aE a ATR TOITE EEEa 148
169. automation not covered by TEMPPO Test Manager 3 1 3 1 Implementing Test Steps You continue your work in the tabs Test Steps and Automation of the test case tab 3 1 3 1 1 Preconditions and Postconditions You have to consider which preconditions must be fulfilled before the test steps can be carried out during test execution You specify this textually in the precondition table of the tab test steps Additionally you can see the preconditions defined in the parent test packages Additionally you can also define postconditions which mut be fulfilled after test steps execution You specify this textually in the postcondition table of the tab test steps You can see the postconditions defined in the parent test packages too Page 55 TEMPPO V6 1 Description of Use User Manual Edition July 2014 Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Toole Windows Help 5 x x Test Structure Notepad RTF Import with Tes System Test W1 H 4d gt HW Eh no fter AL Notepad RTF Import with TCs H 1 Introduction H Ea 2 General description of the product 8 3 Detailed description of the required pr a 3 1 Scope of delivery i 3 2 Sequences fecenarios of inter E 3 3 User goals n aa 3 4 Required functions of the produ E E 43 4 1 File Administration O BA 3411 New fl 341141 New file open 3411 2 Mew file open fg 3 4 1 2 Open B 3 4 1 5
170. base 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 250 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Fi TEMPPO Administrator Testmanager O x Database S Roles E Users a Metadata LA Projects Lacke License BP TEMPPO Editor schema Owner 13 02 2012 13 04 02 HO TEMPPO Guest schema Owner 13 02 2012 13 04 06 Se TEMPPO Key Tester schema Owner 13 02 2012 13 04 04 TEMPPO key User schema Owner 13 02 2012 13 04
171. by pressing the menu item Test Structure gt Import Structure gt From XML Document This menu item is only enabled when a test structure is open and selected or a test package is selected The XML document to be imported can then be chosen in a file dialog The XML document is checked against the DTD Document Type Definition See 13 1 Your XML file has to have the first line lt DOCTYPE TEMPPO_EXCHANGE SYSTEM Test structure dtd gt whereas 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 LY Do you want bo import the requirment assignments too Figure 23 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 1 Parsing and validation of XML file checking of semantics and creation of new objects 2 Saving new or modified objects to the database 3 Reloading of the whole test structure from database Each stage has its own progress bar When the import is finished the following information dialog comes up SITEMPPO x 7 Te
172. can be selected Yes if editable is Yes Fixed Situation Test Case Type Additional Test Level Type Fixed Il Test Level Test Category Requirement Fixed Ill Priority State Page 203 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Yo IN IN Nf voy IN fy fy fff voy IN yf ff voy Ny fy ef YON INN Nf omne Eo ee Table 2 Attributes meanings The user can write free text that may also contain wildcards like x any number of characters any single character Filter Properties Value mnam am Figure 252 Filter criterion 3 3 14 6 Edit filter criterion You delete and add lines of filter criterion When pressing the button o the current line is deleted o ba a line is inserted before the current one Page 204 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 14 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 14 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
173. can be used for all project members Personal filters can be copied to project ones and vice versa 3 3 14 1 Predefined filters There are a lot of predefined filter which are useful for each user Page 198 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Xx Bo fe A automated test cases Testmanager W A created test cases of Testmanager Testmanager MA A manual test cases Testmanager MA A state_approved test cases Testmanager fa Al state designed test cases Testmanager fl Al state in review test cases Testmanager ae a state_in work test cases Testmanager A BC Figure 243 Predefined filters 3 3 14 2 Create filter You can create a new filter when pressing the button New filter in Figure 243 Name ey Filter Conditions Figure 244 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 199 User Manual TEMPPO V6 1 Edition July 2014 Description of Use TEMPPO Note lt Fiter name already used Please enter a different name Remark Due to missing meta data assignments some fiters might not be usable in the opened project and therefore not visible Figure 245 Filter name already used After saving the new filter Figure 246is shown The new filter is inserted and selected in the list box the filter criterion is displayed and the table Impact to selecte
174. ceived from TEMPPO By pressing Save the data can be transferred back to TEMPPO Page 300 User Manual Edition July 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 project test structure must be specified and TEMPPO is opened with the latest version of the test structure Optionally a special version and a test suite can be entered in order to open immediately a test structure version or a test suite separated list of values where the names for project test structure version and test suite 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 th
175. checkbox New or execute can be selected By this way roles can be created and adapted due to user demands Page 252 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator 5 3 User management lolx Database Roes Users a Metadata LA Projects Locke EA E x I LDAP OOOO desmame Firstname f ton O Testeri tester testers tester4 tester6 testerB tester Testmanager temppo_um Figure 316 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 logins named as you like Such manual logins need a password The same functions with the exception of role assignment are offered in TEMPPO Manager for details see chapter 4 2 Fi User properties x General Poles amp Rights M TEMPRO SUPETUSET Choose project User documentation
176. ciples Bal 241 GeneralPrinciples ag A211 Destination Entry via speller EF Al 2 1 1 Destination Entry via speller B E m A 241 414 Speler usage 2353 oe Eb az 414 Speller usage 2353 ae Eii 1 Speller_ Usage _Toyen 26 11 2002 15 08 02 EB dw fd 2114 _1 Speller_Usage_ Town 26 11 2002 15 27 17 pee MW B 2 1414_2 Speller_Usage Street 28 11 2002 15 08 04 offi 2 1 1 1_2 Speller_Usage Street 28 11 2002 15 27 21 Gl oe l H O BB 214 Speller_Usage_Zip_codes 28 11 2002 15 08 Oi p io pf 21141_4 Speller_Usage_Zip_codes 28 11 2002 15 27 2 de O E 2 4 14_5 Speller_Usage_house_numbers 28 11 2002 1 bE te ffi 2 1 1 1_5 Speller_Usage_house_numbers 26 11 2002 15 A O A 2 1 1 2 Best match line rs A 3 2141 2 estan oe O Gl 211 21 Best_Match_Line_Town 2607 efi 2141 24 Best_Match_Line_Town 2607 H O Ql 244 2_2 Best_Match_Line_Street fi 241 22 Best_Match_Line_Street sis O M2112 _3 Best_Match_Line_Housenurmber e fil 2112 _3 Best_Match_Line_Housenumber H O Ql 2 44 2_4 Best_Match_Line_Intersection 2608 efi 241 24 Best_Match_Line_Intersection 2608 Pee 244 2 5 Best_Match Line _Special_Destination 2609 efi 211 2_5 Best_Match_Line_Special_Destination 2609 H O B 2444 Auto Expand and Auto Delete function 2355 m PE H S 244 4 Auto Expand and Auto Delete function 2355 m 4 F 4 a Sa Figure 115 Manual import of test results 3 1 4 7 4Unlocking the test suite As a last resort it is possible to manually u
177. ct Test Suites Chart Vertical Bar Chart Orientation horizontal e vertical Representation absolute relative l Results v V passed V Fi v w VI g j Value v IN v Ready for v zx 4 T State IN Ready for Review Ready Designed Approved Save as gt Figure 133 Text Execution Progress Filtered Chart If you activate the tab Data the values are displayed as table and be saved as CSV file Page 118 User Manual TEMPPO V6 1 Edition July 2014 Description of Use E cren E vaa v Result Test Suites Test object Ver Test object Ver Test object Ver Test Suite Selection Test suite analysis depending on fiter settings Press Select Test Suites for choosing test suites and setting filter a k itt EE 3 d Attribute Value Components req634 req635 Components IN req683 req634 req635 Figure 134 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 pre
178. ctivated requirement structures are not considered If a requirement is not in a view it cannot be linked to a TC In the following example an Excel file with 3 TCs is shown Test case name Test goals Creator Priority Test goal A105123 High can be empty A105123 Low Designed A105123 Mittel Ready wwww wo w Designed can be empty Instruction1 Instruction2 Instruction3 Instruction1 Instruction2 Instruction3 Instruction1 Instruction2 Instruction3 Instruction4 Instruction5 Instruction6 Figure 19 Excel file for TC import State Precondition Instruction Expected result Input Postcondition Expected Result a Expected Result2 b Expected Result3 c Expected Result1 Expected Result2 Expected Result3 Expected Result1 Expected Result2 Expected Result3 Expected Result4 Expected Result5 Expected Result6 Non functional requirements Functional requirements Fct1 Fct2 UDA Creator w N Fct1 N Fct2 green NN1 o blue NN2 Clean up NN3 A TC can consist of more lines due to the number of test steps In this case the Test Case ID can be repeated or remain empty TEMPPO recognizes a new TC if a new Test Case ID identified After selecting the csv file from above the following dialog is displayed Matching attribute names are preselected Page 41 User Manual TEMPPO V6 1 Edition July 2014 Description of Use CSV Import You can assign Excel attribute
179. cution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 v1 1 1 M d gt b NG EE no fter ion XYZ RCO M escription of the required product features uired functions of the product General Attributes Test Steps Atomatian Requirements History Attributes TR Previous Resutts Plan Execution History File Administration Se a a Sr E 3 4 1 1 2 New file opened changes passed acetone A Unbenannt Ed Search Functions nee Datei Bearbeiten ffnen Speichern Speichern unter Seite einrichten Drucken Beenden Untitled Notepad im title hav http atinzp1 Oqa 2849 bugs_sitemppo_internal show_bug cqi7id 5626 Lock Apply Discard al gt i a i Be eo Figure 99 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 100 TEMPPO Test Manager will then sequentially invoke the proper automation tool for each test case and fetch the result obtained by the tool after the automated run Page 92 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Before running automated tests the automation settings in TEMPPO s administration tool see 4 must be configured 10 x Fi TEMPPO Testmanager
180. d Sq Datei Bearbeiten Format Tz Figure 103 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 95 User Manual TEMPPO V6 1 Edition July 2014 Description of Use executions that will be branched from the latest version of the main line What can you do to solve that problem There are two possibilities On one hand you can merge each single edited test case After pressing the Apply button the user is automatically asked to merge the changes Remark The Merge button can always be pressed if enabled x The test case was modified in this branch version Would you like to apply the changes also in the main latest version Additionally TEMPPO Test Manager checks if the test case to be merged is already changed in the mean time and informs the user Merge Warning x The test case on main line was updated by Mh 1 so The merge will overwrite this version in the main line If pressing Yes you may select which content should be merged into the latest version see Figure 104 Eimerse x Select the content which has to be merged Attributes IW Test Steps m Automation iCal Requirements Jw Plan Figure 104 Merge content The corresponding content is copied from the selected branch to the latest version of the main line which mean
181. d 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 U There are two possibilities now Page 257 User Manual TEMPPO V6 1 Edition July 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 entries that match the criterion are listed in the combo box Choose one press the button ok and confirm the assignment question 5 4 1 2 Delete Metadata Entries Choose the right metadata tab and click the button Delete If the metadata is not referenc
182. d 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 276 User Manual TEMPPO V6 1 Edition July 2014 JUnit Table 3 Terms used in TEMPPO and JUnit 6 2 Configuration Two configurations are necessary to use the JUnit extension test collector and classpath The configuration is done in the TEMPPO application via menu Windows gt Options once for the whole TEMPPO session The classpath is entered in the Arguments field in the usual format cp path1 path2 As in the JUnit framework it must point to both the JUnit tests and the Java classes under test The test collector is the part of the JUnit extension which searches for JUnit test cases in the specified classpath Following test collec
183. d Ea ean 286 6 4 2 References to JUnit test CASES sssssssssssesnrnrsernrnnrnrrnrsnsnrenne 290 603 TEST EXECUUOM crirkiniteree r e e a e E i ati 290 OS Description And STEDS muriri cire N a EAE ayant 290 6 5 2 Interpreting the Test ResultS s nsssssssssssnnsnrnnnnrnrnnsnsrnrenrnrnnne 292 60 KNOWN ITSSUCS secs nticredoaiarnnteciatl ded e a ele E setae 293 7 TEMPPO Designer IDATG sssssssssssuusu22u22 s 2unusuununnnnuunnnnnnnnnnnn 295 Zk Creating Task Packages morvrini a a a a aa 296 diz DeSon TeSt CaSe Sam a E 297 73 Updating TeSt Cases ransana a aa dae as 300 7 4 Restore Designed Test Cases ccccccccccccssscccccuuenneeecreeeseeeensseeeggurengs 300 8 Command Line sss 2 222u2225u20u2 20u2uuu2uuennuunnnnnnnnnnnn 301 9 PIUGH UNS viisina aaa a a aaa aaa 303 9 1 Plug in Version Change LIStener ccccceeecccceeeeceeensceceecueennenereeees 303 LO Literat re snina NRS 304 Li TOMO an oases weassewdrassaseetedducmtecenammeusimccs 305 12 ADDFEVIAUIONS sssrinin 307 ES ADDENDA 308 13 1 DTD Schema for XML Import Test Structure cece cece eee eee eens 308 13 2 DTD Schema for XML Import Test Suite c cece cece cece eee eeeeeees 309 13 3 DTD Schema for XML Import Results with CLI ccceeeeeeeeeeees 311 13 4 DTD Schema for XML Export User Profile with CLI 0008 311 1335 Predefined FUNCIONS nieireiserir tinnen ea 312 13 0 Predefined
184. d Window is updated X Bo uP aa Testmanager Market iN a us Market IN JAI US Hide Empty Subtrees Figure 246 Selected filter 3 3 14 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 200 TEMPPO V6 1 User Manual Description of Use Edition July 2014 Filter O yy x OO O ii E mu ey Pri I LU I IPL En I Be ati ey a State_in review 29 04 2013 13 00 33 a i Testmanager 29 04 2013 12 56 53 Market Market IN Al US Hide Empty Subtrees Figure 247 Edit filter Depending on the selected filter the conditions are displayed Filter name is read only filter conditions can be changed See Figure 244 3 3 14 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 201 User Manual TEMPPO V6 1 Edition July 2014 0 Cie cription of Use GA L DO f 29 04 9013 13 00 33 29 04 2013 12 56 53 Figure 249 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 250 Filter deleted After deleting a filter the No filter is highlighted in the list box 3 3 14 5 Defining the fil
185. d at any time by clicking the button Cancel Synchronize with LDAP X Laj i i l User cancelled the synchronization Figure 322 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 256 User Manual Edition July 2014 Fi Synchronize with LDAP The Following users could not be Found in the LOAF server Thomas Andreas Andreas Michael Roland Holzlechner Manfred Kronegger Martin Mayrbaeurl Max Moritsch Karin Moritsch Karin xyz 10by1 xyzl0cl6 xyz9f769 yzi lav xyzll4c5 my2lZbse xyz12903 xyzl sf xyzgf ci xyzgf4z atlnzpl0pa atlnzp10pa atlnzp10pa atinzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa atlnzp10pa TEMPPO V6 1 TEMPPO Administrator Figure 323 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 divided into 6 tabs if the tabs are not enabled you do not have the right to see it The following values are predefined Test Levels module test integration test system test acceptance test regression test Test Categories state base
186. d in task packages Page 296 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG Fi TEMPPO Testmanager Demo Notepad Z olx Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Structure Notepad RTF Import with TCs System Test M3 l Zl E x H d gt H E No filter AL Notepad RTF Import with TCs re TEMPFO Designer DATO Tasks i 1 1 New Task Package General Attributes Details Requirements History Plan 7 D 2 Introduction 3 General description of the product Inherit attributes a mi 4 Detailed description of the required product teal 5 Specifications for project management r 6 Obligations of the client ie Regular ie Wein ster Priority Top r o Ga 7 Literature E a Annex Error C verification State Designed Additional Test Levels Atribute Wales Figure 378 Task Package Tab attributes 7 2 Design Test Cases If you have finished creating some task packages you can design and generate test cases by selecting the node TEMPPO Designer IDATG Tasks and call the menu item Tools gt TEMPPO Designer IDATG gt Design Test Cases Fi TEMPPO Testmanager Demo Notepad gt Project Test Structure Edt Test Execution Evaluation Toole Windows Help loj x e Test Structure Notepad ATF Import with TCs 2ystem Jy JUnit H 4 b H gh E No fiter a TEMFPO Designer ID47TG Design Test Cases Restore
187. dens gt error Report201 214021 44458 9 Nerovision C error Report201 215021 33105 O Obsorge geglo o Ranorex E HF D SAP 3 I MO RA AT Schlosser Home MENS working B SharePoint Dras vernendete Eigene Dateien Arbeitsplatz File name Open n Poed Files of type emt Document File xml Cancel TEMPPO Reporting Progerty File troi Figure 160 Import report settings In the file dialog you can set the type of file to trp or xml After selecting a file and pressing open report setting is imported to TEMPPO 3 2 Multi user ability Multi user ability establishes an environment for working with several users in a parallel way on the same test structure or suite It prevents unintentional overriding of changes manages the synchronization between viewed and stored data and avoids inconsistency if multiple users work on the same database Moreover it provides features to facilitate the collaboration in a team working on the same TEMPPO Project Chapter 3 2 1 describes the behavior when locking and editing an item On the other hand chapter 3 2 2 illustrates the 2 possibilities of refreshing manual automatic Multi user ability is not supported for MS Access databases 3 2 1 Lock modes TEMPPO provides 2 possibilities of locking items test packages test cases e Manual lock e Automatic lock If you are working with manual lock mode you always have to press the button Lock bef
188. directly in touch with the version tree during the course of test execution references to it will be made frequently in the following paragraphs This is necessary in order to illustrate as clearly as possible what is going on behind the scenes as you proceed Just For Demonstration A Edit MS VI editable version i check In Activate Tree style C Versions only Latest test structure version in the main Labels only line This version is checked out for editing i Versions and Labels ClearCase style Order f ascending i descending Close Figure 63 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 68 User Manual TEMPPO V6 1 Edition July 2014 Description of Use A new Test Suite is created by activating Test Execution gt New This will cause the wizard shown in Figure 64 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
189. directly linked to a test case tesena Requirements assigned to all selected test cases are eauiremen parti displayed as usual in white background color Requirements assigned to not all test cases are feno rone ee displayed in a special color grey background color pess ComponentA R2 If you want to assign such a requirement to all ems os selected TCs select it and activate the context menu Se It is displayed in red color as well as new linked requirements The tab Inherited Requirements displays the Inherited Requirements mea requirements which are inherited from test packages Requirements assigned to all selected test Requireme parta cases are displayed as usual in white background color Requirements assigned to not all test cases SES sesa are displayed in a special color grey background req683 Component AR3 v Of course it is not possible to edit anything ae a ere The tab Inheritance displays the common P state of the inheritance flag of the selected eee TCs If the checkbox is not activated MW inherit Legend E Not inherited INotinherted X all selected TCs do not have any REEE inherited requirements If the checkbox is activated merte all selected TCs have at least one inherited requirement If the checkbox looks like M 4ps the common state is mixed TCs with and without inherited requirements Y Inherited 3 3 2 3 1 3 Test Case tab Precondit
190. duct Detailed description of the required prc FE Required functions of the product kal sidt PT Login User defined ID ip74i G I New Name Windows Login g New fle opened no c E New file opened cha Owner Testmanager Updator Testmanager Created 29 03 2012 15 32 45 Updated 07 04 2014 17 10 56 Type Test Package Number of TCs 1 Test Category Description This is an inline image Apphy Discard Figure 172 Inline images 3 3 2 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 e Assigning attributes requirements preconditions in the test structure Page 149 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Assigning test result attributes in the test suite Moving ownership in the test structure Deleting in the test structure 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 2 1 Multi selection The multi selection mode is activated when more than one item is selected If a user selects at least 2 items the right side detailed view is completely empty The user can only activate the multi selection mode when he has the right In
191. e Tool Tip Locked by lt user gt Page 145 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad 3 Project Test Structure Edt Test Execution Evaluation Tools Windows Help O x Test Structure Notepad RTF Import with TCs System Test W 3 AL Notepad RTF Import with TCs Fb 1 Introduction et al 4 General description of the product General Attributes Details Requirements History Plan 3 Detailed description of the required prod 2 a 3 1 Scope of delivery ID S85 _ 3 2 Sequences scenarios of interacti 3 33 3 User goals d 3 4 Required functions of the product Heme Lew O ERJ 3 4 1 File Administration TEREE 4 1 1 Men O E 341141 New file opened Created 16 02 2012 16 45 50 Updated 16 02 2042 17 08 21 3 4 1 1 2 New file opened f 3411 3 New Test Packar LI 3 41 2 Open Number of TCs 2 3 4413 Save 3 44 4 Exit Test Category 3 4 2 Edt Functions 3 4 3 Print Functions Description om 3 4 4 Search Functions few 3 4 5 Help System H E 3 5 External interfaces of the product o H 3 6 ot her product features required a S E F eet a Lock Apply Discard Owner Testmanager Updator Testmanager Type Test Package Figure 164 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 sui
192. e From Ranorex Document f Apply requirement updates From CSV Figure 18 Menu Import Test Cases from Excel When activating the menu Test Structure gt Import Structure gt From CSV Figure 20 is displayed In that dialog you can assign Excel columns to TEMPPO attributes They are automatically selected if their names match Mandatory attributes Name and User Defined ID have to be assigned otherwise an import cannot be performed Fixed attributes like test goal state can be assigned to any Excel attributes Attribute values have to be identically If they re different the default value will be set If the owner is selected and the user is not available in TEMPPO the current importer is used as owner Test step The 3 attributes Instruction Expected 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 If 2 or more values have to be assigned to an attribute Low Medium separate it in Excel with Medium Medium High If an user defined attribute is deactivated for the test structure it is not displayed as a TEMPPO attribute Requirements Since requirements are arranged in requirement structures they can also be imported as well For each requirement structure a column can be defined A test case can be linked to more requirement IDs separated by Li
193. e 287 User Manual TEMPPO V6 1 Edition July 2014 JUnit xi Steps Test Class Selection Introduction Select a JUnit test class 1 Select the JUnit test class to update from 2 3 Select new JUnit test cases Pelem ihe cena lar 4 Select obsolete TEMPPO test cases Active TestTest AllMembers Supplier Test ih Set package default values BG Set test case default values junit tests extensions org juni tests experimental theories 7 Summary junit tests extensions org junit tests junit tests junit tests runner junit samples junit tests framework JUnit Classpath p ATemp_PVAtTeststellung PyAyunitd Mote Only classes that are inthe JUnit classpath can be selected za Prey Met gt Finish Cancel Figure 368 Step 2 The correct JUnit test class is automatically selected TEMPPO Extension Panama In the next step new test packages and test cases will be detected Since we removed two test cases in the import step see Fig 90 they will be detected as new We also removed test package Framework Tests see above so it will also be detected as a new JUnit test suite Fi Update JUnit Tests Sa E xj Steps Add Hew Test Cases 1 Introduction Select the new JUnit test cases to add 2 Select a JUnit test elass 3 Select new JUnit test canes SLES 4 Select obsoltete TEMPPO junit samples VectorTest Select Al test cases i 5 Se
194. e 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 values where the user and password must be specified The user profile is exported to standard out Page 301 User Manual Edition July 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 fil
195. e 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 Plugain Versiton Ovi Plugin Author Muster Max Plugan Class temppo plugin api MyPlugin 9 1 Plug in Version Change Listener A TEMPPO plug in must implement the Plugin interface or one of its sub interfaces Plugin is the super interface for all plug ins It serves methods for basic plug in information and load and unload handling e g loading and saving plug in settings VersionListenerPlugin Is the interface for a concrete plug in which can be used It extends Plugin and serves as a hook for version change notification The plug in developer has to implement a class file packed into a jar file which extends VersionListenerPlugin This class file has to be implemented in the package temppo plugin api After starting TEMPPO the listener is registered and the actions of the plug in are executed when the version is changed in TEMPPO e g by activating another version of test structure by creating a new test suite Page 303 User Manual TEMPPO V6 1 Edition July 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 304 User Manual TEMPPO V6 1 Edition Jul
196. e in the test structure will be applied to the test suite and you can execute this new or edited test step Fi TEMPPO Testmanager Demo Notepad EE Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test abject Version sre ROOT v1 1 1 H 4b WH E Mo fitter i Test object version xY Fuco a 3 Detailed description of the required g Elia 3 4 Required functions of the prod Requirements History Attributes TR Previous Resuts Plan Execution History A 3 4 1 File Administration General Attributes Test Steps Automation BAN 3 441 New A 34111 New efi Ey ed Search FUncHORS File Mew pick Message gt save Unbenannt Ed 5 changes Al z Find g Datei Bearbeiten 3 4414 Find up 34441414 Cases G 3 4 44 4 2 WinPur 3 4 4 1 1 3 QuickT E 34 4144 Test Pe Speichern unter Fl 3 4 41 1 5 UA no gt ffnen Speichern RTF Import with Tos duction eral description of the product ied description of the required product features scope of delivery sequences cenarios of interactions with thi User goals Required functions of the product 3 4 1 File Administration A 3 4 1 1 New fil 3 4 1 1 1 New file opened no change 3411 2 New file opened changes E 3 41 2 Open E 3 41 3 Save offnen E 3 41 4 Exit Speichern 3 4 2 Edt Functions 3 4 3 Print Functions 3 4 4 Search Functions soot E E EP Merge Lock Apply Discar
197. e 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 the batch file TEMPPO bat in the installation directory for running TEMPPO with command line options TEMPERO Daw CxXPOUl CeStSlLruclLure my pro secu Lie test Structure VlZ export xml Page 302 User Manual TEMPPO V6 1 Edition July 2014 Plug ins 9 Plug ins TEMPPO offers a plug in mechanism which automatically loads the implemented Java interface packed into a jar file Each plug in must be deployed in its own jar file and must be installed in the directory lt TEMPPO installation directoy gt plugins A jar file always contains a manifest file which must contain at least the property Plugin Class which must provide th
198. e on it The philosophy of this concept is to upload a file only once and create more references on it if necessary Page 171 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F Upload Properties of launcher properties X General Eg launcher properties tl Origin C AProgram Files TEMPPO 6 OWauncher properties S Size 2 10 kByte Created 16 02 2012 17 55 04 Owner Tester References 0 Type Upload Description Figure 205 Upload properties Upload a new file You have to activate the Upload button to open Figure 205 for specifying a special name and description Additionally owner creation date size the number of references and the type are displayed iieb File ES Database EI Command EJ manual Test Case Reference E ores Figure 206 Hyperlink database Use an existing upload You have to activate tab database and press button create reference to uploaded file to open Figure 207 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 207 and Figure 206 Page 172 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F Uploads 7 X Find a size launcher properties Testmanager 14 02 2012 14 02 33 2 10 kByte logging properties Testmanager 14 02 2012 14 03 06 1 35 k Byte rfimport_1 3293207502261 631 1329320750320 png Testmanager 15 02 2012
199. e path without drive letter see chapter 3 3 21 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 x Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test 11 H dadb HM EE no fter 2 General description of the product 3 Detailed description of the required product features E 341 Scope of delivery E 3 2 Sequences scenarios of interactions with the environmen 3 3 User goals 3 4 Required tunctions of the product AL 3 4 1 File Administration O EME 3414 Mew fi 3 4 1 1 1 New file opened no changes fi 3 4 4 1 2 New ffile opened changes oo 3 4412 Open 1341 3 Save 53 414 Exit 3 4 2 Edt Functions 3 4 3 Print Functions La 3 44 Search Functions BAJ 3 4 44 Find EGS 44 41 41 Find up El 3 441 141 Case sensitive 3 4 4 1 1 2 WinRunner Check Stat lif 3 4 441 1 5 QuickTestPro Test case 3 4 4 1 1 4 Test Partner Test case 3 44115 UA x General Attributes Test Steps EY Automation Recuirements History Plari Execution History UniversalFile Tool UniversalFie File fev
200. e require E 4 1 Scope of delivery f 4 2 Sequences scenarios of i 4 3 User goals BAJ 4 4 Required functions of the pi GS 4 41 File Administration Poi PER 4 4 1 1 Windows Login MMII Login Oi i E E 441 2 New E 4 4 1 3 Open 4 4 1 4 Save E 4 4 1 5 Exit E 4 42 Edit Functions B 4 4 3 Print Functions ff E 4 4 4 Search Functions E 4 4 5 Help System General Attributes Test Steps E Date User Property Info Action Comment 20 02 2012 10 26 57 Testmanager General change 20 02 2012 10 26 57 Testmanager Steps add 20 02 2012 10 53 04 20 02 2012 10 56 57 Testmanager Steps change 07 03 2012 14 51 01 07 03 2012 14 51 01 07 03 2012 14 51 01 Testmanager Platform Windows 7 System Test 07 03 2012 14 51 01 07 03 2012 14 51 01 Device type Type Validation gt Verification change 07 03 2012 14 51 01 Regressiontest add 07 03 2012 14 51 01 add 07 03 2012 14 51 01 Milestone M1 ada 07 05 2013 13 46 22 User defined ID 07 05 2013 13 46 38 Name change 07 05 2013 13 46 38 Test Goal TEMPPO V6 1 Description of Use E 4 5 External interfaces of the pi H S 46 Other product features regi H E 5 Specifications for project manage 4 m E 6 Obligations of the client E 7 Literature pir m
201. e 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 inherit attributes Page 49 User Manual TEMPPO V6 1 Edition July 2014 Description of Use You also have to specify a working or development state for the test case This is necessary for reporting analysis and creating test suites For example the test manager wants to create a test suite only with test cases that are ready for test execution If such an attribute does not exist or has a wrong value the test execution will fail The working state consists of the following values Designed The test case is created and the data in the tabs General Attributes Requirements are specified This state was introduced for the purpose of supporting test teams that separate the work into designing and implementing test cases This is the default state of a newly created test case In Work The test case already contains test steps but is not ready implemented Ready for Review This state is not obligatory it can be used for projects where test sp
202. ecification 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 creating the test structure see 3 1 2 2 1 and want to use the test case in a test execution for an acceptance test you can achieve this by adding Acceptance Test as an additional test level for this test case For the execution of the acceptance test you would then specify this test level as a filter criterion for your test suite see 3 1 4 1 Additionally you can set attributes specified in the Meta Data Editor see 5 3 which can also be used for creating a test suite By specifying a sub string in the Find field you can easily navigate to the attribute s to be related to the test case Multi select allows moving several values to the right part of the window see Figure 41 x Device type zi value tribute l ED wi A Milestone a car c R Offshore 4 Test location 0 Value tribute EF windows 7 64 bit Platform Device
203. ect 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 64 User Manual Edition July 2014 TEMPPO V6 1 Description of Use F Update J x Should the following attributes of the existing test structure be retained during the update process E Attribute inhertance E Requirements E Requirement inhertance Figure 61 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 general parameters in the TEMPPO settings For creating such a test case you have to select UniversalFile Figure 62 Test case settings for Universal Automation Interface and fill in the following data In the text field File you have to enter th
204. ed if the test collector finds test suites named like described above for further details see 6 3 2 Whit Import Warning B xj duplicate names in the same hierarchical level The import of these elements will cause an automatic renaming in TEMPPO and the references to their JUnit counterpart will be last G There are elements in the selected JUnit Suite with Figure 357 Warning of duplicate test suite names The related test suites are marked accordingly and can t be selected for importing Page 280 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fi Import JUnit Tests x Steps Test Case Selection Introduction Select all the JUnit test cases to be imported z Select a JUnit test class Select a set of JUnit test cases Select test cases EH Framework Tests Select All FH junit tests extensions Extension Test a E test Running Error In Test Setup x O testRunning Errore in Test Setup 4 Set package default values 5 Settest case default values Deselect Jl it Summary O test SetupError Dont Tear Down E test Setup Error In Test Setup Bo junt tests extensions Active Test Test El testactiveTest z O test ctive RepeatedTest a H testActive Repested TestO O testActive RepeatedTesti AS junt tests extensions Repeated Test Test test Active Repeated Test junit tests extensions Active TestTest TEMPRFO Extension JUnit ee Prey Next gt Finizh Cancel Figure 358
205. ed 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 Fa move ownership to l X atwi12hg Testeri tester2 testers tester4d testers testerG tester Testmanager temppo_um Figure 324 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 325 all test levels are displayed with name owner and creation date Page 258 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator lj 21 02 2001 00 00 00 21 02 2001 00 00 00 21 02 2001 00 00 00 21 02 2001 00 00 00 21 02 4001 00 00 00 Figure 325 Metadata Test Levels A new test level can be added by pressing the button New in the tab Test levels and Figure 326 is displayed Fi Properties of New Entry xi 8 Ej Properties of New Entry X General Details General Details p Sub system test Created 20 027 2012 15 14 46 Owner Testmanager Type Test Level Description Figure 326 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 poss
206. eeeeeeeeeeeeenes 60 3 1 3 1 7 Automated test CaSES cceeccceeeeeccrsscecceuueenenenreeeeeesnssegs 61 3 1 3 2 Reworking the Test Structure ccccc cece cece neces eeeeeeeeeeeeneees 67 3 424 Test Case EXGCuvlonistscagusseivenessescadus osavasesseesauwesearanerseeauusosarasess 67 LAL Starting TeSt EXECUTION erkeers E Ea ENE ASENN 68 3 1 4 1 1 New Based on current test StruCtUre cece cece eeeeeees 70 3 1 4 1 2 New Based on a predecessor cccccssecceccueennceereeeeeeeessegs 76 3 1 4 1 3 Copy Based on an existing test Suite sessssssererserrrernns 80 3 1 4 1 4 Special Based on an existing test suite with restrictions to test results81 5 1 4 1 5 Manual Test Ex xecuUtON wnsccenciinnitunsaatoesecanwdenwatawantenes 82 SkA G PlaNiawenanstetusieccedneesivenes EEEE ERONEN 86 3 1 4 1 7 Test Result AttributeS ssssessessssssnnnnnnnnnnnnnnnnnnnnnnnnnnnas 87 3124 150 PECVIOUS RESUICS siciicoatcsstanwsadians nnn nEn art 87 3 1 4 1 9 Enter new bug entry aczsists concniacadenrtanontigassanvenbiaseemmnngeeas 88 3 1 4 1 10 Automated Test Execution ccccccccssccccesnsenneenreeeeeeesnsegs 92 3 1 4 1 11 Mixed Test Execution ssssssssssssrrrsernrnnennrnrsnrnrnnrnrenens 93 3 1 4 1 12 Setting several reSults cccccceecccnssceccecneeneeeuueeeeeeenssegs 93 3 1 4 2 Pausing and Continuing Test Execution sessssssssrsrrerrrreren 94 3 1 4 3 Editing Test Cases during Test Execution sssssssersrr
207. efresh Func reg30 1 Func reg32 1 SQ SI Oa a ae se sa a a ea ea e a Figure 138 Requirement analysis over several test suites Data In tab Detailed Data for each requirement a column Requirement Structure and columns for test results with the TC IDs are displayed For each result cell a list of comma separated values is shown as follows lt test case ID gt lt test suite name gt lt test structure version gt lt next test case ID gt lt test suite name gt lt test structure version gt Page 121 User Manual TEMPPO V6 1 Edition July 2014 Description of Use T m Test Suites Select Test Suites New Test Suite V6 1 1 New Test Suite V8 1 1 Requirement Structures Select Structures Components Notepad Requirement attributes Y Chart EE pata E Detailed Data y Requirement Requirement Structu failed passed not executed not on Chart Horizontal Bar Chart b Func_req2 e an m a Sort Func_req21 Je g Fo F alphabetical Func_req22 __ Notepad V1_ E _ tc536 New Test Suite V6 1 1 A oe TO ascending F Not V2 itc536 New Test Suite unc_req22 otepad ew Test Suite pa ing Func_req23 Notepad V 1 l tc742_1 New Test Suite V6 B Pe l Func_req23__ Notepad V2 aia Ris _ tc742_1 New Test Sut l FF Values Func_req24 E a is m 6 Al Only zero valu
208. egory Xd lock Apply Discard Figure 169 Refresh recursive menu also in the context menu 3 2 2 1 3Refreshing on certain user actions An item is automatically refreshed including its lock state and the presence of all direct children after the following actions selecting in the tree view pressing the Lock button If these actions are done on an actually deleted item the following dialog is shown and the item is removed from the view Li x A Cant find tem in database Maybe the tem was deleted by another user Figure 170 Deleted item information after trying to select or to lock 3 3 General principles and user prompting 3 3 1 Inline images In any text fields you can mix up text with pictures images When you click in a text field followed by right mouse button you can activate the menu item Insert image and a window Figure 171 opens where you can either select png bmp jpg or jpeg files from the files system or any existing ones from the data base Page 148 User Manual TEMPPO V6 1 Edition July 2014 Description of Use LA Insert image C Usersiatwl 12no Documentsiscreen shot PNG Figure 171 Insert image After pressing OK the image is automatically uploaded to database and displayed in the text field Cut copy paste functions on images are possible TEMPPO Testmanager Demo Notepad Notepad vet Hilo ies Lite EE E General description of the pro
209. elogic 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 fl User Interface Tree ee ter Cells Server fsesa435 21 2 paralysis e Nlewsboard Port e644 Test Suite Database Context FO aS eeeomenon Database tutorials Telelogic Change H Silk Test iin Runner File of list box entries S H Universal File H Universal Socket l QuickTest Pro File of default values S Test Partner TEMPPO Designer IDATG Authentication Seve User Jat 0832 lCommands i H New Command Pazaword reanna i Java32 El Change Management Role user F Bugzilla Restore Defaults OK Cancel Figure 304 Telelogic Change Page 243 User Manual TEMPPO V6 1 Edition July 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 Database Connection la Database Users Ai Migration OSN User documentation C Ps Databaze oracle SID Jakes schema temppo_um Host Jatinzpt ga Fort f 521 User jatw112h9 W Login manually DE Test User femppo_um Password Connect Database Mame Database Version Figure 305 Manager Database Oracle In this tab you can define var
210. ement Structure added Owner Testmanager Updator Created 19 05 2010 14 06 10 Updated Type Test Structure SITEMPPS Designer UDAT C Test level EGEE Description ere 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 f Project Test Structure Edt Test Execution Evaluation Toole Windows Help l0 x Test Structure Notepad generated System Test 4 l l m x AL Notepad generated f 1 Introduction i 2 General description of the pre General Attributes Test Steps Ei Sutomeation Requirements History Plan Execution History 3 Detailed description of the pri fa 3 1 Scope of delivery 3 2 Sequences Scenarios fil 3 2 4 Sequences scer 3 iser AE A p aTe eal Requirement Structure version B 3 3 User goals Peh 4 c q L E 3341 User goals Func_reqe6 Mew Notepad WH All E Inherit oe 3 4 Required functions of tk Mew implemented 4 3 4 1 File Administratior requirements ER S414 New 3 4 1 2 Open kf 3 44 24 Open 2 S 3 4 1 3 Save ae F Figure 9 Generated Test Structure 3 1 2 2 20pening a Test Structure Using Test Structure gt
211. en m 3 41 3 Save O po hei 341 4 Exit 3 4 2 Edit Functions 3 4 3 Print Functions Ee 4 3 4 4 Search Functions b AAG 3 4 41 Find O E 344141 Find up fil 3441141 Case sensitive 3 4 4 1 1 2 WinRunner Check Stat HE 3 44443 QuickTestPro Test case g 3 4 4 1 1 4 Test Partner Test case 34 4415 UA 5 x General Attributes Test Steps EJ Automation Requirements History Plari Execution History Toal TestPartner File 4 Script Data Scriptname project Lock Apply Discard Figure 60 Create TestPartner test case 3 1 3 1 7 2 Ranorex For importing test cases and folders from Ranorex you have to select test structure root activate the menu item Import structure gt from Ranorex Document and a open file dialog is displayed where you can select a Ranorex project file csproj After pressing the button open the file is imported and test cases and test packages are generated The following table shows the mapping Ranorex Test suite Test case Folder Record Table 1 Ranorex TEMPPO mapping After importing a Ranorex test suite you can add change or delete test cases in the Ranorex studio When finished you can update the existing TEMPPO test cases and test packages by activating the menu item Update structure gt from Ranorex Document selecting the corresponding csproj file and pressing the button Open If the update process is started in Figure 61 you can sel
212. en 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 Schnittstelle a a AutoToolAdapter getResult ein aus returnFromAutoTool Reader Result getResullt Hs getSummary String My Adapter MyResult gertResult int getSummary Object getResult ein aus returnFromAutoTool Reader Result Figure 385 Class diagram of an adapter implementation Interface temppo test tools adapters tTAutoToolAdapter Page 316 User Manual TEMPPO V6 1 Edition July 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 TResult implementation Interface temppo test tools IResult The result returned by the adapter must implement this interface public int getResult Must return one of following results defined in IResult PASSED FAILED BLOCKED NOT_EXECUTED NOT_COMPLETED NOT_IMPLEMENTED ON_HOLD public String getSummary Must re
213. er 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 33 is shown At first you have to select the requirement structure and its requirements are listed The requirement selection dialog allows you to link one more or all requirement s to the package If more requirements are linked they will be displayed in alphabetical order All requirements selected before are shown grey Ei Requirement selection Find P dd Func reqz2 Sequences scenarios of interac im g Func _reg23 User goals i 4 bia Func req24 Required functions of the product 4 ba Func _reg25 File Administration 44 ba Func _reg26 Mew ba Func _reqz Open ba Func _reg25 Save Ata Func reazg Exit E Figure 33 Requirements Selection After pressing OK the requirement s are linked to the test package 5 x Project Test Structure Edt Test Execution Evaluation Tools Windows Help e Test Structure Notepad RTF Import with TCs System Test u1 E m E x L Notepad RTF Import with TCs E1 Introduction HL 2 General description of the pre General attributes D
214. eractions with the environment eg User goals fa Required functions of the product F File Administration H Edit Functions H E Print Functions J Search Functions a Find Replace i Za Help System a External interfaces of the product eg Other product features required H A sf Finish Cancel TEMPPO Test Suite Generator lt lt Prev Figure 77 Test structure pre selection test packages In the 3 step you have to enter name together with a description for the test suite Figure 78 When pressing Next you have to determine the logical expression Figure 79 which is pre selected like the predecessor Page 77 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Bj Test Suite Wizard 7 F x Steps Determine the test suite 1 Introduction Enter test suite name 2 Choose creation mode 3 Select an existing Test Suite 4 Select nodes or subtrees 5 Entertest suite name Test object Version XYZ RCO2 6 Determine the logical expression 7 Remove test cases manually Created 16 02 2012 14 19 55 Owner Testmanager Type Test Suite Description TEMPPO Test Suite Generator Cancel Figure 78 Name and comment Bj Test Suite Wizard x Steps Determine the test suite 1 Introduction Select and apply fiter or attributes values and logical operators 2 Choose creation mode 3 Select an existing Test
215. errrrerene 94 3 1 4 3 1 Adding new test cases during test case execution 05 97 3 1 4 3 2 Adding and changing test packages during test case execution97 524 64 lt FINGING BUC IDS siccue scuehcaacacaataciesbeuresetaeiag a priunineaeriaoeeeanen 98 3 1 4 5 Finishing Test EXSCution s cisisansaaiadiospeyiieeewtiadiaaiawiaanedisoteesavas 98 31 46 Creating More Test SUES 2222 t280 cos han caniaceel cots OE 98 3 1 4 7 Test case execution with an exported test suite 0088 99 3147 0 EXPO a test SUITS esre sire Enn aena TEAREN 99 3 1 4 7 2 Test case execution with an exported test suite 101 3 1 4 7 3 Importing test results ooicsaacetassiaamensiecesgsssscetureasaannsnsegess 101 3 1 4 7 4 Unlocking the test suite n ssssssusssnnsssnrnnnnrnnensrnrsnenrennn 103 Sle EVIA ON ansi a E A S 103 LEL SANGIVSIS ogari ai a EETA E aea 103 3 1 5 1 1 Analysis with previous test SUITES s sssssserenrrsrrererrrrrrns 106 3 1 5 2 Requirement analysis sissuvstitieacviiisDeetes decane iiteaaaaeeter eee 107 3 2555 Afalysis Py BUG UD DFO CCU cinniri nan 110 3 1 5 4 Analysis by Bug ID test SUuite ceeeeeeeeeeeeeeesseeeeenreens 111 Ihs Progress CHARS wataicccu testa a iiacaaw a 111 Skoal Creaton Progres ipana EE a AE 111 2 l2 EXCCULION PROGFESS risinn eei a a 113 SulzosO REDOING asise a a a aaeretatenesedues 122 DESG NCW 7 EdE graria e AEE N 123 3 1 5 6 2 Report of several test suiteS sssessss
216. es Func_req26 Notepad V1 tc537 New Test Suite V6 1 1 aa ee T T or 2 1 i No zero values Func_req26 Notepad V2 tc537 New Test Suite Func_req27 Notepad V 1 tc536 New Test Suite V6 1 1 Func_req27_ Notepad V2 i a __ tc536 New Test Suite Func_req28 Notepad 1 tc703 Ne tc702 New Test Suite V6 1 A J L a es ee ee An FIN tT the A lin Figure 139 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 If atest structure is opened reporting for test structure is opened via Evaluation gt Report selected gt Opened Test Structure e If atest structure is opened reporting for more test suites is opened via Evaluation gt Report selected gt Several Test Suites e If atest suite is opened reporting for test suite is opened via Evaluation gt Report selected gt Opened Test Suite
217. est Case Implementation 4 Test Case Execution 5 Evaluation The following chapters describe in detail how the tasks of these phases can be solved more efficiently by using the TEMPPO test management tool During all chapters a pseudo system test for the MS Windows Notepad application will illustrate the usage of TEMPPO more clearly 3 1 1 Test Planning The definition phase covers the tasks of Writing the Test Plan Writing the Project Plan Defining Test Case Attributes Baselining Importing requirements 3 1 1 1 Writing the Test Plan The test plan is a process document and writing is outside the scope of TEMPPO However it s the base document for all test topics during the development process and covers subjects like test requirements test management test documentation test goals end of test criteria etc Its contents are obligatory for all members of the test team 3 1 1 2 Writing the Project Plan As an output of the test plan 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 14 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 1 1 3 Defining Test Case Attrib
218. est Case manually created 12 09 2012 14 21 01 Test Case manually created 12 09 2012 14 22 11 Test Suite manually created 22 11 2013 13 46 46 Test Case manually created 22 11 2013 13 46 42 Test Case manually created l Treiber Testmanager 22 11 2013 13 4641 Test Case manually created _ o aaaaaaammmmI Figure 331 Copy of UDA Rename the attribute by changing the name of the attribute see Figure 332 If the checkbox Copy values is clicked the values of the attribute to copy example values of Milestone are copied too If the checkbox is not clicked only the attribute is copied not the values Created 09 12 2013 17 13 31 Owner Testmanager Type Attribute Copy values Figure 332 Copy and Rename 5 4 5 Uploads If you activate the tab Uploads Figure 333 you can Upload new files without any reference View uploads properties Delete uploads from the database Delete all non referenced uploads Page 263 User Manual Edition July 2014 S 3e36d25bbb_1265288210525_1385124398879 jpg 49 ADIS Phase 1 20mi 38 Auto i coverage_1273655456963_1385124396112 jpg g launcher properties 9 Navigation Demo xmi F result coverage_1265266203103_ 1365124394534 jpg 4 screenshot_128283857250942838_1282838572962_13 9 screenshot_128283857250942838_1282838572962_13 a screenshot_128283857250942838_1282838572962_13 screenshot_136560483620619091_1365604836346_13 Telematics xmi
219. est Execution Evaluation Toole Windows Help Test Suite Test object Version v2 RC01 41 1 1 x H d b HW EE ho fter EF 12 Test object Version sre ROO i 3 Detailed description of the required g General Details Export Info Attributes Predecessor Plan Attribute values Lock Apply Discard Figure 75 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 test cases manually In the first step the test suite tree is shown Figure 82 where you can select an existing test suite that will be used for pre select all settings in the wizard Page 76 User Manual TEMPPO V6 1 Editi
220. est Partner JUnit TEMPPO Designer DATS i Ranorex El Commands H New Command ESE El Change Management Bugzilla Clear Quest Telelogic Change i JIRA Restore Defaults Cancel Figure 286 Settings Test suite 3 3 21 2 6 Database For the settings of database see Figure 287 Page 227 User Manual TEMPPO V6 1 Edition July 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 Userl1 edits a TC in latest version User2 creates new test suite Userl saves TC and the new test structure version is reloaded Check Locks in Test Suite 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 clie
221. est cases Nar Set package default values Set test case default values Owner jatw108s2 Summary oa Test Package v Test Category Description This description applies to all new JUnit test suites IV Add description Updated by TEMPPO from JUnit Suite TEMPPO Extension Panama lt lt Prev Next gt gt Frish Cancel Figure 371 Step 5 Test package default values can be entered In step 6 Test case values can be entered Fi Update JUnit Tests Steps Summary Introduction Select a JUnit test class 1 Review your settings S Dalect niw JUnik bed cares You choose to update the TEMFFO test package J Select obsolete TEMPPoO Al JUnit Tests test cases 5 Set package default walues with the JUnittest class 6 Set bert cone default values uni sampes ANT ests 7 Summat TEMPPO test cases 2 new test Cases will be added 1 obsolete test cases will be permanently removed TEMPP Extension Panama amon ae rms pu Page 289 User Manual TEMPPO V6 1 Edition July 2014 JUnit Figure 372 Step 5 The summary of the update wizard Fi TEMPPO atw108s JUnit extension tests Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Sample JUnit tests Module Test 1 H d gt W ame JLind test E E Al Jura Tests junit samples Vector Test Jy testCapacty junt samples VectorTest Jy te
222. etails Requirements History Pian os 3 Detailed description of the rec Sa 3 1 Scope of delivery l Inherit _J 32 Sequences scenarios Ea 3 3 User goals Alla 34 Required functions of th E341 File Administration A 03 4 2 Edit Functions E 9 3 4 3 Print Functions product requirements Sao 3 4 4 Search Functions HL 3 4 4 1 Find 33 442 Replace o 3 4 8 Help System BAJ 3 5 External interfaces of th e 3 5 1 User interfaces PoP 3 5 14 Editor Pane ff 3 5 1 2 Search Diak i 3 6 2 System interfaces SR Other nrocdiict fest lt a a Func_reqe4 Required Notepad W1 All functions of the implemented Page 44 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Figure 34 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 F TEMPPO Testmanager Demo Notepad O x Project Test Structure Edt Test Execution Evaluation Toole Windows Help v Test Structure Notepad RTF Import with TCs System Test 4 f ojx Hod b H hior i e J Notepad RTF Import with TCs 2 1 Introduction Hh 2 General description of the pre General attributes Details Requirements History Plan 3 Detailed description of the rec a C 3 41 Scope of delivery Inherit
223. 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 108 The default database name is TEMPPO_export mdb Page 99 User Manual TEMPPO V6 1 Edition July 2014 Description of Use RS r i OsCS Look in E temp Fi gt E m T o extd7680 Zuletzt atg vernendete 9 lEreg Riala ieee co reszuk Deskto E Eigene Dateien Fr a Aarbeitzplatz T File name temppo_export ma Save Peers Files of type Microsc Access Database mdi 7 Cancel i
224. f i fo myResults res e myErrors err Page 66 User Manual TEMPPO V6 1 Edition July 2014 Description of Use In this case the user specifies the general settings for all test cases in the TEMPPO Test Manager Settings Arguments o lt lt ResultFile gt gt e lt lt ErrorFile gt gt and the individual settings in the TEMPPO test case automation tab File temppo test case bat Additional Arguments acy ea If we assume a drive letter setting U the preview window shows a full command line like this U temppo test case bat f i o lt lt ResultFile gt gt e lt lt ErrorFile gt gt where lt lt ResultFile gt gt and lt lt ErrorFile gt gt will be replaced with generated file names including the paths specified in the Administrator at execution time For example lt lt ResultFile gt gt will be replaced with C Documents and Settings atwlt5q2 Result 20021202 1723 test Case out 3 1 3 2 Reworking the Test Structure Possibly you will have to rework your test structure after a review or due to changes of the software under test Editing of the test structure is supported by the Cut Copy Paste functionality Edit gt Cut Copy Paste which even allows you to copy or move around complete test structure sub trees By using Edit gt Order gt Move Up Move Down you can change the order of test packages or test cases as well Edit and evaluation functionalities are also available over the conte
225. f 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 name CDATA REQUIRED gt it will be automatically value CDATA REQUIRED gt it will be automatically lt l cannot created gt lt Se cannot created gt 13 3 DTD Schema for XML Import Results with CLI lt xml version 1 0 encoding UTF 8 gt lt ELEMENT TEMPPO EXCHANGE LOGIN RESULTS gt lt ELEMENT lt ELEMENT lt ELEMENT lt ELEMENT USER PCDATA gt PASSWORD PCDATA gt PROJECT PCDATA gt LOGIN USER PASSWORD PROJECT gt lt ELEMENT lt ELEMENT SUMMARY RESULT lt ATTLIST RESULT testsuiteid CDATA REQUIRED testcaseid CDATA REQUIRED value CDATA REQUIRED PCDATA SUMMARY gt gt gt lt ELEMENT RESULTS RESULT gt Page 311 User Manual TEMPPO V6 1 Edition July 2014 Appendix 13 4 DTD Schema for XML Export User Profile with CLI lt ELEMENT LOGIN ROLES BUGZILLA gt lt ATTLIST LOGIN name CDATA REQUIRED superuser CDATA IMPLIED result CDATA REQUIRED gt lt ELEMENT PROJECT PCDATA gt lt ELEMENT ROLE PROJECT gt lt
226. f the heading if it is different to the Standard one Heading Uberschrift 1 2 3 It is initialized with Heading e 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 e 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 e Generate test packages If checked test packages will be generated Test packages will be generated from document paragraphs which are formatted Page 23 User Manual TEMPPO V6 1 Edition July 2014 Description of Use with the standard formats Heading 1 Heading 9 or berschrift 1 Uberschrift 9 in German documents Their hierarchical position in the test structure will correspond to the heading level in the document e 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 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
227. ffnen Strg 0 Speichern Strg 5 Speichern unter Untitled Notepad in title bar Figure 17 Generated complete test structure Test cases were generated due to the tables in the chapters 2 1 1 1 and 2 1 1 2 The data in column Action was used for test step Instruction the data in column Output for Expected the image for column Action Image The column Comments was ignored A reference to the imported document was applied to all generated test packages which made them be displayed with the yellow folder icon This test structure can still be extended by adding more test packages or test cases if necessary For each package that is a leaf in the test structure tree at least one test case should be defined Of 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 Page 27 User Manual TEMPPO V6 1 Edition July 2014 Description of Use such as headings formatted with Heading 1 Heading 9 or Uberschrift 1 Uberschrift 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 import Structure From RTF Document Update From XML Document l of Export structur
228. finement can be done by adding further 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 Fi TEMPPO Testmanager Demo Notepad 4 2 ioj x Project Test Structure Edit Test Execution Evaluation Toole Windows Help e Test Structure Motepe Test Package Ctrl A T a Test Package before Gl Test Case Ctrl A Shaw Details Gl Test Case before b H Find and Replace Ad Notepad ATF Irr E E 1 Introductior Select All Cirit 2 General de es Details Requirements History Plan Flo 3 Detailed de a E Tree j a 3 41 Scop h foss Compare dh Cut Ctrl x E Search Functions Ep Copy cirie p Testmanager Updator Testmanager Etrit 4 15 02 2012 16 28 59 Updated 16 02 2012 08 12 20 e Test Package i Order o Delete a 4 Specificatia LL 5 Obligations 6 Literature 0 7 Annex KF Ectit Fitter Test automated test case i Refresh recursively fa Move Owner
229. flag have set the same value the value is displayed otherwise the selection is empty ml Additional Test Levels and Attribute Values The values that are assigned to all selected test TPs are displayed as usual white background color The values that are not assigned to all TPs are displayed in a special color grey background color If you want to assign such an attribute to all TPs select it right mouse click and activate we Pes E EES Such attributes or new assigned attributes are displayed in red color Direct inked Attributes Inherited Attributes Inheritance Priority Top r State Designed Attribute Values io TP Type User case F xD Tab Inherited Attributes displays common Toere Test Packages Test Case state of TPs which have inherited attributes Generai Attributes Requirements FOMA Drecinked ties Inverted troutes merianee Radio buttons If all selected TPs with activated inherit flag have set the same value aaa ee Pa the value is selected otherwise there is a foes pe no selection Combo boxes If all selected TPs with activated inherit flag have set the same value the value is displayed otherwise the selection is empty ml Additional Test Levels F E F xE The
230. for result files created by the automation tool The created result files are read from TEMPPO for obtaining the automation results e Result Viewer The result viewer is for opening and viewing the result files It depends on the result file format which viewer can be taken use a text editor e g notepad for WinRunner result files use QuickTest Professional Result Viewer for QuickTest use SilkTest for SilkTest result files e Arguments The automation tool is called via its command line interface This field shows the arguments which are passed to the automation tool during the call Normally the default arguments should fulfill your needs for test automation but for special cases the arguments can be adapted study the command line specification of the automation tool first For the definition of the argument you can use the parameters lt lt TestFile gt gt automation file to execute lt lt ResultBaseDir gt gt Result Path and lt lt ResultDir gt gt generated directory for results during automation Attention Not every tool supports all parameters Use the Default button to restore the default arguments If the check box in the bottom of the tab is checked the temporary automation files will be deleted after automation Page 231 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 21 2 7 2 Universal File Automation Interface For UFAI Universal File Automation Interface you have to activate the
231. 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 188 User Manual TEMPPO V6 1 Edition July 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 Additionally you can decide between Simple or Whole word search in combination w o Case Sensitive mode 3 3 9 1 1Find Test Case Test Package There are three possibilities for finding test case s package s e Find Next With clicking Find Next the first test case package is searched and selected in the tree The first occurrence is marked too With the next click the next occurrence is marked If there are no more occurrences in the test case the next test case package would be searched If there is no element anymore a message is shown see Figure 226 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
232. g reg28 Func rego Fung reg30 Fune regal 2 Fune regqa2 Al Fung rega3 Func_reqa I Only zero values Fune_rega No zero values Fune regq45 i reqhes reg Refresh req 85 requeay Mfailed E passed Mnotexecuted Bblocked Mnot completed Hnotimplemented Mon hold wn a E a a a E Figure 137 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 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 120 User Manual TEMPPO V6 1 Edition July 2014 Description of Use By pressing the button Save As the chart can be saved as jpg or png file Tab Data In tab Data number of test results are displayed as table and exported to csv Test Suites Select Test Suites New Test Suite V6 1 1 New Test Suite V6 1 1 Requirement Structures Select Structures Components Notepad Requirement attributes Chart Horizontal Bar Chart m rae Sort 1 descending Values 2 a 1 6 Only zero values 3 9 No zero values 1 gt 3 ES aa e ba a DAG A i Eepe ul 3 R
233. 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 341 is enabled if a project or a test structure or a test suite is selected After pressing the button Move Ownership the following dialog comes up x e e e ati 12h Tester tester ye al Testmanager ores Figure 346 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 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 271 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator 5 5 7 Freeze Unfreeze loxi Database 2 Roles E Users 8 Metadata LA Projects Lacks License
234. h as rapid response times are A Safety required are to be avoided Exactvalues should best 5 Portability be Used 6 Reliability A number of examples of speed features include 7 Maintenance Real time time sharing batch 5 Reuse Response times 3 gas 288 nd p p Startup times Pecricalors TOF proje manageme Th roughput rate 5 Obligations of the client iui RAs tinn LB Literature i E 7 Annex T Figure 31 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 document name chapter Page 39 User Manual Edition July 2014 Ei TEMPPO Testmanager Demo Notepad Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test pu MH d b W GP E monter L Notepad RTF Import with TCs FA 1 Intraduction E 2 General description of the product 5 3 Detailed description of the required pr 0 3 1 Scope of delivery 3 2 SEQUENCES Scenarios of intere 53 3 User goals 5 i 3 4 Required functions of the produi BL 3 4 4 File Administration
235. hart 309 Orientation horizontal bertical Representation a jal jal la T si Cases Sug sbaolute onl oo rebative 355 i533 3 I Accumulate da a R gig Time Settings i s g gg a 8 8 8 Stort 09 12 2001 El Created End 09 12 2004 Ey Ura is ornis 200 Janu ory _ rs a i i 2501 Gecamben State BOeigned Bin Wok E Ready BB Ready foi Review Figure 156 Test case creation progress Test case creation overview test structure Graphical settings Y axis Sum of test cases X axis Test packages of first level Value subdivision State Display data absolute Chart Selection 3D Stacked Bar Chart Page 140 User Manual TEMPPO V6 1 Edition July 2014 Description of Use MS Betigned BinWok BReady MB Ready toi Review Figure 157 Test case creation overview Test execution progress graph test suite Graphical settings Y axis Sum of test cases X axis Tested Value subdivision Result Date Unit 1 Day Accumulate Data no Display data absolute Chart Selection Line Chart Page 141 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Gl chart E bata H Acme Tested Ya Axis Test Cases al Fi Grupby Ret ff Chart Lins Chart 36 Orientation horizontal a2 vertical Represerdation absolute rebates Accumulate Li Lit v m m2 T m t 20 4 Tim Settings start 09 06 200
236. he Layout if you want your data to be displayed in continuous text or table format Furthermore you can set Format options Do not ignore information fields with empty values Do not generate heading numbers You can limit the size of your report by defining the depth absolutely You can use the slider to limit the reported test structure or test suite tree depth to a fixed level You can add Summary information _about your test package by checking Number of Test cases and or Test Steps The amount of contained test cases test steps will be reported for each test package either in absolute form or by percentage Finally you have the possibility to Generate heading numbers in your report CA TEMPPO report setting in project Demo Notepad es o lt pn i Name NewReportSetting W Generate Heading Numbers Limit depth of report Summary Options Display Number of C Test Case Test Steps Figure 144 Report General Textual Settings Continuous Report Test Package Test Case Test Case Attributes Test Result Attributes Test Step Requirements For each reported object you can define which data the report shall contain If you don t want to show Test Packages Test Cases Test Case Attributes Test Result Attributes Test Steps or Requirements click on the checkbox above the lists Multi select allows moving several values to the right part of the window Page 127 User Manual TEMPPO V6 1 Editio
237. he file system to uploads to a test automation tool to a command or to a test case can be created for the following text fields Description project test structure test package Precondition test package test case Postcondition test package test case Test goal test case Instruction input expected test case Result output actual result bug ID test case in test suite Page 170 User Manual TEMPPO V6 1 Edition July 2014 Description of Use B Bold talic U Underline gt Hyperlink SS Remove hyperlink zE Eownaad Figure 202 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 202 which opens the Hyperlink window see Figure 203 E web S Fie Database URL Jett fn Figure 203 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 204 E B web File Database File C AProgram Fiesi TEMPF O 6 0qunicher properties OK Cancel Figure 204 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 referenc
238. he 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 219 User Manual TEMPPO V6 1 Edition July 2014 Description of Use DA TEMPPO Testmanager ADIS Advanced Driving Information System Project Test Structure Edit Test Execution Evaluation Tools Windows Help to41002 Blue dis es fed route contains fa to41716 Blue displayed route contains i T te41747 Blue displayed route contains Type Test Case ID ted 1002 Requirement ID 1450 Requirement Name Blue displayed route contains white arrows after each mancever On TC will be marked as obsolete Steps EA 4utomation User defined ID lto41717 Name Current car position drive roundabout Owner Schlosser Dietmar Updator E fi 4 mong the route Created 27 08 2010 14 24 14 Updated 15 06 2011 09 26 15 Type G Manual Automated Test Case Test Goal Figure 277 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 Tas
239. he 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 89 User Manual TEMPPO V6 1 Edition July 2014 Description of Use B New Bug TEMPPO my xi fusca Tet SS inspected E Tes w cies SCO 5 New PR TEMPPO m EI Atl a D 2 PO Ce l N S Page 90 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Figure 97 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 99 Limitation With IBM Rational Clearquest s interface it is not possible to attach directly the test report Page 91 User Manual TEMPPO V6 1 Edition July 2014 Description of Use iNew Bug TEMPPO x Standard Fields Project Test Project v Summary First bug entry in JIRA Componentis component 1 Version s 4 9 Version s 4 o component 2 2 0 Assignee v Priority Major x Environment a Description A bug ocurred Attachment Add Test Report Vv Custom Fields Unknown f 1 0 Backport to Version S GE Release Note omes Figure 98 JIRA Project Test Structure Edit Test Exe
240. he x e amp 4 Q a F H Demo Notepad m Example for versioning ce Link test cases to requirements Fe Notepad generated o E Notepad ATF Import O E Notepad RTF Import with TCs O Be EM Test Suites for W1 1 2012 02 16 El eaitable version A Test object Version v2 RCO1 16 02 2012 A Test object Version YYZ RCO 16 02 2012 Test object version XYZ RECD3 16 02 2012 Test object Version X 2 RCO3 COPY 16 02 2012 ee Notepad System amp Acceptance Test dA User documentation Figure 347 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 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 unfree
241. herefore 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 ioj x database Roles Users metadata CA Projects 6 Locks amp License 2i a J Exclude test suites Suppress export locks xample for versioning ey Link test cases to requirements Notepad generated EH Notepad RTF Import 1 editable version E Notepad RTF Import with TCs thd 2 1 Test Suites for V2 1 20124 E 141 editable version g Version 2 of T 2 Branch 3 editable version Notepad System amp Acceptance T Fi User documentation Figure 348 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 ioj x z Database e Roles Users a Metadata DH Projects By Locks a License a Demo N
242. hes of an administration unit Page 306 User Manual Edition July 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 307 User Manual TEMPPO V6 1 Edition July 2014 Appendix 13 Appendix 13 1 DTD Schema for XML Import Test Structure lt ELEMENT TEMPPO EXCHANGE PROJECT TS TP gt lt NOTE these attributes will not be part of the TEMPPO exchange format creator CDATA IMPLIED too many error possibilities creator will be importer created CDATA IMPLIED date will be taken from import NOTE following elements we currently ignore PROJECT ES SE lt Common PCDATA elements gt lt ELEMENT DESCRIPTION PCDATA gt lt ELEMENT PRECONDITION PCDATA gt lt ELEMENT POSTCONDITION PCDATA gt lt ELEMENT TESTGOAL PCDATA gt lt ELEMENT INSTRUCTION PCDATA gt lt ELEMENT INPUT PCDATA gt lt ELEMENT EXPECTED PCDATA gt lt ELEMENT VALUE PCDATA gt lt ELEMENT PROJECT DESCRIPTION REQUIREMENTSTRUCTURE TS gt es Currently IGNORED gt lt ATTLIST PROJECT name CDATA REQUIRED gt lt the TEMPPO project must already exist gt lt ELEMENT TS DESCRIPTION TP gt lt currently IGNORED gt lt A
243. hrough a sequence of test suites predecessors Activate Evaluation gt Analyse selected gt with current opened explorer gt All and Figure 119 opens In the Analysis dialog you can set group values on the Y Axis and chart type Page 106 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Group by Result Chart Vertical Bar Chart Onentation oo o horizontal a 25 ta a kK vertical ha o Representation mH absolute o relative Accumulate RGO 1 31 14 RGO2 We 1 4 Test Suites E passed Mfailed O blocked Don hold Snot executed Figure 119 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 125 Figure 120 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
244. i ay ga P4 Bearbeitung zur cksenden Bearbeitung beenden l Al X f O E E a E a E E A E A E NT 3 Name of Test Structure Systemtest i i 4 Owner nn i i 5 Description i 6 Updator i i Updated i Details 10 Owner nni 11 Description i i 12 Test Category i i 13 Path Systertest New Test Package 14 Created 10 06 2008 15 33 49 i i 15 Document Name i i 16 Document Chapter Updator nni i 18 Updated 10 06 2008 15 33 49 19 Precondition i i p New Test Case 21 Test Goal i i Path Systerntest New Test Package New Test Case 23 Created 10 06 2008 15 33 49 i i 24 ID tc12383 25 Priority Top i i 26 Situation Regular 27 Test Case Type Validation i i 28 State Designed i i 29 Type manual i i 30 Updator nni 31 Updated 10 06 2008 15 33 49 32 Precondition i i 3A Tast Stane i i v M 4 gt rh Temppo_Reporting 2 a gt Bereit NF A Figure 155 Report Excel Page 139 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 1 5 6 5Sample Charts Test case creation progress test structure Graphical settings Y axis Sum of test cases X axis Created Group by State Date Unit 1 Month Accumulate Data yes Display data absolute Chart Selection 3D Stacked Bar Chart Bi chert EE Data X A rested i sti i s SOSOSOSC CSY Yeas Testcases amp Goby Ewe S Chart Stacked Vertical Bar C
245. ible 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 259 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator 5 4 3 Test Categories Test categories are used to denote test packages that contain only test cases of a special type 21 02 4001 00 00 00 21 02 2001 00 00 00 21 02 4001 00 00 00 21 02 2001 00 00 00 21 02 4001 00 00 00 21 02 4001 00 00 00 21 02 4001 00 00 00 21 02 4001 00 00 00 21 02 2001 00 00 00 21 02 2001 00 00 00 Perfomance Test Portabaity Test Relabdity Test Resource Test Reuse Test Safety Test Security Test State Based Test admin admin admin admin admin admin admin admin admin admin Figure 327 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 i x
246. ible 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 fully separated environments So it can be that a latest test structure version works with a not latest requirement structure version This is always the case after an update of a requirement structure An automatic update of the current test structure version to the latest requirement structure version may not be wanted by the user and would cause problems anyway e g if more than one user work on this version It s only possible to update to the latest requirement structure version So an update to the latest requirement structure version can only be made manually initiated Open the TEMPPO test management environment and open the project and open the project and test structure The menu item Test 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
247. idiesen ieee leat as taens 239 4 TEMPPO Manager ssssssssssns22020202020202020202020202unnnnnnnnnnnnnnnnnnnnn nn 244 4 1 Database Connection s sssssssssssrsssursnrsnsnrunsnrnnsnsnnrunrnrunsnrunenreneun 244 4 2 User management ermesini aa E AY 245 42A MS WNdowW TOG I se tasaantaie sni eri EE AEE 246 4 2 2 Eogh WIEN DASSWOLG trvasitiachainsicevansciineiandekmltawiedessneatmnieand 247 AZo Yser Proper eS eiio e e a a ake 247 4 3 Database Migration cccccccccssccecesneeeeeneueeeeecensseeecuueennanurtesseesnssegs 248 5 PEMPPO AGMIMISUAlON siiicdesiiescersiuesawedcnssserusuecebecinussnraduusaseediweaenens 249 5 1 Database COnne ClO orrasa aea a a a a aa 249 Died ROMS oianean E EEA AA dak weaned Malsndn adie 250 Deo WISE management ise tet nt cecwnnd aaa a wahendanenedediies 253 Srb JD AP ippa EEEN 254 Scll LDAP COMNACOUON oesesesrese sadan eann EE EEEE 254 S32 Importing Users from LDAP riers rianan a a 255 5 3 1 3 Synchronizing users with LDAP cccceeeeeeeeeeeeeeeeeeeeeeeeeeeas 256 DA Metajdatarris ninin a EO 257 54At General BENAVION tunnecunmrcensteuraacenes wai tance E E ENNEA 257 5 4 1 1 New Metadata Entries ssssssussssnssnrnnnnrnsnnrsnrnnnnsnrnnenernrnns 257 5 4 1 2 Delete Metadata Entries sssssssnnsnrnrsnnnsnnrnnrnrnnsnrnnensrnrnns 258 5 4 1 3 Move OWNMEESIID risiiisiirrv ceis nri niniira inai A N 258 Dre TESELGVEIS ciniisandneiaraiseuessaivosdatpieeivoiainetsterseveuserisedabaueeseeieenest 258
248. ied 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 240 User Manual TEMPPO V6 1 Edition July 2014 Description of Use l User Interface Tree Test Step Cells Analysis Basic Authentication activate O ta Mewshoarcd User linterna Test Suite REREERELELEEREEREEEEEERELEEEEEAREEAREEEREEREEEREEEEERELEREAEEEREEEREEREEEEEEREEREEREREEREEREEEREES Database Password ssssssesnsrsnnansnnanannansnnanananinnaninnatinnaninaatinantinantinasQQnanAnnnsAnnnaatna ents Fl Test Automation H Silk Test Hetin Runner Universal File URL nttp tatinzpt Oga 24S bugs_temppo_internal Universal Socket QuickTest Fro User testmanger atos net Test Partner T fee 5 JUnit assword TEMPPO Designer DATS i Ranorex Fl Commands New Command ESE Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 301 Settings Bugzilla 3 3 21 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 241 User Manual TEMPPO V6 1 Edition July 2014 Description of Use User Interface Tree Test Sten Cell pos Jatt 927 168 1467
249. iew of the required function General restrictions Hardware and software specificat 6 Product users M 3 Detailed description of the required prac Ea 3 1 Scope of delivery Sequences scenarios of interac D 3 4 1 1 1 Mew file opener 3 4 1 1 2 New file openec 3 41 12 at Packs Merge Apply Discard Figure 186 No filter Project Test Structure Edt Test Execution Evaluation Tools Windows Help 5 x a Test Structure Notepad RTF Import with TCs System Test 01 1 1 Menge Apply Discard amp 81 S amp amp amp Figure 187 Set Filter Page 163 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 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 188 Anew common value is written in red with a white background color see Figure 189 Fi Attribute value selection Attribute atrote vae
250. ile opened changes not executed J Search Functions 2G Find Find up E Case sensitive not executed nA pwn Determine the logical expression 6 Remove test cases manually Af QuickTestPro ed A fTest Partner Test case not executed A JUAI not executed TEMPPO Test Suite Generator lt lt Prey Figure 70 New Remove unwanted test cases Finish Cancel After clicking Finish the current test structure version V1 is checked in If you could open the version tree browser now you would encounter the following situation x oe Motepad RTF Import with TCs Edit Bevi EAHA Test Suites for W141 2012 02 16 I Check In W441 editable version boo editable worsion Activate id Werge Tree style Versions only Labels only Yersions and Labels ClearCase style Order ie azcending i descending Figure 71 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 the criteria defined in the Page 73 User Manual TEMPPO V6 1 Edition July 2014 Description of Use logical expression Furthermore test packages whe
251. ill not be exported importer 4 0 Figure 261 Export Wizard step 2 Results for found modules will be exported results for not found modules will be skipped If a requirement is covered by more than one test case a unique result will be built according to following rules for description of test results please refer to 3 1 4 1 5 e not executed if all test cases are not executed e passed if all test cases are passed e failed if at least one test case is failed e blocked if no test case is failed and at least one is blocked Page 211 User Manual TEMPPO V6 1 Edition July 2014 Description of Use e not completed if at least one test case is passed and all others are not executed e not implemented if at least one test case is not implemented stronger than on hold e on hold if at least one test case is on hold When the export is finished the user will be informed via message box TEMPPO Z Test suite successfully exported to Doors Figure 262 Message box export finished The Export can be canceled at any time by clicking the cancel button in the progress monitor Progress P Starting server Pad Cancel Figure 263 DOORS Export progress monitor The User is asked for confirmation then and if he confirms the export is stopped y Do you really wank to cancel the import process Figure 264 Doors Export confirm cancel 3 3 18 1 Effects in DOORS Fol
252. inistration Database Connection 244 249 Database Migration 248 User Management 245 253 Analysis 103 Bug ID project 110 Bug ID test suite 111 Previous test suites 106 Requirement analysis based on several test Suites 119 several test suites 114 Several test suites 113 Apply 190 Attribute 15 activation 184 customize See Metadata Attributes B Baseline 15 C Command Line 301 D Database connection See Administration Database Connection See Administration Database Connection Discard 190 E Evaluation 13 103 Excel import Test Cases 28 40 Execution progress Standard 114 Export test suite to DOORS 209 E Filter 198 change 200 criterion 202 delete 201 Edit filter criterion 204 export 205 import 205 Predefined 198 Find and Replace 187 Freeze unfreeze 272 TEMPPO V6 1 Index H Hyperlink Download an upload 177 Edit 177 existing upload 172 File 171 new upload 172 Remove 177 to description 170 to fields of test case in test suite 170 to instruction expected input 170 to precondition 170 to test goal 170 to to postcondition 170 Web 171 Hyperlinks and Uploads 170 Implementation Phase 13 Import Characters from other fonts 209 from Excel 28 40 J JUnit 276 Test execution 290 Update 285 K Keyboard Quick navigation 58 L LDAP 254 License Server See Administration License Server Connection Locks 273 Find 144 Login with password 247 Main Window 18 Merge Multi
253. inks to requirements with requirement structure name and the requirement ID e Fixed Attributes Importing the document displayed in Figure 15 with settings displayed in Figure 16 will generate the test structure displayed in Figure 17 Please consider that importing is applied on the selected test package 10 x Project Test Structure Edit Test Execution Evaluation Tools Windows Help z Test Structure Notepad RTF Import with TCs System Test 1 M gt HW Bi non d Notepad RTF Import with TCs HH 1 Introduction 2 General description of the produ General Attributes Test Steps E Aitometion Requirements History Plan Execution History H 3 Detailed description of the requir 3 1 Scope of delivery Oor instruction e Expected Action image g 3 2 Sequences scenarios of Ga 3 3 User goals File New pick Editor Pane cleared 3 4 Required functions of the p Datei Bearbeiten Format Ansicht EH 3 4 1 File Administration H A 3 4 1 1 New 3 41 11 New file il 3 4 1 1 2 New file 3 4 1 2 Open 3 4 1 3 Save Seite einrichten n 3 4 1 4 Exit Drucken Strg P HH 3 4 2 Edit Functions HE 3 4 3 Print Functions Beenden 3 4 4 Search Functions J 3 4 5 Help System 3 5 External interfaces of the 4 a 3 6 Other product features rec a 4 Specifications for project manag eg 5 Obligations of the cliert za 6 Literature SJ 7 Annex
254. instead If the JUnit suite object has no name and no defined test class e g new TestSuite the test package gets the current java object name of the JUnit Suite e g junit framework Suite 12345 Notice that this name doesn t refer to the JUnit suite and thus the reference is lost Since this will disable a proper update the JUnit suite should be always created either by giving it a name or by defining a test class It is highly recommended to create a JUnit suite by giving it a name or by defining a test class in the constructor Otherwise the referenced Test Package in TEMPPO will get the temporary object name of the suite e g junit framework Suite 12345 If this happens the reference to the JUnit suite is lost and a later update won t work properly Page 283 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fi TEMPPO Testmanager Demo Notepad E Ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Helg Test Structure JUnit System Test v1 SE 1 Framework Tests 5 1 1 junit tests extensions Extension Test General Attributes Details Requirements History Plan Hkg 1 44 test RunningErrorinTest Setup junit t say 1 1 2 test Setup Error In Test Setup junit tes ID pres 2 junit tests extensions Active TestTest ay 2 1 testActive Test junit tests extension T Ry 2 2 testActive RepestedTest0l qunittests Mame junit tests extensions Extension Test
255. ion The tab Precondition does not display the oe Pen common state of Precondition of the selected f aa _ TCs You can enter a precondition which can be Override existing Precondition applied to all selected TCs containing an empty This precondition is valid for all selected TCs precondition Additionally you can set a flag Override existing Precondition 3 3 2 3 1 4 Test Package tab General This tab is reduced to the combo box for test category If all selected test packages have set the same value the value is displayed If Tasca there are test packages with different test 0r CE categories an entry with Several Categories is selected If there is no selection an empty entry is selected Page 158 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 3 1 5 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 genera Attroutes requirements not set the inherit flag Type and Situation radio buttons If all selected TPs without inherit flag have set the same value the value is selected otherwise there is no selection Priority and State combo boxes If all selected TPs without inherit
256. ious database connection configurations where each is identified by a DSN Data Source Name A new DSN can be created using theL button which will prompt you to enter a unique DSN A DSN can be deleted by clicking the button A DSN can be renamed by clicking the button If you delete all DSNs TEMPPO will not be able to connect to a database For each DSN you have to specify several connection parameters which are explained in the following TEMPPO supports two database management systems selectable in the field database Depending on the chosen one you must specify several connection parameters Access For Access you just simply have to specify the path to Access mdb TEMPPO automatically creates an ODBC entry Page 244 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Manager lolx Database Users di Migration Dsn E k Pi Databaze Jaccess File CAProgram Filesi TE MPF 6 0 temppo mdb g SF Test User Password Connect Database Mame Database version Figure 306 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
257. irst previous next and last A Test Step can be given the following results not executed the test step hasn t been executed yet initial result y passed the actual behavior matches the expected one X failed the actual behavior does not match the expected one blocked the test step couldn t be executed because some pre condition failed S not implemented the test step couldn t be executed because the SW part to be tested is not implemented amp on hold the test step couldn t be executed because the SW part to be tested is postponed to another milestone Page 82 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Oj x Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RCO1 V1 1 1 J 5 x M 4 gt N GP EE No fiter ALJ Test object Version XYZ RCO1 M 3 Detailed description of the required g 3 4 Required functions of the prodi Autonretion Requirements History Attributes TR Previous Results Plan Execution History Sa 3 4 1 File Administration EEES Attributes Test Steps BA 3 4 1 1 New 3 41 14 New file ope hamama O en expected actionimage sewa e ust EE 3 4 4 Search Functions ff Unbenannt Edit 3 4 4 1 Find Save changes f Datei Bearbeiten F EHE 3 4 4 1 1 Find up j D 3 4 4111 Cases i 3 4 4 1 4 2 WinRur ties EJ 3 4 4 1 1 3
258. ite El Test Automation Silk Test Hin Runner Test Partner 2 es Unit H Ranorex El Commands i Javaa p Bugzilla j Clear Quest 2 Universal File H Universal Socket H QuickTest Fro TEMPPO Designer IDATG Mew Command Fl Change Management Telelogic Change User Interface Expand the tree to edit settings Figure 281 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 O Oo O O Silk Test WinRunner Universal File Universal Socket QuickTest Pro Test Partner JUnit TEMPPO Designer IDATG Ranorex e Commands e Change Management O O O Bugzilla IBM Telelogic Change IBM Rational Clearquest JIRA Page 223 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 21 2 1 Tree Tree settings which can be changed are see Figure 282 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 f
259. iveTest unttests extension Name ftestRunningErrorinTestSetup unittests extensions ExtensionTest ihg 1 2 2 testActive Repeated Test0 junit tests 1 3 junit tests extensions RepeatedTest Test Owner Testmanager Updator Testmanager oly 1 3 1 test Repeated Once junit tests exten why 1 3 2 test Repeated Mare Than Once qunit t oly 1 3 3 test RepeatedZero junit tests extens Type C Manual f A tomated Test Case ah 1 3 4 test Repeated Negative junit tests ex Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 28 Test Goal Lock Apply Discard Figure 364 Step 5 Names of test cases JUnit test methods Basically you are free to edit and change the automatically created structure and the names of test packages and test cases However the update function see below relies on the names to maintain the relationship to the JUnit test classes Page 284 User Manual TEMPPO V6 1 Edition July 2014 JUnit Referencing the JUnit class file In the Automation panel each test case contains a reference to the file where its code is defined This is a JUnit class file and its path is written like in Java E g a reference that reads junit samples VectorTest refers to a class file Junit samples VectorTest class F TEMPPO Testmanager Demo Notepad zZ joj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help gt Test Structure JUnit System Test 41 l x H q P H gf E Mo filter
260. iversal Socket Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex Fl Commands New Command Java3z El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Tallow duplicate names in same hierarchical level Figure 295 Junit configuration 3 3 21 2 9 TEMPPO Designer IDATG TEMPPO Designer IDATG i User Interface p Tree Application Fath Je program flesidaty binvdaty exe S Test Step Cells Analysis Connection time out le Sec He Mewsboard l Le Test cuite Communication time out feo Sec Database Fing wating time fa Sec Cl Test Automation be Silk Test Ping repeats f Hin Runner H Uniwersal File Universal Socket T Check In before Updating with data of TEMPPO Designer QuickTest Pro Test Partner i Ranorex El Commands lew Command SE El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 296 Settings TEMPPO Designer IDATG e Application path Path to IDATG exe e Connection time out Time for connecting successfully with TEMPPO Designer IDATG Page 237 User Manual TEMPPO V6 1 Edition July 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
261. junit tests extensions Active Test Test o hajg 1 2 1 testactive Test unit tests extension ogy 1 2 2 testActiveRepeatedTest0 unit tests Neme Framework Uses ce 1 3 junit tests extensions Repeated Test Test why 1 3 1 test Repeated Once junit tests exten dy 1 3 2 test Repeated More Than Once junit t Created 20 02 2012 15 57 27 Updated 20 02 2012 15 57 29 oy 1 3 3 test RepeatedZera junit tests exten ahg 1 3 4 test Repeated Negative junit tests ex General Attributes Details Requirements History Plan Owner Testmanager Updator Testmanager Type Test Package Number of TCs amp Test Category a Description Imported by TEMPPO fram JUnit Suite junittests extensions AllTests Lock Apply biscanu Figure 366 Starting the update procedure x Steps Introduction 1 Introduction 2 Select a JUnit test class oe i f ay Seleni nen intiena dees e AE a S to update JUnit test cases stored in a 4 Select obsolete TEMPPO test 5 ee Dac ae Cdies 5 Set package default values Welsch e j l The Update is based on name matching The JUnit test class will be searched for the names of the 6 Set test case default values ee La test packages and test cases stored within the TEMFFO test package you choose to update umm any TEMPPFO Extension Panama ex Prey West gt Finish Cancel Figure 367 Step 1 General description of the following steps Pag
262. k and you are ready to create collections of test cases for test execution so called test suites by means of combining the attributes defined above So the appropriate test cases can be filtered from the pool of all available ones Therefore the number of test cases of a test suite is always a subset of those of the corresponding test structure For each test structure you can create as many test suites as you like E g you have the possibility to separate test execution tasks by creating special test suites for each tester Accordingly it is important to write a good test plan especially to plan attributes which are used here see planning phase If you recognize in the execution phase that there is an attribute missing this will cost some time to add it for each test case Evaluation This is the final phase of your test cycle After executing the tests and recording their results you will analyze them and provide reports which illustrate your testing activities and 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 13 User Manual TEMPPO V6 1 Edition July 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 T
263. k lists can be exported to Excel for further working on it Page 220 User Manual TEMPPO V6 1 Edition July 2014 Description of Use DA TEMPPO Schlosser Dietmar ADIS Eee Driving Information System Project Test Structure Edit Test Execution Evaluation Tools Windows Help lt gt Task ists ae ex Eee ADIS requirements Advanced Driving Information System V1 gt V2 i New Requirement New route requirement 5 tc41002 Blue displayed route contains white arrows after es 041716 Blue displayed route contains white arrows after ec Export i tc41717 Blue displayed route contains white arrows after each manoever General zx Delete task Est Delete Name ADIS requirements Advanced Driving Information System V1 gt V2 Created 27 08 2010 Version update V1 gt V2 Figure 278 Task List 3 3 21Settings TEMPPO differs between global and application specific settings 3 3 21 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
264. ked Vertical Bar Chart Stacked Vertical Bar Chart 3D Vertical Bar Chart Vertical Bar Chart 3D Orientation You can choose the orientation of the labels on the x axis Representation Data can be represented absolutely or relatively use option buttons at bottom right If Accumulate is activated data on y axis is displayed accumulated Time Settings If you select in x axis and or Group by a date time attribute you can configure the chart by setting a start and an end date Additionally the units days weeks months or years can be set Page 137 User Manual TEMPPO V6 1 Edition July 2014 Description of Use chart EE Data X Axis Dos CT Groupby T Chart Vertical Barchat o Orientation r a3 horizontal S vertical ap Les Representation absolute relative Accumulate Time Settings s f Stet 09122004 Milestone End 09 12 2004 Priority medium E Top ut 122 bes E Figure 153 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 138
265. ked by Scheduler Start Time 31 12 2012 13 00 Execute Scheduler At Start Time Current State 0 4 Test Cases Figure 271 Execute Scheduler at Start Date e Execute scheduler manually The scheduler is locked and starts executing test cases immediately Page 216 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Locked by Scheduler Start Time 30 06 2012 13 55 o od Figure 272 Execute Scheduler 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 ee hedule r Locked by Strasser Johanna Scheduler Start Time 30 06 2012 13 55 jaj aj Figure 273 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 217 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Locked by Strasser Johanna Scheduler Start Time 30 06 2012 13 55 aj la Current State 0 12 Test Cases Figure 274 Stop Scheduler p Scheduler Mame Locked by scheduler Start Time 31 12 2012 13 00 gt E Create Player 17 12 2012 14 17 12 2012 14
266. l Search Last Name P First Mame FO Login FO Windows group FO Department PSESESMEC nn ss SSSSCSCSCisS Location ing Country NN Clear Nes Lastname Firstname logn Mal Department 1 Aigner Judith atw12083 judith aigner si PSE SES MEC L Linz AUSTRIA 2 2 Fuchs Clemens atwias2 Clemens Fuchs PSE SES MECL Linz AUSTRIA 3 H inzl Thomas atw10by1 thomas hain PSE SES MEC L Linz AUSTRIA 4 Hametner Andreas atwi ci andreas hametn PSE SES MEC L Linz AUSTRIA 5 Hametner Andreas akwor7eg pse Ydo core te PSE SES MEC L Linz AUSTRIA 6 Hampel Michael ati 134 michael hampel PSE SES MEC L Linz AUSTRIA 7 Hofmann Roland atwil4cs hofriannroland PSE SES MEC L Linz AUSTRIA 3 Holzlechner Manfred atw zsz manfred holzlec PSE SES MEC L Linz AUSTRIA J Kronegger Martin atw12903 martin kronegge PSE SES MECL Linz AUSTRIA 10 Mayrbaeurl Max atwiOst max mayrbaeurl PSE SES MECL Linz AUSTRIA 11 Moritsch Karin atwol4e6 psenllbespr1085 PSE SES MEC L Linz AUSTRIA 12 Moritsch Karin abwof3cl psekblbespr213 PSE SES MEC L Linz AUSTRIA 13 Moritsch Karin atwObme karin moritschi PSE SES MECL Linz AUSTRIA 14 Niederwieser Peter atwlOmce Peter Wiederwie PSE SES MEC L Linz AUSTRIA 15 Obermueller Peter abl 23 peter obermuell PSE SES MEC L Linz AUSTRIA El Import Close Figure 319 Importing users from LDAP You can search for a last name first name login windows group department location and
267. l Avtomeation Requirements History Flan Execution History 3 2 Seguences Scenarios e o Ea 3 3 User goals HA 3 4 Required functions of the product H j ile rministr ation Expected Enter accountin test domain and Login successful 7 Pa password i l E 3 4 1 2 1 Mew file opened no 3 4 1 2 2 New file opened ch na BY H i 3 4 1 2 3 Mew Test Package c 3 44 3 Open LEa d Sawe r Lock Apply Discard Figure 233 New items in latest structure version loj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help est Structure Notepad RTF Import with TCs System Test Puz J Notepad RTF Import with TCs EHLI 1 Introduction 2 General description of the product General Attributes Details Requirements History Pian a 3 Detailed description of the required product E 3 1 scope of delivery Mame Fie Administration 2 3 2 Sequences scenarios of interactions a Ee 3 5 User goals Owner Tester Updator Testmanager Ela 3 4 Required functions of the product et 1341 Fie Administration Created 16 02 2012 16 45 49 Updated 16 02 2012 11 28 57 ESS 411 New p 3 4 1 1 1 Mew file opened no fi 3 4412 New file opened ch Murer of TOs 2 3 4 1 1 3 Mew Test Package c o ime i Test Category bi 0 3 41 2 Open i R444 Save r Merge Lock Apply Discar Gr Type Test Package Figure 234 Items not available
268. l expression is applied Bj Test Suite Wizard x Steps Determine the test suite 1 Introduction Select and apply fiter or attributes values and logical operators 2 Choose creation mode 3 Select nodes or subtrees Fitter No filter v Apply 4 Enter test suite name Attribut Val 5 Determine the logical oe ama expression 6 Remove test cases manually Category Gui Layout Test AND Created lt 16 02 2012 AND Platform Windows 7 AND Regressiontest yes AND Req_State Implemented TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 69 New Logical expression When pressing Next the user can remove test cases that should not be executed Figure 70 The de selection can be realized with the lt CTRL gt and lt Shift gt keys Page 72 User Manual TEMPPO V6 1 Edition July 2014 Description of Use For default handling before V3 3 press Finish and all test cases remain in the test suite that will be displayed Bj Test Suite Wizard i x Steps Rework Test suite Introduction Select obsolete test cases hold lt STRG gt and lt Shift gt for mutti select Choose creation mode Select nodes or subtrees E ENAT VAR P MAOR Test object Version XYZ RCO1 16 02 2012 Detailed description of the required product features E E Required functions of the product J File Administration E E New fi New file opened no changes not executed fi New f
269. le varsi Labels only if versions and Labels ClearCase style m Order tf ascending descending Close Figure 236 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 afterwards create a new latest version that is identical with your branch wersion Do you want to proceed Figure 237 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 195 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPP
270. lowing steps will be processed during export 1 Creation of folder for test execution data if not already existing according to following naming convention Test Results lt Version gt lt Name of Test Suite gt 2 Copy of affected DOORS modules corresponding baseline or latest version to test execution folder if copies do not already exist The module is constructed by lt subfolder 1 gt lt subfolder 2 gt lt subfolder n gt lt module name gt lt baseline name gt Page 212 User Manual TEMPPO V6 1 Edition July 2014 Description of Use DOORS Database Test Results 3 1 1 A Sample DOORS Sel File Edit View Favorites Tools Help Hea e amp Favorites Location fT estHesults 3 1 1 A Sample ML pr DEW Copy Formal SITEMPPO gw Test Results E3 3 1 1 A Sample DOORS Database Description s Usemame Administrator User type Administrator Figure 265 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 4 Sample DE 1_Copy SRE File Edit View Insert Link Analysis HSe sme y Table Tools User Help DEV Copy 1 Regi 2 Aege 3 Reg
271. lowing test cases a problem was detected and a default value was used Test Case Error Example Testcase Document Properties Example Testcase Document Properties No user with the name nn1 exists Create Devroom for Product Create Devroom for Product No user with the name nn1 exists Assign Members to Gevroom Assign Members to Devroom No user with the name nn1 exists Assign Group to DevRoom Assign Group to DevRoom No user with the name nnd exists Import Masterptant Incremental Import Masterptant Incremental No user with the name nnd exists Import Masterplant Incremental Import Masterpiant Incremental Normal is an invalid value for this field so the default value was used Figure 22 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 Page 30 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 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
272. lt implements IResult String summary e int result BLOCKED public String getSummary return summary public int getResult return result 13 7 3 3 Implementation and integration steps 1 Create following subdirectories in your TEMPPO installation directory gINSTDIRs dev srco ext INSTDIR dev bin 2 Create the file INSTDIR dev src ext MyAdapter java and implement the adapter 3 For compilation a JDK 1 5 is needed Execute following command in INSTDIR dev javac classpath lib temppo jar d bin src ext MyAdapter java 4 Pack the adapter into a jar file Execute following command in SINSTDIR dev jar cf adapter jar C bin ext 5 Add adapter jar to the classpath for TEMPPO and TEMPPO Administrator via extending common classpath in SINSTDIR launcher properties lib temppo jar lib lib jar lib commons codec jar Lio VCommons herpclient Jari lib commons Logging jar lib eommons cli jare lib unio jar lib registry jar lab sql jdbc jarslib oracle jar lib poqjdbc jar Page 318 User Manual TEMPPO V6 1 Edition July 2014 Appendix lib jcommon jar lib jfreechart jar dev adapter jar The adapter is now available in TEMPPO Administrator for Universal Socket configuration For configuration of UniversalFile admin properties has to be adapted o N D automation UniversalFile adapter ext MyAdapter Page 319 User Manual Edition July 2014 14 Index A Adm
273. lt template is activated he has to add values for the mandatory attributes For details see chapter 3 3 4 2 Page 178 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 4 1 Test case template vi estmanager Test Projec Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Structure Test Structure System Test V2 General Pian Requirements Tempiate Attributes 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 General Attributes Test Steps Requirements Pian Mandatory fields V Test goal condition is mandatory Figure 216 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 216 and Figure 218 e Default values for the fixed attributes e g priority has to be In work if a test case is created see Figure 217 e Inheritance of UDAs and or defining UDAs as mandatory or with a default value see Figure 217 e Inheritance of requirements and or linking at least 1 mandatory requirement see Figure 219 e Default values for a planned tester and a planned execution time see
274. lve over time The update function makes it possible to synchronize these changes with the TEMPPO test structure contents As mentioned above the names of test packages and test cases are used as references to the corresponding JUnit suites and test methods So in order to make the update work as you would expect it do not change any of the following items Names of test packages Names of test cases a Entries in test case Automation tabs Page 285 User Manual TEMPPO V6 1 Edition July 2014 JUnit 6 4 1 Description and steps The update function allows you to update the JUnit test cases as well as their hierarchical structure in accordance with changes in the corresponding JUnit test classes There are two tasks for the 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
275. mitations e Deactivated requirement structures are not considered e If a requirement is not in a view it cannot be linked to a TC In the following example an Excel file with 3 TCs is shown Page 28 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Functional Non functional requirements requirements TF1 1 Test goal A105123 High Designed can be empty Instruction Expected Result a Fett Fct2 N Fet1 N Fet2 green NN1 Instruction2 Expected Result2 b Instruction3 pected Result3 c Test case UDA Creator A105123 Mittel Ready Instruction Expected Result1 Clean up NN3 Instruction2 Expected Result2 Instruction3 Expected Result3 Instruction4 Expected Result4 Instruction5 Expected Result5 Instruction6 Expected Result6 TF3 wowww wo wo Figure 19 Excel file for TC import A TC can consist of more lines due to the number of test steps In this case the Test Case ID can be repeated or remain empty TEMPPO recognizes a new TC if a new Test Case ID identified After selecting the csv file from above the following dialog is displayed Matching attribute names are preselected LA CSV Import You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case Name E Test Goat Prec
276. mp I Test Automation Loe Argumenta ifin Runner Universal File H Universal Socket H QuickTest Pro os est Partner TEMPPO Designer DATS arei FlCommands New Command La Javaga El Change Management H Bugzilla Cl BE Telelogic Change i JIRA Restore Defaults OK Cancel Figure 293 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 293 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 oO ooo n TM TestPartner from Compuware User Mame Admin Password EERE E Database TestPartner Configure e crcl Figure 294 TestPartner Login 3 3 21 2 8 JUnit For Junit see chapter 6 Page 236 User Manual TEMPPO V6 1 Edition July 2014 Description of Use m l User Interface Tree Test Collector at scch panama junittaolLoadingTestCollector Test Step Cells Analysis Arguments cp D Temp_PWAlTeststellung_PvA unitd 7 H Mewsboard Test Suite Database El Test Automation P Silk Test Hin Runner Universal File H Un
277. mp V2 1 Test Suites for V2 1 2012 02 16 B S v2 1 1 editable version fof i Version 2 of Test object RC01 16 Se ok cane Figure 149 Report of several test suites suite selection Page 134 User Manual TEMPPO V6 1 Fi i Name NewReportSetting El Settings Attribute Value en Test Result v IN faled passed not implemented biocked AND XxX General amp Req_Type m v Header annn K Bae Title Page ear rr n a E X Test Result IN failed passed not implemented blocked AND Req_Type Header AND Priority High Lo ce Figure 150 Report of several test suites Filter Page 135 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Additionally to standard reports you select General Information of Report which displays the selected e test suites e selected filter General Information of Report Filter attributevalue 63_ M1 Selected TestSuites Test object Version XYZ RCO3 V1 1 1 Version 2 of Test object RCO1 V2 1 1 Figure 151 Reported information LA TEMPPO report setting in proj Name NewReportSetting El Settings E Text General Information of Report _ Tabular Report General Information of Test Suites Charts Char 4 Text Charts Layout Continuous Tabular Format HTML Microsoft Word Microsoft Excel Preview _ Cancel Figure 152 Report
278. n July 2014 Description of Use Page 128 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Test Case Attributes Selected Attributes Milestone Add columns with popup menu in table header or Page 129 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Name NewRieportSetting pras Requirement Header Footer Text Continuous Report Test Package Eos Test Packag El Test Case L Test Case A Define the sequence and size of columns by drag d Inherited Ww ere attributes Select Requirement Structure csv Available Attributes Selected Attributes Eoo Figure 145 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 at
279. n 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 382 displays a sample step FR IDATG Task SubusecaseNewalreadyopened i loj x Project Edit Draw View Window Generate Help ceH2 i2e 9e 4 S S 8 a 4 a Oo ia x oy amp ee ot So SX x F Task SubusecaseNewalreadyopened E l Project Notepad Elf System amp Acceptance Test Ele IDATG Tasks e Use case File Mew Sub use case New already opened Press OK Window _closed ny H E Sub use case New completely new O SubusecaseNewcompletelynew H Use case File gt Open i 49 UsecaseFileOpen BS Taxks 3 For Help press Fl Figure 381 Design Test Cases Page 298 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Designer IDATG Mame Delay mSec Priority Condit Ente names s SCS jo i anditons Event Actions User Defined Fields Stark Window Destination Window Browse Designators Commands for Test Script Description Input data New file name Enter name Expected Result Name entered Cancel Figure 382 Task Flow Step If the user has finished
280. nctions H 3 4 4 Search Functions bn 3 4 5 Help System H Ea 3 5 External interfaces of the product Fl EJ 3 6 Other product features required ni Ea 4 Specifications for project management O5 Obligations of the client E 6 Literature ET ANNEX Merge Lock Apply Discard Owner Testmanager Updator Testmanager Type Test Package Description Figure 106 Creating new test package on branch After pressing the Apply button the user automatically asked if he wants to apply the new test package or changes on it to the latest version x The test package was modified in this branch version Would you like to apply the changes alsa in the main latest version 3 1 4 4 Finding Bug IDs If you have the problem of finding bug IDs and do not remember the test cases you activate the menu item Find and Replace For more details see 3 3 9 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 98 User Manual Edition July 2014 TEMPPO V6 1 Description of Use F Open Test Suites X Motepad RTF Import with TES EH 4 EM Test Suites for W1 1 2012 0
281. nd 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 112 which means that only the Test Execution Find and Evaluation functionality is available and only the test suite window is opened Test structures are not displayed in that restricted mode TEMPPO x i You are connected to an esport database TERIPPO will be started in arestiched manner The exported test suite willbe opened automatically now ysis al Figure 112 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 113 and colored blue if it matches to the test suite in the export database Page 101
282. nd 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 115 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 102 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Test result comparison Test Suite in Export Database Test Suite in Master Database El w A Test Suite for export a lA Test Suite tor export a B O SA1 Main Menu 2351 Er ai Main Menu 2351 Pe CD BBD iL Main Menu 28 11 2002 15 07 54 aes fi 11 Main Menu e LC BB 1_2 Main Menu 28 14 2002 15 07 56 pei 12 Main Menu be CD BD 1_3 Main Menu 28 11 2002 15 07 59 SE _3 Main Menu El W a 2 Destination Entry Ea 2 Destination Entry Ee Al 2 1 GeneralPrin
283. ne 205 32161 1 Update Process irreais 206 3 3 17 Test Suite XML Export Import cece cece eeeeeeeeeeeneeees 207 Dord EXPO errori Ehe e EE EEEE aE 207 Jo le A2 AMDO arei a E T O a a A 208 3 3 17 2 1 Import characters of other fONtS s ssssssesensrsrrererrrrrrus 209 3318 EXpOrt Test Suite to DOORS sirirarireiia na a 209 3371601 Eirects IM DOORS oars aa 212 SA TEST SUITE Scheduler ernia a a R 214 SIST Create Edit SCNeGUICK aroraa Aaa i 214 2192 Delete Schedule ecir a a Ai 215 5 3 19 9 MPOC SCNeGUIGl oriire Eai 216 3 512 924 RUN SCHEGUI EI eisir ropt nena rA 216 3 39 19 5 Protocol of Scheduler crerierinierirerane a iai 218 See TASKIS Sear E A E E S E ERNA 219 3 3 21 PECE EEE E 221 S512 lt GlOD All SGUUNGS ciceewsssccasenaiueerathiodestdareenthsicanenieeastiaderniel 221 SoZ lalek USEF IMEC ACS onii T EE ANE 221 3 O22 belie LOJON Oier n A A A AE 222 33 21 22 VEMPPO Pest Manager Settings airciririniarn chia N 222 Ll2 Mee a aN 224 Jala TeSt Step Callarse a anes 224 D2 2a ANAS S oireena E AEAN 225 Dale INCWSDOGIC riiiripnins renar A EEN 226 DILL NCSU SUICS rerna a aa E A 227 32226 IDAlLADAS Cicssteung ierni tie EEA EENE NENEN 227 POAZ ESE AULOMALION aser errare EEEE IEEE TA 230 A O JON miea a O AN A UAN 236 3 3 21 2 9 TEMPPO Designer IDATG cccccccccssssceeensenneeeneeseeeenssegs 237 Do2 AAO RINO eiiean Eepe EE ORTES EE EEA ES EEEN 238 DDd COMMANGS ieran E AOE 238 3 3 21 2 12 Change Management ianciivissiania
284. ned execution time L actual execution time Biailed E passed W not executed O blocked E not completed Mnotimplemented E on hold Plan v planned W executed Figure 131 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 116 User Manual TEMPPO V6 1 Edition July 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 133 is shown By pressing the button Select Test Suites Figure 132 is displayed where you can set a filter and select from the test suite tree with the mouse together with lt CTRL gt pressed the suites to be displayed vec tote OA Value Components v IN 683 req684 req685 i Components IN req633 req684 req635 Notepad RTF Import with TCs Tree style VI Versions oniy V1 1 Test Suites for V1 1 2012 02 16 V7 7 1 editable version Test object Version XYZ RCO1 16 02 2012 Versions and Labels Ge Test object Version XYZ RCO2 16 02 2012 Ge Test object Version XYZ RCO3 16 02 2012 ie Test object Version XYZ RCO3 COPY 16 02 2012 Labels oniy ClearCase style Order V2
285. ng 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 231 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 192 TEMPPO V6 1 User Manual Edition July 2014 Description of Use A Edit properties of selected version Example for versioning Edit tf Vi editable version L check In Check in active version Activate Activate selected version id Merge gt Tree style Merge all test cases into latest version of main line Versions only f Labels only Change tree style i Versions and Labels ClearCase style gt Order ie ascending 2 descending Close Figure 231 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
286. nherited Requirements displays the Inherited Requirements abaissa 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 Requirement ID Requirement Name mM displayed in a special color grey background color tess Componanta Fa Of course it is not possible to edit anything here req684 ComponentA R1 x req6s5 ComponentA R2 i The tab Inheritance displays the COMMON D rectinked Requirements innented Requirements Inhentancs state of the inheritance flag of the selected gt TPs If the checkbox is not activated F inherit Legend F Not inherited Notinherted all selected TPs do not have any meses inherited requirements If the checkbox is activated metea all selected TPs have at least one inherited requirement If the checkbox looks like stertedpsrtay the common state is mixed TPs with and without inherited requirements Y Inherited 3 3 2 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
287. ni TEMFPONTEMP P Otsources lspriv bat S Additional Arguments Ai Command Line Previews OsvniTEMPPOMEMPPONsourcesispriv bat 0 i lt lt ResutFiles gt 2 gt lt lt Error File gt gt Lock Apply Discard Figure 62 Test case settings for Universal Automation Interface Results of test cases Page 65 User Manual TEMPPO V6 1 Edition July 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 Manager expects the result output to be produced on the stdout stream of the executable For an executable MyExec exe TEMPPO generates a result file named yyyymmdd_hhmm_MyExec out
288. ning Error In Test Setup junit t Name lint poo he kg 1 1 2 test Setup Error In Test Setup junit tes EI w 2 junit tests extensions ActiveTestTest Owner Testmanager Updator gt mjg i 2 1 testActive Test unit tests extension Crested 12 2012 15 48 24 Updated Bo he hg 1 22 testactive Repeated Testi junit tests E 3 junit tests extensions Repeated Test Test Type Test structure 1 3 1 test Repeated Once junit tests exten hy 1 3 2 test Repeated More Than Once junit t Wy 1 3 3 test RepeatedZero junit tests extens wel System Test j hig test Repeated Negative junit tests extensions Repeated Test Test te793 Lock Apply Discard TEMPPS Designer DATS C Figure 362 Step 5 The result 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
289. nlock 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 11 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 103 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Additionally in most analyses you save your settings as favorites You can create new overwrite existing and delete favorites Figure 117 and Figure 117 show an analysis from a test structure and a test Suite displaying the number of test cases for each priority grouped by the state Page 104 User M
290. nned values a chart can be created 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 130 shows the accumulated values of 2 test suites All 2 test suites contain 134 in sum therefore 134 test cases were planned 124 test cases were executed and 10 test cases were not executed Page 114 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Favourtes RC01 RC02 Favourite 2 Release Candida
291. ns aM Testmanager 20 02 2012 13 22 51 XML File la 3 4 4 4 Find G 3 4444 Find up E 3 444414 Cas El 3 4 41 412 win Lock Apply Discard Figure 255 Export XML information TEMPPO identifies an XML file by a unique ID 3 3 17 2 Import After exporting an XML file it may be edited outside of TEMPPO e g users or test automation tools are filling in some values Valid values are e Result Failed Passed Not_executed Blocked Not_completed Not_implemented On_hold e Result Output Plain text e Tester MS Windows account or a defined user account e Tested DDMMYY HH MM SS If other values are changed they will be ignored Importing an XML file can be started by activating the menu item Import Test suite gt from XML The import is independent from the selected node TEMPPO detects the part to be imported The following possibilities are offered for importing x How should TEMPPO handle conflicting test results during import S Import only newer test results i Import all test resus ores Figure 256 XML Import e Manually choose test results to import When activating this option Figure 257 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 tes
292. nt 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 228 User Manual TEMPPO V6 1 Edition July 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 structure version for a long time then you can define a short duration Opened database connections are closed and used resources are released For example 10 minutes Page 229 User Manual TEMPPO V6 1 Edition July 2014 Description of Use PO l User Interface i Tree Test Step Cells Analysis H Newsboard Test Suite Database El Test Automation Silk Test Hin Runner Universal File
293. o at sun reflect DelegatingMethodAccessorlIupl invoke DelegatingMetl E testhormatize2jund samples money Mor at at scch panama junittool TestRumner doRun Unknown Source F b tA lesiNormaire jund samples morty Mor E te sthcemaizes pand sampdes money Mor A testPrirtipund campies money MoneyTes Test Goat E te tSnpieAdayjund samples money Mon E testSinpieBagAddijund samples money Hl testSinpieMutiply junt samples money A E testSenpietegate und samples money A E testSerpieSubtract und samples money E testSenpityQunt samples money Money al Figure 375 Failed test case result message and stack trace 6 6 Known Issues Unsupported JUnit extensions Currently only standard JUnit test classes are supported i e JUnit test cases are expected to be an instance of junit framework TestCase and JUnit suites are 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
294. object Version XYZ R001 16 02 2012 Versions and Labels A Test object Version XYZ RCO 16 02 2041 2 A Test object Version YZ RECOS 16 02 2012 Labels only ClearCase style a Test object Version XYZ RCO3 COPY 16 02 2012 Order te edabe erly ie ascending gt descending Cancel Figure 102 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 94 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fnd and Replace F3 Edit test case Saat Details Select All Crrl 4 f Tee b Run automated Set Resultis er Edit Refresh recursively Ea love Ownership g Analyse selected E Report selected Then add e g a test step see new test step 4 in Figure 103 The Apply and Discard buttons become enabled When pressing the Apply button the changes don
295. of several test suites General Page 136 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 1 5 6 3 Chart Settings In the charts settings area you can customize the charts added to your report which represents the data of your test structure or your test suite in a graphical Way s i It is possible to add more charts to your report by right a ae mouse click on chart and activate Add new chart By de ee selecting a chart right mouse click and activating Remove Rename chart chart a chart can be removed except the last one By Chart selecting a chart right mouse click and activating Rename chart or double click a char can be renamed Data Selection Choose units for the y and x axis and optionally a value subdivision Y axis sum of test packages sum of test cases default or sum of test steps can be displayed X axis test packages of first level designer date priority situation state type test levels and result only for test suite report can be applied If date is selected the time period considered must be specified Furthermore the time unit can be adjusted day week month year Group by is used for subdividing the values displayed on the y axis The selection possibilities are the same as for x axis Chart The following charts are available Horizontal Bar Chart Horizontal Bar Chart 3D Line Chart Stacked Horizontal Bar Chart Stacked Horizontal Bar Chart 3D Stac
296. ogram Files HPiauickTest ProfessionalibiniaT Report exe Hin Runner Universal File Universal Socket Quick Test Pro Test Partner JUnit TEMPPO Designer DATS i Ranorex Fl Commands New Command fe davad2 El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel ATQUMeEMs wecript 2 lt TestFiles gt IY delete temporary test automation files Figure 291 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 row E Recover Local System Monitor Log Tracking When efor occurs during min session pop up message box Object synchronization timeout 20 seconds Disable Smart Identification during the run session Save image of desktop when error occurs if test is run by the HP Business Process Morutor OF Cancel Apply Help Figure 292 QTP Run Settings 3 3 21 2 7 5 TestPartner TestPartner requires NET Framework 2 0 For Compuware TestPartner you have to activate the automation tab and select TestPartner Page 235 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Test Partner User Interface gt Tree User name tamin Test Step Cell if _ Password e gt Arial sis Newsboard Database TestPartner_Oracle Test Suite Database Temporary Path c t
297. omation While up to now test teams had to spend a huge effort for the implementation and maintenance of automated test cases TEMPPO Designer IDATG aims at generating test cases based on a simple model of the application The advantage is obvious Instead of having to write test scripts from scratch and manually adapt each of them whenever there is a change in the tested application all that is needed now is keeping the model up to date The costs for test maintenance are reduced dramatically thus leading to shorter test cycles and better product quality The unique TEMPPO Designer IDATG tool combines user friendly test specification editors with a patented test case generator that employs a wide range of systematic test methods TEMPPO Designer IDATG supports a number of popular GUI testing tools but can also generate scripts for 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 Fi TEMPPO Testmanager pemo Notepad OO lo x Project Test Structure Edt Test Execution Evaluation Toole Windows Help v Test Structure Notepad RTF Import with TCs System Test V3 oF x E J Motepad RTF Import with TCs E 1 TEMFPO Designer DATO Tasks H 2 Introduction General Plan Requirements E 3 General description of the product a 4 Detailed description of the required product teal Mame Notepad ETF
298. on _ Introduction Select the JUnit test class to be imported Z Select a JUnit test class 3 Select a set of JUnit test saeu rls West ers a 4 Set package default values A 5 Setted egsa detaultysiies 4 ActiveTestTest junit tests extensions L 6 Summar AllMembers Supplier Test org junit tests experimental theories D AllTests junit tests extensions E AllTests org junit tests L AlTests junit tests AllTests junit tests runner L AlTests junit samples T Alitests junit tests framework JUnit Classpath p ATemp_PVAtTeststellung PYAyunitd Mote Only classes that are inthe JUnit classpath can be selected Finish TEMPPO Extension JUnit zz Prey Figure 356 Step 2 A JUnit test class can be selected by which a JUnit test suite is defined Hert z After clicking next the test collector specified in the Administrator see 6 2 starts searching for JUnit test classes JUnit allows having nested test suites one test suite containing others and it also allows naming two or more test suites having the same parent test suite identically e g All Junit Tests jJunit samples VectorTest Junit samples money MoneyTest Framework Tests Framework Tests Framework Tests Framework Tests Since TEMPPO will create a Test Package for each JUnit test suite and TEMPPO does not allow identical names of items with the same parent a warning message will be rais
299. on July 2014 Description of Use Bj Test Suite Wizard E x Steps Select Test Suite 1 Introduction Select an existing Test Suite 2 Choose creation mode 3 Select an existing Test Suite 4 Select nodes or subtrees Notepad RTF Import with TCs 5 Enter test suite name Erw S PAATE EE te eee SIA Test Suites for V1 1 2012 02 16 nissan 9 V1 1 1 editable version 7 Remove test cases manually p aiibi i vererven i Test object Version XYZ RCO1 16 02 2012 VW editable version TEMPPO Test Suite Generator lt lt Prev Next gt gt Cancel Figure 76 Select a test suite Figure 77 shows the first step for creating a test suite It shows the whole test structure and the test packages are pre selected like the predecessor If you want to consider a whole test structure with all the test packages and test cases for test execution select the root node and press Next Bj Test Suite Wizard x Steps Test structure pre selection 1 Introduction Select test packages hold lt STRG gt and lt Shift gt for mutti select 2 Choose creation mode 3 Select an existing Test Suite 4 Select une or subtrees Notepad RTF Import with TCs i Enter test suite name I a Introduction Determine the logical expression Ea General description of the product T Ramcwitest caver manai E aan psoas of the required product features cope elivery Sequences scenarios of int
300. ondition Precondition Priority Priority State State Test Step Instruction Instruction C Expected Attributes UDA UDA Functional requirements Functional requirements Figure 20 Matching attributes are preselected After that you have to select the 2 mandatory fields see above which are necessary for importing TCs Additionally you have to select the attributes which are not matching Page 29 User Manual TEMPPO V6 1 Edition July 2014 Description of Use LA CSV Import oe You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by Selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case Names Test case name Userdefined ID Testcase ID Test Goal iw Owner Creator Precondition Precondition Planned tester Postcondition Postcondition Planned test execution time Priority Priority Validstion Verification State State Reguiar Error Test Step Instruction Instruction Input Input Expected Expected result Attributes UDA UDA Requirement structure Non functional requirements Non functional requirements Y Functional requirements Functional requirements Figure 21 Select non matching attributes After pressing OK the user is informed about errors of the import All test cases were importiert For the fo
301. ontext 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 85 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Set Result s xj Set Result s to i failed not executed I blocked not implemented on hold Overwrite existing resus Test Result template Attribute Assigned defaut value Brower version Firmware Figure 89 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 Fi TEMPPO Testmanager Demo Notepad i i oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Suite Test abject Version 72 R01 41 1 1 Wo d P H GP EE no nter AL Test object Version XYZ RCO 3 Detailed description of the required product features l 3 4 Required functions of the product General AES Test Steps rorencn Plan a E34 File Administration Requirements History Attributes TR Previous Results EF Ss Mew 3 4 1 1 1 Mew file opened no change lA 3 4 1 1 2 Mev file opened changes Planned tester Testert a 3 4 4
302. ooks like 5 At first sight assigning test categories seems to be superfluous because they have no further influence on the test structure than being a flag for a test package A closer inspection makes their purpose plain Firstly you can obtain statistical information from your test structure or test suite like How many functional or performance test cases does my test structure contain How many functional test cases are failed For further 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 37 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad O x Project Test Structure Edt Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test u m x H gt b Hyg Mo filter d Notepad RTF Import with TCs Fb 24 Introduction Bt 2 General description of the product General attributes Details Requirements History Plan Detailed description of the required prods Gr ll 3 1 Scope of delivery ID tr a 3 2 Sequences scenarios of interactic eo 3 3 User goals 5 Ay 3 4 Required functions of the product Mame Detailed description of the required product features E EJ 3441 File Administration i EH 59 3 4 2 Edit Functions m 3 4 3 Print Functions Created 15 02 2012 1
303. or deleting a scheduler press the Delete button The button is enabled if at least one scheduler is selected Lay Md gt wW 69 E No fiter E S 1 New Test Package E 1 1 New Test Case not executed Figure 269 Delete Scheduler Page 215 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 19 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 7 Select Test Suites New Test Structure r Tree style Versions only V1 1 Test Suites for V1 1 2012 05 03 i V1 1 1 editable version Labels only New Test Suite 03 05 2012 Versions and Labels est EEPE D ClearCase style Order ascending descending Figure 270 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 19 4 Run Scheduler For running a scheduler 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 A Scheduler Name Loc
304. or order numbers i e the number added to the internal a order which is 0 based User Interface EEEN Automatic save Test step Celle IW Save changes automatically suppress confirmation dialog Analysis Newsboard Automatic numbering Test Suite l aa Databaze M Displays automatic numbering of test cases and test packages l Test Automation Silk Test M Oniot for recursive numbering e g 1 2 3 Poin Runner Delimiter for numbering Universal File Universal Socket a Defines where numbering starts H Quick Test Pro Test Partner TEMPPO Designer DATS i Ranorex El Commands H New Command SE El Change Management Bugzilla Clear Quest Telelogic Change Bosh JIRA Restore Defaults Cancel Figure 282 Settings Tree 3 3 21 2 2 Test Step Cells For the test step cells some settings can be changed see Figure 283 Property Default Description value Refresh when resizing activated Switches on off refreshing the row heights in a multi line table when changing column widths or table bounds Multiline height 52 Sets the minimum height of the edited row in pixels in a multi line table Page 224 User Manual TEMPPO V6 1 Edition July 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
305. ore 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 143 User Manual TEMPPO V6 1 Edition July 2014 Description of Use i DSM Chooser ser Interface Gl Test Automation IY Switches on off a database chooser window on TEMPPO startup H Commands Change Management fi O Timeout in seconds displaying DSM chooser Locking E Switches onioff to lock the whole test structure before checking in and to prevent check in it an tem iz locked Check for new test structure version when saving an tem in main latest wersion Switches onJoffto check if the entire test suite is unlocked before exporting Locking Made Locking mode in test structure and test suite automatic C manual History i 0 Number of history recordsa to load Restore Defaults Cancel Figure 161 Settings gt Database gt Locking The following chapters are describing the locking in manual mode 3 2 1 1 Find locks unlock xi Unlock selected elements See RAL OEE Detailed description of the required product features User Super 23 05 2006 16 13 33 Wl Exit Yes file open changes nn 23 05 2006 15 53 55 M New file opened changes nn 23 05 2006 1553 37 di Hew Tile opened no changes nr 23 05 2006 15 53 07 Mew Test Package 1 Schlosser Dietmar 23 05 2006 15 57 36
306. otepad Example for versioning Demo Not Notepad v2 44 editable v Test Pac Find tp555 export dat 20 02 201 i uae a Demo Not Notepad v2 44 editable v Test Pac Search F tp564 export dat 20 02 201 To Notepad RTF Import Demo Not Notepad W214 editable v Test Pac Help Syst tp557 export dat 20 02 201 1 editable version Demo Not Notepad W214 editable v Test Pac Replace tp556 export dat 20 02 201 E Notepad RTF Import with TCs Demo Not Notepad v2 14 editable v Test Pac Print Fun tp551 export dat 20 02 201 a i Demo Not Notepad W214 editable v Test Pac Set Fort tp550 export dat 20 02 201 4 Test Suites for V2 1 20124 Demo Not Notepad W244 editable w Test Pac Print tp553 export dat 20 02 201 4 editable version Demo Not Notepad W214 editable v Test Pac Page Setup tp552 export dat 20 02 201 Version 2 of T Demo Not Notepad W244 editable w Test Pac Select AlI tp547 export dat 20 02 201 C Demo Not Notepad W214 editable v Test Pac Delete tp546 export dat 20 02 201 oe Notepad System amp Acceptance T Demo Not Notepad W214 editable v Test Pac Word Wrap tp549 export dat 20 02 201 Fi User documentation hed Demo Not Notepad W214 editable v Test Pac Time Date tp546 export dat 20 02 201 Demo Not Notep
307. port procedure Fi Import JUnit Tests X Steps Introduction 1 Introduction z Select a JUnit test class f f 3 Select aset of JUnit test This wizard guides you through the steps necessary to import JUnit test cases into a TEMPPO cases test structure 4 Set package default values a eee ee Anew test case will be created for each imported JUnit test case A new test package will be 5 l created for each JUnit test suite reflecting the hierarchical structure of the imported JUnit test umm anm class Mote Updating is bated on name matching The generated names of the test cases and test packages should be preserved to maintain their relation ta the JUnit classes TEMPPFO Extension JUnit fe Frew Next EN Finish Cancel Figure 355 General description of the following steps In the next step the JUnit test class can be selected All classes with names that start with All Tests are shown with a folder icon all other classes get a sheet icon This is in conformance with the TestRunner of the original JUnit distribution The icons are to some extent misleading because they suggest that only test classes with folder icons will be converted to TEMPPO test packages However each class that can be selected in this step will be converted to a potentially hierarchically structured test package Page 279 User Manual TEMPPO V6 1 Edition July 2014 JUnit F Import JUnit Tests i X Steps Test Class Selecti
308. 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 54 User Manual TEMPPO V6 1 Edition July 2014 Description of Use This tab shows only executed results over the complete version tree of the test structure For each test suite the following attributes are displayed Test Suite Version Result Bug ID Tester Tested Plan Execution History 16 02 2012 15 11 02 Test object Version XYZ RCO1 16 02 2012 15 11 23 07 03 4012 14 59 15 Figure 48 Execution History only executed results lf you want see all information for this test case over all test suites you have to activate the button Load Information for not executed test cases see Figure 49 General Attributes Test Steps IEI uion t00 Requirements History Pian Execution History Test object Version V1 1 1 editable 16 02 202 15 11 02 XYZ ROOS version V1 1 1 editable version V1 1 1 editable version V2 1 1 editable version 16 02 2012 15 11 23 O 03 2012 14 59 15 Figure 49 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
309. pre General attributes Details Requirements History Plan os 3 Detailed description of the rec S 3 1 Scope of delivery I Inherit D 3 2 Sequences scenarios E 333 User goals E 24 3 4 Required functions of th 3 4 1 File Administration l Func_reqe4 erat i Notepad E E eat Edit Funttigns External interfaces of the product unctons of ie A 3 4 3 Print Functions product Eb 3 4 4 Search Functions Fune_reqe SEQUENCES gi oe Editor Pane eee a wl 3 4 4 2 Replace interactions with po D345 Help System the environment oa 3 5 External interfaces of th o a A 3 5 1 User alaise BE B i 54 ry Search Diak E 3 5 2 System interfaces w b Lock Apply Discard Figure 36 Requirement Inherited Figure 36 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 36 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 poss
310. predecessors there is also the possibility to get known about the results in the predecessor test suites The table isn t changeable Page 87 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad e F iol xj Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version XYZ RC03 v1 1 1 M d b AGS E No fitter ALJ Test object Version XYZ RCO3 5j oh 3 Detailed description of the required g 3 4 Required functions of the prodi General attributes Test Steps BI outonction Requirements History attributes TR Previous Results plan Execution History LM 3 4 1 File Administration B E E ma Test Suite version Res Bwm 4 1 1 1 New file ope E 3 4112 New ffile ope Test object Version lt Z RCO1 1 1 1 editable version failed Testmanager 16 02 2012 1 E 2 3 4 4 Search Functions Test object Version XYZ RCO2 1 1 1 editable version not executed ve Test object Version XYZ RCOS 1 1 1 editable version passed Lock Apply Discard Figure 93 Previous Results 3 1 4 1 9 Enter new bug entry An actual behavior and in case of errors a bug ID can be recorded for each test step and for each automated test case too The bug ID would point to a problem report in a bug tracking tool like Bugzilla IBM Telelogic Change IBM Rational Clearquest or JIRA Before you can generate a bug automatically
311. r 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 15 02 2012 11 24 15 13 02 2012 16 50 26 14 02 2012 09 34 44 14 02 2012 14 54 30 14 02 2012 11 13 39 13 02 2012 17 05 45 14 02 2012 10 32 11 14 02 2012 09 20 13 14 02 2012 09 20 49 14 02 2012 09 19 32 Manual Manual Manual IEM RequisttePro Manual Manual Manual Manual Manual Manual Figure 335 Metadata Requirement Structures Test Levels Test Categories Attributes Uploads Requirement Structures J User Fields f x a show requirement attrintes __ Components Testmanager S Learning Project Use Cases 1 Figure 336 Show requirement attributes Testmanager Testmanager Testmanager 16 02 2012 11 2415 13 02 2012 16 50 26 a 14 02 2012 09 34 44 14 02 2012 14 54 30 Manual Manual Manual IBM Requisite Pro With the button Show requirement attributes the assigned attributes are shown in a new window see Figure 337 It s only possible to un assign attributes when the requirement structure is not imported Page 265 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Fj Meta Data Editor Ea Attributes
312. re stored e Result Viewer optional An editor which is best suited for viewing result and output files e 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 21 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 232 User Edition July 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 Universal Socket Universal Socket 2 Analysis MHewsboard he Test Suite fl User Interface El Test Automation be Silk Test Hin Runner H Universal File QuickTest Pro Test Partner be TEMPPO Designer IDATG i Ranorex Fl Commands Fl Change Management Bugzilla Clear Quest Telelogic Change Tree Drive Letter ee Test Step Cells Application Path C Program Files TEMPPO 6 5 4utoTools Proprietary tester bat IF Address
313. re no test cases are selected at all are not displayed Fi TEMPPO Testmanager Demo Notepad Project Test Structure Edit Test Execution Evaluation Tools Windows Help Test Suite Test object Version 2 RCO1 W1 1 1 H dab HM EE no fter j Test object Version lt 2 RCO Bfm 3 Detailed description of the required g EAA 3 4 Required functions of the prod Requirements History Attributes TR Previous Results Plan Execution History A 3 4 1 File Administration General Attributes Test Steps EJ Automation ERG 3 411 New i nett 2 New m aaa er Instruction Expected Actionimage actual R 8 3 4 4 Search Functions E 3 4 4 1 Find E t 3 4444 Find up fl 344144 Cases f 3 444142 WinRur fF 3 4 4 143 QuickT LEE 3 4 4 14 4 Test Pe B ERR REI Test Structure Motepad RTF Import with TCs System Test 11 1 1 M d4 b H GP EE wo ter oe 3 4 4 4 Exit 3 4 2 Edt Functions 3 4 3 Print Functions E a 3 4 4 Search Functions EM 3 4 41 Find EF a 3 4 4 14 Find up Db be fi 34 41 14 Case sensitive a 3 4 4 1 1 2 WinRunner Check Stat HoE 3 4 4 11 3 QuickTestPro Test case 3 4 4 1 414 Test Partner Test case 2 7 3 4 44 2 Find down oe ho 3 442 Replace 34 6 Help System E T 3 5 External interfaces of the product E e 3 6 Other product features required ni ga 4 Specifications for project management a Obligations of the client ro
314. rent test steps of the same test case 10 21 11 Zooming rules 2650 1 10 2 1 1_1 Zooming rules 2650 1 10 2 1 1_1 Zooming rules 2650 1 Figure 127 Analysis by Bug ID test suite In the text box Bug ID you can enter the bug ID or a regular expression if you want to create a list of more or all test cases that are referenced By pressing the button Analyse the test case list is shown and can be saved as csv file by pressing the button Save By selecting a test case in the window Analysis the 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 128 is shown By pressing the button Select Test Structures Figure 129 Page 111 User Manual TEMPPO V6 1 Edition July 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 follo
315. requirement updates Figure 37 is shown All assigned and updated Page 46 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 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 37 Apply requirement updates All links are changed to the new version of the requirements Deleted requirements are unassigned from the test cases Updating a requirement structure does not cause that a task list is created a task list 3 3 19 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 38 is shown TEMPPO Note X Laj i 1 There are no newer checkeddn requirement structures versions Figure 38 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 script
316. roduct features required that cover mandatory quality attributes like performance mass or stress test The result of the steps above is displayed in Figure 31 Page 38 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Ioj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help Test Structure Notepad RTF Import with TCs System Test V1 H gt b Hyg E Mo fitter AL Notepad RTF Import with TCs Fb 24 Introduction HHL 2 General description of the product General attributes Details Requirements History Pian E 5 3 Detailed description of the required prod ll 3 1 Scope of delivery ID ftp562 a 3 2 Sequences scenarios of interactic i 3 3 User goals l Pertormancse sd 5 3 4 Required functions of the product Mame Performance E 33 4 1 File Administration i EH 59 3 4 2 Edit Functions m 3 4 3 Print Functions Created 15 02 2012 16 45 57 Updated 16 02 2012 09 55 20 23 4 4 Search Functions H E3441 Find oon 3 4 4 2 Replace Number of TCs 0 Owner Testmanager Updator Testmanager Type Test Package Oi bei 345 Help System H 23 5 External interfaces of the product Test Category Performance Test 2 a 3 6 eal amie aa required Description This section describes the features which determine 2 Resource the speed of the product required values Standard 4 Security formulations suc
317. ror 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 25 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 Page 32 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad Oj x Project Test Structure Edit Test Execution Evaluation Tool Windows Help e Test Structure Notepad RTF Import with TCs System Test pu J l x El E Notepad ATF Import with Tos H 1 Introduction a a 2 General description of the product General Plan Requirements C 3 Detailed description of the required g EL 4 Specifications for project manageme Name Notepad RTFimportwithTCs SSCS 5 Obligations of the client a 6 Literature Owner Testmanager Updator Testmanager 7 Annes H 8 troduction 1 9 General description of the product 1 Type Test Structure a 10 Detailed description of the required H E 11 Specifications for project managen TEMPPS Designer IDATS D a 12 Obligations of the client 1 i 143 Literature 1 Test level System Test H14 Annex 1 Created 15 02 2012 16 36 29 Updated 16 02 2012 16 44 37 Description Lock Appl Discard Figure 25 name of test package alread
318. rt is created 3 1 5 6 1New Edit When pressing the button New or Edit a new window opens for set the properties for creating a report see Figure 141 Page 123 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 4 TEMPPO report setting in project Demo Notepad SEE E a eee ei Name NewReportSetting SB sctings General io Created 07 05 2013 11 41 09 _ E Continuous Report oe E Test Package Updated Test Package Attributes oe Test Case Attributes Test Step i Requirement Charts Figure 141 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 124 User Manual TEMPPO V6 1 Edition July 2014 Description of Use E A TEMPPO report setting in project New Project Name NewReportSetting El Se
319. s test requirements baselined requirements in TEMPPO Requirement Manager test management responsibilities planning and organization CM etc preparations for the test e g setting up the test infrastructure creating test aids conventions etc tests to be performed including test goals end of test criteria test procedures sequences etc test cases test documentation error reporting procedure TEMPPO supports the issues test cases planning design implementation execution and test documentation evaluation i e you can refer to TEMPPO in your test plan for these topics Although your testing activities just started in the phase of test planning you might already anticipate the situation as it will be at the beginning of the test case execution or evaluation phase by that time you will have a lot of test cases However you have to consider now how test cases should be designed to make it easy to 1 select a 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 Te
320. s 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 test package is selected It can be activated by the menu or a right mouse click A new child node El 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 The test cases tab consists of the tabs General Attributes Preconditions and Postconditions Test Steps Automated Requirements History Page 47 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 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
321. s Hewshoard T Versions amp Find locks Figure 11 Reopen a test structure 3 1 2 2 4Importing an RTF formatted document TEMPPO is able to generate test packages and test cases from headings within RTF formatted documents You can either generate a basic test structure containing just test packages and no test cases or even a complete test structure with test cases 3 1 2 2 4 1 Generating a basic test structure If requirements are specified in Software Requirement Specification SRS documents they can be used to generate a basic test structure The obvious advantage of creating a test structure according to the structure of a base document is that the test case to requirement relation is evident every time This enables the test responsible to easily verify which requirements are covered by test cases Page 21 User Manual TEMPPO V6 1 Edition July 2014 Description of Use tailed descripti 3 125 9pe of deli 3 225equences pO OU 44114Ne 4 240pe 41 d45ave 3 4 1 44Exit 3 4 24Edit Functions 4 4 2 14Undo 34 2 22 Uti 34 2 3 2Copyi 3 4 2 44Paste 3 4 2 64D elete 3 4027 8 aSelect Al 3 4 2 7 lime Daten 34 2 84VVord Wrapt 3 4 2 945et Font 3 4 34Print Functions 34 5 14Page Setup So 34 35 24Print 3 4 44Search Functions o 344 1 FReplace oe 344 24Find FP AE Lale Oe ee OT Figure 12 Sample Software Requirements Specification for MS Notepad dt Cz gt J J J j 4 Mooo00
322. s in the context menu see Figure 199 and afterwards Figure 200 is shown 4 4 rF Hy Jes No riter zij a 1 New Test Suite amu i New Test Package j e E New Test C Find and Replace F3 ae PM New Test Show Details el New Test Packe Select All e Tree gt p Run automated Set Resultis er Edit OS Refresh recursively Ea Move Ownership g nalyse selected b EF Report selected Figure 199 Context menu Set Result s Page 169 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Set Result s x Set Result s to Failed i passed not executed blocked f not implemented i on hold Figure 200 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 201 If a test case contains no test steps it remains not executed TEMPPO X 1 Humber of test cases with new result 5 Humber of locked test cases 0 Figure 201 Information message 3 3 3 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 3 1 Creating hyperlinks Hyperlinks to the web to t
323. s 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 signaling that the test structure in this version is checked out for editing The version tree can be displayed any time by selecting Test Structure gt Versions Although you never get
324. s 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 96 User Manual TEMPPO V6 1 Edition July 2014 Description of Use ee Motepad RTF Import with TCs Edit Ew EAM A Test Suites for W441 2012 02 16 I Check In LW editable version fe Activate M Merge all test cases into late Versions only Labels only e Versions and Labels ClearCase style r Order O azcending descending Close Figure 105 Versions After pressing the merge button a warning window comes up that asks you if you are sure to go on If you commit this window the latest version will be checked in and checked out again Then all test cases of the branch version are copied to this checked out version 3 1 4 3 1Adding new test cases during test case execution As a matter of fact new test cases have to be added to test case execution although that test phase already started Therefore such test cases have to be created in the corresponding test structure branch versions If the pre selection of test packages
325. s to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case ee E Test Goal Precondition Precondition Priority Priority Test Step Instruction Instruction Non functional requirements Non functional requirements a Figure 20 Matching attributes are preselected After that you have to select the 2 mandatory fields see above which are necessary for importing TCs Additionally you have to select the attributes which are not matching Page 42 User Manual TEMPPO V6 1 Edition July 2014 Description of Use LA CSV Import oe You can assign Excel attributes to TEMPPO ones Please activate the corresponding checkbox of an TEMPPO attribute and assign one by Selecting an item from the combobox Remark New attribute values of UDAs wil be automatically created in TEMPPO s meta data Test Case Names Test case name Userdefined ID Testcase ID Test Goal iw Owner Creator Precondition Precondition Planned tester Postcondition Postcondition Planned test execution time Priority Priority Validstion Verification State State Reguiar Error Test Step Instruction Instruction Input Input Expected Expected result Attributes UDA UDA Requirement structure Non functional requirements Non function
326. selection of changed TPs and TCs 160 Multi selection of unchanged TPs and TCs 155 Metadata 257 Attributes 260 copy 187 Page 320 User Manual Edition July 2014 Requirement Structure 264 Test Categories See Metadata Test Categories Test Levels 258 Uploads 263 User Field 267 Migration See Administration Database Migration Move ownership 186 Multi selection Delete 168 Move ownership 167 Multi selection mode 149 Multi user ability 143 N Newsboard 190 P Pictures inline 148 Plug ins 303 Progress charts 111 Creation 111 Execution 113 Requirement analysis based on several test suites 119 Project 16 copy 270 create 16 268 open 17 properties 17 Test case template 179 Projects 268 Assign metadata 270 delete 270 Freeze unfreeze 272 Move ownership 271 Test Result template 183 R Refresh 147 recursively 147 Reload whole tree 147 Report Export to XML 142 Import from XML trp file 143 Import Templates 142 New 123 Several test suites 133 Templates 142 Reports 122 Chart Settings 137 General Settings 124 preview 138 samples 140 save 138 Textual Settings 126 Requirement Analysis 107 delete 45 TEMPPO V6 1 Index Test package 43 46 Requirement Structure activation 185 Requirements Import 15 Roles 250 Predefined 312 S Settings 221 Bugzilla 240 Change 242 Change Management 239 Clearquest 241 Global 221 JUnit 236 QuickTestPro 234 Ranorex 238 TEMPPO Designer 237 TEMPPO
327. ship E Figure 26 Create new test package In Figure 27 such a test package Search Functions was identified and split up into Search Up and Search Down A reference to the document containing the 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 Page 34 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad P oj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help a Test Structure Motepad RTF Import System Test 4 f E ajx H d b Hg E Mo filter Notepad RTF Import H 1 Introduction ni E 2 General description of the product General Attributes Details Requirements History Plan FI 4 3 Detailed description of the required prods 3 1 Scope of delivery r lip g Sequences Scenarios of interactions with the environment 3 3 User goals search Functions 2 SO S lt S 5 a 3 4 Required functions of the product Mame search Functions EF 3 4 41 File Administration EH E 3 4 2 Edit Functions E Z 3 4 3 Print Functions Created 15 02 2012 16 26 59 Updated 16 02 2012 08 37 12 2 a B4 4 Search Func tic IS _ fl 3 4 44 Search up Owner Testmanager Updator Testmanager Type Test Package of 3 4 4 2 Search down Number of Tos 0 3 4 5 Help System E 7 3 5 Extern
328. splayed 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 Page 24 User Manual TEMPPO V6 1 Edition July 2014 Description of Use objects with nothing and the import of this rtf document will work 3 1 2 2 4 2 Generating a complete test structure In certain circumstances you may have already written down your test cases in a document e g test case specification This happens if you don t have a test 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 o
329. ss the button Select Test Suites A Select Test Suites E Notepad RTF Import with TCs p Besse Eb V9 Versions only EbV4141 Test Suites for V1 1 2012 02 16 VT 1 1 editable version Test object Version XYZ RCO1 16 02 2012 Versions and Labels Test object Version XYZ RCO 16 02 2012 Test object Version XYZ RCOS 16 02 2012 L Test object Version XYZ RC03 COPY 16 02 2012 Oni a v2 a V2 1 Test Suites for V2 1 2012 02 16 ascending Poi fe z 1 1 editable version descending i Version 2 of Test abject ROD 16 02 2012 ae E Page 119 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Figure 135 Select test suites Additionally you have to select the requirement structures by pressing the button Select Structures LA Select Requirement Structure Components Tesimana 16 02 2012 11 2 Manual Pe Learning Project Use C 14 02 2012 14 5 IBM Requisit 14 02 2012 11 1 Manual Notepad Tesimana 13 02 2012 17 0 Manual Figure 136 Select requirement structures Each time you change anything on test suites or requirement structure selection button Refresh get enabled If you press button Refresh chart is refreshed Test Suites Select Test Suites New Test Suite V6 1 1 Regressiontest Test Obeject 1 123 beta W8 1 1 Requirement Structures Components Notepad Fune reg22 Fune reg23 Fune reg26 Fung regq2 Fun
330. st design is either done with TEMPPO Designer available as Add on please refer to chapter 3 3 21 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 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
331. st structure Version Test Suite Test Case Test Case ID Page 110 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Eianalysis x Bug IDs Ealnare ale O02 1003 100 Load Fil Analyse Test Structure Test Suite Testcase us simo Payee S Notepad System amp Acceptance Test W1 1 1 editable wersion Field test w01 New file opened changes bce 1 oe Notepad System amp Acceptance Test W1 1 1 editable version Field test w01 New File 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 oe Figure 126 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 127 is displayed Fj Analysis X Bug ID owhe Analyse Jame eao But 10 1 1 1_1 heading up route guidance on 2416 1 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 1 1 1_2 north up route guidance off 2416 2 10 2_3 3D Map 2649 2649 A bug ID like 1 is reported in diffe
332. st structure successfully imported The imported test packages and cases are placed below the selected node Page 31 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 1 2 2 7 1 Possible errors during the import eros o reato OO 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 24 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 Figure 24 Information message er
333. st 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 71 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Bj Test Suite Wizard E x Steps Determine the test suite 1 Introduction Enter test suite name 2 Choose creation mode 3 Select nodes or subtrees 4 Enter test suite name 5 Determine the logical Test object Version XYZ RC01 expression a Remove test cases manually Created 16 02 2012 13 39 43 Owner Testmanager Type Test Suite Description hole structure Release canidate 01 TEMPPO Test Suite Generator lt lt Prev Next gt gt Finish Cancel Figure 68 New Name and comment In the 2 step you have to enter name together with a description for the test suite Figure 68 When pressing Next you have to determine the logical expression Figure 69 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 expression If you have already defined a filter for your test issue you can select it and press the button Apply The filter s logica
334. stContains jiunit samples VectorTest General Jy testEiementAtguni samples Vector Test Neme Sample JUnit tests Jy tesiRemoveblement iund samples VectorTest Owner Mwi08s Jy testClone junt samples VectorTest Jy testRemoveAlgund samples WectorTest Crested 10 12 2002 13 41 07 BB junit samples money MoneyTest Teton A Jy testBsaghutpiiunit samples money MoneyTe Structur i Jy tesiBagtlegate und samples money Money Te Test Levet Tesi Ju lesiBeghotEquals junt samples money Money Jy testBagSimple Addijund samples money Mone Description Jy testBagSubtractijunt samples money MoneyT Jy testBagSumAdd und samples money MoneyT Jy testis Zero jundt samples money Money Test Ju tesiMiced Simple Add junit samples money Mon Jy tetMoneyBagEquals unit samples money Mor Jy testMoneyBagHashQund samples money Mor Jy testMoneyEquals jund samples morty vero gt Figure 373 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
335. t 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 ATTLIST TP name CDATA REQUIRED gt lt if zero length then name New Testpackage generated gt lt l if it already exists add 1Y T 2p xas gt lt ATTLIST TP t st category CDATA FIMPLIED gt lt t If it does not exist Auton create it for the test level of the containing test structure gt lt ATTLIST TP document CDATA IMPLIED gt lt ATTLIST TP doc name CDATA IMPLIED gt lt ATTLIST TP chapter CDATA IMPLIED gt lt ATTLIST TP inherit requirements Crue Talse falge gt lt ATTLIST TP lastupdate CDATA IMPLIED gt lt ATTLIST TP lastupdateby CDATA IMPLIED gt lt ELEMENT TEST RESULT TESTGOAL PRECONDITION POSTCONDITION RESULTOUTPUT REQUIREMENT TEST STEP RESULT AUTOMATION ADD TEST LEVEL USER DEFINED ATTRIBUTE USER DEFINED ATTRIBUTE TRESULT gt lt ATTLIST TEST RESULT tc id CDATA REQUIRED gt lt 1ATTLIST TESI RESULT user defined id CDATA IMPLIED gt lt If It already exists
336. t 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 261 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator x eneral Details Browser Created 20 02 2012 151812 For Use of y Test Case Quwiner Testmanager Tesi Package Type Atribute Test sure E Test Result E Reguiremernt Description cancel Fi Properties of New Entry x General Details EF Browser Chrome E Browser Firefox ED Browser Netscape E Browser Opera Cancel Figure 330 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 262 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator Attribute Type Creation Type 22 11 2013 13 46 46 Test Case manually created 12 09 2012 14 21 37 Test Package manually created 22 11 2013 13 46 45 Test Case manually created 22 11 2013 13 46 43 Test Case manually created 22 11 2013 13 46 44 Test Case manually created 22 11 2013 13 46 45 Test Case manually created 22 11 2013 13 46 47 T
337. t 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 INSTRUCTION PCDATA gt lt ELEMENT INPUT PCDATA gt lt ELEMENT EXPECTED PCDATA gt lt ELEMENT ACTUALRESULT PCDATA gt lt ELEMENT BUGID PCDATA gt lt ELEMENT VALUE PCDATA gt lt ELEMENT PROJECT DESCRIPTION gt lt ATTLIST PROJECT name CDATA REQUIRED gt lt ELEMENT TS DESCRIPTION gt lt ATTLIST TS name CDATA REQUIRED gt lt ATTLIST TS test level CDATA IMPLIED gt lt if it does not exist autom create Page 309 User Manual TEMPPO V6 1 Edition July 2014 Appendix lt ATTLIST TS version CDATA IMPLIED gt lt ATTLIST TS lastupdate CDATA IMPLIED gt lt ATTLIST TS lastupdateby CDATA IMPLIED g
338. t Case Command Universalle Fie MTemp Testcase Ooml O00000 l Additional Arguments Command Line Previewy DaTempitest Case O cmd gt lt lt ResutFile gt gt 2 gt lt lt ErrorFile gt gt Figure 209 Hyperlink test automation tool Hyperlink with a command can be defined with additional arguments Pressing on the hyperlink defined with a command then the command is executed and then a message box shows the output of the process iieb File Database EJ Command EJ manual Test Case Command Fath e Program FilesiSiTEMFPO S 3ijretbinijava exe E Arguments Jar OStempimeinjar jar args argi Additional Arguments Cancel Figure 210 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 174 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad E joj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help e Test Structure Notepad RTF Import with TCs System Test 13 H da b W GP E No iter d Notepad RTF Import with TCs EH 1 Introduction E E 2 General description of the product
339. t Structure irccanririnonaannin n 18 Il Creating atest StruUctU e pia E ea 18 Sud 2 2 2 Openinga Test Structure ep a a 20 SileZ 23 REOPEN a TESE STUCTUTE orictoniessi aia a 21 3 1 2 2 4 Importing an RTF formatted dOcUMENt ccceeeeeeeeeeeeees 21 3 1 2 2 5 Import Test Cases from Excel as cisesatewmeerarenaneiaiewkemadeunys 28 JAA Buld Manually aamnseseccnasessanenisameenesseeniaresa aneaa TEIE 30 K222 AME IMPO eaaa EE a Ea 31 3 1 2 3 Extending the Test Structure s s ssssessssssssunsnsnnnrunsnnnnnrnnnennnn 33 3 1 2 3 1 Adding Test Packages ccccccceeccccctsceeccuueenneeureeeseeenssegs 34 3 1 2 3 2 Categorizing Test PackaGeS cccccccccseseeesseeeeeeeeeeeeeeeeeeeeas 37 3 1 2 3 3 Referring to documents sssssssssssssrsnsnsnnrnnrnesnrnrnnenrrnrns 39 3 1 2 3 4 Referring to requirement numbers OF namesS sssessssrsesss 43 2l 244 Designing TeSt CASS S irinin E N 47 3 1 3 Test Case Implementation sssssssssssenssnnsnrnrsnsnrnnenssnrnnrnrnnrnrnnnns 55 2a Implementing Test Steps aier a aa 55 3 1 3 1 1 Preconditions and PostconditionsS ssssesssssssnrerenrsrrerrne 55 SAS elie TESE tC 0S oer stes raced tir to eee oe has Senne eae Sane oes 56 3 43 13 Test Creation ASSISCAMU excecutecomsteieiaciennoetonni EE EOE 57 3 1 3 1 4 Keyboard edit MOC sciessesiwrtasacnswonrtsemngstsdavenisaeasaawseek 58 313 15 Adding More COMMMNS reriorisiennerri riar Ea 58 3 1 3 1 6 Upload paste reference IMAGES ccceeeceee
340. t Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test 11 1 1 l E x H db WH no tte Notepad RTF Import with TCs ITM 21 Introduction 2a 1 1 Purpose of the document General Test Packages Test Caze od 1 2 Validity of the document ga 1 3 Definitions of terms and abbreviati Ea 1 4 Relationship with other documents Total number of selected TPs 49 j Ea 1 5 Overview of the document a 2 General description of the product Total number of selected TCs 2 ZE 2 1 Relationship with existing projects m 2 2 Relationship with earlier and follow 2 3 Purpose of the product gg 2 4 Delimitation and embedding of the Eg 2 5 Overview of the required functions P 2 6 General restrictions Ea 2 7 Hardware and software specificat i Eg 2 8 Product users M 3 Detailed description of the required prac ca 3 4 Scope of delivery 3 2 Sequences Scenarios of interac Fy 3 4 Required functions of the product Merge Apply Discard amp amp S amp amp amp Figure 180 After Show Details content is shown 3 3 2 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
341. t allowed to start TEMPPO twice with the same login This could cause inconsistencies in the database 4 2 1 MS Window login For creating a super user with MS Windows login you have to connect to the database without activating the checkbox Login manually Fi TEMPPO Manager temppo_um Ioj x 1 Database E Users aie Migration Schema ftemppo_um Host fatinzp 0ga Port f 521 User fatw112p9 B Login manually F Test User jtemppo_um Password ge Disconnect Database Mame Oracle Database Version Oracle Database 10g Enterprise Edition Release 10 2 0 5 0 Production With the Partitioning OLAF Data Mining and Real Application Testing options Figure 308 DB connect to create MS Window Login When pressing the button Connect Figure 307 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 246 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Manager Fi User properties x General Login jit 23456 Login TYPE F automatic C manual Last Mame Mustermann First Marne mend Comments M SUpErTUSET OK Cancel Figure 309 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
342. t on speed fast fun_minimized delete temporary test automation files Restore Defaults JK Cancel Figure 59 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 63 User Manual Edition July 2014 TEMPPO V6 1 Description of Use Fi TEMPPO Testmanager Demo Notepad l Oj x Project Test Structure Edt Test Execution Evaluation Tools Windows Help a Test Structure Notepad RTF Import with TCs System Test W1 2 General description of the product 3 Detailed description of the required product features ool 3 41 Scope of delivery Ea 3 2 Sequences Scenarios of interactions with the environmen Eg 3 3 User goals 3 4 Required functions of the product Ea 3 4 1 File Administration oO B4 3411 Mew o E 3 4 1 1 1 Mew file opened no changes fi 3 444 2 New file opened changes 59 3 4 1 2 Op
343. t suite Now you can activate the checkboxes of test cases that you want to import Page 208 User Manual Edition July 2014 TEMPPO V6 1 Description of Use e Import only newer test results If a user already imported a test result for an automated test case and you also executed the same test case o Earlier the result in the central database won t be overridden by yours o Later your result will be written into the database The other result is lost e Import all test results All test results of already executed test cases are overridden by your results Note All test results that are marked are overridden in the central database after closing the window with OK A Test result comparison 7 x Test Suite in XML File v New Test Suite B v Detailed description of the required product features Detailed description of the required product features c M Required functions of the product Required functions of the product c M lt A File Administration File Administration O Ga New E EN New O Bd new file opened no changes E New file opened no changes O BB new file opened changes 31 01 2004 13 27 10 TE New file opened changes 27 01 2004 13 27 10 Fuchs Clemens Test Suite in Master Database New Test Suite E Open normal 28 01 2004 13 27 14 Save Open Tile opened changes 27 01 2004 13 27 15 Od Save O Gl Save
344. t suites 1X XP O pt Assign Requirements X 1x FP T pt id sign Testcategory X Ix T y Pt AssignTestlevel X TX po Assign UDA XX Po Assign Uploads XX pd Assign UserFields EX x FP Pt onsistency checker TX TFT ti FreezeTest Structure X TF ti id Freeze Test Suite X J TF Pp Moveownership EX TT pt id infreeze Test Structure X J ti CCC freeze Test Suite X FFT po nlock test suites X Administrator pt id Testecategories EXT XT XT XE XX S Page 313 User Manual TEMPPO V6 1 Edition July 2014 Appendix Test levels po plots XXX XK ser feds ma ee Po User User defined attributes attributes bee structure Apply requirement updates O Pe ac Edit main LATEST po export XY Ee ne ee AOA po UnitInterface TX po tock items X x Test structure root TP TC Z Z o TEMPPO Test package Assign requirements __ X X I T To ooo O Assign test categories XL L eee D 7 Edit xxix x x moe eee i TEMPPO Test case Assign requirements S allowed if user is TC editor a test Assign test level X XO A e PLTA TOATA A A OPET T P R OR oe Edit X xp x x x x f Consider User concerns only the deleting __ Merge T if user is editor of a version TEMPPO Test suite Assign test suite attributes eaa l SS IE E is only allowed if test suite has no test Edit pe E op E ee E A A A S S po mport x e e S S Remove from export database e S a S D a Unlockitems X L T XK
345. tab Inheritance displays the COMMON Directinked Attributes inherited Attributes Inheritance state of the inheritance flag of the selected TPs If the checkbox is not activated alni i cas ee Ntinheted all selected TPs do not inherit any 7 inherited partially attributes If the checkbox is activated Miinherted all selected TPs inherit their attributes If the checkbox looks like E Inhented partially the common state is mixed TPs with and without attribute inheritance M Inherited Page 159 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 3 1 6 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 Requireme parti displayed as usual in white background color Requirements assigned to not all TPs are displayed Requirement ID Requirement Name ant in a special color grey background color New OOA requirements are displayed in red color If you want req686 ComponentB R1 x req687 Componente R3 Ta to assign such a requirement to all selected TPs select it and activate the context menu aaa ee Such requirements or new linked requirements are displayed in red color The tab I
346. te V Test Result template activated Remark Test result template is oniy applied in case of result recording Test case viewing is not concerned Attributes Attribute TR1 TR2 Figure 221 Test result template In Figure 221 test result attributes are defined If you record a test result TR1 Releasel is assigned automatically and you have to specify a value for TR2 Otherwise the test case cannot be saved 3 3 5 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 and can be used e g for filtering Attribute activation can be defined for each test structure in tab Attributes see also Figure 222 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 184 User Manual TEMPPO V6 1 Edition July 2014 Description of Use TEMPPO Designer IDATG Tasks E General description of the product H a Test location 40 Test IN IN_ IN J TP Type 0 Treiber J Window 7 client Figure 222 Attribute activation 3 3 6 Requirement Structure activation In some cases requirements shouldn t be assigned to test cases anymore because they are
347. te During the creation process the current version is locked so that no other user can create a version based on the same version Is the version already locked the following dialog is shown Lock information q X FA Current label i locked Mew version could not be created Figure 165 Version locked 3 2 1 4 Creating a test suite You can only create a new test suite if the test structure and all of its items are not locked Otherwise you cannot create a test suite and you will get the following dialog see Figure 166 after pressing the Finish button on the test suite wizard memeo ij x N j There are locks intest structure Do you want to continue with creating atest suter Figure 166 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 146 TEMPPO V6 1 Description of Use User Manual Edition July 2014 see Figure 167 this is an invalid lock which can have two reasons Either you are currently running a second TEMPPO Test Manager or your last TEMPPO session terminated abnormally crash etc If so you should confirm the dialog by pressing Yes to remove all invalid locks TEMPPO Test Manager a x Warning Found locks by the current user in database Maybe another instance of TEMPPO Test Manager is running by the current user or T
348. ter 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 202 User Manual TEMPPO V6 1 Edition July 2014 Description of Use First of all you have to choose an attribute and an operator IN NOT IN If IN or NOT IN is selected the combo box value changes to a 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 251 is displayed and the attribute values are selected by moving them to the right Pressing OK applies the selection to the filter window The selected values are displayed separated by a comma Now the user can edit this line Because the comma is used to separate the selected values commas in the selected values have to be escaped with a VY e g Component 3 No blank is allowed commas has to be escaped with a A Build In Clause r LA Filter Properties 28 Name New Fiter rConditions Attribute Value Miestne v IN T M1 2 M113 M3 a ao y X se v v v v Pas M estone IN M1 2 M1 3 M3 AND Hide Empty Subtrees Attribute Valu Value Wild S e card set allowed 3 Yes if operators IN NOT IN are selected Yes if a set of values
349. tes Test Suite Selection Overall test suite analysis Press Select Test Sutes for choosing test suites Select Test Suites Result Vertical Bar Chart Show 0 values Orientati in a i m i in a H T horizontal vertical Representation absolute relative Results faled passed not executed blocked not completed not implemented on hold Plan V planned W executed Test Suites MO planned O executed W failed M passed Enot executed O blocked not completed Bnotimplemented E on hold Figure 130 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 115 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Favountes New Test Suite 1 RC01 Favourite 114 RC02 Test Sule Selection 2h 30 min Overall test suite analysis Press Select Test Suites for choosing test suites 2h 15 min Select Test Suites 2hO min 1h 45 min 1h 30 min 1h 15 min a E E 2 3 T T LL 1hO min i a absolute relative Results IM failed V passed W not executed IM blocked W not completed not implemented M on hold Test Suites E plan
350. 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 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 286 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fi TEMPPO Testmanager Demo Notepad Z ioj x Project Test Structure Edt Test Execution Evaluation Toole Windows Help Test Sucre Urt System Test VN a M dab MG EE no nter D TEMPPO Designer DAT J Juni ES 1 Framework Tests ce 1 1 junit tests extensions Extension Test O wqhy 11 1 testRunningErrorinTest Setup qunitt iaJ 1 1 2 test Setup Error n Test Setup junit tes ID prez 1 2
351. test goal is entered and the corresponding checkbox in TCT see Figure 216 is ticked if checkbox Inherit in tab Requirement is activated and the corresponding checkbox in TCT see Figure 219 is ticked if at least one requirement is linked and the corresponding checkbox in TCT see Figure 219 is ticked if checkbox Inherit in tab Attributes is activated and the corresponding checkbox in TCT see Figure 217 is ticked If an UDA plus value is assigned and the corresponding checkbox in TCT see Figure 217 is ticked If a TCT is activated and a test case with missing e g default attribute values is edited those are not added automatically 3 3 4 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 4 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 183 User Manual TEMPPO V6 1 Edition July 2014 Description of Use A esf anaq er Test Hec K Project Test Structure Edit Test Execution Evaluation Tools Windows Help a Test Structure Test Structure System Te o pes a M 4 gt M Gh E Nofter Test Case template Test Result templa
352. the possibility to specify a label Release 1 Then the version tree looks like displayed in Figure 232 The test structure gets checked out immediately and version 2 is created The symbol 2 signals the active version which is again latest Se Example for versioning Edit VI Release 1 ener ae l Ga V2 editable version 1 Check In E Activate id Merge m Tree style Versions only C Labels only Change tree style abels ClearCase style r Order _ ie ascending t descending Close Figure 232 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 233 In the prior versions items are not available of course see Figure 234 You can see the active version of your test structure in the title bar of the test structure explorer Page 193 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Testmanager Demo Notepad l jol x Project Test Structure Edt Test Execution Evaluation Toole Windows Help e Test Structure Notepad RTF Import with TCs System Test va ga 2 0 Product users M a 3 Detailed description of the required product H031 Scope of delivery General Attrinutes Test Steps E
353. tion State Designed activated inheritance have set the same value the value is selected otherwise there is n set 7 A x no selection 2S TP Type User case Ta Ta Combo boxes If all selected test cases with activated inheritance have set the same value the value is displayed otherwise the selection is empty m Additional Test Levels and Attribute Values The values that are assigned to all selected test cases are displayed as usual white background color The values that are not assigned to all test cases are displayed in a special color grey background color The tab Inheritance displays the COMMON precinkes atimoutes innented attnbutes Inheritance state of the inheritance flag of the selected TCs If the checkbox is not activated F inherit Legend T Notinherited Notineited all selected TCs do not have any Be inherited attributes If the checkbox is activated meite all selected TCs inherit their attributes If the checkbox looks like E Inherited partly the common state is mixed TCs with and without inherited attributes W Inherited Page 157 User Manual TEMPPO V6 1 Edition July 2014 Description of Use 3 3 2 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
354. tors are available SimpleTestCollector searches for JUnit classes in files matching the pattern classFileName endsWith class amp amp classFileName indexOf S lt 0 amp amp CclassFileName indexOf Test gt 0 LoadingTestCollector searches for JUnit classes by instantiating all class files in the classpath and verifying if class containsSuiteMethod class extends junit framework Test amp amp Cclass isPublic amp amp class hasPublicConstructor Page 277 User Manual TEMPPO V6 1 Edition July 2014 JUnit Settings x JUnit l User Interface Tree Test Collector at sch panama junittool Loading Test Collector ew Test Step Cells Analysis Arguments co O Temp_PvAiTeststellung_PVAyunita 7 H Mewsboard he Test Suite El Test Automation pe Silk Test Hin Runner Universal File H Universal Socket Quick Test Pro Test Partner b TEMPPO Designer IDATG i Ranorex Fl Commands New Command Tallow duplicate names in same hierarchical level i Javas El Change Management Bugzilla Clear Quest Telelogic Change Restore Defaults OK Cancel Figure 353 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
355. tpackage default valves testClone junit samples Vector Test 5 Settes cose default values El testRemoveAll junit samples vectorTest Dessert Al T Summar 5 Kj Frai sank Tezi TEMFF Extension Panama lt s Prey Next Finish Cancel Figure 369 Step 3 Two new test cases and a new test package are detected automatically Now the test case Obsolete TestCase that we created just before see above will be detected as obsolete because it is not contained in the JUnit test class junit samples VectorT est Page 288 User Manual TEMPPO V6 1 Edition July 2014 JUnit Fj Update JUnit Tests Steps Remove Obsolete Test Cases 1 Introduction 2 Select a JUnit test class 2 Select new JUnit test caves 4 Select absoltete TEMPPO test cases 5 Set package default values 5 Settert case default values 7 Summat Select the obsolete TEMPPO test cases to remote TEMPRO Extension Panama Prey Next gt Finish Cancel Figure 370 Step 4 An obsolete test case was detected and we mark it for being removed In the next steps default values for JUnit test suites and test methods can be entered just like in the import procedure F Update JUnit Tests xj Steps Package Default Values 1 Introduction Enter default values for the new test packages in SiTEMPPO 2 Select a JUnit test class 3 Select new JUnit test cases 4 Select obsolete TEMPPO General Detaas t
356. tributes Page 130 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Test Package Attributes Test Package Attributes Test Package Attributes V Test Package Attributes Selected Attributes Page 131 User Manual Edition July 2014 TEMPPO V6 1 Description of Use Test Case Selected Attributes ID Name Owner Test Case Attributes Test Case Attributes Page 132 User Manual TEMPPO V6 1 Edition July 2014 Description of Use TEMPPO report setting in project New Project Name NewReportSetting E sona Test Package Test Case Test Step Requirement General Header Footer Text V Requirement V Requirement attributes poate i Available Attributes Selected Attributes z Selected Attributes Inherited Requirement ID i Object ID Requirement Description Requirement Name To be tested by Cc Object type Requirement Path VP1 Relevant Requirement Short Description VP2 Relevant gt Requirement Structure mike type Version Requirement Requirement attributes gt 4 4 s 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 146 Tabular Report
357. ttings eh Text E Title Page l Continuous Report Test Package C General Information of Test Structure o Test Case A Requirement E Chart Layout Format HTML Microsoft Word Figure 142 Reporting General If Microsoft Excel is selected e you can define a header and a footer within the settings e Inline images aren t reported since Microsoft Excel doesn t support it If HTML is selected reports known 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 125 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Page Right Fages Date Time Fath Fie name Name NewReportSetting El Settings General 2 Title Page Figure 143 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 126 User Manual TEMPPO V6 1 Edition July 2014 Description of Use First you can choose t
358. ture Notepad System amp Acceptance Test System Test Ma i m x H gt b Hg E Mo fitter iotepad System amp Acceptance Test General Plan Requirements Name Notepac System amp Acceptance Test Owner Testmanager Updator Created 15 02 2012 13 26 40 Updated Type Test Structure TEMPPO Designer DATE O Test level System Test Description This tast structure is used for Lock Apply Discard Figure 6 Empty Test Structure General 3 1 2 2 1 2 Creating a test structure based on a requirement structure This feature allows you to create the same structure like in a requirement structure For each requirement a test package and a dummy test case is created plus automatic link to the requirement When activating Test Structure gt New gt Based on a requirement structure the window shown in is displayed All requirement structures are Shown which are assigned to the opened project and checked in see also Figure 7 Fi Select Requirement Structure E xX Mew Requirement Str atwi0905 25 08 2009 10 55 15 Manual Figure 7 Select Requirement Structure After selecting one requirement structure another window is shown see Figure 8 You may enter a name and description Also a test level has to be related to the new test structure Page 19 User Manual TEMPPO V6 1 Edition July 2014 Description of Use F Test Structure Properties i x General Mame Mew Requir
359. turn 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 rE Implementation of adapter for universial automation interface oy public class MyAdapter implements AutoToolAdapter public IResult getResult Reader returnFromAutoTool throws Exception Result ret new Result TODO add parsing of returnFromAutoTool here and set result and summary Example use buffered reader to process returnFromAutoTool line per line BufferedReader br new BufferedReader returnFromAutoTool read all lines and search for result and summary String line null StringBuffer summary new StringBuffer while line br readLine null if line startsWith Result process result here if line equals Result FAILED meee result IResult FAILED else if line equals Result PASSED bee result IResult PASSED Page 317 User Manual TEMPPO V6 1 Edition July 2014 Appendix else vest is for summary summary append line summary append System getProperty line separator ret summary summary toString mi return ret xk Implementation of result interface Ki class Resu
360. ual test case it does not make sense to define one common and therefore abstract goal for all test cases Fi Import JUnit Tests X Steps Test Case Default Values 1 Introduction Enter default values for the new test cases in TEMPPO z Select a JUnit test class 3 Select a set of JUnit test General attributes SE ditions Cares 4 Set package default values cs Regular Priority To 5 Settes case default values 4 x 6 Summary Error Designed i 7 adhe ce lens attribute Values TIE TEMPPFO Extension JUnit F Import JUnit Tests x Steps Summary 1 Introduction Review your settings z Select a JUnit test class 3 Select a set of JUnit test You choose to import the JUnittest class cases junit tests extensions Al Tests 4 Set package default values 5 Settest case default values into the TEMPPO test package 6 Summar JUnit tems to import 5 new testcases willbe added 4 new test packages willbe added TEMPRFO Extension JUnit Page 282 User Manual TEMPPO V6 1 Edition July 2014 JUnit Figure 361 Step 5 The summary of the import wizard Fi TEMPPO Testmanager Demo Notepad l lo x Project Test Structure Edt Test Execution Evaluation Tools Windows Help gt Test Structure JUnit System Test v1 Ioj x a 1 Framework Tests A w 1 junit tests extensions ExtensionTest General Plan Requirements rs hyg 1 1 1 test Run
361. ucture Additionally to the settings illustrated in Figure 13 you can do the following e Generate test cases If checked test cases will be generated Test cases will be generated from document paragraphs which are formatted with the standard formats Heading 1 Heading 9 or Uberschrift 1 berschrift 9 in German documents 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 instruction input and expected output of test steps These columns may have arbitrary headers like Anweisung 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 Page 26 User Manual TEMPPO V6 1 Edition July 2014 Description of Use The hierarchical position of the test case in the test structure will correspond to the heading level in the document 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 e Attributes Fixed and user defined attributes UDA For both you add for each TC a table with attribute and value see Figure 15 Additionally you can map attribute names of Word to TEMPPO one s by activating the checkbox and entering the name e Requirements In addition to attributes and UDAs you can specify l
362. ucture Edt Test Execution Evaluation Toole Windows Help LHil a Test Structure System amp Acceptance Test System Test v2 Ho d P H GP EE No iter ALI System amp Acceptance Test IDATG Tasks ea R IEE General Attributes Test Steps A eeen Requirements History Plan o Sub use case New already opened B a SUb use caze Mew REE Subus ECAS seMew ompletelynew 1 oe E oot eee 2 Input conte fia Use case File Open Enter name Input data Mew file ae fea 3 Detailed description of the required product feature name Lock Abi Discard tod Figure 384 Test cases generated by TEMPPO Designer IDATG 7 3 Updating Test Cases Chapter 7 2 describes the creation of task packages and the design and generation of test cases with TEMPPO Designer IDATG Of course it is possible to change the existing task packages or to add new ones by calling TEMPPO Designer IDATG again 7 4 Restore Designed Test Cases If the connection between TEMPPO and TEMPPO Designer IDATG is lost e g because the user 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 re
363. uly 2014 Description of Use Bj Test Suite Wizard g x Steps Choose creation mode 1 Introduction 2 Choose creation mode New based on current test structure C New based on a predecessor Copy based on an existing test suite Special based on an existing test suite with restrictions to test results TEMPPO Test Suite Generator lt lt Prey Figure 65 Creation mode selection 3 1 4 1 1 New Based on current test structure This mode is the usual way to create a test suite The following steps are necessary e Test structure pre selection e Test suite name e Logical expression e Remove test cases manually Page 70 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Bj Test Suite Wizard a xj Steps Test structure pre selection Introduction Select test packages hold lt STRG gt and lt Shift gt for multi select Choose creation mode 4 2 3 Select nodes or subtrees 4 Enter test suite name 5 TR Notepad RTF Import with TCs ga Introduction ga General description of the product E 5 Detailed description of the required product features Scope of delivery fe Sequences scenarios of interactions with the environment User goals E a Required functions of the product File Administration Fl New D New file opened no changes D New file opened changes 7 Open a Save L exit J Edit Functions J Print Functions J Search Functions
364. ut tasks from the design phase after test case import E E EE N 3411New 3 4 1 1 1 New file opened no changes The test case pursues the aim of testing the function New with no changese Desiqned Offshore f Requirement ID Action images k zox cleared Datei Bearbeiten Format Ansicht Strgot h ffnen Strg o Speichern Strg 5 Speichern unter Seite einrichten Drucken Strg F Beenden KI LU ntitled fsi a a Notepad intitle bara 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 25 User Manual TEMPPO V6 1 Edition July 2014 Description of Use LA Import Settings Document Ds wniTEMPPO documents 3_Implementatonimanuals 6 0 PiichtenhettNotepad_wathT Crit Generate document path Heading Mask Heading _ Limit test structure depth to Generate numbers and start with i Generate test packages M Import description W Generate test cases Fixed test step columns A test case is identified by a table with following headers Fa Instruction Anweisung Input Eingabedaten E V Expected Erwartetes Ergebnis Fi Ignore empty table rows do not create empty test steps User defined test step columns srclN srcOUT Zusditeliche Spalte Figure 16 Import Settings for generating a complete test str
365. utes After the implementation phase you will have a lot of test cases even in small projects and it s very likely that you want to have just a few of your test cases bundled for test execution because you don t have the time to execute all of them and therefore you decide to execute the high priority ones only there are several testers each of which should execute several test cases Furthermore we could consider that you want to get a survey of your test cases or test results under certain criteria For example it could be interesting for you how many test cases have the implementation state ready which means they can be executed how many high priority test cases are failed TEMPPO offers features for both situations namely the filtering of test cases for test execution see 3 1 4 1 and the creation of analysis charts see 3 1 5 1 But for being able to use these features it is indispensable to define attributes The following test 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
366. will be displayed in TEMPPO Test Manager instead of the Login Fi User properties x General Login Testmanager Login Type automatic manual Password fees Retype Password fees Last Name Mustermann O First Mame Mm E comments iCal Superuser OK Cancel Figure 310 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 247 User Manual TEMPPO V6 1 Edition July 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 Fj TEMPPO Manager system iol x Database Users Al Migration Database Version 6 8 Build 46 Application Version 6 0 Build 0 Database must be migrated Attention You may need administration privileges for migration Index Tablespace temppont Data Tablespace sitemppoindex Save Migrate Migration Loy Figure 311 Manager Database migration This tab is only active if the Administrator is connected to the database see Dat
367. wing chart types are available e Horizontal bar chart e Horizontal bar chart 3D e Line chart e Stacked horizontal bar chart e Stacked horizontal bar chart 3D e Stacked vertical bar chart e Stacked vertical bar chart 3D e Vertical bar chart e Vertical bar chart 3D With the radio button Orientation you can display the description of the x axis either vertically or horizontally The data can be switched from absolute to relative and vice versa Using the checkboxes States the chart can be customized By pressing the button Save As the chart can be saved as jpg or png file Page 112 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Test Cases 35 42 49 Test Structures V Designed IW In Work V Ready for Review V Ready V Approved E Designed Min Work E Ready for Review Ready E Approved Refresh Test Suites for V3 1 2012 10 24 l base 7 edabe Versi M Test Suites for V4 1 2012 12 04 H edabe version EM Test Suites for V6 1 2012 12 11 EM Test Suites for V7 1 2013 02 12 EM Test Suites for V8 1 2013 10 24 bw Sqiane hens EM Test Suites for V9 1 2014 04 01 Figure 129 Select Test Structures 3 1 5 5 2Execution Progress There are 3 analysis available Page 113 User Manual TEMPPO V6 1 Edition July 2014 Description of Use e Standard Execution progress of test suites can be created For several test suites which can be selected results and pla
368. with TCs Fb 4 Introduction Hh 2 General description of the product General Attributes Details Requirements History Plan EF w 3 Detailed description of the required prod 2 213 1 Scope of delivery Document C temp Pfichtenheft_Notepad_with TC rtf E 3 2 Sequences scenarios of interactic ea 3 3 User goals Marie 3 4 Required functions of the product 3 4 1 File Administration Chapter o BE 3 4 2 Edit Functions 3 4 3 Print Functions Ea 3 4 4 Search Functions meee ee S 4 41 Find Precondition wd 34 4 2 Replace J Search Functions file testtxt opened be 345 Help System Es 3 5 External interfaces of the product H 3 6 Other product features required Fa 4 Specifications for project management a 5 Obligations of the client LU 6 Literature Postcondition He 7 Annex Precondition me Find Postcondition file testixt closed Lock Apply Discard bi Figure 29 Precondition and Postcondition for test package 3 1 2 3 2Categorizing Test Packages After creating a test package you can select a test category Here all categories are available that are connected to the current test level for further details of test categories see 5 4 3 These are some typical test categories Task Based Test GUI Layout Test State Based Test In Figure 30 the test category Task Based Test was assigned to a test package After assigning a test category the node l
369. xt 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 11 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 TEMPPO Test Manager automatically checks in your current Page 67 User Manual TEMPPO V6 1 Edition July 2014 Description of Use test structure This means that its state test package
370. y 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 10 User Manual TEMPPO V6 1 Edition July 2014 Introduction The Test Process All testing activities deal with planning designing implementing executing and managing a sometimes quite big amount of test cases TEMPPO supports a well defined approach to these activities We can distinguish five phases in the test process Test structure Engineering Analysis y Prioritize TEMPPO Evaluation TEMPPO TEMPPO Requirement Analysis amp Wanaaer Reports Test Manager Designer Engineering g Elicitate Implement Specify Test cases Engineering Baseline View b n Design Engineering Execute Import Update Test results Bug entry Bug ID Test cases Test cases equirements impor update Change ffline T Management Management paren a external external Figure 1 Test Process with TEMPPO Execute Automated TC external e Offline Test SS execution Page 11 User Manual TEMPPO V6 1 Edition July 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 issue
371. y 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 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
372. y exists 3 1 2 2 7 3 Transfer data via XML Import the test structure from one project P1 to another project p2 same database e Export the test structure via XML TEMPPO Test Manager e Assign the needed requirement structures of the test structures to the project P2 TEMPPO Administrator e Import the test structure via XML TEMPPO Test Manager Import the test structure from one database di export to another database d2 project p2 import e Export the test structure via XML TEMPPO Test Manager e Export the requirement structures in the needed version TEMPPO Requirement Manager 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 Page 33 User Manual TEMPPO V6 1 Edition July 2014 Description of Use will lead to a badly arranged test structure The solution is to split them up Such a re
373. yed see Figure 195 These items aren t changed Page 167 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Locked Items i x Locked Items kaor Mew Test Case aSa Mew Test Case 1 Figure 195 Locked Items 3 3 2 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 wr jes r Li on New Test Package i is Gl A Sass M He A fien Tes D Mew b Find and Replace F3 r HE Show Details 7 E New Tes Select All Dare Gl New Tes G Tree b Copy Ctrl C Fa Paste Ctrl Order Edit Refresh recursively fa Move Ownership Analyse selected b E Report selected Figure 196 Context menu delete x DY Do you really want to delete these tems Figure 197 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 198 Page 168 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi Locked Items x Locked Items kaor Mew Test Case aSa Mew Test Case 1 Figure 198 Locked Items 3 3 2 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
374. yed 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 190 Page 165 User Manual TEMPPO V6 1 Edition July 2014 Description of Use Fi TEMPPO Tester1 Demo Notepad Ioj Project Test Structure Edt Test Execution Evaluation Tools Windows Help e Test Structure Notepad RTF Import with Tes System Test W3 Z x H db WH no tte r Notepad RTF Import with TCs IT 1 Introduction 211 1 Purpose of the document General Test Packages Test Case 201 2 Validity of the documert aoe m E 1 3 Definitions of terms and abbreviati Attributes nequremems Plan Iw Inherit 2 Relationship with earlier and follow componente Components WI 3 Purpose of the product C iien 4 Delimitation and embedding of the 5 Overview of the required function Delete 6 General restrictions lt Hardware and software speciicat Product users M 3 Detailed description of the required prac JS8 210 Well SUE ES ae ap 3 1 Scope of delivery Ty Assign to all test cases 3 4 1 2 Open 3 41 3 Save J 3 4 1 4 Exit Apraly Discard G Bu G amp amp amp Figure 190 Assign to all test cases If the button Apply is pressed all common values white background color and red foreground color are set for the selected items
375. ze 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 272 User Manual TEMPPO V6 1 Edition July 2014 TEMPPO Administrator only be generated from a frozen test structure in any branch version but not in the main version If a main version is frozen and activated a new test suite cannot be generated the new test suite menu item is not enabled If a branch version or latest version is frozen and activated a new test suite can be generated and the new test suite menu item is enabled If a version is checked in and is frozen no branch can be generated and t

Download Pdf Manuals

Related Search

Related Contents

Operações Diversas  Samsung SCP-3120VHP surveillance camera    Sistema de Ayuda a la Explotación Manual de Usuario    Lenovo VIBE Z2 Pro 32GB 4G Brushed steel, Metallic  ProForm Razor 831.23743.0 User's Manual  User Guide - Electronics DIY  S3041 user`s manual - Sea  PentiumM(1.6GHz)搭載 高信頼「ケミコンレス」 省スペース（200×200mm）  

Copyright © All rights reserved. Failed to retrieve file