What is the difference between a Module and a TestStep?

A Module stores the technical information for controls. A TestStep applies a Module in a TestCase with the specific values and actions for that test.

Are ScratchBook results saved?

No. The ScratchBook is for trial runs, and results do not persist. Use an ExecutionList to record official results.

Creating Tosca TestCases and TestSteps

Introduction

With Modules in place you can build tests. A TestCase in Tosca is an ordered set of TestSteps, and each TestStep applies a Module to the application with specific values. This lesson shows how to assemble one and check it works.

Prerequisites

Modules created by scanning an application
Familiarity with Tosca Commander's layout

Step-by-Step Guide

Step 1: Create a TestCase

Create a TestCase in a sensible folder structure, named for the behavior it checks, such as Login with valid user. Organize TestCases by feature or area from the start; it is much easier than reorganizing later.

Step 2: Add TestSteps from Modules

Add a TestStep for each part of the flow by using the Modules you created. Each TestStep references a Module, so the technical information stays in one place and the TestStep only holds what is specific to this test.

Step 3: Enter values for each control

For every control in a TestStep you choose what to do with it and the value to use. For example, enter a username and password and click the sign-in button. Keep test data in the TestCase and the technical information in the Module.

Step 4: Try it in the ScratchBook

The ScratchBook is meant for quick trial runs while you build a test. Tricentis recommends it for trial runs only, because its results are not kept. Use it to confirm your steps work before putting the TestCase into an ExecutionList.

Step 5: Keep TestCases focused

Each TestCase should verify one clear behavior and be able to run independently. Add verification steps at the points where the application should show a specific result, not only at the end.

FAQs

What is the difference between a Module and a TestStep?: A Module stores the technical information for controls. A TestStep applies a Module in a TestCase with the specific values and actions for that test.
Are ScratchBook results saved?: No. The ScratchBook is for trial runs, and results do not persist. Use an ExecutionList to record official results.

Summary

Build TestCases from TestSteps that reuse Modules, keep values in the TestCase, try them in the ScratchBook, and keep each test focused on one behavior.