ZUG User Manual (Version V5.0)
Contents
1. Hd Ld e The Word file is opened by executing the OPENFILE EXE Read Gi test Microsoft Word File Edit view Insert Format Tools Table Window Help E A TmesNewRoman i2 B Z U E x Number of TestCase to Execute is 2 x pee Start Executing the testcases e AIDED III HII AISA IIIS IS ISI III PEHEE MCCC HOO MOOR Running TestCase ID Test 1 201801102 160326 peeceeococcoeeoccooer Running Molecule Test881 OpenWordf pp Working on Test Case Variable Combination Open ordApp D0101102 168326 TEST G1_OPENWORDAPP Action SETCONTEXTUAR Execution STARTED With Arguments AppT ET TEST G1_OPENWORDAPP Action SETCONTEXTUAR SUCCESSFULLY Executed 201011027160326 Il PENWORDAPP Action STARTAPP EXE Execution STARTED With Arguments APP RETURNWINDOW AppT ype CTEST 1_OPENWORDAPP fiction STARTAPP EXE SUCCESSFULLY Executed OPENWORDAPP Verification GUERIFYSTARTAPP EXE Execution STARTED With Ar RPP Uord ITESTOB1 OPENUORDAPPI Verification UERIFYSTARTAPP EXE SUCCESSFULLY Executed 201801102 160440 T 1_OPENWORDAPP fiction OPENFILE EXE Execution STARTED With Argume Documents and Settings Administrator Desktop ZUG Kit ZUG Input File WINDOW 6x 0246122 RETURNWINDOW AppT ype FOLDER olele lt Page 1 P English U S E ListPPTestPlans lt ZE c CommandPrompt ru f amp Input Files ww Morc PE JC ESL e After the Word fil2. texas Storing the TestCase Result to 192 168 5 5 framework Database Saving Result for TestCycle ID 97 and Test Plan ID 61 of Test Plan Demo test S Following are the Details of the Topology Topology ID Ro le Build Number null null 2 T null Ha 11 null BO 12 null Following are the Details of the TestCases Result getting added to the 192 168 5 S framework Database TestCase ID Status Time Taken lt In mili seconds gt Comments Test G1 pass 165735 SUCCESSFULLY SAVED Result for TestCycle 7 and TestPlan ID 61 of Test Suit Demo test Suit SUCCESSFULLY Stored the TestCase Result to 19 2 168 5 5N Nframework Database Results in Log Files Zug will generate four types of Logs These logs will be created inside the AppData Folder Application Data folder of windows OS of logged in user All the Log File Name will be appended with a Date Time For example Debug log will be named as 2008128 163637543 Debug log format is yyyymmdd hhmmssmillisecond debug which means that this Debug Log is created on 8th December 2008 at 16 hours 36 minutes last 5 are seconds and milli seconds Following is the description of the log files Result log This log will contain the result of the test case It will contain the status of the action s specified in the TestCase worksheet and also the appropriate error result if any error thrown during the test case series execution 2 Debug log This log will contain all the debu
3. ISBIOIK ais saeua e eS Ia n Ea ERREUR PA ERU Rer EE 7 cmFAlcEs I A 3 1 TestCaseID TestUD L iiiseiske sapie rr EERR Rp RgRxARax2iXR da put 8 3 2 Repeat MoRepneasb uie ci rada edu dew Ei xd e EE bic ai 8 3 3 Autorecover NoAutorecover sseeseene nnne 8 2 4 Verbose NoVBIDOSS cise scissa erra rata e RR dua Ria 8 B5 Depu NODE DI aiiis a i 9 3 5 verify NOVENRiesiiecniercdevreiaccactevtonszeereeeieseeneereasiuns 9 3 4 AtomPathie localis arinei nia aE 9 3 8 Includesesclocaligiis ecc eee tein rap rene rrr x FERE ERR EAR 9 3 9 Execute NoEXecuUte iu ciii xke ec exa EL za es 9 3 10 macroname value cccccccccccveceeeccueeeucuueueeeens 9 3 11 TestCycleIDz integer eeeeeeeen nnn 9 3 12 TestPlanz Product Release Sprint TestPlan 10 3 13 TopologySetIDs Integer eren etapa naX en en uten 10 3 14 TopologySet AlphaNumeric eere 10 3 15 B uildTags AlphaNumerles i ieeeecieeee cinere tren rhet 10 4 ZUG MOLDUGS is siskno saxklaauuxcua aAusbasRax ARE Rua Ken REA PERLES DoD 4 1 Production Mole iiic sco p e ira ot c ER ER cR eni 11 4 2 Developer MORG ascistexi set eue pesi Re ERE SER a 1d 4 3 Performance MOoci iiir acie cei e Ra ep ERES diia 11 5 Process FIOW us onsassiaESEAREPERRARR ARA PARARE M RR GE PIA bo 5 1 Architecture OVOervieW us ccccedascssssias secscdaseasssdnsinnsi a 13 6 Running your firs
4. LogArchive MEE Li 7 Troubleshooting 7 1 Debug Log Zug generates different log file Debug file stores messages which contain extensive contextual information They are mostly used for problem diagnosis In failures this file can be referred back to diagnose and investigate problems exception The step by step execution messages are appended during Zug automation The file can be browsed through and 7 2 Primitive log Zug executes Atoms To learn how to write Atom please refer to Automature s Zuoz Programmer s Guide Inside Atoms some logging command mechanism can be used to help future diagnosis of Atom execution The Atom Logs are stored in Primitive Log File In failures this file can be referred back to diagnose and correct Atoms 7 3 Database connection problem In order to integrate test results with Zermatt there should be establishment of proper database connection You can allow access to certain machines for the specified user connection Do database user administration to add and modify users permission Put proper connection details in preparing Zug for Zermatt Refer Page 15 6 3 Preparing Zug for Zermatt Command Prompt runZUG Bat Input Files Demo Copy xls testplanid 1 topologysetid 1 v Ig x C2 ZUG gt runZUG Bat Input Files Demo Copy xls testplanid 1 topologysetid 1 verbose Automation Started Controller Main Validating Command Line Arguments Controller Main Command Line A
5. TWiki Windows Internet Explorer Go e http 192 168 5 5 twikibin view ZERMATT ListPPTestPlans projectphase id 39 File Edit View Favorites Tools Help v search vi m cy A Sharer Bh Apcheck gt dg Translate gt gt Ae o Sign In we Im lt ZERMATT lt TWiki Al Ic D Ar Erase res Word Application fy gt Release Plan V1 0 H gt Phase gg Test Plans pg Hello Debabrata Das a Log Out Sprints Phasel m My links You may modify planning data on this page My home page My ZERMATT Create A New Testplan I activities WorkFlowRoot Actions Purpose Status Acceptance Milestones Schedules Test Tops di i i Ed Criteria i f i pi Cycles Buttes CET NEUE Test 2 B Testingif Active OB 158 QualityDashboard Pan e E word ProductDashboard file can ReleaseDashboard be TestsuiteDashboard opened e Open the command prompt Md Hd Li e Type runzug C ZUG Input Files Demo xls testplanid 61 topologysetid 1 verbose c Command DI O x C gt runzug C ZUGN Input Files Demo xls testplanid 61 topologysetxml C NZma Input Files TopologySetXML xml verbose m e The following screens will appear automatically The automation starts C gt runzug C ZUG Input Files Demo xls testplanid 61 topologysetxml C ZUG Input Files TopologySetXML xml verbose Automation Started Controller Main Validating Command Line Arg
6. Um OUEST ZUG User Manual Version V5 0 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 2012 Automature LLC All rights reserved ZUG User Manual Page 2 28 iudi Revision History TT Pd Li Contents Table of Contents 1 Introductio IPEouac s adalatesh n R diae UO Mebalakibacaxdd aan biu 1 1 Document PUN DOSES cescex aeree OK ER DER ORDER ORBE Dati c dic 5 1 2 mtended Audiente ecco e E ADR a 5 2 Concepts and Terminologies 6 2 1 TOSE Euboea repa vare v xEF oxEPIxEF D ME REGENS EDS MINA RENE 6 Zu best C gbioeriiepaddi E ida auri ET ideae rit d idebadibidsaegs 6 ACIS 6 E EE 6 27 nis rrenean aa 6 2 9 de e n 6 PES Lem 6 2d FESt SUC Racecar md edo e Medi ace cH race cedi EE E ERE 6 2 8 Verification EOD ia coated ke n Erce Ha cond cain kei eU I RReeI Kew TRE 7 2 9 MYM CSRITOU
7. e is opened the CloseFile and the ExitFile executable files are called which closes the Word file and then exits from the Word application CTEST 61_OPENWORDAPP Action CLOSEFILE EXE Execution STARTED With Arguments WI DOW 6x66246122 FILE C Documents and Settings Administrator Desktop ZUG Kit Z GNInput Files test doc CTEST 1_OPENWORDAPP Action CLOSEFILE EXE SUCCESSFULLY Executed 20101102 160524 ITEST881 OPENUORDAPP1 fiction CEXITAPP EXE Execution STARTED With Arguments APP Jord e The following screens appear on the command prompt which gives the result of the automated test TT CUT Pani zjsix E STATUS PASS FOR TestCase ID Test 1 Eaxad Storing the TestCase Result to 192 168 5 5 framework Database Saving Result for TestCycle ID 97 and Test Plan ID 61 of Test TT Following are the Details of the Topology Topology ID Role Build Number null null null 14 null 30 12 null Following are the Details of the TestCases Result getting added to the 192 168 5 5 framework Database TestCase ID Status Time Taken lt In mili seconds gt Comments Test 1 pass 165735 SUCCESSFULLY SAVED Result for TestCycle 7 and TestPlan ID 61 of Test Suit Demo test Suit The detailed explanation will be stated in the following section 6 5 6 5 Viewing results in Zermatt _ T Li 6 5 Viewing results in Zermatt e You will see that the test cycle is automatically increased to one Refer t
8. file can be edited to by putting the values in the tags of lt inprocesspackages gt lt inprocesspackage name language gt lt file path gt lt file path gt lt jar package gt lt jar package gt lt class name gt lt class name gt lt inprocesspackage gt lt inprocesspackages gt This xml file ZugINI xml is in ZUG installation folder For any Java inprocess atoms the inprocesspackage tag contains file path jar package and class name tags Example lt inprocesspackages gt lt inprocesspackage name Zbrowser language Java 7 lt file path gt C Programfiles Automature ZUOZ Builtins lt file path gt lt jar package gt com automature zuoz builtins zbrowser lt jar package gt lt class name gt BrowserOperations lt class name gt lt inprocesspackage gt lt inprocesspackages gt For any C dll atoms the same inprocesspackage tag will contain different tag values example the language tag will be changed to JNT The file path tag will specifies the dll The dll name tag specifies the name of DLL file Example lt inprocesspackages gt lt inprocesspackage name JNIDLL language JNI gt lt file path gt C Programfiles Automature ZUOZ Builtins lt file path gt lt dll name gt TestDLL lt dll name gt lt inprocesspackage gt lt inprocesspackages gt For any COM dll atoms the Program ID is needed For the same inprocesspackage tag language attribute value will be COM and there will be
9. following way Example BuildTag Build074 LOMA pany 4 ZUG Modes 4 1 Production Mode In production mode the tests are run and result are registered in Zermatt This is done for unattended testing The following options are primarily used to design in this mode e NoRepeat e AutoRecover e NoVerbose e Verify e Execute e TestCycleID integer e TestPlanID integer e TestPlan String String e TopologySetID integer e TopologySet String e BuildTag String The above options are discussed in detailed in Chapter 3 ZUG Options 4 2 Developer Mode In this mode Test Automation Developer can debug the automated scripts The following options are primarily used to design in this mode e Verbose e Debug The above options are discussed in detailed in Chapter 3 ZUG Options 4 3 Performance Mode This mode is done to stress and measure performance parameters values and attributes The following options are primarily used to design in this mode e Repeat e NoVenfy e Execute e TestPlanID integer e TopologySetID integer The above options are discussed in detailed in Chapter 3 ZUG Options TE OUEST abd UTI Li 5 Process Flow 5 1 Architecture overview o Chur Spreadsheet Zug Machine Test ycles zeman B e Zug p 2 ev Lo Chur Spreadsheet Zug Machine M B gm B Terminals The atoms written in any scripting language a
10. g related messages 3 Error log This log will contain the error and warning messages if any error occurred during the execution 4 Primitives log This log will contain Logs from the Atoms during atom execution Viewing the test results from Zermatt To view the results in Zermatt navigate to the page where the test plans are written As said earlier the test cycle is incremented from 0 tol ZUG User Manual Page 23 28 mE T E ZERMATT Word Application gg gt Release Plan V1 0 gt Phase H gt Test Plans Holo pebabata OCA pplication j gt Release Plan V1 0 gp Phase o n Das a Log Out Sprints r3 D Phasel My links You may modify planning data on this page My home page yee Create A New Testplant f activities WorkFlowRoot Acceptance Test Test Topology Criteria i n n Sets i edit Dashboards x T ane ifa Active QualityDashboard an no OENE ProductDashboard can be ReleaseDashboard opened Click on View and you will be able to see the following page It states the time and the date of the initialization and completion of the test cycle ERE O Cop Sanon gg n NECASE TANIE TOP 7 Rase S RR IESE Tani Das B a Log Out My links Test Plans 3 0 My home page My ZERMATT You may modify test execution data on this page TROU Add New Test Cycle WorkFlowRoot Cycle Completed i ms to Execution edit Descript
11. ion i Complete i Topologysets i NULL Z 8 2010 11 02 2010 11 02 13000 183843 Dashboards 16 03 21 16 06 10 QualitvNashhoard If you navigate into the topology set of that test plan the test execution results are shown It stated that the test has passed and also the duration and the date of the test execution You may modify test execution data on this page Test Test Execution Performance Case i Suite Date i Details i i Test001 Z Demo 2010 11 02 Automation pass 165735 E Bl aet test Suit If you navigate to the Dashboards the various kinds of results that might be possible is shown in various formats For further information regarding dashboards kindly refer to Zermatt User Manual ET MEE D 6 7 Archival the Log files Zug supports log archiving If Zermatt integration is used then Zug will archive the log Zug will archive two types of logs eTested product like LMDC Client Server log files Log file specified in Config sheet of Test design sheet This is done by specifying ProductLogLocations in the Config sheet of Chur Test Suite Zug created log files Debug Error Result These are the log files which are generated by the Zug during test plan execution Log Archival Setup You can specify Archive Location in the Zermatt Configuration Page Zermatt Configuration fj You may modify configuration data on this page Create New Configuration Property E ArchiveLocation 2 attic C ZUG
12. jvm max memorysize 247 gt 2500 lt mvm configuration gt mvm configuration jvm max memorysize 122 gt 1500 lt mvm configuration gt lt configurations gt ed ia an 3 ZUG Options Zug has a set of standard options that are supported in the execution test environment The syntax the launching Zug is as follows RunZUG bat options FILE xls 3 1 TestCaseID Test001 If TestCaseID is specified Zug will execute only specific test cases as listed and will ignore the rest The value to be specified is comma separated list of Automated Test Case Ids This option is not required By default all test cases specified in the input file are executed 3 2 Repeat NoRepeat The Repeat option allows the user to run a selection of test cases repeatedly for a specified duration or a specified number of iterations The Longevity tests run the test plan setup and cleanup only once and record a single result as the outcome Note Zug debug logs are turned OFF during LONGEVITY MODE to ensure Zug does not consume too much disk space By default NoRepeat is selected Count integer This option specifies number of times the test cases mentioned in the test plan will be executed in iteration This should be a number Example Repeat Count 5 Duration time This option specifies how long the test cases mentioned in the test suite will be iterated through The time value has to specified in e days d e hours h e minutes
13. ll generate a new ID and update the results under it By default Zug always generates a new testcycle in ZERMATT unless explicitly specified to use an existing TestCycleID TestCycleID can be found in ZERMATT page navigating to Test Cycle Report CHsCycelD Iun dd Li Example TestCycleID 72 3 12 TestPlan Product Release Sprint TestPlan This is required to upload test case execution results in Zermatt under a particular Test Plan Instead of using the testplanid you can also report to Zermatt by naming the testplan in the following way Example TestPlan ZUG First Release rc7 sprint Smoke test plan 3 13 TopologySetID integer This is required by Zug to register results in a testcycle for the specified Topology Set The Topology Set has to be written in Zermatt and its id 1s to be specified The Topology Set Id can be seen in the Zermatt page as shown below in the status bar of List all Topology Sets for a chosen Test Plan Example Topolog Seius NN 3 14 TopologySet AlphaNumeric Instead of using the topologysetid Zug can register results in a testcycle by specifying the name of the topologyset The topologyset set associated with the test cycle should be stated while running zug Example topologyset First TopologySet 3 15 BuildTag AlphaNumeric This is required by Zug to upload the name of the Build in Zermatt for a particular sprint You can report to Zermatt by naming the BuildTag in the
14. m e seconds s Example Repeat Duration 3d Note Duration and Count are mutually exclusive If both of them are specified on the command prompt then Count takes precedence over Duration 3 3 Autorecover NoAutorecover The option Autorecover specifies Zug to run cleanup during test plan test step timeout or failure By default Autorecover will be selected unless specified otherwise If NoAutorecover is specified then there are no cleanup steps to execute 3 4 Verbose NoVerbose The option Verbose is used to display debug messages on the output console By default No Verbose will be selected unless explicitly mentioned The option NoVerbose does not display any debug messages on the output console UT CUT LH 3 5 Debug NoDebug The Debug option is specified to run the Automation in Debug Mode In this case if any atom is not implemented then the Zug will prompt with a default atom By default NoDebug will be selected unless explicitly disabled 3 6 Verify NoVerify The option Verify specifies Zug to execute the testcase without verification By default Verify is selected means ZUG will run verification actions for each testcase unless explicitly No Verify is specified 3 7 AtomPathz location This option specifies the location from where ZUG will pick up atoms for Test Automation Execution This should be a fully qualified location and should not be a relative path We can give multiple l
15. ms The atoms in Zug can be written in any scripting or programming language In this manual we have created the atoms using AutoIT a freeware BASIC like scripting language designed for automating the Windows GUI and general scripting For web based products we have our own proprietary libraries named Zuoz For more information regarding Zuoz kindly refer to www automature com The demo atoms are written in AutoIT and stored in a folder inside the Input files folder of the Zug Kit UT HE Ld 6 3 Preparing Zug for Zermatt Once the atoms are written the Chur spread sheet is prepared For more information on how to write a Chur file please refer to the Language Reference Manual of Chur The figure below shows the configuration page of Chur file for this test ile Edit View Insert Format Tools Data Window Help B Bus Anan sAn 9 652 ad Calibri x B 7 U Jb Ta C ZUGWnput Files Demo Exes localhost test root DBUserPassword password Test Suite Name Demo test suite 7 Test Suite Role ZUG Client 1 I4 J J gt X onfig Macros Users TestCases Molecules Prototypes Sheet 1 6 PageStyle Config See RR Sum 0 The Config page states the environmental information which is used by Zug to locate supporting programs and uploading results into the database e ScriptLocation states location of the folder where the Zug atoms are written for this test e DBHostName states the host
16. name for the database server To keep the data repository of Zermatt in the Zug machine localhost is given as input We can provide the exact port number also for reporting e DBName states the database name e DBUserName states the name of the user to do authentication to database e DBUserPassword states the password of the user required for SQL authentication e Test Suite Name states the name of the test suite which was stated in Zermatt e Test Suite Role states the role of the node where Test Suite will be executed The figure below shows the macros page of Chur file for this test ZUG User Manual Page 16 28 NN UT 2 Demo OpenOffice org Calc File Edit View Insert Format Tools Data Window Help B Buena vmxse6 4 95 ON NE fad Aria klo B7 u E Jh X Comment UGWnput Files Test doc Name of the file to be used J 1 Config Macros Users TestCases Molecules Prototypes l EAE li ila stp jL J l Sum 0 The macros allow the testcase designer to declare short names that can then be substituted in the testcase descriptions during execution In this case the path of the file Test doc is given as input 6 4 Executing the automated test Time has come to execute the automated test in Zug While executing the test cycles will be incremented in Zermatt automatically Before executing the Zermatt page will look as shown in the figure below 2 ListPPTestPlans lt ZERMATT lt
17. o section Executing the automated test to see the previous value of test cycle Now every time you run Zug the value increments by itself E ZERMATT WARTEN Word Application gy gt Release Plan V1 0 flf gt Phase gf Test Plans yl Das amp Log Out Sprints r3 D Phasel My links You may modify planning data on this page My home page My ZERMATT Create A New Testplan L Ki activities WorkFlowRoot P we E de OU e grees sues ons 7 Test Z Testing ifa Active BEF 16E 1 EDT Dashboards i E a u z QualityDashboard a AUS RS ProductDashboard can be ReleaseDashboard opened 6 6 Interpreting the results gt Results in Command Prompt The progress of the test cases are displayed one after another The specified Action and Verification Steps inside the test cases are executed and are shown at the same time in the command prompt If any step fails then the exception message is displayed explaining the cause of failure At the end the brief result are shown in tabular form The table has columns TestCase ID status Time Taken Comments TestCase ID The identifier of the test cases which ran inside test suite status Pass Fail Time Taken milli seconds Milliseconds taken to execute the test case Comments On failing this states the exception message with the reason of failing _ CUMET ni x STATUS PASS FOR TestCase ID Test i
18. ocations by separator Example Atompath C Tests Atoms 3 8 Includez location This option specifies the location from where ZUG will pick up molecules for Test Automation Execution This should be a fully qualified location and should not be a relative path We can give multiple locations by separator Example include C Tests Molecules 3 9 Execute NoExecute NoExecute mode will verify if the Test Design Excel sheet prepared by the user is syntactically correct or not By default Execute mode is selected unless explicitly specified If NoExecute is selected Zug will just validate the test suite design sheet display a list of errors and exit without executing any test cases in the test suite 3 10 macroname value lt macroname gt lt value1 gt lt value2 gt This option specifies the macro value of the macro in the chur sheet If the macro name is not written in the macro sheet of the chur spread sheet then it will add one while it is passed in the command line The macro name should not contain any blank space and the macro value should not contain any blanks also The macro value should be normally passed without giving any quotes Multi valued macro is also can be passed by providing the braces It is also possible in providing of macro value as 1 2 for extended macro values 3 11 TestCycleID integer Use Zermatt to look for TestCycleID If it is not provided then Zug wi
19. one additional tag as prog id _ CUTT Li Example lt inprocesspackages gt lt inprocesspackage name ZCOM language COM gt lt prog id gt Automature Pioneer lt prog id gt lt inprocesspackage gt lt inprocesspackages gt For further problems visit ZUG Forum
20. re executed in Zug platform with the help of Chur spread sheet in different Zug machines After execution the results are stored in the data repository of Zermatt The end users can access the results in Zermatt through the internet at real time _ ae Li 6 Running your first automated test In this manual we are using an example for illustration where we open a document using an office application and close it automatically If you are not using Zermatt then kindly ignore the following sections 6 1 6 1 Preparing Zermatt for Zug e Once the test plan is created in Zermatt it can be used to store automated test results The testplan id of the test plan is one of the inputs required by Zug to file the results The testplan id can be found in Zermatt e The topology sets are also needed to be written in Zermatt for integration with Zug The topology sets has to be added to the list of topology sets of the test plan The topology set written should have at least one topology The topologyset id is found in the status bar of List all Topology Sets for a chosen Test Plan e We can see the participating topologies of the topology set in the Zermatt page List All Topology Sets e The role of any one topology as shown in the above figure should match with the role stated in the Chur spreadsheet that is to be written later For deeper understanding on CHUR please refer to the Language Reference Manual of Chur 6 2 Managing Ato
21. rguments Validated Current date is 2010 11 8 Expiry date is 2011 5 1 Automation started for Automature Inc Reading the TestCases Input Sheet Input Files Demo Copy xls SUCCESSFULLY Read the TestCases Input Sheet Input Files Demo Copy xls Connecting to the Database test of Host 192 168 5 5 with User zermattadmin Connection to the Database is successful org hibernate exceptio at org hibernate X cate CerTU J 3 verter j ava 725 at org hibernate exception JDBCExcept ionHe lper convert JDBCExcept ionHelp er java 43 gt at org hibernate exception JDBCExcept ionHe lper convert JDBCExce pt ionHelp er java 29 gt at org hibernate jdbc Connect ionManager openConnect ion Connect ionManager java 327 gt org hibernate jdbc ConnectionManager getConnect ion Connect ionManager org hibernate jdbc JDBCContext connect ion JDBCContext java 127 gt org hibernate transaction JDBCTransaction hbegin JDBCTransaction java org hibernate impl SessionImpl beginTransaction lt SessionImp1l jayva 1307 ae ae 7 4 Unable to Archive Log Files Archiving of Log files are done on location specified in Configuration Refer page 24 6 7 Archival the Log files Zug machine should be given proper write permission for the location specified An exception can occur as following 0 E SUCCESSFULLY Stored the TestCase Result to 192 168 5 5 framework Database Total time taken to execute all the
22. t automated test 14 Gul Preparing Zermatt fOr ZU di easadazuk re ckr basa hh eR era da 14 p Managing ALOIS ues oki eon PAR e to PN EVE N RT E PNVO UNE UNE E PORE PE 14 6 3 Preparing Zug far ZEN Alt ya ise rrr er rns Ren eR RRS 15 6 4 Executing the automated tesa iui coasesesast uasa eina danke 16 6 5 Viewing res lts In Zemialt oie eerte tke ita 21 6 6 Interpreting the results rsimisamcsseriidsnatieeireiaeneaaisudes 21 amp 7 Archival the Log MSS ox se iuis ero Eno HIER pa Ria 24 ul ibd Lll 7 Troubleshooting 12er 25 ZI Debug Letuscidecesceva nt tetodusdAs exl deer ERd 2 Fibra danda bii 25 Fe OUI ec EE 25 7 3 Database connection problem aiio cesare tutos reme tende 25 7 4 Unable to Archive Log Fes ia oeccexa irae praep eria 26 7a Lense EOI e TM I QUI ri 26 8 ZugINI xml Inprocess atoms configuration 27 LR pads Edd 1 Introduction Zug is Automature s software test automation tool Zug provides an execution environment for tests specified using a high level test specification language namely CHUR Zug is platform independent and can be used on any environment that supports the Java Runtime Environment 1 1 Document Purpose The user manual explains you operation of Zug options You will be able to use several options for customizing the execution of test cases 1 2 Intended Audience The user manual is intended for users who want to learn or run execution of tes
23. t suites Test suites are written in Chur The test suite file is given as input to Zug Wa Hia an 2 Concepts and Terminologies 2 1 Test Suite As explained before Test Cases are individual programs designed to test a feature of a product As there are usually hundreds or thousands of features in a single application therefore the number of Test Cases would be equally high To manage so many of them Test Cases are grouped into Test Suites 2 2 Test Case A Test Case is a program whose purpose is to test a certain feature of a product It tells the developer or whoever else is trying to make the product work whether the feature is working properly by verifying the results and if not help them identify the cause of the malfunction The Automature Framework has a hierarchical structure in which Test Cases are at the core of it 2 3 Atom Atoms are the smallest unit of action in Chur They are entities such as programs or scripts that can be executed at the command line level in a shell e g the Command Prompt in Windows Atoms can be invoked on the Test Cases or Molecules worksheets in the Test Suite spread sheet on a single line An example of an atom can be a program that enters text into a form field inside a web page or can simulate a button click 2 4 Molecule Molecules are a collection of atoms in a sequence with the added ability to express more complex logic Molecules may call atoms directly or through other nes
24. ted molecules Test Cases themselves could be considered Molecules themselves except that no other test case or molecule can call them Example of a molecule can be to simulate a user login by using the atom examples above 2 5 Action A test case is a sequence of one or more Actions Each Action may take as many arguments as necessary An Action atom is expected to return an exit status code that implicitly tells Zug if the action was successful By convention a non zero status is interpreted as a failure When Zug encounters a failure status it automatically invokes the appropriate clean up steps 2 6 Test Plan Test plan is the comprehensive planning of how features can be tested with the respective test cases in certain topology sets Each test plan may contain one or more test cycles which may be executed during the course of a certain phase of the product 2 7 Test Step A Test Step should be specified for each Action of a test case or a Molecule but not for a Verification Step It should be monotonically increasing number for each test case action If two steps of a test case have the same steps then the two steps are executable concurrently Some of these steps can be considered as initialization steps few others the action steps and the rest as cleanup steps nds Edi Eid 2 8 Verification Step Each Action of a Test Case may consist of none or several Verification methods And each Verification method may take several argumen
25. test cases End to End gt is gt 168313 mill leconds Utility copyFile gt Unable to copy file Error message is flutomature Servu kup N61 98 Demo test Suit 1 26161168 262642 Zug 26161168 261744 Debug log Cu n failure account currently disabled Exception occured while archiving log on N Hutomature Serv Bac kup b1 738 Vemo est Suit 120101108 202042 fAutomature Serv Backup 61 98 Demo test Suit 1 101108 202042 Zug 20101108 201744 Debug log lt Logon failure account currently isabled gt Cleanup starting Closing Log Exiting ZUG Automation Finished iG gt zi 4 E 7 5 License Expired License can expire under the two following cases 1 You are using an expired license Each license has a certain validity period and it expires on a particular date as mentioned 2 You are using an improper license The license may be incorrect or intended for other use ontroller Main Validating Command Line Arguments ontroller Main Command Line Arguments Validated 2616 11 1 2616 11 1 urrent date is Expiry date is ontroller Main The License of ZUG has expired Please renew Visit www automature com Automation Finished puoi Edd 8 ZugINI xml Inprocess atoms configuration Zug3 0 version can call the external java jar files as built in atoms through chur spreadsheet To make this happen the ZugINI xml parsing 1s needed Inside the Zug installation directory the ZugINI xml
26. ts as needed A verification atom is expected to return an exit status code that implicitly tells Zug if the verification was successful By convention a non Zero status code is interpreted as a failure When Zug encounters a failure status in verification it automatically invokes the corresponding clean up steps 2 9 MVM Configuration While running any testcase if it contains more than a certain level of multivalued macro it may fail due to java jvm max memory which is not sufficient for keeping that many Cartesian producted testcases Due to low machine configuration it fails but it can run in high configuration machines As so from Zug3 2 version this configuration dependency is introduced in ZugINI xml as lt configuations gt tag Under that tag there is another type tag lt mvm configurationjvm max memorysize 853 gt This name attribute of this tag mainly identifies the machine JVM memory configuration which helps to find out what is the JVM max memory it can avail Under the tags the mvm cardinality is defined which have the number of cardinality of testcases Cardinality the total testcases generated by Zug doing Cartesian indexed expansion over the number of MVMs in the testcase Below is a example of a configurations tags in ZugINI xml configurations mvm configuration jvm max memorysize 853 gt 4000 lt mvm configuration gt mvm configuration jvm max memorysize 455 gt 3000 lt mvm configuration gt mvm configuration
27. uments Controller Main Command Line Arguments Validated Current date is 2018 11 2 Expiry date is 2611 5 1 Automation started for Automature Inc Reading the TestCases Input Sheet C ZUG Input Files Demo xls SUCCESSFULLY Read the TestCases Input Sheet C ZUG Input Files Demo xls Connecting to the Database framework of Host 192 168 5 5 with User zermattadmi n Connection to the Database is successful NUN Hd nd e The atom named STARTAPP EXE is called to execute otal time taken to initialize the Harness is gt 13666 milli Seconds Number of TestCase to Execute is 2 Start Executing the testcases Running Molecule Test 61_OpenWordfpp Yorking on Test Case Variable Combination OpenWordfpp 26161162 166326 CTEST6 61_OPENWORDAPP Action SETCONTEXTUAR Execution STARTED With Arguments pe 8 CTEST 61_OPENWORDAPP Action SETCONTESTURR SUCCESSFULLY Executed 26161162 166326 CTEST 61_OPENWORDAPP Action STARTAPP EXE Execution STARTED With Arguments Mord RETURNUINDOU fippT ype e The Word Application is opened Microsoft Word ri File Edit View Insert Format Tools Table Window Help Total tine tollat x pe Number of pee Start Exed Running TestC 26161162 1663 Working on Te 26161162 1663 ITEST881 OPENU ype 8 ITEST8B1 OPEN 20101102 16032 ITEST881 OPEN iguments APP ITEST881 OPEN 20101102 1684 44 start Ce e e LJ Ej Microsoft ord UT
Download Pdf Manuals
Related Search