This tutorial is made to help you learn the basics of creating tests with GoTestPro and help you create and execute your first test case for a sample web application - “Simply Travel”.
Prerequisites
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 support@gotestpro.com.
Chrome Extension/Plugin: The extension will automatically render/capture steps (in readable natural language) based on how you interact with the application under test. You can add GoTestPro’s extension from the Chrome webstore by visiting this link: https://chrome.google.com/webstore/detail/gotestpro/ldmfmccaoihffboppndecjpfldhamafn.
Basics of GoTestPro
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 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 used to group the tests, e.g., Sanity, Smoke, Regression, etc.
Tags are mandatory to have to perform the execution on the Cloud/Server side.
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 Record button at the top right to start recording your interactions.
You will see that a new window appears that will navigate you to the URL you just entered.
Note: Ensure you are updated with the latest Chrome Extension by navigating to Project Setting–> Chrome Extension setup.
At this point, you can begin executing the actions you intend to take within your web application. It's important to recognize that every click and keystroke you make will be documented as individual steps. The associated straightforward English tests will be generated automatically and appended beneath the initial step you have just established.
This step is required only in a QA/Dev environment until the GTP 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.
For inputting a value, simply click on any text field located within the form and proceed to type in a name (for instance, "John Doe"). The intelligent recorder will automatically capture both the input you've provided and its corresponding address.
Verify the statements manually through the assertion feature*. From the dropdown list, select ‘Verify that the current page displays test data’.
Once these foundational actions have been executed, it's essential to validate their success.
This is achieved by employing a verification statement, also known as an assertion in the context of test automation.
Click the ‘Stop Recording,’ scroll down, select ‘Application Name,’ then select ‘Script Name.’
Note: In QA/Dev Environment, we need to add the TEAF Recorder Extension to our Chrome Browser. The steps to follow are given below:
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 Manual Scenarios (Manually)
Login as Test Engineer.
Select a Project from the Select a Project drop-down (at the top left corner) list.
Click on the Test option from the Navigation menu.
Click on Add New Scenario.
Enter the Scenario Name and Scenario Tags, and select the Application type from a drop-down list.
To add Scenario steps >> Click on the Edit icon from the Actions column >> Select the needed values like Action, Elements Name, and Field Value, then click on the ‘Yes’ icon, and the steps will be saved.
Click the + icon to add more steps.
Select the application type from the Application type and choose the Save Scenario.
Creating Data Driven Scenarios
Select Project and navigate to the Test Page.
Click on the Add New Test button on the Test Page.
Enter Test Name and Tag Name.
Now Create a Test manually or through recording.
Execute the created Test to check the Result.
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. The ‘File Upload Pop-Up’ form will open.
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 & click “Submit.
Now Parameterize the values & elements accordingly.
Click on the ‘Edit’ step icon of the step.
Click on Execute icon & you can see the no. of iterations captured and uploaded on the Excel sheet.
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.
Navigate to the Test page >> Record Scenario >> click Save.
Then, navigate to the Run.
Select Tag (Script) in the Execute page for execution.
Click Execute Now.
Update the Test Configuration Environment details >> click Update and navigate to the Results.
The user can view the Overall Results table with Script& 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!
Validating Visually
Create a Project and Navigate to the Settings Page.
Clicks on the Settings page and select the Applitools Integration tab.
Enter the API key in the text field.
Navigate to the Tests Page and Create New Test
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 the eyes 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.
After adding the Visual Assertions, save the Scenario, and Execute it on Cloud Level.
Once the Execution is completed, click on the Visual Results from the Context Menu on the Result Detail Page.
It navigates to the Applitools page, and users can see the Visual images. First, executed results are considered as a baseline image.
Execute the same Test again at the Cloud level; that result image will compare with the baseline image.
10. If any Mismatch is found, it highlights the Visual changes with a pink highlight.
Next Steps…
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!
Generate Test Plans and set up a schedule. Click on this provided link!
Experiment with more sophisticated functionalities. Refer to our comprehensive documentation.
Contact us if any inquiries arise!
Add Comment