GoTestPro account: If you haven't signed up for a free trial, you can use following link https://app.gotestpro.com/#/signup to sign up. The trial includes all product features and free support (always!). You may reach out for help via the in-app chat or email to email@example.com.
GoTestPro is an Automation Test tool that enables continuous testing across diverse applications and Technologies.
It is a user-friendly, robust automation tool that supports easy test case creation, configuration and execution of test cases.
Creating a Project
Let’s define the key terms:
Project - Can be your web application for instance.
Test Case - specific scenario that needs to be tested, say, login functionality.
Test Steps - the actual set of instructions/steps required to test the functionality.
Note: By default, few Projects will be readily available on your account. These projects (here, Web application) will also have a few sample Test Cases and Test Steps ready for your reference.
Start by creating a Project first.
Login as Test Manager
Click on Projects from the Navigation menu.
Click on Add New Project button.
Enter Project Title, Project Type.
Select 'Add Environment,' enter Environment Name and Base URL (Application Test End Points), and then click on 'Save.'
Again, click on Save- the project has now been successfully created.
Note: In Add Environments, users can add up to 5 Environments, i.e. ( DEV, QA, UAT, Stage, PROD).
Recording Test Steps using GTP Extension
The Extension by GoTestPro operates within your web application, functioning as both a recorder and an object spy. This allows crafting highly reliable tests in no time at all.
Note: If you have not installed the Chrome extension, you will be prompted to install the extension when you try recording your steps in this stage.
Log in as the Test Manager/Test Engineer.
Select the Projects from the 'Select a Project' drop-down list.
Click on 'Tests' from the Navigation Menu.
Create the Test Name and Tag (the above steps are to be followed):
Tags are mandatory to have to perform the execution on the Cloud/Server side. Tags are used to group the tests, e.g., Sanity, Smoke, Regression, etc.
You can execute scripts/tags without the Tag in Local Run if needed.
Click on the Test View icon from the Tests Table.
Click on the REC button on the Test Worksheet page.
Ensure you are updated with the latest Chrome Extension by navigating to Project Setting-->Chrome Extension setup. (This step is required only in a QA/Dev environment until the GoTestPro Recorder Extension is published on the chrome store – steps to get the extension id are given below):
If the user has multiple environments, navigate to the Projects page, and click on the 'True Under Default' column to select a default environment.
This step launches a new browser and a GTP Recorder extension. The browser should be loaded with an app URL added in the project>> Environment Base URL stage.
Once the Application is launched on the web app, start recording.
Now perform the needed actions in the Application.
Click to Save to stop recording.
Watch this video on how to record a test:
*GTP has the following Assertions:
Add Mouse Hover Action: In some cases, we may want to mouse hover on an element and check if the button state/color changes after mouse hover.
Assert Element: It checks whether that element is present on the page or not
Add Wait Time: Some cases need a hard waiting time.
Add Check Assertion: Verifies whether the check box is checked or not during test execution.
Add Uncheck Assertion: Verifies whether the check box is checked or not during test execution.
Add Enabled Assertion: Checks whether Button/Text Box is enabled or not during test execution.
Add Disabled Assertion: Checks whether Button/Text Box is disabled or not during test execution.
Add Page Title Assertion: There are cases where we need to check the title of a particular page
Add Tool Tip Message: Verification Some cases need verification of the tooltip message during test execution.
Creating Data Driven Scenarios
Login as Test Manager/Test Manager.
Select Project and Navigate to the Test Page.
Click on the Add New Test button on the Test Page.
Enter Test Name and Test Plan Name.
Create a Test or through Extension
To add data-driven to the Test, capture the data in an Excel sheet which will be parameterized.
Click on the Data-Driven table icon.
.Click the '+Choose' button >>then Browse for an excel/.xls File >> Click 'Open' in File Dialog >> Click the Upload button (Make sure we clicked the Upload button to upload the data).
After uploading, we can select the column as Value or Element and click "Submit."
Now Parameterize the values and elements accordingly, By Clicking on the 'Edit icon' of the test step.
Click on three dots near Field Value ,Select DDS Parameterization ,Select the Values or element accordingly
Click on Run icon and see the no. of iterations captured and uploaded on the Excel sheet.
Login to GTP as Test Manager/ Engineer.
Select the Project from Project drop down Menu.
Go to Test Page, click on Add new Test Button.
Create a Test with appropriate Tag.
Click on Test Name.
Click on Record Button. The GTP Web App with Extension will be launched.
Go to the step, where the Visual validation is to be added.
Click on Edit icon, and turn on Toggle for Visual validation. Click OK.
While recording the scenario -> Right Click-> Select GTP Context Menu-> Select Visual Testing -> Select Visual Assertions.
Eyes Check Window – Captures all the content in the browser or application window.
Eyes Check Element – Captures the image in a rectangular area defined by the element, which is provided as a parameter.
Eyes Set View Port Size – a visible area of an application within the application window. The viewport size can impact the layout of a page.
Eyes Set Match Timeout – Sets the timeout using theeyes set match timeout. This command takes as a parameter the timeout time in milliseconds.
Exact – pixel-to-pixel comparison.
Strict – Strict compares everything, including content (text), fonts, layout, colors, and position of each of the elements.
Content – Content works similarly to Strict except for the fact that it ignores colors.
Layout – Layout, as its name implies, compares the layouts (i.e., structure) of the baseline and actual images.
Once the Test is recorded, click on Save and Close Button.
Execute the Test to Capture the Base line Image.
Once the base line image is captured, user can re execute the Test to validate the Current Image with the Base line Image.
Any Change’s in the Current image will be highlighted.
If any Mismatch is found, it highlights the Visual changes with a pink highlight.
Viewing Test Results
You will now be taken to the Test Results page where you will see all the steps that were captured as a result of your interactions with the application. GoTestPro provides simple, accessible and easy to analyze reports.
Select the required project from the drop-down options.
Login as Test Manager/Test Engineer.
Select the required project from the drop-down options.
Navigate to the Test page >> Record Test >> click Save.
Then, navigate to the Execution menu.
Select Tag /Test in the Execute page for execution.
Click Execute Now button.
Update the Test Configuration Environment details >> click Update and navigate to the Results page.
User can also filter the Test result as per Test Plan/ Test Name / Run date and Run Status from the filter Button.
The user can view the Overall Results table with Test and Tag name, Run Date, Username, Execution Results Status, Scenario Status, Execution Total time, Platform, Browser name, Scheduled/ Manual indicator, and can view the Detailed Report link too.
Note: This is a basic test that can be recorded by interacting with your app. We will dive into more advanced capabilities in other tutorials or ping us for awesome support!
Practice in your account. If you don't have an account Try out!
Explore all available choices within the Extension feature. Give them a try!