Tosca Interview Questions and Answers 2025 | Tricentis | Part 4 - Scenario based Questions

TSka Interview Questions and Answers Part 4

Introduction to TSka Scenarios

• The video introduces the topic of TSka interview questions and answers, specifically focusing on scenario-based questions that are increasingly requested by interviewers.

• Previous parts of the series (1, 2, and 3) are mentioned as foundational content for understanding the current discussion.

• Emphasis is placed on assessing not just theoretical knowledge but practical problem-solving skills in real project scenarios.

Question 1: Taking Screenshots on Test Case Failure

• The first question addresses how to take a screenshot every time a test case fails, combining two different scenarios into one solution.

• A standard module called "T-box take screenshot" is introduced as a method for capturing screenshots during test execution.

• The importance of identifying when a test case fails is highlighted; this can be managed through a cleanup scenario that executes before moving to the next test case.

• By integrating the screenshot function within the cleanup process, it ensures that screenshots are taken only when failures occur due to various reasons like dialog or verification failures.

• A practical example illustrates how to set up this process in an application environment, ensuring efficient handling of failed test cases.

Question 2: Extracting Order ID from Success Message

• The second question focuses on extracting an order ID from a success message after an order has been placed successfully.

• Understanding whether the text is treated as a single object or separate objects is crucial for determining how to extract data effectively.

• If separate objects exist for "order placed" and "order ID," creating distinct modules for each allows for straightforward extraction using buffers.

Understanding Object Identification in Testing

Identifying Complete Text Objects

• The challenge arises when developers define complete text as a single object, such as "order placed. order id: 766592." This necessitates creating a module to identify the entire object.

Methods for Verification

• Two practical methods exist for verifying these objects, with the first method being preferred. After identifying the object, it is dragged into the test case for verification.

Dynamic Value Handling

• The verification process involves checking if the inner or outer text matches a specific format (e.g., "order placed. order id: [dynamic number]"). The dynamic nature of this value requires special handling.

Utilizing XBuffer for Dynamic Values

• By using an XBuffer option alongside verify action mode, testers can instruct tools to verify static text while dynamically buffering changing values (e.g., order IDs).

Best Practices in Interview Responses

• When discussing methods in interviews, it's beneficial to present multiple solutions to demonstrate hands-on experience and problem-solving capabilities.

Exploring Partial Buffering Techniques

Trimming Values with Partial Buffering

• An alternative method involves using partial buffering to trim values from identified objects. This allows testers to specify which part of the string they want to retain.

Implementation of Partial Buffering

• Testers can apply partial buffer techniques by defining start and end points within a string (e.g., trimming from character 24 to 29), storing results in a new buffer.

Limitations of Static vs. Dynamic Approaches

• While partial buffering is effective, it may lead to complications if input strings vary significantly or exceed expected lengths. Thus, dynamic approaches are often preferred due to their flexibility.

Data Manipulation in Excel Workbooks

Reading and Writing Data Across Sheets

• It is possible to read data from one sheet and write it into another within a single test case using Excel workbooks, specifically through defined ranges.

Handling Multiple Sheets Within One Test Case

• To manage multiple sheets effectively within one test case, testers must open the workbook and define separate ranges for each sheet involved in the operation.

Example Application of Range Definitions

Defining Ranges in Excel

Overview of Ranges

• The speaker defines a range named R1 for personal information, spanning from A1 to H15 in the first sheet.

• A second range, R2, is introduced for salary data on another sheet within the same workbook. The specific ranges can differ between sheets.

Range Manipulation

• The speaker emphasizes that both R1 and R2 can be utilized for range manipulation in Excel, which is straightforward.

• It’s important to use the latest version terminology when discussing range manipulation to demonstrate up-to-date knowledge.

Understanding Tbox Start Program

Importance and Usage

• The Tbox start program is underutilized by newcomers but holds significant importance in launching or closing non-UI applications.

• This tool is essential for handling applications like command prompts that lack a graphical interface.

Practical Examples

• To launch an application using Tbox, you provide the path; this includes starting programs like command prompts where scanning requires special tools (e.g., Vision AI).

• Another key function of Tbox is managing browser options, such as closing specific tabs or instances of browsers effectively.

Deleting Cell Values in Excel

Deleting Specific Cell Values

• The discussion shifts to deleting values from specific cells, focusing on removing data from the "location" column in row four.

How to Manipulate Excel Cells and Handle Timer-Based Popups

Excel Cell Manipulation

• The process begins by opening an Excel workbook and defining a specific range, referred to as R1. The focus is on the fourth row and a designated column location.

• It is crucial to input an empty cell rather than using incorrect notations like flower brackets, which would result in unintended values being entered into the sheet.

• After passing the empty value, saving the workbook is essential; otherwise, changes won't be retained, particularly for deleting specific cells or columns.

• This method of manipulating cells can be useful in various projects where clearing or modifying cell content is necessary.

Handling Timer-Based Popups

• A common challenge arises with timer-based popups that appear briefly (2-3 seconds), making them difficult to capture for verification purposes.

• To address this issue, one must identify how to scan the page effectively before the popup disappears after triggering an event (e.g., clicking a button).

• An example scenario involves adding a product to a shopping cart, which triggers a popup indicating success but vanishes quickly.

• Inspecting the properties of the object that triggers the popup allows for better understanding and preparation for capturing it during its brief appearance.

How to Handle Timed Pop-Ups and Excel Row Iteration

Handling Timed Pop-Ups

• Refreshing the page can remove pop-ups, but this method may not always be effective. Different strategies exist for managing pop-ups in various applications.

• Introducing timers (e.g., 10 or 15 seconds) within HTML code can control when a pop-up disappears. The next option will remain until the timer completes.

• There are programmatic methods to handle pop-ups, including freezing the browser to scan modules and identify objects. This is a straightforward approach that may not work in every scenario.

• When addressing timed pop-ups that appear briefly (2-3 seconds), it's essential to explain scenarios and provide examples for clarity.

Identifying Total Rows in an Excel Sheet

Understanding Requirements

• The question of how to identify total rows in an Excel sheet reflects one's understanding of requirements and module usage, showcasing framework handling skills.

Practical Application

• In real-world scenarios, such as generating credit card reports from client-provided lists, knowing the number of rows is crucial for automation testing iterations.

• Various methods exist for counting rows: using row count functions or loops until an empty value indicates the last data line.

Best Practices

• After opening an Excel workbook, define a range and navigate to the last content row. This allows you to determine how many rows contain data effectively.

• By accessing properties like "row number," you can store this information into a buffer (total_rows_b), which holds the total count of rows present in the sheet.

Iteration Process

• Utilize iteration techniques (for loop, while loop, do while loop). Set up counters based on total rows identified earlier for processing each row without manual calculations.

How to Handle Row Counts and Browser Execution in Test Cases

Understanding Row Counts

• The row count is dependent on the defined range; for example, if the range is set to Z100, the row count will return 100, which does not represent the total number of rows but rather the specified range.

• Identifying total rows can be used as an iteration method in test cases.

Executing Steps Across Multiple Browsers

• A question arises about executing different steps of a test case in different browsers (e.g., first three steps in Chrome and next three in Edge).

• The solution involves configuring each test case with a browser variable that allows dynamic assignment during execution.

• By using a placeholder for the browser value (e.g., B), you can specify which browser to use without hardcoding it into the test case.

• For instance, setting browser B to Chrome will execute initial steps in Chrome, while changing it to Edge will run subsequent steps there.

• This approach is flexible enough to apply across multiple test cases, allowing different browsers for various scenarios.

Refreshing Web Application Pages

Importance of Page Refresh

• Refreshing a web application page may be necessary to load calculated objects or correct any loading issues encountered previously.

Methods for Refreshing Pages

• One effective method is sending function key F5 using Tbox's send keys module. This simulates a refresh action within the application.

• In older versions of Tbox, double quotes are required around function keys like F5 due to limitations in handling functions directly; newer versions do not require this workaround.

• It's crucial to consider wait times before and after refreshing since loading may take time post-refresh.

How to Scan Applications and Group Test Cases

Scanning Applications

• To scan an application, right-click on it and select "scan." A pop-up will display all applications present on your laptop.

• When scanning in the Chrome browser, right-click to access options such as HTML, UIA, and non-UI. Generally, HTML is selected for web applications.

• Change the option to UIA before clicking "scan" to analyze the entire browser interface including buttons and settings.

• The scan identifies various elements of the browser, allowing you to use objects like "reload" in test cases for refreshing pages.

Grouping Test Cases in Execution List

• The discussion shifts towards how to group test cases effectively within an execution list, emphasizing architectural skills beyond mere test case creation.

• It’s crucial not only to create but also execute test cases multiple times in a scratchbook before moving them into the execution list for reliability checks.

• After successful execution in scratchbook, drag and drop test cases into the execution list; this step is vital for ensuring technical accuracy.

• Before scheduling tests on platforms like Jenkins or Azure, ensure that they have been executed multiple times; this history may be requested by administrators for verification.

Structuring Test Cases

• Test cases can be grouped based on two main categories: releases (aligned with sprint methodologies) and types of testing (functional vs. regression).

• In agile environments with sprints every two weeks, organize folders by release cycles (e.g., Release 1 Sprint 1).

• Differentiate between types of testing within your folder structure; not all test cases need executing across all testing types (regression, smoke, UAT).

Understanding Functional and Regression Testing in Software Development

Overview of Testing Types

• The discussion begins with the relationship between functional automation testing and regression testing, emphasizing that regression testing follows functional tests. Key areas for regression include login, cart functionality, registration, and order maintenance.

• It is highlighted that within releases, different types of testing must be prioritized. Generally, functional testing aligns with releases and sprints while regression testing focuses on specific folder structures like login and cart.

Project Dependencies in Testing

• The speaker notes that there is no one-size-fits-all approach to structuring tests; it depends on project deadlines, scope, and strategy. This flexibility allows teams to adapt their testing processes based on specific project needs.

• An example structure is provided where projects can be organized by release or sprint phases. However, the speaker reiterates that this structure is not standardized but rather a suggested method depending on planning.

Interview Preparation Insights

• The speaker introduces ten questions designed to aid both interviews and practical project scenarios. These questions are intended to demonstrate a candidate's understanding of concepts through real-world applications rather than mere theoretical knowledge.

• Emphasis is placed on the importance of articulating experiences during interviews effectively. Candidates should convey their problem-solving skills through examples rather than simply stating they have faced challenges.

Training Opportunities

• A final note invites viewers interested in training programs to reach out via email for more information regarding course content (TOC), financial details, and support offered.