Does Tosca require programming?

Tosca is designed for building tests without writing code, using scanned Modules and configurable steps. Understanding test design and the application is still essential.

What is the benefit of keeping Modules and test data separate?

Reuse and maintenance. The same Module can be used in many TestCases with different data, and if the application changes you update the Module once.

Tricentis Tosca Introduction: Model-Based Test Automation

Introduction

Tricentis Tosca is an enterprise test automation tool built on a model-based approach: technical details about the application are stored separately from the test data and logic. That makes tests reusable and easier to maintain. This first lesson of the Tosca course introduces the idea and the objects you will work with in Tosca Commander.

Prerequisites

Basic software testing knowledge
Access to a Tosca installation or trial if you want to follow along

Step-by-Step Guide

Step 1: Understand model-based automation

In Tosca, the technical information needed to find and operate controls is kept in Modules. Test data lives in the TestCases. Because the two are separate, one Module can serve many TestCases, and a change to the application is fixed in the Module rather than in every test.

Step 2: Learn the key objects

A Module holds the technical information for a part of the application. A TestCase is an ordered set of TestSteps, and each TestStep uses a Module together with the values and ActionModes you choose. An ExecutionList collects TestCases to run in a specified order, and each TestCase added becomes an ExecutionEntry.

Step 3: Find your way around Tosca Commander

Tosca Commander is the main workspace for designing and running tests. It is organized into sections for creating Modules, building TestCases, designing test data, and executing tests. The exact layout depends on your Tosca version.

Step 4: Know the product variants

Tosca Commander is the established desktop client. Tricentis also offers Tosca Cloud, which uses related concepts with some different names and workflows. This course uses Tosca Commander terminology and points out differences where they matter.

Step 5: Follow the typical workflow

The usual flow is: scan the application to create Modules, build TestCases from those Modules, add test data and dynamic values, organize reusable steps, collect TestCases into ExecutionLists, run them, and review the results. The following lessons take each step in turn.

FAQs

Does Tosca require programming?: Tosca is designed for building tests without writing code, using scanned Modules and configurable steps. Understanding test design and the application is still essential.
What is the benefit of keeping Modules and test data separate?: Reuse and maintenance. The same Module can be used in many TestCases with different data, and if the application changes you update the Module once.

Summary

Tosca keeps technical control information in Modules and test logic and data in TestCases, which are run through ExecutionLists. Next you will learn how to create Modules by scanning an application.