Design and manage your test case

You have an empty test case, and you have modules that you created by scanning. So far, so good!

If you haven't yet, check out our best practices for test case content to learn golden rules for creating useful test cases.

If your workspace is linked to a qTest project, converted qTest test cases also appear in your inventory. These come with specific restrictions, so it's worth checking them before you start.

Once you're ready to start building an automated test sequence, add these elements, also referred to as assets, to your test case:

Modules, which are the technical representations of parts of your application in Tosca Cloud. They help you define how Tosca Cloud interacts with your application at runtime.

You can use modules you created by scanning, or you can use standard modules. Standard modules are pre-built modules for common tasks that Tosca Cloud provides out of the box.
Reusable test steps, which are steps that you maintain in a central location and reuse in multiple test cases. They help you reduce test maintenance effort.
Logic elements, which are elements that add structure to your test case: groups and if statements. They help you keep your test cases easy to read and allow you to design dynamic test sequences for specific conditions or criteria.
Parameters, which let you define a value once and reuse it across your test cases, playlists, workspaces, and tenant. They reduce repetition, keep values consistent, and lower maintenance effort.
Test step folders, which are organizational elements in your test case. They help make even complex test flows easy to read, understand, and work with. To add a folder, go to Standard objects > Structural objects > Test step folder and add the folder to your test case. Then drag and drop test steps into the folder.

You can also use shared assets from other workspaces in your tenant. If an admin has shared a workspace as an asset library, you can use all the assets from that workspace directly in your test case without rebuilding them from scratch. You can find all design elements in the test case editor. To access the test case editor, go to Test cases and select your test case.

Test case editor

Manage your assets

The left menu bar gives you a single place to access all your assets. From there, you can manage them throughout their complete life cycle: create, review, maintain, and delete them.

This table explains what's available in each section:

Section in the menu bar	Description
Prepare	Everything related to planning and designing tests. For example, test data, test sheets, and business flows.
Build	Everything in your inventory related to building tests. For example, test cases, modules, and reusable test steps. In addition to managing these assets, you can also track the following: Provenance. Use the columns or an asset's details view in Build > Assets to review key activity details. For example, who created an asset or last updated it. Revisions. Use the revision history to track changes and restore previous revisions.
Run	Everything related to running tests. For example, playlists, agents, and results.
Configurations	Everything related to configuring tests and setting up connections. For example, test parameters, mobile connections, and connections to databases.
API Simulations	Everything related to simulating services.