Test Automation
Test Modeller 101 Tutorials - Test Automation
Go back to the index at any time to see more of these Test Modeller 101 Tutorials.
5.1 Introduction to QuickStart (Framework) Tutorials (2mins 28secs) 5.2 Overlaying Test Automation (4mins 25secs) 5.3 Code Templates (2mins 03secs) 5.4 Custom Code Snippets (3mins 04secs) 5.5 Code Generation and Execution (3mins 45secs) 5.6 Test Plans and Scheduling (3mins 15secs) |
5.1 Introduction to QuickStart (Framework) Tutorials
Objectives
See an overview of our 5 main automation frameworks: Web, API, Mobile, Dynamics 365 and Mainframe.
Get started with the QuickStart Tutorials sign up for a 2-week TestModeller.io.
Access the QuickStart tutorials via the links in the description below.
In this Test Modeller 101 Tutorial, you’ll get an overview of the QuickStart frameworks for test automation available in Test Modeller. The aim of providing these frameworks in the tool is to get you quickly up and running with your test automation journey.
So, in the clip you'll see an overview of the 5 main automation frameworks and associated applications including: Web, API, Mobile, Dynamics 365 and Mainframe.
For the first of the QuickStart framework tutorials we have Java Selenium for Web Automation, followed by Java with REST-Assured for API Automation to push complex sets of data into various APIs, then an Appium library connected to SauceLabs or another device farm for Mobile Automation, followed by C-Sharp Selenium and web scanner plus EasyRepro action pack for building out models and processes, and finally Java with Jagacy Jar with a pre-defined action pack for 3270 Mainframe Automation.
To get started with the QuickStart Tutorials sign up for a 2-week TestModeller.io. You can access the QuickStart tutorials via these links:
Web Automation:
Create a Project https://www.youtube.com/watch?v=LUe7c...
Scan an Application https://www.youtube.com/watch?v=qa4_l...
Edit the Model https://www.youtube.com/watch?v=VzEfP...
Generate and Run Tests https://www.youtube.com/watch?v=yNoQP...
API Automation:
Create a Project https://www.youtube.com/watch?v=lxVK-DfQxJc
View and Create Modules https://www.youtube.com/watch?v=KGR27SsDgIs
Create a Model and Run Tests https://www.youtube.com/watch?v=aScaoASSQUA
Mobile Automation: (playlist) https://www.youtube.com/playlist?list...
Create a Project https://www.youtube.com/watch?v=zxHlW...
Configure a Connection https://www.youtube.com/watch?v=LPL4O...
Create and Edit a Model https://www.youtube.com/watch?v=e8riB...
Generate and Run Tests https://www.youtube.com/watch?v=09icQ...
Dynamics 365:
Here’s a link to how to use the UI Scanner which accelerates building out models: https://knowledge.curiositysoftware.i...
Mainframe Automation:
Get Started https://www.youtube.com/watch?v=BP-Sv...
Model out Combinations https://www.youtube.com/watch?v=-8TT0...
Generate and Run Tests https://www.youtube.com/watch?v=e6uU7...
Publish a Test Suite https://www.youtube.com/watch?v=y018v...
That's all for this Test Modeller 101 tutorial. Continue with section 5 on Test Automation for tutorials including: Overlaying Test Automation, Code Templates, Custom Code Snippets, Code Generation, and Test Plans and Scheduling.
5.2 Overlaying Test Automation
Objectives
Use QuickStart Web, based on Java Selenium.
Where best to overlay automation and the techniques for getting automation assets onto the model.
See an Automation Reference used on a waypoint ‘Open URL’.
See how to apply a Test Data Variable and its parameters.
Build a model from using assets imported via the Project Explorer pane.
See how to out automation manually in advance for taking an automation reference from a list.
In this Test Modeller 101 Tutorial on Overlaying Test Automation, you'll learn where best to overlay automation and the techniques for getting the automation assets onto the model and how this integrates with any automation framework. In this example we are using QuickStart Web, based on Java Selenium.
In the example model you’ll see that clicking on a waypoint ‘Open URL’ opens the Automation Reference. The block Enter Email you’ll notice this can take a Test Data Variable. The Test Data Variable comes from the model and is added as a parameter and parsed from the previous block with a Variable Assignment Invalid Email.
Building a model from scratch the assets are best imported via the Project Explorer pane. It should be noted that these can be scanned objects, imported objects or pre-defined action packs in Test Modeller and can include automation such as AssertURL, Enter Email and Click Signin Button etc.
Alternatively overlaying the automation manually is used on models built out in advance prior to knowing the actual automation. This is done through the Automation pane where you’ll Add an automation reference from a list. In the example this is from the Module titled WebGeneralActions from which the available functions at which point can also be defined by adding a parameter. To get a waypoint onto the canvas simply drag it from the Actions area of the screen and drop it on the model canvas.
That's all for this Test Modeller 101 tutorial, hopefully you’ll be more familiar with the principles are Overlaying Test Automation, which can be done as you build out a model or manually overlayed onto an existing model.
5.3 Code Templates
Objectives
Code Templates in relation to an automation framework.
Publish the generated automation assets to a CICD pipeline.
Use the Project Configuration wizard to select a pre-defined QuickStart framework.
Identify age Objects which generate classes.
Identify Test Case Templates which descriptively generates test scripts.
In this Test Modeller 101 Tutorial on Code Templates, you'll learn about their relation to an automation framework, and how templates allow you to define any code based language you want inside Test Modeller before publishing it to a Git repository, thus enabling you to publish the generated automation assets to a CICD pipeline.
In the example you’ll see the Project Configuration wizard of pre-defined frameworks, but alternatively there’s an option to get test Modeller to create and set-up your own code templates or which can be cloned from an existing repository, or if required you can also start from scratch.
A benefit in having Code Templates available in Test Modeller is that they are separated into Page Objects which generates classes, but also Test Case Templates which descriptively generates test scripts. Additionally, for easy navigate, keywords are displayed, and it’s worth reinforcing that these are all fully customisable to match any custom framework. In our example you see there’s C# Selenium, Cypress, Desktop Automation, Dynamics 365 and more.
That's all for this Test Modeller 101 tutorial. Hopefully you’ll have seen how to use Code Templates which are not only fully customisable, but can easily be cloned from existing repositories, created from scratch or set-up in Test Modeller’s pre-defined Project Configuration wizard, enabling you to publish the generated automation assets to a CICD pipeline.
5.4 Custom Code Snippets
Objectives
Use importers to quickly populate Test Modeller with automation and classes that may already exist.
See how Code Templates can also be directly imported from a Git repository, and Custom Code Snippets.
Identify a requirement for a Sleep or Wait function, better created as a custom function.
Use of the Code Editor where you’ll be able to paste any code for embedding in any models.
See that importers including Swagger Specification can be used to import and bring in specific code.
Import a zip file containing existing page objects.
In this Test Modeller 101 Tutorial on Custom Code Snippets, you'll learn how to how to use importers in Test Modeller to quickly populate Test Modeller with automation and classes that may already exist. As with being Code Templates also being able to be directly imported from a Git repository this is also the case for Custom Code Snippets. This pulls in any Objects and Functions from the connected repository and sets them up inside Test Modeller. Additionally UFT, Ranorex and Swagger repositories are all available in Test Modeller.
So, beyond importing Custom Code Snippets, and for instance if you have a requirement for a Sleep or Wait function it may be better created as a custom function. This gets added to your workspace. In the tutorial you’ll see these can be attributed as Abstract, Page Object, Pending Automation, Embedded Code, Custom Code and Function Map.
In the example a new Module Collection called Customer Code Snippets, using a pre-determined framework QuickStart Web Automation (remember this is based on Java Selenium). At this point you see New Functions are created, and remember at this point to add in the attributes including Object and Qualified Name and specific Function Type (listed above).
Using the Function Custom Code the example demonstrates the use of the Code Editor where you’ll be able to paste any code for embedding in any of the models. A series of importers including Swagger Specification can also be used to import and bring in specific code. And not forgetting the feature to import a zip file containing existing page objects, but also connecting to a Git repository.
That's all for this Test Modeller 101 tutorial. Hopefully seen the flexibility in which Customer Code Snippets can easily be imported and edited, and also the ease in which repositories can be pulled and utilised.
5.5 Code Generation and Execution
Objectives
Learn how a pre-built automation model can be used to create and run automation scripts.
Use the Run button in the Scenarios pane.
Use the Automation Code export in the Run wizard.
Refer to an automation model for a HR system and its Subprocesses.
Use Waypoint blocks to include automation such as Go to page and Positive Enter username.
Use advanced settings in the Scenarios pane and manage where and how to see results.
Identify Source Control which relates to whichever repository you’re committing to.
Identify Test Data either fetched from an external source like SQL Server database or an excel spreadsheet.
Execute a job using the web automation to see what’s Passed and what’s Failed.
Navigate to Workspace > Configuration to see pre-defined features including Directory (setting target machine), Command (for triggering a batch file).
In this Test Modeller 101 Tutorial on Code Generation and Execution you'll learn how a pre-built automation model can be used to create and run automation scripts and use the Run button in the Scenarios pane and you’ll use the Automation Code export in the Run wizard. At this point it’s notable to indicate this automation can be triggered by one of the QuickStart Automation frameworks available in Test Modeller or any framework you’ve chosen to set up yourself.
In the example you’ll see an automation model for a HR system also referring to a couple of Subprocesses. Within the many blocks which compose the model, specific waypoints seen here include automation such as Go to page and Positive Enter username. In the Scenarios pane on clicking the Run button a series of advanced settings give was of managing where and how to see the results of the automation.
The first two settings include Source Control which relates to whichever repository you’re committing to, then Test Data which is about deciding if you are fetching data from an external source like SQL Server database or an excel spreadsheet. The final two settings are more concerned with Executing and Publishing of the automation tests. Clicking Execute you see Test Modeller runs a job to execute the web automation. Here you see what’s Passed and what’s Failed.
The benefit of using the QuickStart framework is the execution settings are already set up. Should you be using a custom framework the three Min settings to consider are: Directory (target machine), Command (triggering a batch file) and Parameters. This is done under Workspace > Configuration. Once ready to configure the settings you’ll need to choose the relevant Code Template related to the automation framework. Once there you can set up the Directory, Command and Parameters, as well as set up a source control. Basically this is everything you need to come in and run automated test.
That's all for this Test Modeller 101 tutorial. Hopefully you’ve seen how Code Generation and Execution in Test Modeller can accelerate your test automation journey.
5.6 Test Plans and Scheduling
Objectives
Identify the benefits of Test Plans as part of a CICD pipeline where you can set up Regression Suites.
See how to set up and name a test suite for publishing.
Use the Publish tab for setting up Test Plans and Scheduling.
Identify Results Summary with further information which can be traced to a specific model (with preview link).
Identify how to run a test plan in isolation, and the option to just re-run failed test.
In this Test Modeller 101 Tutorial on Test Plan and Scheduling you'll see there’s two places to review tests. This is at one time at a model level in the Automation pane, but you can also the tests can be filtered and passed to the Test Modeller results portal for giving sequential oversight and summary of the Passed and Failed tests. And this is beneficial as part of a CICD pipeline where you can set up Regression Suites to run on a schedule inside of test Modeller. You’ll also see how to set up and name a test suite for publishing.
In the previous clip on Code Generation and Execution we saw the Source Control, Test Data and Execution tabs. As part of that same palette is the Publish tab. This Publish tab is crucial for setting up Test Plans and Scheduling. So to Publish a test suite regularly you’ll see it’s necessary to give the plan a name. This is done in the Test Plan tab.
In the example you’ll access the Tests tab from the main menu and this reveals a Results Summary with further information can be traced to a specific model (with preview link), and specific run (with preview link). The benefit of having a regular test plan scheduled is the ease of analysis of the runs. Finally, you may want to run the test plan in isolation, but also there’s an option to just re-run failed test.
That's all for this Test Modeller 101 tutorial. Hopefully you’ve seen the benefits of being able to both have test execution available at a model level but also as part of a summary in a scheduled test Plan.