Zermatt User Manual
Contents
1. fi vmi 5 3 4 Test Case to Requirement Mapping Sometimes the test cases already exist or have already been specified In this workflow the association between a test case and the requirement s it validates begins from the test case List all Test Suites for a chosen product List all Test Cases for this Test Suite 2 List all Requirements for this Test Case E Add an existing Requirement for this Test Case choose by Feature Remove a Requirement from this Test Case Create a new Requirement covered by this Test Case ZERMATT gt WORKFLOWSUITE 0 gt RP LP 04 1 gt Associate Requirements with Test Case i RELEASE PLANNING Apply Selected Filter Reset Filter ADDPRODUCT From the Product List page must be able tc LISTPRODUCTS Shall be able to List all Products DELETEPRODUCT Shall be possible to remove a product fi MODIFYPRODUCT Shall be possible to modify the descripti CREATERELEASE Shall be possible to create a new releas LISTRELEASES Shall be possible to list all Releases for the _ CREATESPRINT Shall be possible to create new project p LISTSPRINTS Shall be possible to list all project phases or s DELETERELEASE Shall be possible to remove a release frc DELETESPRINT Shall be possible to remove a project phas MODIFYRELEASE Shall be possible to modify the descriptic Shall he nmccihle t modif the deger rintinn 4 t 4 n k m2. Untagged Test Suites 0 Action Tagged Test Suites FEATUREPLANNINGSUITE ZERMATT ReleaseCycleTestSuite ZERMATT ISSUEVERIFICATIONSUITE ZERMATT E FeaturesandRequirementsTestSuite Z7ERMATT LABEQUIPMENTPLANNING ZERMATT ExecutionCycleTestSuite ZERMATT TESTEXECUTIONSUITE ZERMATT TestSuiteandTestCase ZERMATT TESTRESULTSUITE ZERMATT TagsCycleTestSuite ZERMATT QUALITYDASHBOARDSUITE ZERMATT zuozsuite ZUOZ NEWFEATURETESTSUITE ZERMATT ZERMAT TINSTALLATIONSUITE ZERMATT MIGRATIONTESTSUITE ZERMATT List all Test Cases associated with Tag value Associate a new Test Case to this Tag value Disassociate a Test Case from this Tag value Associate or Disassociate Tag with from Test Cases Execution gt AUTOMATION gt Test Cases Filters ZERMATT Test Suite Name Apply Selected Filter Reset Filter Untagged Test Cases Action Tagged Test Cases RQ MF 01 Verifies that the description of the selected feature is modified and listed pro RQ AF 01 Verifies that a new feature is added and listed RQ AR 01 Verifies that a new requirement is added from the Feature Listing Page and RQ DF 01 Verify that it is possible to delete a feature we have just created RQ DR 01 Verifies that it is possible to delete a requirement of a feature with no referer RQ MR 01 Verifies that the description of the selected requirement is modified
3. 15 4 2 Step 2 Release d OU cR tu S RO I DR RR 15 4 3 Step 3 Requirement Planning 16 4 4 Step 4 Test Case Designing amp Mapping 17 1 5 Step 5 Ga aaa aaa Ba an NB 16 4 6 Step 6 Lab Environment 19 4 7 Step Test Planhlhd raka ka a aa SAK aka Ka a pare ee aia ee ELEM 20 4 8 Step 8 Store Manual test 21 4 9 Step 9 Store Automation Test 22 4 10 Step 10 Trend Analysis 23 4 11 Step 11 Change daa cu a RR da 23 2 12 Step L2 COFFelatl ON casio dne ROO RC nd 24 5 Work FlIOWS i cususosuruswsEEERRIGERESWEREWER E WEREEX RENE RR ER E EE ER EE EE 2D 5 LI COMMGULAUON TASKS usssebavitexiiXavtxad dan id dax aa d 25 5 1 1 Archive Location Setup 25 5 1 2 Lab Environment Planning 25 5 2 POSE TASKS isa gagana pan sessi tea Ra dion edo ipe ban Gar ag i cd 25 5 2 1 Manage User Permissions 25 5 2 2 Check Audit Logs 28 Suspend Ils S wipes pem DEED 29 5 3 1 Release Planning for a Product or a Project 29 5 3 2 Requirements Planning for a Product 32 5 3 3 Test Case Design 33 5 3 4 Test Case to Requirem
4. 5 2 Concepts and 6 2 A PROGUGCE EE 6 S 6 2 3 ROICASCs eds Ok ERE ONERE E PU Ea C MEE EN 6 2 4 Sprint or Project Phase 6 2 5 Per 6 DEO NCS rc aas b E O 6 27 VOSE OVCE 6 220 TEST SUNG E E E N N E E EE S 7 2 A 7 2 10 TOPOIOGY Sarani NE 7 Dal TIODOlOgy Set kak akan eee DL E EE DLE DLE DA EM 7 2 12 aud uua VV EV EM 7 2 13 Reledse Test 7 D TA Fatre MEET I UI 7 2 15 Detail Requirements 7 2 16 Regu rement ab 8 Zermatt 9 3 1 Getting Started cuota ERIT UD UD Ed 9 Zermatt Homepage 9 3 2 SCcreen baVolulbau coercet du ce nu ea 10 3 3 The Navigation Bar on the top 10 gt eS RHEINE IEEE EE 11 3 5 Object Creation Hot LINKS aise 11 TS 12 4 Process 14 4 1 Step 1 Roles and
5. 4 11 Step 11 Change Tracking Refer to topic 5 2 2 In Zermatt change tracking is done by a feature called Audit Log Audit Entries are created whenever any planning data 15 created deleted or modified Open Audit Log Page View Audit Entries e Filter Audit Entries by Table Name e Filter Audit Entries by User Name e Filter Audit Entries by Operation Type e Filter Audit Entries by Time Period Start Date amp End Date pom ERES ERN 4 12 Step 12 Bug Correlation Bug Correlation in Zermatt is an ability to correlate defects encountered during test execution and defects that are being tracked in a bug tracking system such as Bugzilla or Redmine Note that this feature 15 not available in V1 of Zermatt 5 Work Flows 5 1 Configuration Tasks 5 1 1 Archive Location Setup This workflow allows you to specify the location on disk where ZUG log files as well as any other application specific log files will be compressed and archived The name of the key 15 ArchiveLocation Note that the location must be a network folder that 15 accessible from all machines where ZUG might be running Check where Logs are being archived Create a new archival location Modify current archival location 5 1 2 Lab Environment Planning This workflow allows you to catalog all the equipment used for testing These may be either physical machines or virtual machines Later these machines may be referenced as part of a
6. Cases Total Test Cases Passed Total Test Cases Failed TC 20120410 2012 2012 04 10 97733 170468 185 191841 04 10 19 20 25 19 18 49 Remove an existing Test Cycle from Test ZERMATT i gt Theta V2 17 gt First Sprint gt Fair weather Testing U gt Add New Test Cycle Test Cycle Description seco List all Test Cycles for the Test Plan Adda Topology set to the test Cycle Remove existing Topology Set ZERMATT Gi gt Theta V2 17 gt First Sprint gt Fair weather Testing gt TC 20120410 191841 1 gt Add or remove Topology Sets Topology Sets not in Test Cycle Action Topology Sets in Test Cycle O Select Sets to Add Select Sets to Remove XP and IE based topologyset and Firefox based topology set and Chrome based Topologyset e Create an Execution Detail Record for the chosen Test Cycle 7 Execution Details ZERMATT gt Alpha V2 0 gt Sprint 1 gt BETATESTPLAN gt testTestCycle gt DARJEELING SHILLONG AUTOSCOUT KURSEONG gt Test Execution Details Test Cycle Topology Set 22 10759 Create Manual Test Execution Result Topology Sets Summary Total Execution Details 1 Total Test Cases Passed 0 Total Test Cases Failed 0 Test Action Test Suite Execution Date Status Comment Build Duration Performance Bug Tag Details
7. Close Window List all Requirements associated with the Tag value Associate a new Requirement to this Tag value Disassociate a Requirement from this Tag value Associate or Disassociate a Tag with from Requirements Execution O gt AUTOMATION gt Requirements Filters il ZUG gt i Apply Selected Filter Reset Filter i RQ MF 01 Verifies that the description of the selected feature is modified and listed pro RQ AR 01 Verifies that a new requirement is added from the Feature Listing Page and mi RQ DR 01 Verifies that it is possible to delete a requirement of a feature with no referer RQ MR 01 Verifies that the description of the selected requirement is modified and liste RQP 009 Verifies that a selected requirement can be moved from one feature to anothe RIVOO1 Verifies that the description of the test case can be modified in the requirements RIVOO2 Verifies that the log file can be viewed in the Test cycle report Redmine issue If RIVOO3 Verifies that the test case can be viewed in the Beta release RIVOOA Verifies that the requirements be associated and disassociated from a test RIVOOS Verifies that the manual test execution page is working Redmine issue ID 39 m 4 1 Close Window 5 3 8 Release Sprint Planning RQ AF 01 Verifies that a new feature is added and listed RQ DF 01 Verify that it is possible to delete a feature we have just created
8. This workflow is designed to allow the person responsible for planning the testing for a sprint or a release to choose test suites test cases test environments for carrying out a series of tests designed to meet the objectives of the release or the sprint This workflow assumes that the test cases already exist and have been tagged and the test environments have already been entered into Zermatt List All Products List all Releases for a chosen product List all Sprints or Project Phases chosen release Project Phases gt Milestones Schedules Start Backlog o 9 9 9 Date Date Items First 4 Alltests in Release Test Plan have V30tobe 2012 2012 02 18 of Sprint been executed and no show released 04 09 04 25 a 15 stoppers have been discovered month end ZERMATT gt Theta V2 17 gt Add New Project Phase 5 Acceptance Criteria Milestones Schedules List all Test Plans for a chosen Sprint or Project Phase Normally there will be at most one such Test Plan Create a Test Plan for a chosen Sprint or Project Phase Remove an existing Test Plan provided there are no test suite lists or topology set lists referencing this test plan T Modify an existing Test Plan Test Plans 5 Plan paja Purpose 0 Acceptance Criteria y y Test Test Topology DATES y rp Me Aine This is to see all the
9. Remove a Topology Set which does not have any Topologies Add a Topology to a Topology Set WI Remove a Topology from a Topology Set List of Topology Sets Action Topologies 1 Ubuntu and XP based topology set 4 4 6 Leh Zermatt Reporting Functional Testing Leh Zermatt Server Black Box Testing 2 Test VM Zug Client Black box testing 2 Shillong Davos Client Black box Testing 2 Smoke testing Fair weather Testing Ubuntu and Win 7 based topology set 4 T 4 6 Leh Zermatt Reporting Functional Testing Leh Zermatt Server Black Box Testing 42 Test VM Zuoz Launch Black box Testing 22 Fair Weather Testing 2 Configuration Testing 22 Smoke testing Create a new Topology Set Description 5 3 7 Tag Management This work flow allows tagging test cases using arbitrary keywords This feature allows the user to pick and choose test cases by any chosen criteria For example you could choose all test cases that verify bugs reported by a specific customer or all test cases that do stress testing Tags may be created and assigned at any time during the product lifecycle Thus test cases may be grouped in many different ways to serve many different purposes and facilitate quick selection for a particular task List all Tag Categories Create a New Tag Category e g Testplans Internal Bugs Customer Bugs Performance Security OS etc Remove a Tag Category having no tag values Modify
10. Delete Product 2011 07 04 4 17 El 14 Close Browser 2011 07 04 1 E 16 1 ZERMATT gt Theta V2 17 gt First Sprint gt Test Plan gt FeaturesandRequirementsTestSuite gt Test Cases Test cases not Test Plan Action Test cases in Test Plan RC 101 Verify that it is possible to map multiple test cases to a requirement RC 102 Verify that it is possible to map multiple requirements to a test case RC 112 Test that the requirement does not mapped to a test FWF001 Create New Product a FWF002 Create A New Release FWFO003 Create new Feature FWF004 Create A New Requirement FWF005 modify requirement FWFO06 modify feature FWFO07 Create New Testsuite FWFO08 Create Testcase FWFO009 Map Testcase and Requirement FWF 010 Disassociate testcase and Requirement 111 List all Topology Sets for a chosen Test Plan E Add a Topology Set to a chosen Test Plan s List of Topology Sets Remove a Topology Set from a chosen Test Plan s list of Topology Sets Topology Sets for Fair weather Testing 4 Pme P XP and IE based topologyset 48 Leh Shillong Leh Xp and Chrome based Topologyset Leh Leh Shillong Test VM Test VM ZERMATT gt Theta V2 17 gt First Sprint gt Fair weather Testing gt E
11. Pars Test EngineerO RP LS 01 WORKFLOWSUITE 2011 06 09 ChayanHazra Tag1 200 No Performance 0 E G Records Modify an Execution Detail Record for chosen Test Cycle T ZERMATT gt Alpha V2 0 gt Sprint 1 gt BETATESTPLAN gt MyCycle gt Test VM 1 gt RQP 009 gt Modify Test Execution Record 1 Engineer Dipusg Test Uy FEATUREPLANNINGSUI Name Test Case RQP 009 Execution 2011 01 34 Date Build Tag Status Bug Id Comment Test Execution Time e Remove an Execution Detail Record from the chosen Test Cycle 4 5 4 Reporting tasks 5 4 1 Total Quality Dashboard The Total Quality Dashboard represents all the products with e Requirements Overview by Product e Requirements Coverage by Product e Requirements Tested by Criticality e Requirements Failing by Criticality e Bugs Outstanding by Product miota Quality Dashboard Products 2 SPI dene 5 4 2 Product Quality Dashboard The Product Quality dashboard represents an individual Product with Requirements having Test Cases by Release Cumulative outcomes in each Release Requirement count by Criticality Progress against Plan by Release Critical Requirements tested in each Release Requirements Overview by Test Suites Outcome of tests in each Test Suite Total Variables Declared and Tags Used By Test Suites Test Case Count b
12. outed E 5 4 5 Test Plan Report The Test Plan Quality Dashboard represents a Test Suite with e Test Plan Suites amp Topologies Overview by test Cycles e Plan amp Execution Metric by Test Cycles e Test Execution Outcomes Overview by Test Cycles Fian E Execution By Tesi Percent Test Executed ow t F 8 E PO E a 4 22 1 L F 3 i Moopebre S Merete Tied ieii wedi Lipa Det st HE LEOTE AREE 16 07 iT Tea uc Tea Cycles n Tent Execution utor Ww ag ke Dind Deje Heember Sind ied 2001 1123 idii Text 5 4 6 Test Cycle Report The Test Cycle Quality dashboard represents a Test Cycle with Recent Outcomes by Topology Sets e Test Case execution Details By Test Cases e Test Case Outcomes in Topologies gt November 22nd Cycle Test Case Execution Details By Topology 5ets Io mai E Tesi Gas Emeceuiion Tesis Pas sad Tasis Falleg Tesis 13 z 11 Local e Recent Outcomes By Topology Sets Topology fed Desoripiton Falling Recenti Passing Lorca ars Overview By Test Cases Tent Execution Details Bu Test Tea Cape
13. topology for a test session List All Lab Physical or Virtual Machines Add a New Machine to the catalog 7 Remove a Machine from the existing catalog Modify the description of a Machine 4 Test Equipment Catalog Catalog New Machine 7 Attic Zermatt Server for Automature 75 68 89 140 2 64 bit 1 North Korea 0 Zug residing on Windows XP 192 168 0 25 Pelling Worth Korea 2 E 32 bit Leh 4 Zermatt Database 192 168 0 2 Shillong Leh 2 E 32 bit Thimpu 47 Zermatt Twiki 5 on Ubuntu residing on Attic 75 68 89 140 Attic Thimpu 1 32 bit server BHUTAN 4 Zug residing on Windows 7 11 22 33 44 BHUTAN 12 32 bit 5 2 Administrative Tasks 5 2 1 Manage User Permissions Zermatt 2 different authorization levels to distinguish between different classes of users viz Administrators and Users Only the Administrator can make changes in this page You can make someone TWiki Administrator or Super user by visiting the page http localhost twiki bin view Main TW1kiGroups If you want to give administrative privileges to a particular user click ZermattAdminGroup and edit the page in the following way Set GROUP Main Y ourTWikiName and save this page This makes the user the administrator for the Zermatt product ZermattAdminGroup edit lt nop gt ZermattAdminGroup Member list comma separated list Set GROUP TWikiAdminUser DipuDeshmukh Main PatA amp dmin Main MarkTes
14. 37 DipuSg product exported x ZURICHproduct xml manage 214K 2012 03 14 15 48 DipuSg product exported x projectphase xml manage 0 8K 2011 07 07 07 51 DipuSg projectphase exported x testsuite xml manage 11K 2011 07 07 10 43 DipuSg testsuite exported OAfter clicking the link to the attachment the browser opens up the XML file Now you can save the XML file on your computer This XML file does not appear to have any style information associated with it The document tree is shown below w lt product product name ZERMATT description Automature Dashboard for Planning and Reporting creation date 2009 08 14 00 00 00 created by DipuDeshmukh acceptancecriteria All tests in Release Test Plan have been executed and no show stoppers have been discovered milestones 1 A11 popups working properly 2 Search page working properly Item creation workflows complete schedules V2 1 will be released end of March w lt features gt w lt feature name RELEASE PLANNING description Supports a workflow that allows users to plan regular service pack or patch releases and also supports the agile Software development model created by DipuDeshmukh modified by SankhaSil w lt requirements gt w lt requirement requirements name LISTPRODUCTS description Shall be able to List all Products priority 3 release 1 major version 2 minor version 0 gt lt testcases gt lt testcase testcase identifi
15. 5 3 5 Requirement to Test case mapping Test cases typically validate that one or more requirements are adequately implemented This workflow starts from product requirements and identifies which test cases validate them If a requirement is missing a Testcase then this workflow will help you create a placeholder test case that can be implemented by automation engineers or manually executed List All Products List all Features for a chosen product List all Detail Requirements for chosen Feature List all Test Cases that test this Requirement Add an existing Test Case for this Requirement choose by Tag Add an existing Test Case for this Requirement choose by Test Suite Remove a Test Case from this Requirement H Create a new Test Case for this Requirement 7 ZERMATT gt RELEASE PLANNING gt LISTPRODUCTS gt Map Test Cases to this Requirement ess Shall be able to List all Products WORKFLOWSUITE v Test cases not Requirements Action Test cases in Requirements Verify that all the existing phases of a release for a product can be listed Verify that all existing products can be listed Testsuite WORKFLOWSUITE Verifies that it is possible to delete a release of a product with no referen Verifies that it is possible to delete a sprint for a release Testsuite WOF Verifies that the description of the selected release is modified and listed Verifies that
16. Active All tests in Release Test Plan have V30tobe 352 B 6 2 0 El weather workflows are working fine been executed and no show released Testing under normal conditions stoppers have been discovered month end ZERMATT Gi gt Theta V2 17 gt First Sprint gt Create or Update A Test Plan Status Select Status Purpose Acceptance Criteria Milestones Li E Schedules Li Close Window List all Test Suites for a chosen Test Plan gt Add a Test Suite to a chosen Test Plan s List of Test Suites Test Suite List for Fair weather Testing a Test Plans FeaturesandRequirementsTestSuite 4 O 14 ReleaseCycleTestSuite 13 E ExecutionCycleTestSuite 2 o 4 TestSuiteandTestCase zT BackLogsCycleTestSuite 47 TagsCycleTestSuite 2i OQ E L4 ZERMATT V gt Theta V2 17 gt First Sprint V gt Fair weather Testing gt Add remove Test Suites TP882 Fr re P d uma Select Suites to Add Select Suites to Remove FEATUREPLANNINGSUITE HeleaseCycleTestSuite ISSUEVERIFICATIONSUITE FeaturesandRequirements Testsuite ExecutionCycle TestSuite TESTEXECUTIONSUITE TestSuiteandTestCase TESTRESULTSUITE TagsCycleTestSuite QUALITYDASHBOARDSUITE BackLogsCycleTestsuite NEWFEATURETESTSUITE ZERMATTINSTALLATIONSUITE MIGRATIONTESTSUITE m Close Window List all selec
17. Release Default Schedules 5 3 2 Requirements Planning for a Product Projects have requirements that must be delivered In Zermatt requirements describe details belonging to a high level feature For example a feature could be that there will be a GUI management interface The requirements will then spell out all that the management interface will allow you to do Test cases will typically validate that one or more requirements are adequately implemented List Products 2 List all Features for a chosen product Add a New high level Feature e g Security for this product 7 Remove an existing features for which no requirements have been entered H Modify the name or description of an existing feature 4 Features for ZERMATT ZERMATT gt Features Products 0 Create New Feature E RELEASE PLANNING Supports a workflow that allows DipuDeshmukh Sankhasil 1 4 users to plan regular service pack SIZE or patch releases and also VALIDATION supports the agile Software INPUT development model VALIDATION REQUIREMENTPLANNING Z4 Supports a workflow for building DipuDeshmukh DipuDeshmukh 9 E 6 E 4 hierarchical catalog of product TEM features and requirements for each Testing feature Bugs by Type Add New Feature Update Feature Feature Feature RELEASE PLANNING 4
18. deeper than object currently chosen Detailed View Export to XML Attach a File Selecting by tag value For Association and Disassociation Comments View the attached document Cancel Edit mode while assigning a story to a team Performance Details A Release ee A Sprint A Test Plan A Test Cycle A Test Suite A Test Case A Feature A Requirement 4 Process Overview lanning mi INE p lanning 1 Permissions EET Change y E zwi 1C of Fess e 4 12 Bug 4 1 4 2 4 d 4 rater Step 1 Roles and Permissions Refer to topic 5 2 1 Create users in the Planners group Create users in the Testers group Create users in the Admin group Create users in the Browsers group Step 2 Release Planning Refer to topic 5 3 1 Create a Product Create a Release for the Product Create a Sprint for the Release 4 3 Step 3 Requirement Planning Refer to topic 5 3 2 e Capture a product feature in Zermatt e Create a Requirement for the feature e Requirement can only be created if there is a Release A test case written for the requirement 4 4 Step 4 Test Case Designing amp Mapping Refer to topic 5 3 3 5 3 4 5 3 5 e test case can only exist if there is a test suite A test suite must belong to a Role Create the Role if it does
19. released month end The concept of Sprints is borrowed from Agile Software Development Methodology One may think of a Sprint as a development phase within a release cycle of a project In Zermatt even maintenance releases are referred to as project phases and belong to a specific release List all Releases for a chosen product Quick create a new release for this product Remove a release which does not have any project phases defined Modify the properties of a release 4 Releases for ZERMATT 5 Products 2 2 v I v Description Acceptance Criteria Conceived Release Project Backlog Date Date vM v First release All tests in Release Test Plan of this have been executed and no version show stoppers have been discovered Delta 0 31 August All tests in Release Test Plan Release have been executed and no show stoppers have been discovered Code Major Version Minor Version Description Conceived Date Released Date Acceptance Criteria Milestones Schedules Zermatt 3 0 to 2011 07 01 4 be launched month end V 3 0 to be 2011 08 08 2011 09 2 EE OFF 0 released 09 month end Code Name Major Version Minor Version Description First release of this vers 2011 07 01 2012 08 05 Acceptance Criteria 17 All tests in Release Test Plan have been executed and no show stoppers have been dis
20. Description 222 1217 Supports a workflow that allows users to 1 regular service pack patch releases and also supports the agile Software development model List all Detail Requirements for a chosen Feature Add a new detail requirement for this feature and associate a release Remove an existing detail requirement for this feature T Modify the description or the release association of an existing detail requirement 4 Requirements for RELEASE PLANNING ZERMATT gt RELEASE PLANNING gt Requirements Features 0 0 EESIN Create New Requirement Requirement Action Release Description LISTPRODUCTS 5 4 Alpha Shallbe able to List all Products HIGH 1 H V20 a SIZE VALIDATION INPUT VALIDATION ADDPRODUCT 5 7 Alpha From the Product List page must be able to add a New Product if the desired one does 2 02 V2 0 notexst 38 SIZE VALIDATION n INPUT VALIDATION ZERMATT gt RELEASE PLANNING gt Add New Detail Requirement ZERMATT gt RELEASE PLANNING gt Update Detail Requirement LISTPRODUCTS Release Alpha 2 gt Shall be able to List all Products Criticality Description 5 3 3 Test Case Design This workflow allows you to specify test cases and group them under a test suite so that test cases testin
21. Document Title Zermatt User Manual Page 1 64 Author Anuradha Chanda Version 2 17 11 04 12 Zermatt User Manual Whilst all reasonable care has been taken to ensure that the details are true and not misleading at the time of publication no liability whatsoever is assumed by Automature LLC or any supplier of Automature LLC with respect to the accuracy or any use of the information provided herein Any license delivery and support of software require entering into separate agreements with Automature LLC This document may contain confidential information and may not be modified or reproduced in whole or in part or transmitted in any form to any third party without the written approval from Automature LLC Copyright O 2010 Automature LLC rights reserved Document Title Zermatt User Manual Page 2 64 Author Anuradha Chanda Version 2 17 11 04 12 Revision History 1 1 10 27 2010 Dipayan Sengupta Revised Edition 1 3 12 07 2010 Anuradha Chanda Revised Edition 2 1 18 01 2011 Dipayan Sengupta New Display layouts He DEN Document Title Zermatt User Manual Page 3 64 Author Anuradha Chanda Version 2 17 11 04 12 Contents 222555555 aaaea 12 4 Document PAN DOSES cna uscite Ote estet 5 1 2 rc On Cet ae e ar acc aane 5 1 3 References and Other Related Documents
22. and liste RQP 009 Verifies that a selected requirement can be moved from one feature to anothe RIVOO1 Verifies that the description of the test case can be modified in the requirements RIVOO2 Verifies that the log be viewed in the Test cycle report Redmine issue If 003 Verifies that the test case can be viewed in the Beta release RIVO04A Verifies that the requirements can be associated and disassociated from a test RIVOOS Verifies that the manual test execution page is working Redmine issue 10 39 4 IRWF001 Create A New Product RWF012 Delete Product E RWF002 Create A New Release RWF003 Create A New Sprint IRWF004 Create Testplan RWF005 Modify Testplan RWF O006 Delete Testplan RWF007 Modify Sprint RWF008 Modify Release RWFO009 Modify Product List all Features associated with the Tag value Associate a new Feature to this Tag value Disassociate a Feature from this Tag value Associate or Disassociate a Tag with from Features Execution U gt AUTOMATION U gt Features Filters Filter by B P Apply Selected Filter RELEASE PLANNING ZERMATT REQUIREMENTPLANNING ZERMATT AUDITLOG ZERMATT ROLESANDPERMISSIONS ZERMATT LABEQUIPMENTCATALOG ZERMATT LOGARCHIVAL ZERMATT TESTCASEDESIGNING ZERMATT TAGMANAGEMENT ZERMATT REQUIREMENTCOVERAGE ZERMATT TESTPLANNING ZERMATT
23. and password credentials you will be redirected to the Twiki Main web Home Main Web View Edit Site map Main web th Jump Sandbox web iki sear Edit Attach TA TWikiweb view all tags Search ka Ea Attach ZERMATT web V d xr web th e M web Recent changes in Main web TWiki Preferences Congratulations you have finished installing TWiki This site is running TWiki version TWiki 5 0 2 Tue 03 May 2011 build 21156 Plugin API version 1 9 Select Zermatt Web from the drop down menu of Home and you will be navigated to the Zermatt home page Zermatt Homepage Home 0 ZERMATT Config Dashboards Releases Agile Features Test Suites 4 Account r V Search Tags create new tag view all tags Welcome to ZERMATT V 2 6 This is the Automature home for Configuring Planning and Browsing through Reports Getting Started Setup amp Configuration Links Latest News e Which version am running gt What is new in this release How do get around product This 15 the Zermatt web home page It contains all necessary links to tutorials and other pa
24. at we call Products Example of a product could be Adobe s Flash or Automature s ZERMATT Products may often be referred to as projects in some contexts 2 2 Role e We normally use more than one machine in conducting a specific test Each machine participates in a specific role that is assigned to it for the purpose of a test 2 3 Release product is developed for customer consumption in increments known as releases Each release can have a code name internal to the organization and a version number by which it 1s identified outside of the organization where it is developed Code Names are normally used during development of a specific release Arelease maybe created for various reasons viz o Development of new features o Emergency bug fixes also known as patch or hot fix releases o Rollup bug fixes also known as Service Packs 2 4 Sprint or Project Phase Each development release 15 organized in a series of sprints or phases each of which provides incremental levels of functionality The goal at the end of each sprint is to achieve a reasonably stable version of the product The final sprint is known as the Release Sprint Forthe purposes of quality management product sustaining activity that lead to service packs or patch releases are also considered project phases 2 5 Test Case Test Case describes a specific test procedure in concert with all the variables identified as being significant
25. covered Conceived Date Released Date Milestones Product Default Schedules Zermatt 3 0 to be launched month end List all Sprints or Project Phases for a chosen release Remove a Sprint or Project Phase from a release not containing a Test Plan Modify the properties of a specific Sprint or Project Phase 4 Project Phases ZERMATT gt ALPHA V2 0 gt PROJECTPHASES Create New Project Phase IC Sprint ys Acceptance Criteria Milestones Schedules Start End c lans gka Date C Sprint1 All tests in Release Test have been executed and 1 All popups working V2 1 will be released 2 4 E E show stoppers have been discovered properly end of March i B 2 Search page working properly 3 Item creation workflows complete Sprint2 Z Alltests in Release Test Plan have been executed and 1 All popups working V2 1 will be released 2011 2011 0 Off n show stoppers have been discovered properly end of March 03 01 03 25 2 Search page working properly 3 Item creation workflows complete ZERMATT gt Alpha V2 0 gt Add New Project Phase ZERMATT gt Alpha V2 0 gt Update Project Phase Sprint Name Sprint Name Start Date X 2010 08 01 00 00 00 Fr End Date Es 212727117 2010 08 31 00 00 00 Acceptance Criteria 12222 2 Release Default Criteria Milestones 12 72
26. der a product LIST OF PRODUCTS Create New Product amp 1 Name Description OE uS Backlog 5 items 0 Dashboard for Planning and Reporti Atom library addon for ZUG ZUOZ 2 3 2 1 0 ELDER ELE EEE EM ze First release All tests in Release Zermatt 30 2011 07 01 2012 08 4 384 of this Test Plan have to be 05 version been executed and launched no show stoppers month end have been discovered Example To Copy a single project phase under a release Project Phases Releases README cE Sprint Action Acceptance Criteria Start Builds Name vv Li First 4 tesis in Release Test Plan have V3 0tobe 2012 2012 0 E 1 Sprint H E been executed and no show released 04 09 04 25 E stoppers have been discovered month end Example To Copy a single Test plan under a Project phase Test Plans Active All tests in Release Test Plan have V30tobe 685E 085 6 2 0 been executed and no show released stoppers have been discovered month end Example To Copy a single Test suite under a product ZERMATT gt Test Suites Products r3 c Create New Test Suite E_E Suite Name Acti j Comment Status t Variables Suite Tags 0 Li WORKFLOWSUITE This test suite Under 16E 10 Ej 2 4 contains functional Development 1 INTERRA test ca
27. dit Topology Set List Topology Set to Include First Topology Set Save Close Window 5 3 9 Copy Paste Function Zermatt allows you to copy the data under an object and then allows you to paste it in the desired location Copy Feature Allow you to copy an object E g Product Release Test Suite Feature Project phase Test plan Test Case requirement Shallow Paste Allow you to paste the parent object without the objects under it E g If you shallow paste a product then only the product gets copied and not the objects under it like test suites release features etc Deep paste Allow you to paste the parent object with the objects under it E g If you deep paste a Product then all the Releases Test suites and features get copied Example For Product Copy Products 5 Shallow Paste Products ld Deep paste Products e Product can be copied along with the objects under it without the objects under it e Product can be pasted in the same page without any objects under it 0 Product can pasted in same page with objects under it LIST OF PRODUCTS Create New Product re ree 9 Fs Fs I 4 i 3 i I 4 1 11 Automature Dashboard for Planning T 18 21 5 and Reporting IFES ELS FARES v ZERMATT 2 n il Atom library addon for ZUG z z 1 UE EE BEES EE ZUOZ Example To copy and deep paste all releases Test suites and Features un
28. ent Mapping 34 5 3 5 Requirement to Test case mapping 35 5 3 6 Lab Environment Planning 36 5 3 7 Tag Management 41 5 3 8 Release Sprint Planning 44 5 3 9 Copy Paste Function 49 5 3 10 Data Migration 54 5 3 11 Manual Test Result Entry 56 2 TASKO bika KKN NABA KAB AKEN Ba Str Rd 59 5 4 1 Total Quality Dashboard 59 5 4 2 Product Quality Dashboard 60 5 4 3 Release Quality Dashboard 61 5 4 4 Sprint Quality Dashboard 62 5 4 5 Test Plan Report 63 5 4 6 Test Cycle Report 64 1 Introduction ZERMATT is Automature s browser based quality management framework for Planning and Reporting ZERMATT is used to store the results of the tests the test environments and everything else that 15 contextually relevant to the tests It also provides an infrastructure for planning creating requirements and grouping test cases 1 1 Document Purpose The user manual will help you navigate Zermatt s Work Flows and create reports 1 2 Intended Audience This manual is intended for the users who would be using Zermatt for planning and reporting purpose 1 3 References and Other Related Documents The following documents provide additional useful information about Automature s other products and how they relate to Zermatt 1 Zermatt Install Guide 2 Zug User Manual 2 Concepts and Terminology 2 1 Product Acompany develops and sells several individually releasable software packages These are the entities th
29. er RP LP 01 testsuite_name WORKFLOWSUITE gt lt testcases gt lt requirement gt w lt requirement requirements name ADDPRODUCT description From the Product List page must be able to add a New Product if the desired one does not exist priority 3 release 1 major version 2 minor version 0 gt w lt testcases gt lt testcase testcase _ identifier RP AP 01i testsuite name WORKFLOWSUITE gt testcase testcase identifier RP AP 02 testsuite name WORKFLOWSUITE lt testcases gt lt requirement gt w lt requirement requirements name DELETEPRODUCT description Shall be possible to remove a product from the existing list of Products provided there are no references to it priority 3 release 1 major version 2 minor version 0 gt w lt testcases gt lt testcase testcase identifier RP DP 01 testsuite _name WORKFLOWSUITE gt lt testcase testcase identifier RP DP 02 testsuite name WORKFLOWSUITE gt lt testcases gt lt requirement gt w lt requirement requirements name MODIFYPRODUCT description Shall be possible to modify the description of existing product priority 2 release name Alpha major version 2 minor version 0 gt w lt testcases gt lt testcase testcase identifier RP MP 01 testsuite _ name WORKFLOWSUITE gt lt testcase testcase identifier RP MP 02 testsuite _name WORKFLOWSUITE gt lt testcases gt lt requirement g
30. for testing the feature Note that an environmental variable such as the operating system version while also significant for the test case is normally tracked using topologies 2 6 Test Suite e Test Suite consists of a collection of Test Cases which somehow are related together for reasons considered appropriate by the Test Plan designer e Usually Test Cases inside a specific Test Plan may use similar test procedures may test a specific product feature 2 7 Test Cycle Test Cycle describes a logical test session during which tests are conducted Typically but not necessarily some environmental conditions remain constant such as the build the test engineer etc While certain other environmental conditions may vary such as the Topology Sets where the tests are being executed results of Test execution are stored within context of a test cycle There can be no more than a single result stored for a specific test case executed on a specific topology set inside one test cycle A test cycle usually but not necessarily refers to a specific build of the software being tested 2 8 Test Suite List A collection of Test Suites that might be used for a specific purpose such as a test cycle a release regression test plan 15 called Test Suite List 2 9 Topology A topology describes a single machine participating in the execution of a Test Case The machine 15 described in terms of various significant at
31. g a certain product feature or similar requirements can be placed in a common container List all Test Suites for a chosen product Create New Test Suite for this product Remove an existing Test Suite that does not have any test cases in it Modify some properties of a Test Suite for this product 4 List all Test Cases for this Test Suite Add a New Test Case for this Test Suite 1 Remove a Test Case that does not have any test execution detail referring to it T Modify properties for a Test Case in this Test Suite 4 Test Suites for ZERMATT ZERMATT gt Test Suites Products c 08 Suite Name i Action s 0 Comment Test Variables Suite Tags i Lists Create New Test Suite E_E amp WORKFLOWSUITE Zermatt This test suite contains Under 168 108 2 4 WES server functional test cases for all Development INTERRA the workflow paths Ad Hoc Testing AUDITLOGSUITE Zermatt Test suite to verify that all Under 95E 28 04 uj d Server audit logs are properly Development T generated ZERMATT i gt Add New Test Suite ZERMATT i gt Update Test Suite Test Suite Test Suite WORKFLOWSUITE Comment Comment This test suite contains functional cases for all the workflow paths Status status Under Development Role Role Zermatt Server 8 Test Suite s
32. ges of Zermatt which are required for Configuring Planning and Browsing through different reports If you are a first time user we strongly recommend you to go through the topics under Getting Started If you want to navigate to Releases Agile or Features or Test Suites you need to select a product first If you want to create a new product then go the Products page from Zermatt drop down Menu 3 2 Screen Layout The screen has been divided into several sections viz top menu bar and the search bar containing the Automature logo and the main display area that covers the rest of the browser window ZERMATT Config l l 4 Account Zermatt Q automature LIST OF PRODUCTS G Automature Dashboard for Planning and ZERMATT Engine for executing automated Test Suites 4 written in CHUR Automatic Deployer for VMWARE 3 3 The Navigation Bar on the top The Navigation Bar can used to quickly move between workflows There are ten pull down topics in the menu 1 ZERMATT Config Dashboards Releases v Agi Features v Suites v GB Cydes v Account v automature 3 4 Breadcrumbs Breadcrumbs can be found on most pages that are at leaf nodes of a workflow The purpose of the breadcrumbs 15 two fold viz toidentify the objects selected during the navigation of the current workflow to arrive at the current page e toallow the user
33. hat have test cases for requirements to be tested Choose the test cases within the test suites associated with the test plan 4 8 Step 8 Store Manual test Result Refer to topic 5 3 11 You can store the test results in Zermatt by following the below Step e We assume you have already created a Test Plan as described in the previous section Now create a test cycle under the test plan Inthe execution topology set of test cycle create manual test execution result 5 Cun 4 9 Step 9 Store Automation Test Results The results of the tests run by Zug are automatically stored in Zermatt This topic is covered in the Zug User Manual 4 10 Step 10 Trend Analysis Refer to topic 5 4 Quality Dashboard shows the overview of all the products e Product Quality Dashboard shows the overview of individual products e Release Quality Dashboard shows the overview of all the releases under a Product e Sprint Quality Dashboard shows the overview of all the sprints under a Release e Test Plan Quality Dashboard shows the overview of all the Test Plans under a Sprint Test Cycle Quality Dashboard shows the overview of all the Test Cycles under a Test Plan e Test Suite Quality Dashboard shows the overview of all the Test Suites under a Product Test Case Quality Dashboard shows the overview of all the Test Cases under a Test Suite a m
34. k to the attached file Images will be displayed for other attachments a link will be created Hide file Do not show attachment in table Attachments will not be shown in topic view page e FileAttachment has more information about attaching files Cancel Attachments of ImportExternal Dummy Productproduct xml manage 295 2010 10 26 07 07 Main AnuradhaChanda New Text Document TXT manage 0 1K 2010 09 23 06 17 Main DebabrataDas Z TXT manage 0 1K 2010 09 23 06 26 Main DebabrataDas ZERMATT 1 xml manage 84 9 K 2010 09 23 18 12 Main DebabrataDas x uj 1 X 5 3 11 Manual Test Result Entry Normally test execution results are expected to be uploaded ZUG Automature s automation execution engine However not all tests are automated and some ad hoc tests may also be performed manually This workflow facilitates recording of results from tests that were executed manually List All Products List all Releases for a chosen product List all Sprints or Project Phases for a chosen release List all Test Plans for chosen Sprint or Project Phase Normally there will be at most one such Test Plan List all Test Cycles for the Test Plan E e Create a New Test Cycle for the Test Plan TestCycles for FAIR WEATHER TESTING CYCLES Test Plans r3 c 02271586511 Create New Test Cycle Test Plan Summary Total Cycles Total
35. lso enter or modify test execution related data A planner can cannot add or delete any product Tester Allowed to enter or modify test execution related data but not the planning data Examples of test execution data are Test Cases Test Cycles Test Execution Results etc Admin The Admin has all the privileges to a particular product including deleting the product to which he is assigned as administrator Allowed to view planning data and execution reports Edit User Permissions Mike Viewer MikeViewer Mike Viewer has permission for the following products i i Li T Planner Tester Ld viewer ld Admin ZERMATT Planner Planner kd Tester Ld viewer kd Admin Authorize Mike Viewer for the following products U BUG TRACKER CHUR LF ZUOZ u 5 2 2 Check Audit Logs Audit Entries are created whenever any planning data 15 created deleted or modified This workflow allows you to browse through the log entries for all changes to the ZERMATT data store List Audit Log Entries Audit Log Filters Table User Product Start Date 2012 03 09 2012 04 00 Apply Selected Filters Reset All Filters Logs 183 audit entries selected from a total of 4095 Date Time User Table Operation Product Details 2012 03 30 17 54 52 PatAdmin PRODUCT DELETE 276 Name CopyofZ ID 276 2012 03 30 15 28 46 PatAdmin PRODUCT DELETE 2 5 Name C
36. not already exist Create a test suite in a Product e Under the test suite write a test case Now associate the test case to a requirement n au Seis Totum 4 5 Step 5 Tagging Refer to topic 5 3 7 Test cases and requirements may be grouped in many different ways to serve many different purposes and facilitate quick selection for a particular task e Create Tag Categories e Create Tags under the category Associate test cases and requirements to the tags UU E pus 4 6 Step 6 Lab Environment Planning Refer to topic 5 3 6 You can catalog all the equipment used for testing These maybe either be physical machines or virtual machines and later these machines may be referenced as part of a topology for a test session e Add a new Machine Adda new Role Add an Attributes for the Role e Add a new Topology for the Role Add Attribute Value for the Topology Add a new Topology Set Associate a topology to the Topology Set a n ARAD mite 4 7 Step 7 Test Planning Refer to topic 5 3 8 Now to test the requirement you need to have test plan Create a test plan under the project phase Sprint A test plan will have test suites and Topology sets e Associate one or more topology sets to the test plan Associate test suites t
37. ns for that release 2 14 Feature Each product is assumed to contain a number of high level features 2 15 Detail Requirements Each product feature can be further decomposed into a number of individual detail requirements These requirements may be spread over releases Such requirements are considered testable entities and can be associated with one or more test cases Requirements may also be assigned a priority LOW MEDIUM or HIGH Assigning a priority to requirement is often useful for planning and scheduling which test cases need to be developed early in the release cycle and which ones may be deferred until later 2 16 Requirement Variants A specific detail requirement may apply in more than one way to the target For example the requirement to copy a file may be dependent on various factors such as its size its structure its permissions its visibility etc These are the variables for the requirement Each variable can take on a number of variants For example the variants for file size could be zero byte small medium large or huge Thus a single requirement might be testable under a large number of variant combinations A test case usually tests one such combination Coverage is determined not only by the number of requirements tested but also by the number of variants of those requirements tested 3 Zermatt Navigation 3 1 Getting Started Once you have registered in Zermatt or logged in giving the username
38. odify an attribute value for this topology Attributes for Zug Client 5 Zug Client gt Rationale Testing again gt Attribute 0 Create New Topology Attribute Attribute Action s Attribute Value Physical Memory Physical Memory Add New Role Attribute i Role Zug Client Name a Required Optional Mandatory VCS Single Multiple Clear Close Window List Topologies for this Role Add a New Topology if desired one does not exist This will automatically inherit all attributes defined for the role represented this topology Remove a topology from the existing list Modify the description of a topology 4 Topologies for Zug Client Rationale 5 Machine Description 05 05 05 05 Base VM Attribute Topology Product Li f Architecture Version Language Service Identifier Sets References Zug 4 0 48 Test VM this is for testing 32 bit XP English SP2 Test VM 2 testing in latest releses of zug nad zuoz CHUR XP ZERMATT Zug testing 40 Test VM this is for testing 64 bit Windows English Test VM 1 off 0 Win 7 latest releses of zug nad zuoz 7 Zug Client gt Add New Topologies Machine Name Rationale Operating System Service Pack Language Architecture VM Name List all Topology Sets this Topology is in Quick create a new Topology Set
39. on Release Description Criticality Test Tags Name i i Cases LISTPRODUCTS Z Alpha Shallbe able to List all Products 0 2 V2 0 SIZE VALIDATION EJ INPUT VALIDATION 5 3 10 Data Migration Zermatt allows you to export data in xml format and import data from an external xml file So it becomes easy to migrate data from one Zermatt installation to another Zermatt installation Export Feature To export an object e g product release test suite feature etc from Zermatt click on the export link in the Action column of the Listing Table LIST OF PRODUCTS Create New Product E_E 4 Name ONE Description GA ORE ym Teams Tes 0 i Engine for executing automated Test Suites 1 written in CHUR JEDA The exported file can be viewed in user home page Attachments 1 Attachment Action Size Date Who Comment x CHURproduct xml manage 42K 2011 07 06 06 01 DipuS oduct exported GHURproduct xm Dipusg pr port x NYONproduct xml manage 2 6K 2011 07 06 06 15 DipuSg product exported 16 9 K 2010 10 06 07 06 DipuSg Test plan RELEASEPLAN exported x SSRMproduct xml manage 180K 2012 04 11 04 14 DipuSg product exported x manage 114 7 K 2011 08 11 03 49 DipuSg product exported x ZUGproduct xml manage 19 7K 2011 07 06 06 13 DipuS oduct exported p 4 Dipusg pr port x ZUOZproduct xml manage 2012 03 01 03
40. opyofZ ID 275 5 3 Planning Tasks 5 3 1 Release Planning for a Product or a Project planning data must belong to a product the Zermatt name for a large project Product delivery consists of one or more release cycles and each release cycle may be further subdivided into Sprints or Project Phases Typical releases may take several sprints to complete each sprint delivering a functional but not complete testable kit The idea here is that test cycles validate a specific project phase of the release List All Products Add a New Product if the desired one does not exist 17 Remove a product from the existing list Modify the description of a product 4 Product Listing Page LIST OF PRODUCTS O Create New Product E amp J Name Action Description Releases TestSultes Features Backlog items Teams 148 Engine for executing automated Test Suites written in CHUR 4 2 ZUG PRE Pegler IA are ae gt Atom library addon for ZUG 2 3 0 Pigs Ex SPEA SPEA E wf X 148 Automature Dashboard for Planning and Reporting 7 18 21 5 2 ZERMATT ORGE BE SPER EPRA BPRS Et EX Add New Product Update Product Product ZERMATT E Automature Dashboard for Planning and Reporting Acceptance ll tests in Release Test Plan have been executed Criteria and no show stoppers have been discovered Milestones Milestones pymes V 3 0 to be
41. ses for all Ad Hoc the workflow paths Testing Example To Copy a single Test case under a Test suite Test cases for WORKFLOWSUITE ZERMATT gt WORKFLOWSUITE gt Test Cases Test Suites Create New Testcase ee Test Action Description Test Steps Verification Steps Variables Requirements Execution Bug Identifier Records ees Li Q RP LP 01 14 Verify that all existing products can be 1 Navigate to Product Listing 3 1 Verify that the new product is 2 Total 2 0 a listed Page listed INTERRA Passed 2 2 Get the count of products 4 1 Verify that that the new countis Automation 3 Add a New product called higher than the old count INTERRA MyNewProduct Ad Hoc 4 Get new count of products Testing 5 Delete the MyNewProduct Example To Copy single feature under product Features for ZERMATT o ZERMATT gt Features Products c Create New Feature E 0 RELEASE PLANNING 4 Supports a workflow that allows users DipuDeshmukh SankhaSil 12 4 E to plan regular service pack or patch SIZE n E releases and also supports the agile VALIDATION Software development model INPUT VALIDATION Example To Copy a single requirement under a feature Requirements for RELEASE PLANNING ZERMATT gt RELEASE PLANNING gt Requirements Features 0 c HESTIN Create New Requirement G Requirement Acti
42. st suite BAY TECH Server some suite234 Test Product some suite234 Test Product Web Server 4 Where the Web 2 2 Application is Performance Suite SSRM hosted Stress ZUG VM Host This is the VM OF 2 ELT Hardware host OpenFile SSRM EditFile SSEM Add New Role Name Description a F MEN x 7 Se List All Topology Attributes for this Role Add a New Role Attribute if desired one does not exist If a topology already exists for this role then the attribute will be automatically propagated to that topology Remove a Role Attribute from the existing list provided no topologies have been defined for this role 9 Modify the description or properties of a Role Attribute 4 Topologies for Zug Client 5 Zug Client gt Topologies Create New Topology Rationale Action s Machine Os 05 Os Os Base VM Attribute Topology Product Li 0 Description Architecture Version Language Service Identifier Sets References 0 0 0 Graphics KALIMPONG Windows SP3 6E 0 intensive Windows 7 7 Machine Performance 4 9 AUTOSCOUT x86 Windows SP 5 Compaq 001 8000 SSRM Test Product ZERMATT ZUG Zug Client gt Add New Topologies Machine Name Rationale Operating System Service Pack Language Architecture VM Name List attribute value in all Topologies for this Attribute Assign or m
43. t Import Feature To import an object e g product into Zermatt click on the import link on the top right hand side of the table LIST OF PRODUCTS Li V 14 Engine for executing automated Test Suites ZUG PRE written in CHUR B Bh PE B E EX B Click on the browse icon and select the file that needs to be imported into Zermatt and then upload the file automature xistingz attachments for ImportExternal 2012 03 30 12 25 2011 04 14 07 37 2011 04 15 18 13 2011 05 27 08 50 2011 0425 14 55 DebabrataDas Local No file chosen Create a link to the attached at the end of the topic Hide attachment in normal topic view Organize New folder lt ZERMA x 3 Yahoo India gt lt Name Date modified y Favorites BE Desktop SSRMproduct 12 7 2010 2 55 PM ib Downloads 51 Recent Places TORR ImportExternal B Documents a Music Pictures videos Comnuter TM File SSRMproduct for other attachments a link will be created ill not be shown in topic view page e FileAttachment has more information about attaching files EIS gt Cancel Attachments of ImportExternal collaborate with ey Ga Twiki Attach file to ImportExternal Attach new file Attach new file Ektop Exported Files Export Product SSRMproduct xml Comment Link D Create a lin
44. ted Test Cases in the chosen Test Suite for this Test Plan select the Test Cases which are tagged for this Test Plan Add a Test Case to the Test Plan for this Test Suite Tag the test case with the Test Plan ID Remove a Test Case from Test Plan for this Test Suite Untag Test Plan ID tag from this test case Remove a Test Suite from a chosen Test Plan s list of Test Suites 8 Test cases for Fair weather Testing Test tion Description Tags Identifier Date FWVFOO1 LA Create A New Product 2011 07 04 Of oO EB A 19 FVVFOO02 Create New Helease 2011 07 04 El 4 19 Le Create new Feature 2011 07 04 1 E 14 19 181 Create New Requirement 2011 07 04 1 19 5 Lf modify requirement 2011 07 04 O EB A 1 4 18 modify feature 2011 07 04 1 E 18 El FVVFOO 7 Create New Testsuite 2011 07 04 4 12 4 18 El FVVFOOS Create Testcase 2011 07 04 4 1 17 El Testcase and 2011 07 04 o lt 4 1 17 El Requirement FYVFO10 Disassociate testcase and 2011 07 04 4 1 E 17 Requirement FWFO 1 delete requirement 2011 07 04 12 14 17 FVVFO12 delete feature 2011 07 04 4 1 17 El FVVFO13
45. ter Main YOURTWIKINAM Persons group who can change the list Set ALLOWTOPICCHANGE ZermattAdminGroup JeMAKETEXT Related topics ro WIKIUSERSTOPIC s TWikiGroups Yo TWIKIWEB TWikiAccessControl Now the administrator can add new users in Zermatt who have registered 1n TWiki These users can be given different levels of permissions for the existing products in Zermatt To give User Permissions for Products navigate in the following way and you will be redirected to the User Admin page 4 ZERMATT Config Dashboards e Releases Agile Features Audit Log Permissions 41 Machines 13 Topologies 47 Topology Sets p pn p p L 5 39 Roles Twiki Name Product Authorizations admin admin ERMATT Super User Performance CHUR Viewer DAVOS Viewer MarketMatrix Admin NYON Viewer Sixchex Planner Skype Admin ZERMATT Viewer Zermatt Performance Viewer ZUG Viewer Mark Tester MarkTester ZERMATT Super User Testing Admin ZERMATT Planner Zermatt Performance Planner Each category of user is allowed to do certain activities Some authorization levels are subsets of others For instance Planners are allowed to do everything Testers and Browsers are allowed to do The authorization to different products can only be given by the Zermatt Admin Group Allowed to enter or modify planning data in Zermatt Planners may a
46. the description of the selected sprint is modified and listed p Verifies that a new product with an existing product name cannot be verifies that it is not possible to delete a product if there is a reference to Verifies that the selected product name cannot be modified Testsuite V testing audit log Testsuite WORKFLOWSUITE m m E 5 3 6 Lab Environment Planning In this workflow section users can define roles that will participate a testing environment and the characteristics of those roles that may be considered significant for analyzing the effectiveness of the test To begin the user will need to create a role and then define some attributes that will need to be tracked for these roles Then various physical or virtual machines will need to be selected and the relevant attribute values will be needed to be entered Finally because a test cycle will involve a collection of machines referred to here as topologies those collections will need to be identified as topology sets List All Roles Add a New Role if the desired one does not exist 7 Remove a Role from the existing list Modify the description of a Role 4 Roles Create New Role E Action Description Topologies Testsuites Attributes Li DB Server Data Base Sewer 2 E 1 2 BEE Machine changed 2 many times Active Microsoft Active 15 3 1 ELT Directory Directory Host second te
47. the name of a Tag Category Tag Category lt Add A New Tag Category Customer Clear Close Window Execution AUTOMATION MANUAL INCLUDE Testing 2 E Megetive Testing Fair Weather Testing List all Tags for a given Tag Category Create a new Tag within the Category e g TP5678 Bug1234 Vista etc Remove a Tag not applied to any Test Case or Test Suite Modify a Tag Add New Tag Value Execution AUTOMATION 4 MANUAL Clear Close Window INCLUDE List all Test Suites associated with the Tag value Associate a new Test Suite to this Tag value Disassociate a Test Suite from this Tag value List Test Suites associated with Tag AUTOMATION Execution gt AUTOMATION gt Test Suites Filters Filter test Suites by Product Name Apply Selected Filter Reset Filter ReleaseCycleTestsuite The release cycle of Zermatt is tested by Zug AUTOMATION FeaturesandRequirementsTestSuite The features and requirements cycle of Zermatt is tested by Zug AUTOMATION Execution Cycle TestSuite This test suite contains functional test cases for Test execution AUTOMATION TestSuiteandTestCase AUTOMATION TagsCycleTestSuite AUTOMATION zuozsuite This is for testing the atoms of zuoz for different features AUTOMATION Associate or Disassociate a Tag with from Test Suites Execution gt AUTOMATION gt Test Suites Filters Filter by Product Name Apply Selected Filter
48. to backtrack easily to a previous step along the current workflow by clicking on the link Note that breadcrumbs allow only backward navigation on the currently selected workflow To jump to the last visited page on a different workflow one has to select from the Navigation Bar on the left Frame Releases g g 3 5 Object Creation Hot Links Object creation links are usually found on the top right corner just above the table These links allow the user to create a new object either from scratch or by pasting from the clipboard The object created depends on the context of the current page Note that the Zermatt clipboard has nothing to do with Windows clipboard 3 6 Icons In order to provide a consistent user experience Automature has standardized on use of a few icons viz Icon Significance Help Video Help text Navigate to context dependent dashboard page Modify the properties of the chosen object Create a new object of the chosen type Delete the chosen object Generate a printable view of this object Generate a XML dump of this object useful for loading into a spreadsheet or migrating data into another Zermatt installation Make a copy of this object the clipboard Paste a copy of the object from the clipboard Paste a copy of the clipboard object and all dependent objects under it Move laterally choose another object of same type as currently chosen Drill down one level
49. tributes such as its role its operating system the software installed on it etc 2 10 Topology Set A Topology Set describes a collection of machines required to execute a Test Case Each machine may participate in a different role e g client server database Active Directory proxy server etc test case may typically be executed on more than one topology set 2 11 Topology Set List A collection of Topology Sets that might be used for a specific purpose such as a test cycle or a release regression test plan 15 called Topology Set List 2 12 Test Plan A Test Plan identifies the following entities viz o Therelease and the project phase for which the plan exists o complete list of test suites and specific test cases contained them that should be executed during the course of the sprint o complete list of topology sets where the test cases must be executed during the sprint Multiple Test Cycles 1 one or more may be executed during the course of a single sprint and contribute to the Test Plan Some of these tests may be manually executed while others may be automated 2 13 Release Test Plan A Release Test Plan or is a special case of a Test Plan Specifically it is the Test Plan for the final or Release Sprint It identifies all the same entities as a normal Test Plan but 1s furthermore considered a formal release document A RTP 15 normally a superset of all individual Test Pla
50. y Test Suites Product Dashboard Quality Dashboard Boot Regulam Count in Ress by Cross Requirements Having Gases By ives i 1 belean Cumulative Duicorme s im sso Rada sa Progress AgxinziFimn 5 4 3 Release Quality Dashboard frat E 2 The Release Quality Dashboard Represents an individual Release with Total Builds and Test Cycles by Project Phases Topology set Count by Project Phase Unique Test Cases amp Total Execution in Each Release Cumulative Outcome in each Project Phase gt Alpha V2 4 Topology Cound Ey Pro Ard Test Cyclen Tesi Cases 5 Tois Execution Project Phases Tete Caen Pokai i a Unique Tost Gomes Total Execution 5 4 4 Sprint Quality Dashboard The Sprint Quality Dashboard represents the individual project phases with e Sprint overview by Test Plans e Topologies by Test Plans e Outcome of Test by Test Plans e Plan and Execution Metric by test Plans e Progress against plan by Test Plans e Sprint Overview by Build e Total Topologies by Builds e Outcome of Test by Builds gt Alpha V2 4 gt winter phase I2 5 Tesi bons Progress Fade fgoinet Flan Total Topologios ps F pm i meae tesin Test Plan Gumulsiive Duicomess Aorass Diferan Tesi Pies ll fetal Teed Plage amp Tess
Download Pdf Manuals
Related Search