Test Modeller is a flow-driven model-based tool that provides accelerators and connectors to quickly build flowcharts. It has importers for existing requirements and test cases, as well as recordings and scans of already built systems. This tutorial covers adding projects and releases, example models for QuickStart frameworks, creating your first model, and managing existing projects. Projects can include models, page collections, module collections, test data variables etc. Releases are used to commit changes when requirements or test data needs to be changed.
2.1 Projects and Releases
In this Test Modeller 101 Tutorial, we quickly look at adding Projects, moving towards automated testing. You’ll also see the individual panels for Project and Releases where you can create, but also modify settings, commit changes and switch contexts between releases.
You’ll see the set-up of a project using one of Test Modeller’s automation frameworks, in this instance, QuickStart Web Automation. And the asset types available in a Test Modeller project include models, but also Page Collections, which can also be linked to Module Collections.
Using releases is a powerful way to commit changes, for instance you may create a release for a particular model (flow) if the requirements have changed, or test data needs to be switched up. Releases get sequentially labelled as v1.01, v1.02 and so on.
The example picks off test data for an email, showing you where to alter test data in the Variables tab of the Test Data pane. Saving this out as a new release means you can review the old data and identify changes. To save a Model as a new version, simply go to File and Save; then select New Version, add a commit message.
2.2 Example Models for QuickStart Frameworks
In this Test Modeller 101 Tutorial, you'll see the example projects related to the main QuickStart automation frameworks that accelerate getting started in Test Modeller. The common benefit of going through these project examples is seeing how to generate test cases and execute automation without any external configuration.
The project example for Web Automation gets you familiar with a Model showing logic from a Login page including valid and invalid username and password combinations. Our API Automation project teaches you about chaining an API. And there’s also a QuickStart Mainframe project to try out.
For the Mobile Automation example project you’ll see how to establish a connection in models built out for both Appium but also SauceLabs connections, and additionally see models for a shopping app on mobile plus also native. Following that there’s also a SwaggerLabs app model which uses smaller components where you’ll load a device, check in and check out.
2.3 Creating Your First Model
In this Test Modeller 101 Tutorial on modelling out an existing system or requirement, you'll learn about the blocks that compose a flow in Test Modeller. It’s useful to start modelling on the canvas by adding one start and two end blocks, labelling them Authenticated and the other Not Authenticated.
In the example, you’ll build out a Model using the logic for an authentication system, i.e. valid username and password or alternative invalid username and password, or other edge cases including a mix of both invalid and valid.
You’ll use condition blocks which help to visualise forks in a path or decisions that need to be considered in a flow, which then connect to respective task blocks. These decisions could be made by a system or a user.