Master TOSCA – The Future of Test Automation

• Tosca Commander
• Tosca Executor
• Tosca CI
• Tosca Wizard

• Introduction to Automation Testing
• Various Automation Testing Tools
• Pros and Cons of automation testing

• Introduction to Tosca
• Comparing Pros and Cons with other tools
• Working with Tosca Automation Tool Testing Syntax
• Reading Tosca Automation Tool Testing Data Sets
• Tosca Installation Process
• Tosca Installation Process
• Architecture of Tosca

• Actions/Sections – Requirements
• Modules
• Test Cases
• Execution List
• Test Case Design
• Check-in, check out and Update all

• Single Repo
• Shared Repo
1. SQLITE
• MS SQL Server
• DB2 .
• Oracle

• Tbox
• Classic

• Tbox Engine
• Classic Engine
• How to Recognition

• XSCAN
• Steer Controls Uniquely
1. Basic View
2. Advance View

• Identify by own properties
• Identify by Anchor
• Identify by Image
• Identify by Index
• Xpath

• How to launch browser And Desktop applications
• Different Approaches
• How to launch private browsers

• What is TCP
• Where we need to declare this parameter
• What is the use of TCP
• Difference between TCP and Business parameter

• Buffer Operations – Setting buffer
• Deleting buffer
• Partial buffer
• Expression evaluator
• Process Operations
• Window Operations – Send Keys, Window Operations

• Wait On
• Default Settings
• Static Wait

• Minimize & Maximize Browsers
• Take screenshot
• Send keys
• Dialog
• Clipboard
• Scrolling behavior
• Save As

• Create Word document for screenshots

• Buffers
• Partial buffers
• Dynamic buffers

• Explicit Name
• Constraint Index
• Constraint Index

• Date
• Time
• Random Number
• Random Text
• Random Regular Expressions
• Month
• Day
• Regular Expressions

• Reusable Test step block
• Library
• Business parameter

• If Condition and Else
• While
• Do
• Repetition

• MATH( )
• CALC( )

• How to handle Web tables
• Implementations of Web Tosca
• Scanning & Development
• Real time Example

• Excel Operations
• Read and write operations
• Real-time Example

• Click 7
• Percentile
• Pixel method
• JUMP
• Horizontal First
• Vertical First

• What is recovery scenario
• What is Clean up scenario
• Where we need to declare
• Global settings
• Recovery Scenario declaration

• TC Shell Operations
• Create workspace
• Drag and drop activities
• Login to applications
• Execution
• How to take reports in Tosca

• Creating and Using Libraries
• Examples

• Clean Up Scenario

• Creation of Execution set
• Linking the Test Cases to execution set
• Test execution results
• Examples

• What is web service
• What is API Testing
• Create Request
• Create Response

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.

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.

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.

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.

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.

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.

Linking Tosca test cases with requirements ensures test coverage based on requirements, providing a high-level overview of requirement coverage for test analysis.