TOSCA SECTIONS

Tosca Commander consists of several sections, including the Module Section, Test Case Section, Test Case Design Section, Execution Section, Requirement Section, Issues Section, and Configuration Section, each serving a specific role in the testing process.

Module Section: The Module Section holds all the technical data. Modules are of two types:

• Standard Module: Standard modules are the ones provided by Tosca during installation.
• User-defined Module: User-defined modules are the modules created by the user on the SUP software under test.

Tosca modules are classified into two categories:

• Classic Modules: These are created by classic engines during the scanning process.
• XModules: These use XEngines, which are based on the Tosca TBox framework.

Without the module section, we cannot develop test cases, which would make manual test cases the only option.

Tosca Commander provides the flexibility to perform both manual and automation testing.

• Manual Testing: Yes, for manual testing, you can directly go to the Test Case Section and create a manual test case.
• Automation Testing: Yes, for automation testing, the test case depends on the module section. Without the module section, automation testing cannot continue.

Steps for Automation Testing:

First, create the module section based on the requirements using the scanning mechanism.

• There is no need to write XPath and CSSPath; this is not required.
• Tosca provides flexibility in scanning. First, scan and identify elements as unique and save the module.
• If any control is not unique, you can make it unique using the identification mechanism.

Test Case Section:

To create a new Test Case, follow these steps:

1. In Tosca Commander, go to the Test Case tab.
2. You can create a new Test Case in the main Test Cases folder or you can create a custom folder structure.
   1. To create a new folder, right-click the Test Cases folder and select Create Folder from the mini toolbar.

1. Testcase Design Section (TCD)

This is an approach to isolate the test data from the technical sections of test cases. So, the data and test cases are kept separately. The Tosca Test Case Design section has the capability to break our test cases into a logical structure. It also helps us to plan and design the test cases in an efficient and structured way to reduce development and maintenance efforts.

Use the Tosca Test Case Design section to perform the below activities:

1. Create the test sheets, which are a combination of all possible test cases for any scenario or template. Basically, test sheets hold data for different combinations.
2. The concept of classes in the test case design approach helps to reuse common data across the test cases, which reduces the efforts of data management.
   With the help of instances, we can create specific data for Test Sheets, TCD Attributes, or TCD classes.

1. Create Test Case Templates and assign the Test sheets.
2. We need to instantiate or re-instantiate Templates to generate the instance test cases as per the test sheets.
3. Manage test data in test sheets and execute the instance test cases.

Execution section:

1. In this section actually we executed our scripts, whatever scripts we have developed in testcase section we drag those testcases in to the execution section and we execute it
2. so the results will be saved here.

Executing Test Cases

Tricentis Tosca allows you to compile and run all finished Test Cases in Execution Lists. An Execution Entry is displayed for each Test Case. The outcomes of the execution and their history are automatically saved to a log file (Actual Log).
The Scratch Book method can be used to run individual Test Steps separately or check Test Cases that are not yet completed.

Execution Lists :

1. Use an Execution List to run your automobile test case.
2. In Tosca Commander, select the Execution tab.
3. Select Create Folder from the mini toolbar when right-clicking on the Execution List
4. You can use the dynamic menu Execution Lists to create a folder by left-clicking on the Execution List folder and selecting Create Folder.
5. Name the new Execution List folder My First Execution List.

Create Execution Entries:

You can construct Execution Entries in Tricentis Tosca by dragging and dropping Test Cases into the Execution List.

1. Select the Execution List folder from the right-click menu. Select Create Execution List from the small toolbar for “My First Execution List.”
2. You can select Create Object from the dynamic menu Execution Lists by left-clicking on the Execution List folder.
3. Give the new Execution List the name Vehicle Insurance.
4. Drag and drop your Vehicle Insurance Execution List onto your Automobile Test Case.
   The Execution Entry Automobile is automatically created and linked to the associated Test Case.

• Execute test cases in Scratch Book
• Execute test cases from the Execution List

Execute test cases in Scratch Book:
Tricentis advises using the Scratch Book for a dry run (to check the test case readiness) only, as the results do not get stored for future reference. You can also perform the execution of individual Test Steps.

Executing the test cases from the Execution List:
The Execution section provides the feature of selecting and preparing multiple Test Cases for execution. Execution performed in the Execution List will be available for future reference.

Requirement Section:

1. The Requirement Section means we will get the requirements of the use cases from the client.
2. Based on the requirements, we will start our testing.
3. This is risk-based testing requirements.

1. Issues section:

• We create issues when executing the test case if any issues or bugs are found during execution.
• Any bugs or errors that are found in a test case will be recorded.

2. Configuration Section:

We perform the required configurations here, such as during distributed execution, API configurations for performance testing or mobile testing, or when using TDS (Test Data Services). This is where all necessary configurations are made.