Answer:
Tosca is an automation testing tool developed by Tricentis. It uses a model-based testing (MBT) approach, allowing testers to automate functional, regression, API, mobile, SAP, and web applications without extensive coding.
Answer:
Answer:
Model-Based Testing is a testing approach where test cases are created from application models instead of writing scripts. It reduces maintenance and improves reusability.
Answer:
The main components are:
Answer:
Tosca Commander is the main interface used to create, organize, execute, and manage automation test cases.
Answer:
A Workspace is the project repository where all Tosca objects such as modules, test cases, execution lists, and requirements are stored.
Answer:
The Tosca Scanner identifies application controls and creates reusable modules used in automation.
Answer:
A Module is a reusable object repository that stores application controls and properties required for test automation.
Answer:
A TestCase is a collection of test steps used to verify application functionality.
Answer:
TestSteps represent individual actions such as clicking buttons, entering text, or verifying values during test execution.
Answer:
TestCase Design is a feature used to create reusable business test data and automatically generate multiple test cases.
Answer:
Attributes represent input fields or business parameters like Username, Password, Product Name, etc.
Answer:
Instances are combinations of attribute values used to generate different test scenarios.
Answer:
TCP is used to configure dynamic values for test cases without modifying the original test case.
Answer:
Buffers temporarily store values during execution so they can be reused later.
Example:
{B[CustomerID]}Answer:
Business Parameterization allows the same test case to run with multiple data sets.
Answer:
A Reusable TestStep Block is a collection of reusable test steps that can be called from multiple test cases.
Answer:
ExecutionList contains one or more test cases scheduled for execution.
Answer:
Execution Entries represent individual test cases inside an ExecutionList.
Answer:
ScratchBook is used to execute test cases quickly without adding them to an ExecutionList.
Answer:
Recovery Scenarios automatically handle unexpected application errors during execution.
Answer:
Synchronization ensures that Tosca waits until an application is ready before performing the next action.
Answer:
Verification Points validate whether the actual result matches the expected result.
Answer:
ActionMode specifies the action to perform on a control.
Common ActionModes:
Answer:
Input ActionMode enters data into an application field.
Answer:
Verify ActionMode checks whether the actual value matches the expected value.
Answer:
Buffer ActionMode stores runtime values into buffers for later use.
Answer:
Constraint ActionMode searches for controls based on specified conditions before performing actions.
Answer:
Dynamic Expressions generate values dynamically during execution.
Examples:
{DATE}{TIME}{RANDOM}{TODAY}Answer:
Test Data Service (TDS) is Tosca’s centralized solution for managing and supplying test data across multiple test cases and environments.