Script-Less Introduction

ZAPTEST Script-Less enables the Quality Assurance community to deliver test automation with easy and just in time without a sophisticated learning curve, and to make test automation approachable by anyone from manual testers to application developers. zap test is proud to introduce a script list approach in building automated test cases this approach is intended for users with no programming skills the new step view offers a convenient way for quick and easy test development the side toolbar contains draggable icons for special steps such as CFLs block the weight and comment steps to control an iteration or test run and steps to access zap tests internal objects or test parameters the view toolbar includes controls to navigate through the test diagram and drop-down lists for quick access to any variable or test parameter we will start building our test case by scanning the applications UI and collecting test objects next we will add objects to the diagram and define our test steps for this we need to locate an object either in the GUI map or in the repository Explorer we can simply double-click the object or drag it into the diagram in the step view in the first step we will use the application object in the launch method to open the Firefox browser and navigate it to our website next we will validate the loaded homepage using Zapp test object and the exists method then we will click on the login link next we will include a logical step we will use the if block to check if the username object appears on the next page and based on that we will branch our test flow we will use true path in the if block to add steps to do a user login from the second view we will drag the Edit field object for the user name and select the type method the type value must be included in the argument field for the password field argument we will include the password value and enter keyword to submit the login page to validate a successful login we will drag the Welcome object from our third view and select the exist method in addition we can use an alternative or false path in the if block to stop the test run if the login page did not load and for both the comment and the stop test step we need to find a corresponding icon in the toolbox to make our test data-driven we will define two parameters using the local data table for the user name and password now we will include a reference in the parameters in the type steps arguments our test is ready let's run it and review the results [Music] any test created using the script list approach can be used to generate test documentation to do this we will navigate to the dock module and press the generate from script button the dock module provides controls for editing auto-generated documentation for saving it to a file or for exporting it to one of the supported test management systems script list tests can also be used for a parallel test execution in multi run mode we will navigate to the EM run module and connect to for remote devices we will use our test for parallel execution on all the connected devices as you can see we are able to run our script list test on the iOS Android and Windows platforms without any modifications please visit our website at to start your test automation today

Contact Us

3150 Roswell Rd NW

Atlanta, GA, 30305, USA

(800) 795-3552