ZUG User Manual (Version V6.2)
Contents
1. m 11 3 21 OEDITIGXC CODINRS siento snas mda ie cise Pi E Ro REPRE RR RP REIS 11 4 ZUG MOUGE iar kinh Rada n AAR EE RIKR RR AA AER ER EAR KR RA AA Rn ee 4 1 Production MOG is iius iiec iecit etait ot i VER cR ci did 12 4 2 Developer MONG ausis uetaue pesi eeu REI RF HDEHI EK EE LERR MERE 12 4 3 Performance MOUS iiia evo kp eR eaa 12 5 Process FIOW iiiusoen ssuas snEsEaRRRRARARR earannan LA 5 1 Architecture overview us esscsdetezxcadadkvbeeubd a PRG 14 6 Running your first automated test 15 MT Nm udi 6 1 Preparing zermatt for ZU caisses eie e te E nidiir ERREUR 15 b e Managing AQIS es cenigeenbricpinrndEYe ne cH Yan eade Ra o ca 15 5 3 Preparing ZUG f r Zermatt ui iic scan iderien 16 5 4 Executing the automated test iecit rre 17 6 5 Viewing results Tri Zerit osos ptecx d eH Ri t Ee Rd ne eic da 22 6 6 Interpreting the resulte sco iieseasice eto I RES IE E IA SERE a tEE 22 6 7 Jachival the Log TIISSLoasscieietudttedad adada Ad ren 25 6 8 Reporting t TOSEUIDE uu rice ead aa 25 6 8 1 Basic Terminologies of TestLink sseseeseseessse 25 6 8 2 Preparing ZUG for TeStLink ccceee eee eee teens eee eeeees 26 6 8 3 Preparing TestLink For ZUG cccceceeee teens estes eeeeeeeas 27 6 8 4 Executing the automated tests cceeeeeeeee eee eee ees 30 7 Implicit Molecule Calls 32 raw mE 32 Jod BORD WEIL eve laudas Sdisude2. Taken from Ext js VTypes js StlCfg validation cfg user email valid regex js StlCfg validation cfg user email valid regex php E Vix yap XML RPC API used to display API 303 t1lCfg gt api gt id_format 304 then set it to true by replacing the line with tlCfg gt api gt enabled TRUE UT BE dd 1 config inc php rms L4 DESCR GRON ed Rn TER Dr ELE ROAST EON ace e LASTE T er EL e e ORTU ER ESAME Em 293 StlCfg validation cfg user email valid regex js 9p erxwlI4 Q Cj 294 tiCfg gt validation cfg user email valid regex php w ae x 295 e d 296 Ws 297 New projec 238 C Folder 299 300 StiCfg api enabled TRUE 301 302 NSE Z gt 303 StlCfg api id format Ip 4s jJ 304 305 306 Now save the file and upload the folder to the server and start the server If the server was already running then it should be stopped first and then needs to be restarted after the changes have been made 6 8 4 Executing the automated tests Open a command prompt Type runzug file path filename xls verbose testplanname mytestplanname buildname mybuildname For example C Windows system32 cmd exe EXE E gt vunzug C NUsersNskhanNDesktopNU6 UNTestSuitesNcontextvar xls verbose testplanname TP1 buildname B 20130328 14 a Automation Started Warning ZugINI xml contains blank inprocess package definition Please refer to the r
3. 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 UT p iie T 8 6 JRE Dependency If the JRE 1s updated from java 1 6 to java 1 7 after installing ZUG then ZUG will stop working and it will give an error message similar to the message given below E C Windows system32 cmd exe ca x E testsuites mytestsuites gt runzug verbose ExecutionCycleTestSuite xls testcaseid EWFO16 Automation Started Registry key Software JavaSoft Java Runtime Environment CurrentUersion has value 1 7 but 1 6 is required could not find java dll could not find Java SE Runtime Environment Automation Finished E testsuites mytestsuites gt _ Solution Reinstalling ZUG will fix the problem T IUS CEPIT 9 ZugINI xml 9 1 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 is needed Inside the Zug installation directory the ZugINI xml file can be edited to by putting the values in the tags of lt inprocesspackages gt lt inprocesspackage name language gt lt file pa
4. Ej z amp cvooe EJ z rcvoor Summary z 8 0v008 z 9 CV009 2 10 V0010 Preconditions Ej 241 Cv012 EA ceronnes f Apply Reset Filters Advanced Filters W i Testing sign in Append to Context var second Combination Execution type Automated m UT 7 Implicit Molecule Calls Often we would like to run some operations or some verification that are implicit in nature For example sensing the environment on which the tests are being run or checking after each test case that the application that is being tested is reachable or running For this purpose there are some molecule names that have been reserved When a molecule is defined in the test suite with the reserved molecule name that molecule is called implicitly by ZUG 7 1 ZCase Verify If a molecule of this name exists in the Molecule sheet then that molecule is implicitly invoked after the execution of each Test Case We don t have to call this molecule explicitly ZUG Implicitly calls this molecule after running each of the Test Case However this Molecule is not invoked for the Init and CleanUp test case 7 2 ZStep Verify If a molecule of this name exists in the Molecule sheet then that molecule is implicitly invoked after the execution of each test step The test step can be of a Molecule or that of a Test Case ZUG Implicitly calls this molecule after running each of the test step However this Molecule is not invoked for the test st
5. 6 PAM i MR 6 FPE ONI du mms 6 VEA oo TET 6 2 0 VBPFIICSHOn SIBI uec e E REA UP d UR 7 2 9 MYM Conna atO ie EE EE 7 Ja ZUG DBEIDHE a iE Lid dkdbxd da kil nnana 3 1 T6590 asciDs TOSLUDL ioi nth IRPIApIUREE E PP S RYREA RR PRESA 8 3 2 Repeat NoRepeal uer chrer xe seu re X Re eet EResi n ex IINE 8 3 3 Autorecover NoAutorecover seeseeneen nnn 8 3 4 Verbose NoVerbose eeeeeeeene ennemi 8 ao Dein MODO uucce sedit kbbrbexe ka dca a doro ca d Rd otc dc 9 3 b Merihy NOVEM assises siiamaani 9 3 7 At mPath lt loca hona sessexsesxrpr av EE TEUER RET RET Y UXEKRr AER 9 3 B Iriclude locatio ius sccesicovesdxk aka kV aX ax E Rd a dv 9 3 9 Execute MoEXOCULO ui eI RIA EE WERKE kinn aE 9 3 10 macroname value cccccccccccvccceecceeeeuuuueueeeens 9 3 11 TestCycleIDz integer eeeeeeeeeee nnne 10 3 12 TestPlan Product Release Sprint TestPlan 10 3 13 TestPlanIDe integer ia vice wie vexadaia rike veta wid Yea Ee kane 10 3 14 TopologySetID lt iNteGer gt cccccccceeee eee eeeeeeeeneeaees 10 3 15 TopologySet AlphaNumeric eere 10 3 16 BuildTag AlphaNumeric eseeseeiees eene 10 3 17 LogFileNamez AlphaNumeric eesesses 10 3 18 macrocolumnz file identifier column value 11 3 19 macrofiles file locati gt iu sonos tr etx RES rAEEEEHTERIF ses 11 LN EIS e
6. Events E Account Settings Personal data Login admin First Name Testlink Last Name Administrator Email English wide UK English is the default development language and is always up to date Save Personal password Change password API interface Personal API access key 1234 Generate a new key However if the last section of the page API interface is not there and there is no button for generating a new key then follow the subtopic Enable API interface in our next topic 6 8 3 Preparing TestLink For ZUG Create a Test Project and while creating a test project make sure that Enable Test Automation API keys box is checked If the project is already created then click on the project and see if the check box is selected or not If not then select the check option and save it P die dl Test TestLink Prague 1 9 5 admin admin My Settings Logout Link Project Requirement Specification Test Specification Test Execution Test Reports User Management Events est Project Management Create a new project Create from existing Test Project No IE Name ZUG Prefix used for Test case ID Project description i SE GR Em d 5 Elt B zZ Uu Font v Size Ta u 4 B i i MW Enhanced features Enable Requirements feature Enable Testing Priori
7. OS of logged in user AII 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 debug 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 24 38 aic UT E ZERMATT Word Application gg gt Release Plan V1 0 gt Phase H gt Test Plans Holo pebabata NondA pplication fg 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
8. 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 NoVerbose will be selected unless explicitly mentioned The option NoVerbose does not display any debug messages on the output console bn idR CEPIT 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 locations by separator Example Atompath C Tests Atoms 3 8 Includez location This option specifies the location from where ZUG will pick up molecules and macros for Test Automation Execution The location can be a file name residing in the same director
9. hibernate jdbc JDBCContext connect ion JDBCContext java 127 gt at org hibernate transaction JDBCTransaction begin JDBCTransaction java 57 gt at org hibernate impl SessionImpl beginTransaction lt SessionImpl java 1307 int NN UT 8 4 Unable to Archive Log Files Archiving of Log files are done on location specified in Configuration Refer page 25 6 7 Archival the Log files Zug machine should be given proper write permission for the location specified An exception can occur as following m of xi SUCCESSFULLY Stored the TestCase Result to 192 168 5 5 framework Database Total time taken to execute all the test cases End to End gt is gt 168313 mill leconds Utility copyFile gt Unable to copy file Error message is flutomature Servu kup 61 98 Demo test Suit 1 26161168 262642 Zug 26161168 261744 Debug log a failure account currently disabled Exception occured while archiving log on wsHutomature SeruNBackupwNb1 N78 Demo est Suit 1 20101108 202042 Automature 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 SES M 4 gt 8 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
10. third party upload area cvsignore CHANGELOG CODE_REUSE config inc php config_db inc php custom_config inc php custom_config inc php example firstLogin php index php license login php logout php lostPassword php readme SCHEMA_CHANGES 9 sysinfo php SD DsSgSEDESSSSESDDDEeEEEEEEEEFE Date modified 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 3 1 2013 8 14 PM 1 20 2010 11 23 PM 3 1 2013 8 27 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 3 1 2013 8 14 PM 3 4 2013 11 54 AM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM 1 20 2010 11 22 PM Open this file with any text editor and search for the line Type File folder File folder File folder File folder File folder File folder File folder File folder File folder File folder CVSIGNORE File File File PHP File PHP File PHP File EXAMPLE File PHP File PHP File File PHP File PHP File PHP File File File PHP File FALSE Size 1 KB 105 KB 1 KB 39 KB 1 KB 6 KB 6 KB 3 KB 2 KB 18 KB 4 KB 1 KB 2 KB 8 KB 2 KB 7 KB StlCfg gt api gt enabled If StlCfg api enabled 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 l e o A
11. 1 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 _ oo dili 6 5 Viewing results in Zermatt 353 You will see that the test cycle is automatically increased to one Refer to 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 r3 Phase My links You may modify planning data on this page My home page My ZERMATT Create A New Testplan L Ki activities WorkFlowRoot P 7p Pee ope gres suites sets Test Z Testing ifa Active BEF 16E 18 Dashboards i re s B QualityDashboard ani LET or 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 i
12. 6 PENWORDAPP Action STARTAPP EXE Execution STARTED With Arguments APP RETURNWINDOW AppT ype CTEST 1_OPENWORDAPP fiction STARTAPP EXE SUCCESSFULLY Executed RPP Uord CIEST G1_OPENWORDAPP Verification UERIFYSTARTAPP EXE SUCCESSFULLY Executed 20101102 160440 G1_OPENWORDAPP fiction GOPENFILE EXE Execution STARTED With firgune Documents and Settings Administrator Desktop ZUG Kit ZUG Input File WINDOW 6x 0246122 RETURNWINDOW AppT ype FOLDER a 2 English U S 754 start F tistpptestPlans lt ZE cx Command Prompt ru f Input Files w c EL 365 83 12 After the Word file 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 fiction 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 CTEST 61_OPENWORDAPP fiction CEXITAPP EXE Execution STARTED With Arguments APP Jord 1 The following screens appear on the command prompt which gives the result of the automated test _ BE dd 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 6
13. ASHA SIA ASIA SIA SSAA SALAS SISA SASA SISA SAHA NN UL e Once the execution is finished we can go to the Execute Test cases link in the Test Link and select the test plan name and the build name that we mentioned in the command prompt in the runzug command Test TestLink Prague 1 9 5 admin admin My Settings Logout Link Project Requirement Specification Test Specification Test Execution Test Reports User Management Events zuc 4 Test Plan TP1 Build B 20130328 140 Test plan Test Case Execution Settings al 5 Purpose Build TP1 f RR Allows user to execute Test cases User can assign Test result to Test Case fo Build to execute B 20130328 140 x Update tree after every operation v Get started Export Test Plan Export Test Plan 1 User must have defined a Build for the Test Plan 2 Select a Build from the drop down box 3 If you want to see only a few testcases instead of the whole tree 4 Click on a test case in the tree menu 5 Fill out the test case result and any applicable notes or bugs 6 Save results Note TestLink must be configured to collaborate with your Bug tracker if you Any x Any x 3 Any include unassigned Test Cases Any x Build chosen for execution lApply Reset Filters Advanced Filters Expand tree Collapse tree 4 C3 ZUG TP1 64 53 11 0 0 4 C3 contextvar 21 10 11 0 0 gt
14. Gacv 11XC0 11 0 0 zuG e cvooe ZUG 7 CV007 Fi ZUG 10 CV001 ZUG 11 Cv008 ZUG 12 Cv009 ZUG 1 TC001 Once we choose the test plan and the build we ll be able to see the executed test cases as shown in the above pic To see the execution result of a test case click just click on it as shown below Test TestLink Prague 1 9 5 admin admin My Settings Logout Link Project Requirement Specification Test Specification Test Execution Test Reports User Management Events E 4 Test Proj eevee reou tary ie Test plan notes Filters A 7 Build description Test Case ID z ee Print Show only last execution Import XML Results Execute and Save Results jest Case Test Suite x m abd Seite Priorit yl d am NW Test case 1D z 2 Version 1 Execution type Any cvoo2 gets fang No tester assigned n include unassigned Test Cases Execution history Build My ZUG B 171422013 un Bm v Date Tested by Status Test Case Version attachments jon Build chosen for execution v 14 03 2013 13 00 21 admin Passed 1 7 Notes Time to execute 0 542 sec Completion Time Thu Mar 14 17 30 20 IST 2013 Expand tree Collapse tree m 4 CjMy ZUG TP1 67 2 63 2 0 4 ECV Q5 2 22 1 0 E mev 12X0 12 0 0 Ej z4 cvo01 amp dcvo E z3 cvo03 E z 4 cvoos 1 5CV005
15. LLORA PROCESSOR_ARCHI TECTURE x86 NUMBER OF PROCESSO TC 611 Action ZSTRING COMPARE SUCCESSFULLY Executed STATUS PASS FOR TestCase ID TC 1 On lt Current Date 2613 05 13 16 46 39 HHH HH HAHAHAHAHAHA AL AAA E AHA LAA ASLSAAAC LA AAA SAA ACSACL AA E E SAA SASL DE DE DE DE E E E DE DE ASA SH E E E SIAC E E E E E AE EAE AE Je e ee e eaae e aaa LL ALLLLLLLSAUULULULUIDCLILOLLLLLLLLZ O eLACOBUOALZL A ABaLIN L nN LLANAN LLLLLLLLLLLLLLLLLLLLL O bOOBAL N Running TestCase ID TC 2 On lt Current Date 2013 05 13 16 46 40 TC002 Execution Started Action Zstring compare with values OS Name Windows 7 Java ve on 1 7 LOGON SERUER ELLORA COMPUTER NAME ELLORA USER NAME skhan APPDATA C Users skhan AppData Roaming USERDOMAI LLORA PROCESSOR_ARCHITECTURE x86 NUMBER_OF_PROCESSORS 2 RAM 3999 MB OS Name Mindous 7 Java version 1 7 LOGON SERUER ELLORA COMPUTER NAME ELLORA USER NAME han APPDATA C Us khan AppData Roaming USERDOMA IN ELLORA PROCESSOR_ARCH ITECTURE x86 NUMBER_OF_PROCESSO IRS 2 RAM 3999 MBI ITC8821 Action ZSTRING COMPARE SUCCESSFULLY Executed STATUS PASS FOR TestCase ID TC 2 On lt Current Date 2613 65 13 16 46 46 HCH MCHCHOM REA RIE AE BERK E CMM MH CH COMM EEE MM CC AEE HCM MC MORE E BEREAN HCM HC e E E EE HHH ARERR C AHH AHA AAA ALAA LACSEA 4 4 LA SIAL E C4 MCCC MCCC MCCC ACSA CSLCACACSCS CAA Running TestCase ID cleanup On CCurrent Date 2613 05 13 16 46 46 CLEANUP Action UNSETCONTEXTUAR Execute
16. Lb Pod AE iili ZUG User Manual Version V6 2 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 38 iia iili Revision History 20 05 13 Md Sarfaraz Khan Added command line options ignore atomexectime and DB and script location configurations TT BE ddl Contents Table of Contents ZUG User Manual Version V6 2 jacas REVISION HEISTOFV u s seibeiqadxdad d dEcblkikdciid adl bd idola dabit CODO iesad dddad aba ER Eth e RR RE d d ir ERES Ro dr xd d rd iria 1 Introduction cicca 1 lpocumentr PU DOS uei ne mi Reauie Kad annes skUe vuuM E IEEDLA MEE 5 1 2 Intended AUOIBICB e sic sceccios e cle RI a EFMIR ERR XE RA aves aa RI ads 5 2 Concepts and Terminologies 6 CANI UE Irc TRE 6 PE d4 d eH 6 PCIE Ir ME 6 Wa Nurs wr
17. UAR 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 1 The Word Application is opened a Microsoft Word E Fie Edit View Insert Format Tools Table Window Help jj Total tine talline z f pe Number of pee Start Exe Running TestC 20101182 1603 Working on Te 26161162 1663 ITEST881 OPEN ype 8 CTEST 61_OPEN 20101102 3 TEST A1_OPEN TEST 1_OPEN ljuments APP CTEST 61_OPEN 2 4161162 1684 LETC estPla e TMe ZUG User Manual Page 20 38 Author Md Sarfaraz Khan Date 20 05 13 Rad ll test Microsoft Word File Edit view Insert Format Tools Table Window Help INE mE t a bx Number of TestCase to Execute is 2 Bl A TimesNewRoman 12 gt B Z U i e mum EE NPE pee Start Executing the testcases e 2 AIDE IDI IDI HAA AISA AA IAA SASSI SIS III AI IIIA IIA IIS AAA AA ISIS SIS SAI AIIM Running TestCase ID Test 1 24161162 168326 pecceeococcoeeecocoer Running Molecule Test 01_Opentlordfpp seeeeccoococcooon Working on Tes e Variable Combination OpenWordf pp 26101102 16032 TEST G1_OPENWORDAPP Action SETCONTEXTUAR Execution STARTED With Arguments AppT ype 8 CTEST 1_OPENWORDAPP Action SETCONTEXTURR SUCCESSFULLY Executed 216116216832
18. 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 UvOnocppecummnt gg e NECASE TANIE TOP EE eee S RR IESE Tan 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 Description 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 we ni de ili 6 7 Archival the Log files Zug supports log archiv
19. d With NO Arguments STATUS PASS FOR TestCase ID cleanup On CCurrent Date 2613 065 13 16 46 41 MOE HE RE Ho NEE REE BER ME E E E E HOME i E E E AE HOMO E E E E E E E E E E HOMO E E E E E E E HOE EEE Following are the Details of the TestCases Result Executed by ZUG Version gt ZUG Premium 6 2 20130507 TestCase ID Status Time TakenCIn milli seconds gt Comments pass pass Total time taken to execute all the test cases End to End gt is gt 5954 milli Seconds Above is the console output of the test case We can see that in the console output that the Zenv_Sensor molecule have been implicitly invoked in the end of the Init test case UT Ll da ddl 8 Troubleshooting 8 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 8 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 8 3 Database connection problem In order to integ
20. eadme txt or Zug User Manual If the test plan name doesn t exists then it creates one with the mentioned test plan name and also creates a build with the mentioned build name The build name is optional if we don t give a build name it will create a new build with a new system generated build name The following lines will appear automatically The automation starts E C Windows system32 cmd exe C fa E gt runzug C Users skhan Desktop U6 TestSuites contextuar xls verbose testplanname IP1 buildname B 26136328 14 ul Automation Started Warning ZugINI xml contains blank inprocess package definition Please refer to the readme txt or Zug User Manual Command Line Arguments Validated Current date is 2013 3 28 Expiry date is 2014 1 1 Zug is Valid Automature LLC This Generic License is issued to Automature and Manimitra for usage of Zug Reading the TestCases Input Sheet C Users skhan Desktop U6 TestSuites contextuar xls SUCCESSFULLY Read the TestCases Input Sheet C Users skhan DesktopW6 TestSuites contextvar xls Connecting to Test Linkhttp localhost 8698 test Llink lib api xmlrpc php Connection to testlink is successful TestLinkReporter Build name was not provided or the build name doesn t exists System has created a new build B 201383 28 140 Ld Total time taken to initialize the Harness is gt 13764 milli Seconds HIER HHH HHH AHHH HAHAHAHAHA IAA SALA ASIA SISA SASHA LASSIE S
21. ep of Init and CleanUp test case and also for the test steps of ZCase Verify molecule 7 3 ZEnv Sensor A molecule is defined with this name to sense the environment in which the tests are being run This molecule is invoked implicitly after running the Init test case or after running the first test case of the test suite Init SetContextvar envValues TC001 Zstring compare YenvValues ZEnv_Values cleanup UnSetContextvar envwalues Zen Sensor appendtoContextvar enwalues ZEnv Values print inside molecule In the above pic we can see there is a test case and a molecule Zenv_Sensor Also we have used a context variable ZEnv_Values This context variable is defined by ZUG to store some environment related information Initially it holds some values like OS Name Windows 7 Java Version 1 6 User Name Ellora etc as a comma separated list We can further add some more details in the ZEnv Values context variable in this molecule which may be needed For example the name and the version of the browser that will be used for the browser operations ZUG User Manual Page 33 38 Author Md Sarfaraz Khan Version 6 5 Date 20 05 13 pees Start Executing the testcases 3 4 4C94CMCCMCCXCMCMCMCMCOMCM COCOA COMO OCC COO COCOOMCOCCOCOOCOCMOMCOMCOCOMCOMCOCOCOCMCOMCOCOMCOCCOCOCOMCOMCOOCO C Running TestCase ID Init On lt Current Date 2613 65 13 16 46 38 INIT Action SETCONTEXTVAR Execution STARTED With Arguments envUalues INIT Act
22. g results into the Test Frame Work e ScriptLocation states location of the folder where the Zug atoms are written for this test DBHostName states the host name for the Test framework server Here we have to provide the the IP address along with the port number in which the server is listening and the rest of the part is the location of a PHP xmlrpc php file in the Test Link framework TestFramework states the name of the Test Frame Work in which we want to report the results of the test case execution Since we want to report in TestLink the value of the field is testlink DBUserName states the name of the user to do authentication to the Test Frame Work In this case we are using the admin DBUserPassword states the dev key also named as Personal API access key or script key for the user e Test Suite Name states the name of the test suite which was stated in Test Link Test Suite Role states the name of the Test Project to which the Test Suite belong Note The dev key also called Personal API access key can be found in the MySetting link in TestLink If the key is not generated then click on the button Generate a new key A key will be generated Below is the snapshot of the page BE UT Q D localhost8098 testlink index php Test TestLink Prague 1 9 5 admin admin My Settings Logout Link Project Requirement Specification Test Specification Test Execution Test Reports User Management
23. ing If Zermatt integration is used then Zug will archive the log Zug will archive two types of logs Tested 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 gt ArchiveLocation 2 attic C ZUG LogArchive 6 8 Reporting to TestLink 6 8 1 Basic Terminologies of TestLink Test Projects are the basic organizational unit of Test Link Test Projects could be products or solutions of your company that may change their features and functionality over time but for the most part remain the same A Test Project includes Test Specifications with Test Cases Requirements and Keywords Users within the project have defined roles Test Projects are independent and do not share data Test Case describes a testing task via steps actions scenario and expected results The Test Case is the fundamental element of Test Link Test Suite organizes Test Cases into units Each Test Suite consists of a title a formatted description Test Cases and possibly other Test Suites Te
24. 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 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 ni ix TENIS 3 ZUG Options Zug has a set of standard options that are supported in the execution te
25. ion SETCONTEXTUAR SUCCESSFULLY Executed STATUS PASS FOR TestCase ID Init On lt Current Date 2613 05 13 16 46 38 M en nnn a a e a a poeeeooooeoeoeooeoeoeoeceoe Running Molecule Init zenu sensor 399900000000000000000O00O0 9 RRR ERE NACHE ENERO AGERE CHO WHY EA RRR REPRE E E RE SERENE ERE Wo RH E WR CINIT_ZENU_SENSOR Action APPENDTOCONTEXTUAR Execution STARTED With Arguments contextuar enuUalues valueTofippend 0 Name Windows 7 Java version 1 7 LOGON SERUER ELLORA COMPUTER NAME ELLORA USER NAME skhan APPDATA C Users skhan fAp pDat a Roaming USERDOMAIN ELLORA PROCESS OR_ARCHI TECTURE x86 NUMBER OF PROCESSORS 2 RAM 3999 MB CINIT_ZENU_SENSOR Action APPENDTOCONTEXTUAR SUCCESSFULLY Executed CINIT_ZENU_SENSOR Executed Action print with values inside molecule poceecceecceeeceeeece Molecule Init_zeny_sensor Execution Finished sseeseeeeHHEHHEEEHEEEHEEeE p RRR ESE EE E E RRR RADA EE RR RA EEE RAH REE HC HOO E NE A EE PRN RO EE Running TestCase ID TC 1 On lt Current Date gt 2613 05 13 16 46 39 gie Execution Started Action Zstring compare with values 0S Name Windows 7 Java version 1 7 LOGON SERVER ELLORA COMPUTER NAME ELLORA USER NAME skhan APPDATA Users skhan fppDat a Roaming USERDOMAIN ELLORA PROCESS OR_ARCHI TECTURE x86 NUMBER_OF_PROCESSORS 2 RAM 3999 MB OS Name Windows 7 Java version 1 7 LOGON SERUVER ELLORA COMPUTER NAME ELLORA pn Nania eB eG eSsers vs khan NI ppData s oaming USERDOMAIN E
26. le for this test File Edit View Insert Format Tools Data Window Help a Buena SE KSB o D s ORK Calibri x BZU Jb Ta C ZUGWnput FilesiDemo Exes localhost test root DBUserPassword password Test Suite Name Demo test suite 7 Test Suite Role ZUG Client THE gt Jibi X onfig Macros Users f TestCases i Molecules Prototypes Sheet 1 6 PageStyle_Config i LODS Sum 0 The Config page states the environmental information which is used by Zug to locate supporting programs and uploading results into the database 1 ScriptLocation states location of the folder where the Zug atoms are written for this test 1 DBHostName states the hostname 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 12 DBName states the database name 1 DBUserName states the name of the user to do authentication to database 1 DBUserPassword states the password of the user required for SQL authentication 1 Test Suite Name states the name of the test suite which was stated in Zermatt 1 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 17 38 i UL Fite Edit View Insert Format Iools Data Window Help B Bae Bao v9mxse 4 9 e 545A2 4 Arial Fw Bru Ax Comment UGWnput File
27. lly 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 UT DU UT 3 11 TestCycleID integer Use Zermatt to look for TestCycleID If it is not provided then Zug will 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 CfesCydelD Example TestCycleID 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 TestPlanIDz integer This is required to upload test case execution results in Zermatt under a particular Test Plan Instead of using the testplan you can also report to Zermatt by putting the testplanid in the following way Example TestPlanID 84 3 14 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 is to be specified The Topology Set Id can be seen in the Zermatt page as shown be
28. low in the status bar of List all Topology Sets for a chosen Test Plan Example Topology Sea NUN 3 15 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 16 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 following way Example BuildTag Build074 3 17 LogFileName lt AlphaNumeric gt This is required by Zug to change the logfile names where zug logs the execution messages error debug The logfile name will be created as lt logfilename gt Atom log lt logfilename gt Debug log un UT 3 18 macrocolumnc file identifier column value We can have multiple value column in a test suite for a macro This option let us select a particular macro value column for a test suite The syntax for macrocolumn is macrocolumnz file identifier column number file identifier column number The file identifier is the file name default name space or the optional name space provided in the include option If we have provided any optional name space in the include option then it should be the file identifier in the macrocolumn If any cell of the selected column is empty then i
29. 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 ani iin TENIS 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 arguments 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
30. 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 Ao NG We can see the participating topologies of the topology set in the Zermatt page List All Topology Sets E NG 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 Atoms 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 ZUG User Manual Page 16 38 di ad AT 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 fi
31. nscidbi ad aestu data E EA aid UE RadbE rd 32 Zi LENY SEDBSOliecornetb ce ka kel eds ER FAR MERI RR Eg CK DAN ER ERR 32 8 Troubleshooting 11 1 34 c ifc T 34 CRUS Primitive OG E D D Ea 34 8 3 Database connection problem ccccscceceeeeeeeeeeeeeeaees 34 8 4 Unable to Archive Log Files iicet retta th 35 8 5 License EXplFed iude ides pe bx vend ku IR kk IRR EA SEM 35 9 ZUugIMIJXml usssexonixobsinbxxc d dixe Fd GNE RE dF 9 1 Inprocess atoms conrigulatidltesiuiisacexuk o kunt e rn Ka rei 37 9 2 DB Configuration and Script Locations 38 Te IUS EPIS 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 test suites Test suites are written in Chur The test suite file is given as input to Zug Gin IUS TEST 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 h
32. nside 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 TT BE dd x STATUS PASS FOR TestCase ID Test i 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 gt 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
33. o End gt is gt 185266 milli Seconds 1 Most time consuming Atom in the Test Suite along with thier execution time in milli seconds Atom Name Min vg Max gotourl 4028 4028 browsetopagebyurl 3711 7026 clickbuttonbyvalue 3113 3113 initialize 2523 2523 clicklinkintablebyrowco lumnandlinkindex 1641 2991 browser clickimagebytit le 1596 1697 browser clickbuttonbytext 1392 66 2265 brouwser gettableco Lumnnrbyco Llumnname 666 86 731 browser gettablerownrbyco lumnnameandtext 653 66 696 browser getrovcount intable 649 67 672 Exiting ZUG Automation Finished op IUS sa 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 NoRepeat AutoRecover NoVerbose Verify Execute 35 17 35 17 35 17 35 17 35 17 35 TestCycleID integer 35 TestPlanID integer 35 TestPlan String String 1 TopologySetID integer 1 TopologySet String 35 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 1 Verbose 1 Debug The above options are discussed in detailed in Chapter 3 ZUG Options 4 3 Performance Mode This mode is done t
34. o stress and measure performance parameters values and attributes The following options are primarily used to design in this mode Repeat No Verify Execute TestPlanID integer PETG as 30 w Aw No No No No No TopologySetID integer The above options are discussed in detailed in Chapter 3 ZUG Options sib Author Md Sarfaraz Khan Date 20 05 13 dnb a dili 5 Process Flow 5 1 Architecture overview o Chur Spreadsheet Zug Machine Test Cycles 9 me e oe Chur Spreadsheet Chur Spreadsheet eo Machine e Machine Terminals The atoms written in any scripting language are 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 UT P da dili 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 Ao NG 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 Ao NG The topology sets are also
35. rate 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 16 6 3 Preparing Zug for Zermatt E Command Prompt runZUG Bat Input Files Demo Copy xls testplanid 1 topologysetid 1 v C2 mms C ZUG gt runZUG Bat Input Files Demo Copy xls testplanid 1 topologysetid 1 Controller Main Validating Command Line Arguments Controller Main Command Line Arguments Validated Current date is 2010 11 8 Expiry date is 28011 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 S C 34 4 3 TU T verter j at org hibernate exception JDBCExcept ionHe lper convert JDBCExcept ionHelp er java 43 gt at org hibernate exception JDBCExcept ionHe lper convert JDBCExce pt ionHe lp er java 29 gt at org hibernate jdbc Connect ionManager openConnect ion Connect ionManager java 327 gt at org hibernate jdbc Connect ionManager getConnect ion Connect ionManager jjava 118 gt at org
36. s Test doc Name of the file to be used 1L gt J Config Macros Users TestCases Molecules Prototypes Tl She leMaco STD _ Sumo O 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 ListPPTestPlans lt ZERMATT lt TWiki Windows Internet Explorer 68 e http 192 168 5 S twiki bin view ZERMATT ListPPTestPlans projectphase_id 39 hed X File Edit View Favorites Tools Help v search Hi Gey E harer Eh Apcheck Gy Translate Ae 7 CS Signin fpc E wee Page D Tools S Word Application fy gt Release Plan V1 0 gj Phase gg Test Plans pg Hello Debabrata Das amp Log Out Sprints Phasel m My links My home page My ZERMATT Create A New Testplan t JB activities WorkFlowRoot Actions Purpose Status Milestones Schedules Test di g 3 E Crite s Di E Cycles oag Topology sets i Dashboard Test Z Bj Testingif Active E QualityDashboard Pan e R 3 word ProductDashboard file can ReleaseDashboard be Test
37. st environment The syntax the launching Zug is as follows RunZUG bat options FILE xls 3 1 TestCaseID TestOO1 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 3fdays d hours h t minutes m td 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
38. stLink uses a tree structure for Test Suites Test Plans are the basis for test execution activity A test plan is created when you wish to execute Test Cases A Test Plan contains name description collection of chosen Test Cases Builds and some optional attributes Test Results milestones tester assignment and priority definition Each Test Plan is related to the current Test Project iib ica dili 6 8 2 Preparing ZUG for TestLink We need to provide some information in the configuration page of the Chur spread sheet in order to report the execution results of test cases in Test link The figure below shows the configuration page of Chur file for this test contextvar xls OpenOffice org Cale Jm ne File Edit View Insert Format Tools Data Window Help E 2 Bos Arnan Exte g O o ON by HABO BRAA E Arial xj fo x B 7 Ux am AXE RB EE O B A 87 zuc A JE rs ScriptLocation C Program Files Automature Zuoz GeneralPurpose Ruby 2 DBHostName http localhost 8098 testlink lib api xmlrpc php gt TestFramework testlink DBUserName admin DBUserPassword 1234 Test Suite Name CV J Test Suite Role Include 9 CHL Config Macros TestCases Molecules Prototypes m p Sheet1 5 PageStyle_Confi STD Sum 0 e e 240 gestyl g The Config page states the environmental information which is used by Zug to locate supporting programs and uploadin
39. suiteDashboard opened You may modify planning data on this page e Internet 1 Open the command prompt UT Dl da UT 35 17 Type runzug C ZUG Input Files Demo xls testplanid 61 topologysetid 1 verbose ommand jo x C gt runzug C ZUGN Input Files Demo xls testplanid 61 topologysetxml C Z Input Files TopologySetkML xml verbose m Ao NG 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 Arguments 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 UT BE UL 12 The atom named STARTAPP EXE is called to execute otal time taken to initialize the Harness is gt 136660 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 SETCONTEXT
40. t prog id gt Automature Pioneer lt prog id gt lt inprocesspackage gt lt inprocesspackages gt 9 2 DB Configuration and Script Locations In the config sheet of the test suite we have to mention the script location and also some information of the Test Management Framework credentials host name etc for reporting the execution result of the test cases However Test suites running on the same machine may report to the same Test Management Framework with a default data base credentials and also we may want to have a default repository for the out process atoms Thus we can mention default script locations and default configuration for the Test Management Framework in ZugINI xml file In the ZugINI xml file inside the configurations we can mention the default script locations under the script location tag and the Test Management Framework information in their respective tags as shown below configurations lt scriptlocation gt C ProgramFiles C ProgramFiles x86 lt scriptlocation gt dbhostname http localHost 4567 dbhostname lt dbname gt Framework lt dbname gt lt dbusername gt davosuser lt dbusername gt lt dbuserpassword gt user lt dbuserpassword gt lt configurations gt For further problems visit ZUG Forum
41. t takes the value of the default column cell 1 column i e the value column 3 19 macrofile lt file location This option is used to include a macro text file from command line The text file contains macro in the format macro value Each macro should begin in a new line At run time ZUG treats these macros as it belongs to the main test suite The syntax is macrofile filelocation Example macrofile D Files macroFile txt 3 20 ignore This command line feature act as an overview mode As the name suggests ZUG ignores all the errors that occur during the execution of test steps If a test step of a Test Case or of a Molecule fails ZUG shows the error message but does not stop the execution and all the test steps of the test cases and that of the Molecules are executed 3 21 atomexectime This command line feature is used to measure the performance of the atoms that are invoked from the test suite After executing each atom ZUG appends the time taken to execute the atom in the end of the success message of the atom and at the end of the execution ZUG reports the min avg max execution time of the 10 most time consuming atoms in milli seconds Given below is a sample output format for this command line switch TC001 Execution Started Action Zbrowser GoToURL with values 148283 http www google com TC001 Action ZBROWSER GOTOURL SUCCESSFULLY Executed in 3023 milli sec otal time taken to execute all the test cases End t
42. th 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 mE P EA dd For the same inprocesspackage tag language attribute value will be COM and there will be one additional tag as prog id Example lt inprocesspackages gt lt inprocesspackage name ZCOM language COM gt l
43. ty E Enable Test Automation API keys T Enable Inventory Issue Tracker Integration 7 Active ssue Tracker L Iz Availability Vv Active 7 Public Create Cancel Create a new Test Suite in the Test Project e Once the Test Suite is created we can add test cases in the Test Suite We need to create a Test Plan and a build for that test plan Finally once the Test Plan and the build is created the test cases need to be associated with the test plans Note For reporting from ZUG in Test Link Test Project and Test Suite only needs to be created before running the tests Last 3 steps mentioned above can also be performed by ZUG However for that the user whose credentials is mentioned in the chur s configuration sheet must be authorized in test link to do the mentioned operations For more information on TestLink read the user manual for test link http www teamst org tldoc 1 9 testlink user manual pdf Enabling the API Interface This section if needed only if the API interface is disable and the user is not bale to generate API key By default the API Interface is not enabled in the TestLink In the TestLink folder there is file config inc php ZUG User Manual Author Md Sarfaraz Khan Version 6 5 Page 29 38 Date 20 05 13 Local Disk C xampp htdocs testlink My c Share with Burn New folder zZ a 3 n gui install lib locale logs
44. undreds 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 Jest 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 nested 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 1s a sequence of one or
45. y of that of the test suite or fully qualified location of the file but it should not be a relative path We can give multiple locations by comma separator Example include C Tests Molecules One more powerful feature of this option is to provide name spaces to the test suite included from command line The syntax for giving name space in the include option is include namespace1 filename1 namespace2 filename2 In the test suite when we are using the macros and molecules of the included test suite then we should append the name space For example if we are using a macro say test of filename1 then in the main test suite we should write namespace1 test 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 lt macroname gt lt value gt macroname value1 value2 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 norma
Download Pdf Manuals
Related Search