1. Explain about Tricentis Tosca?
Tricentis Tosca stands out as a leading test automation tool in the market, showcasing the
capability to automate diverse application types. This tool facilitates the creation of script-less
automated tests, contributing to its effectiveness. Key attributes of Tosca include:
Swift execution and compatibility with a Continuous Testing approach, aligning with
DevOps practices.
Emphasis on module-based test development, optimizing reusability for efficient testing
processes.
Demands minimal maintenance efforts, enhancing overall operational efficiency.
Seamless integration with major third-party tools, bolstering its adaptability and
compatibility.
Simplified test development through script-less automation, ensuring ease of use for testers.
2. What are the major components of Tosca?
The important components which are available in Tosca are –
Tosca Commander.
Tosca Executor.
Tosca ARA (Automation Recording Assistant)
Tosca Wizard
Test Repository.
3. Explain the advantages of Tosca as a test automation tool?
The benefits provided by the Tosca automation tool are mentioned below
One tool combines many features.
Supports script-less test automation.
Test management.
Bulk updates are possible.
Assets can be reused.
Compatible with different platforms.
It follows a model-based testing approach.
4. Define TOSCA Commander?
TOSCA Commander serves as the user interface of the tool, enabling users to design, maintain,
execute, and analyze test cases. It is the foundational component of the Tosca Test Suite,
structured with various sections such as Requirements, Modules, Test Case, Test Script Design,
Execution, and Reporting.
5. How to execute test scripts from Tosca ExecutionLists?
Executing test scripts in Tosca can be accomplished through different approaches
Initiating execution using the shortcut key F6.
Right-clicking on selected test cases and choosing the “Run” option.
Running the ExecutionLists.
6. What are the different types of components available in TOSCA?
TOSCA comprises four key components:
Tosca Commander
Tosca Executor
Tosca Wizard
Test Repository
7. How to execute test scripts from Tosca ScratchBook?
To perform trial runs or check correctness, Tosca allows the execution of test cases from
ScratchBook. Two options are available for executing test cases from ScratchBook:
Execution at any time.
Organizing test cases in ScratchBook before execution.
8. Is it possible to integrate Tosca with Jira?
Yes, integration with Jira is possible. Jira serves as a test management tool, managing bugs or
issues raised in Tosca. Any new issues raised in Tosca can be synchronized with Jira through
the interface.
9. Explain the benefits of Tosca integration with Jira?
The advantages of integrating Tosca with Jira include:
Synchronizing failed tests from Tosca.
Automatic raising of bugs in Jira after Tosca execution failure.
Enabling the DevOps process.
Achieving cross-tool traceability.
10. What are the different types of errors that can occur in Tosca?
Three types of errors may occur during Tosca execution:
Verification Failure: This occurs when expected and actual results do not match for the
verification step.
User Abort: Occurs when the execution is stopped by the tester.
Dialog Failure: Occurs due to unhandled exceptions or steps.
11. Explain Tosca TestSuite?
Tosca is a leading test automation tool capable of automating various applications, allowing
the design of script-less automated tests. Key features include fast execution, support for
module-based test development, minimal maintenance efforts, integration with major third-
party tools, and easy test development through script-less automation.
12. How can you read data from Excel using Tosca?
Data from Excel can be read using Tosca through two approaches:
In Test Case Design, data can be read from an external Excel file with a predefined format.
The “Excel Engine” allows importing and reading from an Excel file.
13. Is it possible to launch multiple browsers in TOSCA?
Launching multiple browsers directly in Tosca is not possible. However, users can achieve
cross-browser execution by defining a Test Case Parameter named “Browser” and selecting
values like InternetExplorer, Firefox, or Chrome.
14. Explain how to perform data-driven testing in Tosca?
Data-driven testing in Tosca is facilitated through the Test Case Design (TCD) approach. The
TCD test sheet represents a template where instances are created to represent test data for
individual test cases. Data parameters are linked to attributes within the test sheet, allowing for
data reusability and the creation of test cases based on different data sets.
15. How to initiate cross-browser execution in Tricentis TOSCA?
Launching multiple browsers simultaneously is not supported in TOSCA. However, users can
achieve cross-browser execution by following these steps:
Design a Test Configuration Parameter named “Browser” at either the TestCase or its Parent
Levels.
Users can select values such as InternetExplorer, Firefox, or Chrome for the “Browser”
parameter.
Executions will be triggered separately for each selected browser.
16. What are the different types of status available after post-execution in Tosca?
After test execution in Tosca, the available default statuses are
Passed
Failed
No result
Error
17. Explain the limitations of TOSCA ScratchBook?
TOSCA ScratchBook stores temporary execution logs and is used for temporary execution
during test development. Limitations include the lack of details for repeated actions within a
test step and the non-permanent availability of execution logs.
18. Explain the benefits of linking Tosca test cases with requirements?
Linking Tosca test cases with requirements ensures test coverage based on requirements,
providing a high-level overview of requirement coverage for test analysis.
19. Explain Test Data Management?
Test Data Management in Tosca involves handling the test data required for test execution.
Data-driven test automation is achieved through Test Case Design (TCD), where test sheets
represent templates with instances representing test data for individual test cases.
20. What are String Operations in Tosca?
String Operations in Tosca involve verifying or changing strings using regular expressions.
These operations can count specific characters/words, align words, confirm number structure,
etc. The execution of String Operations requires the AidPack module.
21. Why is ScratchBook required in Tricentis TOSCA?
ScratchBook in TOSCA allows for trial runs of newly created or enhanced test cases to check
correctness. It logs execution results temporarily and enables the execution of entire or partial
test cases (test steps) for verification.
22. What is exploratory testing in Tosca?
Exploratory testing in Tosca involves manually recording test scenarios while navigating,
capturing screenshots with technical information, and generating a PDF document. This
document serves as a reference and training material for future use.
23. What is the purpose of Tosca Query Language (TQL)?
TQL, short for Tosca Query Language, serves as an advanced search tool in Tosca. Similar to
SQL, it enables users to perform searches based on specified conditions.
24. Is it possible to compare PDFs using Tricentis Tosca?
Tricentis Tosca includes a standard module that allows users to compare PDF files. After the
comparison, any mismatches are documented in the execution logs.
25. What is Tosca WebAccess?
Tosca WebAccess is a web interface that allows users to access workspaces through web
browsers without requiring the installation of Tricentis Tosca Commander. The data of
workspaces is stored on the workspace server system, and users can access it using client
browsers.
26. What types of logs are available in Tosca?
Tosca provides two types of logs after test execution:
ActualLog: Stores the latest execution results and the execution history.
ExecutionLog: Generated by selecting the option “Archive actual ExecutionLog.” This type
of log provides additional information.
27. Examine the steps involved in manually creating test case templates in Tosca?
To create TestCase templates in Tosca, users can follow these steps:
Create a TestCase based on user requirements.
Convert a technical test case into a template by selecting the “Convert to Template” option
from the context menu after right-clicking on the test case.
Drag and drop the appropriate TestSheet onto the desired TestCase Template.
Assign TestSheet attributes (data parameters) for the required TestStepValues using the XL
tag.
28. Explain the merits of Tricentis Tosca?
The primary advantages of Tosca as a test automation tool are outlined below:
Supports a script-less test automation approach.
Easy to learn with a minimal skill set.
Allows the initiation of test automation in the early testing phases.
Supports the model-based test automation framework, eliminating the need for extensive
test framework creation efforts.
Facilitates a high level of reusability through components such as Modules, Reusable
TestStepBlock, TCD, etc.
Provides built-in support for test management and functional testing activities.
Enables ALM integration.
Allows the triggering of Selenium test cases from Tosca.
Facilitates mass updates using Tosca Query Language (TQL).
29. Is API Testing possible with Tosca?
Yes, Tosca supports API Testing. The API Scan feature is utilized to create modules
corresponding to APIs, enabling the sending of requests and receiving responses for API calls
30. What is TOSCA Classic Engine?
The TOSCA Classic Engine, also known as the Base engine, is responsible for test execution.
It follows the architecture of test cases managed as business-based objects, accepting
information and activities related to test scripts.
31. Discuss Tosca Model-Based Testing?
Tosca Model-Based Testing involves creating models that represent the functionalities by
scanning the application. Test cases are then developed and executed based on these modules.
Modules, containing technical information, are added to test cases through a drag-and-drop
approach, requiring no scripting for test case development.
32. How to run Tests using ScratchBook?
To run tests using ScratchBook in Tosca, users can perform trial runs of newly created or
enhanced test cases to ensure correctness. Execution results are logged in ScratchBook
temporarily, and entire or partial test cases (test steps) can be executed by right-clicking on
selected items and choosing the “Execute” option from the context menu.
