Tosca Interview Questions and Answers

Last updated on Nov 24, 2023

Tricentis Tosca (Topology and Orchestration Specification for Cloud Applications) is among the top testing tools available in the market right now. Over time, it has evolved as a big competitor in the field of automation tools. So landing a job as a Tosca expert will guarantee you a promising career.
In this post, we will be discussing Tosca Interview Questions for those who are aiming to grab a good job opportunity Beginners, Experianced. These questions are gathered after conferring with professionals and after analyzing data collected from several interviews held for the Tosca job position. Make sure to take a look at the below frequently asked questions and answers to gain confidence before you attend an interview (or) just go through them to enhance your learning curve.

Now let's have a look into the tosca interview questions for beginners and experienced in detail.

Most Frequently Asked Tosca Automation Interview Questions and Answers

Tosca interview questions and answers for beginners

1. What is Tosca Testsuite?

Ans: Tosca Testsuite, created by Tricentis Technology and Consulting GmbH, is a sophisticated testing tool primarily developed using C#, with Java and VB6 also contributing to its creation. It's extensively utilized for comprehensive functional and regression testing of software products, with notable adoption by major firms such as Allianz, Toyota, Starbucks, BMW, HBO, and Whole Foods.

                                    Take your career to next level in Tosca with HKR.Join Tosca Training Hyderabad now.

2. What is TCShell?

Ans: TCShell, an integral part of Tosca Commander, offers command-line control. It operates in two modes: Interactive mode, providing a user-friendly GUI, and Script mode, where users execute pre-written command scripts with limited control.

3. What is the use of Tosca Qc/Alm integration?

Ans: Integrating HP Quality Center with Tosca allows seamless creation, updating, and storage of Tosca test cases in ALM, with test execution results also visible within HP ALM, enhancing efficiency and traceability.

4. What are the loops available in Tosca?

Ans: Tosca offers two types of loops: Incremental Loops, executed a predetermined number of times, and Dynamic Loops, which run until a specific condition is met, akin to do-while or while loops.

5. What are the advantages of Tosca Testsuite?

Ans: Tosca Testsuite's benefits include intuitive drag-and-drop functionality, scriptless automation capability, model-based automation, a user-friendly GUI, asset reusability, and notably reduced regression testing time.

6. What is the methodology that the Tosca tool is based on?

Ans: Business parameters in Tosca are customizable values for test cases, including XML elements, JSON data, headers, settings, and response details. These can be manually set within modules and are adjustable if payloads change.

7. Define business parameters in Tosca?

Ans:  Business parameters in Tosca are customizable values for test cases, including XML elements, JSON data, headers, settings, and response details. These can be manually set within modules and are adjustable if payloads change. 

8. What are the components of the Tosca Testsuite package?

Ans: The Tosca Testsuite package comprises four main components: Tosca Commander (akin to an IDE), Tosca Executor (for test execution), Tosca XScan (for scanning input fields), and the Test Repository (for workspace storage).

9. What types of testing can be done with Tosca?

Ans: Tosca supports a range of testing types, including GUI testing, mobile testing, API testing, BI and data warehouse testing, and exploratory testing.

10. What is Tosca CI?

Ans: Tosca CI enables automated test case execution directly from a build server, with the CI client running tests and reporting results in XML format to the build server.

11. What is synchronization in Tosca?

Ans: Synchronization in Tosca aligns automated test case execution with application speed using processes and events.

12. What is exploratory testing?

Ans: Exploratory testing in Tosca is a dynamic approach combining learning, test design, execution, and result interpretation simultaneously, categorized under the Execution Section in Tosca Commander.

13. What is a recovery scenario in Tosca?

Ans: A recovery scenario in Tosca outlines steps for the tool to follow in unexpected situations, ensuring continued test execution or appropriate handling of test failures.

14. What happens if the recovery scenario fails?

Ans: If a recovery scenario in Tosca fails, the tool escalates to the next higher-level recovery scenario. If all scenarios fail, the test case is marked as failed.

15. What is the use of Rescan?

Ans: Tosca's Rescan feature is utilized for re-evaluating already scanned modules, particularly useful when UI updates occur.

16. What is a template in Tosca?

Ans: Templates in Tosca are structured models for creating reusable, consistent test cases, particularly beneficial for tests with similar step sequences.

17. What are the types of errors in Tosca?

Ans: Tosca identifies three error types: Verification-Failure (unmet expected results), Dialog-Failure (application errors), and User Abort (manual test termination).

18. What is Test Data Management?

Ans: Test Data Management is the process of managing data required to carry out the TestCases. When a workspace is created, Tosca automatically establishes a connection to the common repository where the test data resides. We can even connect to another test data source, we can manually change the connection string to a different repository.

Tosca interview questions for experienced

19. Explain about Tosca Query Language

Ans:  Tosca Query Language (TQL) is pivotal in Tosca for crafting intricate search queries. It intricately navigates through a project's landscape, focusing on objects, their relationships, and attributes. The nuanced nature of TQL, being context-sensitive, allows for a tailored approach to querying within Tosca's environment.

20. Can we perform Excel operations in Tosca?

Ans: Tosca excels in integrating with Excel, allowing seamless operations. It utilizes specific Excel modules that must be imported into the workspace. For optimal functionality, it's essential to have Microsoft Excel 2003 or 2007 installed, showcasing Tosca's compatibility with Microsoft's software.

    

21. How can we fetch test data from Excel using Tosca?

Ans: Tosca offers dual methodologies for importing test data from Excel. For single TestCase scenarios, TemplateInstance is utilized, effectively generating the required number of test cases from Excel datasets. For scenarios involving different TestCases and external data sources, the Excel Engine module or custom VB scripts can import Excel data efficiently.

22. How can we use multiple browsers in the same test case in Tosca?

Ans: We cannot trigger multiple browsers in Tosca. However, we can perform cross-browser execution. When we need to automate a TestCase with an application that has to run on different browsers, then we can use buffers. Using buffers, we can change the value in the test configuration parameter at run-time. And then specify which browser needs to be used for each buffer using the TBox Set Buffer.

23. How can we identify objects in Tosca Testsuite?

Ans:  In the Tricentis Tosca Testsuite, object identification is a critical aspect of test automation. The suite offers four distinct methods for object identification:

  • Identification by properties, where objects are recognized based on their inherent attributes.
  • Identification by anchor, which involves using a stable neighboring object as a reference point.
  • Identification by image, where objects are identified through visual recognition.
  • Identification by index, which relies on the position of the object within a list or a collection.

24. How can we run ExecutionLists?

Ans: ExecutionLists in Tosca can be initiated in a straightforward manner. Users can simply select the 'Run' option from the context menu in Tosca Commander, or utilize the F6 key as a shortcut for execution in the Execution section.

25. How can we run tests in ScratchBook?

Ans: Tosca's ScratchBook feature offers flexibility in test execution. It allows users to perform trial runs on TestCases with options such as running objects immediately upon creation, or arranging and executing them in a specific order through drag-and-drop functionality.

Tosca Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project-Based Learning

26. What is the difference between ExceutionLists and ScratchBook?

Ans: ExecutionLists in Tosca serve to gather and execute a set of completed TestCases simultaneously. On the other hand, ScratchBook is designed for running individual TestCases, especially useful for testing newly created or incomplete TestCases.

27. Can Tosca be integrated with Jira?

Ans: Yes, integration of Tosca with Jira is feasible and beneficial, particularly using the Tasktop Integration Hub within Tosca Connect. This integration fosters improved collaboration between development and testing teams by allowing synchronization of failed tests in Tosca with defects logged in Jira.

28. Can we perform a pdf compare using Tosca?

Ans:  Tosca supports PDF comparisons through the TC PDF Compare tool available on the Tosca Exchange Portal. This tool allows users to compare two PDF files, highlighting differences in the ExecutionLog post execution.

29. Can we create TestCase templates manually?

Ans: Creating TestCase templates manually is possible in Tosca, utilizing the Tosca BI modules. Users can generate templates by right-clicking on a test case and selecting the “Convert to Template” option from the context menu.

30. What is the need for the test configuration parameter?

Ans: Test configuration parameters in Tosca are essential for setting values for objects. They are instrumental in simplifying the maintenance of tests and reducing repetitive tasks, thereby enhancing the efficiency of the test automation process.

31. How can we perform API testing?

Ans:  API testing in Tosca is conducted using the Tosca API Scan. This tool allows for the comprehensive scanning of API definitions and functionalities, enabling end-to-end testing that verifies both performance and error-handling capabilities of an API.

32. How does Tosca Testsuite support Model-Based And Risk-Based Testing?

Ans: Tosca Testsuite's support for Model-Based and Risk-Based Testing is evident in its ability to describe test cases through application scans. The suite's automation model decouples test logic from the automation logic, facilitating both automated and manual test cases with precise input and verification data.

33. Explain about test configuration parameters?

Ans: Test configuration parameters in Tosca are designed to customize tests by setting various values. These parameters can be utilized across different Tosca objects like the Project root element, ExecutionList, Component folder, ExecutionEntry folder, Configurations folder, ExecutionEntry, TestCase folder, ScratchBook, TestCase, TestCase-Design folder, and ExecutionList folder.

34. Can we compare Pdf using Tosca?

Ans: Tosca provides a standard PDF comparison module, enabling automated linkage and comparison of two PDF files. This feature is particularly useful in identifying variations between documents, which are then reported in the ExecutionLog post-test.

 

35. How can you check if a file exists in a specific directory or not in Tosca?

Ans: Tosca includes a "TBox File Existence" function, allowing users to verify the presence of a file in a specified directory. This feature encompasses attributes like the directory path and the file name, and supports action modes like Verify or WaitOn.

36. What is TOSCA Commander?

Ans: Tosca Commander is the central user interface of the Tosca Testsuite, integral for designing, executing, maintaining, and analyzing test cases. It encompasses various sections like Requirement, Test Case, Modules, Execution, Reporting, and Test Script Design, making it a cornerstone of the Tosca Test suite.

If you have any doubts on Tosca, then get them clarified from Tosca Industry experts on our Tosca Community!

Subscribe to our YouTube channel to get new updates..!

 

37. How can we execute test scripts from the Tosca ExecutionLists?

Ans.  Tosca provides multiple methods to execute test scripts:

  • Utilize the F6 shortcut key for quick execution.
  • Right-click on the selected test cases and choose the "Run" option.
  • Select and execute from the ExecutionLists.

38. What are the various post-execution statuses in Tosca?

Ans: Post-execution, Tosca categorizes test results into:

  • No result
  • Error
  • Passed and
  • Failed.

39. What are the limitations of TOSCA ScratchBook?

Ans: The ScratchBook, used for temporary execution logs during test development, has limitations:

  • Repeated execution of a test step's action may lead to loss of details.
  • Execution logs may not always be accessible.

40. What are the advantages of linking Tosca test cases with the requirements?

Ans. Linking test cases with requirements ensures:

  • Testing aligns with specific requirements.
  • High-level overview of requirement coverage for test analysis.

41. What are the benefits of the specifications that are connected to the Tosca test cases?

Ans: Linking specifications with test cases in Tosca provides:

  • A method to track requirement coverages.
  • A comprehensive view of demand coverage for efficient test analysis.

42. What do you mean by String Operations?

Ans. String operations in Tosca, typically involving regular expressions, include:

  • Counting specific characters or words.
  • Aligning words and verifying numeric structures.
  • Note: AidPack module is required for string operations.

43. Why does Tricentis TOSCA require ScratchBook?

Ans: ScratchBook is essential in Tosca for:

  • Conducting trial runs of new or improved test cases.
  • Temporarily logging execution outcomes.
  • Ability to run complete or partial test cases.

44. In Tricentis Tosca, Describe the organizational units of testing procedures?

Ans: In Tosca, the automated testing includes the following organizational units:

  • Specification
  • Planning
  • Logging
  • Execution
  • Analysis

45. What is Tosca WebAccess?

Ans: Tosca WebAccess is:

  • A web interface for workspace access via browsers.
  • Independent of Tricentis Tosca Commander installation.
  • Allows accessing workspace data stored on the Workspace server via a client browser.

46. How can Tosca Connect be integrated with HP ALM?

Ans.

  1. Integration steps include:

    • Installing the Rest API.
    • Using Tasktop with a license.
    • Synchronizing Tosca test scripts with HP ALM's Test Plan and Test Lab modules.
    • Ensuring recent Execution logs in Tosca are accessible in ALM Testlab.

47. How many different kinds of logs are there in Tosca?

Ans: Tosca provides two types of logs:

  • ActualLog: Maintains latest and historical execution results.
  • ExecutionLog: Generated when archiving the execution log is enabled.

48. What do you mean by BDD in TOSCA?

Ans: BDD in Tosca stands for Behavior Driven Development, a software development technique derived from agile methodologies. It produces workable documentation, describing behavior and actions in text, used as executable documentation.

49. What does an ActionMode Constraint do?

Ans. The ActionMode "Constraint" in Tosca is used to search for specified values, such as locating a specific value in a table column.

50. List out the Default object components in TOSCA?

Ans. Default objects in Tosca, found in the standard.tce file, include:

  • Standard modules like TBox XEngines and Automation Tools.
  • Virtual folders.
  • Standard Reports.

51. What do you mean by Damage class?

Ans: The Damage class in Tosca calculates the damage values for events, ranging from 0 to 10, based on cost.

 If you want to Explore more about Tosca? then read our updated article - Tosca Tutorial.

Tosca Training

Weekday / Weekend Batches

52. What do you mean by Frequency class?

Ans: The Frequency class in Tosca calculates event damage values based on frequency and quantity, with values ranging from 0 to 10.

53. What do you mean by TOSCA Classic Engine?

Ans: The Classic Engine in TOSCA orchestrates test execution, leveraging a structure where test cases are constructed as business-focused objects. This engine processes these objects and connects them with test scripts through specific steering activities.

54. What is a Distributed Execution in TOSCA?

Ans: Distributed Execution in TOSCA refers to executing a large array of test scripts across multiple machines. This is achieved by setting up TestEvents in Tosca Commander, enabling efficient and scalable testing.

55. What purpose do TestMandates serve

Ans: TestMandates in TOSCA are designed for executing batches of tests at predetermined times, crucial for domain-specific projects in sectors like banking and insurance. They enable simultaneous execution of different execution list components without impeding the primary list.

Tosca interview questions for 7 years experience

56. What is TOSCA, and what are its primary features and benefits?

Ans: TOSCA, standing for Test Automation Suite for Continuous Testing, offers end-to-end testing solutions. Key features include model-based test automation, seamless integration, and efficient data management. Benefits include accelerated test creation, enhanced reusability, and optimal support in Agile and DevOps.

57. Explain the difference between manual testing and automated testing. How does TOSCA facilitate automation?

Ans: Manual testing involves direct human involvement, while automated testing uses tools and scripts. TOSCA streamlines automation with its model-based approach, reducing the need for complex coding and focusing on efficient test design and maintenance.

58. Can you describe the main components of TOSCA Suite?

Ans: TOSCA Suite comprises TOSCA Commander for test management, TOSCA Executor for test case execution, TOSCA XScan for importing tests, TOSCA Test Data for data management, TOSCA Analytics for insights, TOSCA TBox for artifact management, and integration with version control systems like Git.

59. How do you create a test case in TOSCA? Walk me through the process.

Ans: Creating a test case in TOSCA involves launching TOSCA Commander, modeling test steps using its graphical interface, defining test data, and executing the test case with TOSCA Executor.

60. What is the significance of modules in TOSCA, and how do you use them effectively?

Ans: Modules in TOSCA encapsulate test steps for reuse, enhancing efficiency and maintainability. Effective use involves identifying repetitive actions, creating modules for them, and integrating these modules across different test cases.

61. How does TOSCA support data-driven testing, and why is it important?

Ans: TOSCA facilitates data-driven testing by allowing parameterization of test data, enabling the creation of versatile test cases with varying inputs, thereby increasing scenario coverage and reducing redundancy.

62. What are TOSCA Execution Lists, and how do they help in test execution?

Ans: Execution Lists in TOSCA are grouped test cases for organized and efficient execution, allowing for categorization based on criteria like priority or functionality.

63. Discuss the concept of test automation frameworks. Have you worked with any specific frameworks in TOSCA?

Ans: In TOSCA, test automation frameworks provide structured guidelines for test design and execution. My experience includes working with TOSCA's data-driven frameworks, enhancing test reusability and maintainability.

64. How do you handle dynamic elements or elements with changing properties in TOSCA scripts?

Ans: Managing dynamic elements in TOSCA involves using stable identifiers, regular expressions, and wait statements to accommodate dynamic behaviors effectively.

65. Can you explain the concept of Test Case Design?

Ans: Test Case Design in TOSCA involves crafting test scenarios, steps, and expected outcomes to form the foundation of automated testing. This approach ensures clarity in objectives and enhances test coverage.

67. What is the role of Test Configuration and Test Data Management in TOSCA?

Ans: Test Configuration in TOSCA involves setting up test environments, while Test Data Management handles data provisioning. Both are essential for executing tests under controlled, repeatable conditions.

68. Describe the process of integrating TOSCA with version control systems like Git.

Ans: Integration involves setting up a Git repository for TOSCA projects, configuring TOSCA to work with Git, utilizing TOSCA's version control features, and managing project versions collaboratively.

69. Have you used TOSCA's Continuous Integration and Continuous Testing (CI/CT) capabilities? If so, how?

Ans: I've integrated TOSCA with CI/CT pipelines, using tools like Jenkins to automate testing as part of development, ensuring continuous testing and early issue identification.

70. How do you handle exception handling and error reporting in TOSCA test scripts?

Ans: In TOSCA, exception handling involves using conditional statements and error blocks to manage errors, with built-in reporting capabilities for detailed analysis.

71. Discuss the advantages and disadvantages of using TOSCA for cross-browser testing.

Ans: TOSCA excels in code reusability and browser-independent test design for cross-browser testing. However, it may require additional configuration for complex scenarios compared to specialized tools.

72. What is TOSCA's approach to handling mobile application testing? Have you used it for mobile automation?

Ans: TOSCA's Mobile Engine facilitates mobile application testing on Android and iOS. My experience with mobile automation in TOSCA involves creating test cases and utilizing the Mobile Engine for testing on devices or emulators.

73. How do you generate reports and analyze test results in TOSCA?

Ans: TOSCA offers customized reporting and analytics for test execution, including integration with third-party tools for advanced analysis.

74. Explain the concept of reusable test assets and their significance in TOSCA.

Ans. Reusable test assets in TOSCA, like test cases and modules, are significant for promoting efficiency, consistency, and reducing effort in test case creation and maintenance.

75. Have you worked with TOSCA's API testing capabilities? If yes, describe your experience.

Ans: My experience with TOSCA's API testing includes creating test cases for RESTful and SOAP APIs, defining API endpoints, and managing request parameters and expected responses.

76. How do you handle test data management and parameterization in TOSCA?

Ans: In TOSCA, test data management involves creating data sets separate from test cases and parameterizing them for reuse. The Test Data Management module facilitates this process, enhancing test coverage.

77. Can we run a template in the scratchbook?

Ans: Running templates directly in the Scratchbook may not be a default feature in TOSCA. Instead, templates are typically executed via Test Configurations in TOSCA Commander.

78. Will recovery scenarios work in the scratchbook?

Ans: TOSCA's Scratchbook is mainly intended for quick test creation and debugging, with recovery scenarios managed in test suites or through the TOSCA Commander interface.

79. What options are available if you want to run a test in the scratchbook?

Ans: In TOSCA's Scratchbook, tests can be run using the "Execute" option for the current test case, the "Debug" option for step-by-step analysis, or "Run Configuration" for executing with specific settings.

       Take your career to next level in Tosca with HKR.Join Tosca Training Hyderabad now.

About Author

As a senior technical content writer for HRK tainings, srivalli patchava has a greater understanding of today's data-driven environment, which includes key aspects of data management and IT organizations. She manages the task of creating great content in the areas of software testing, DevOps, Robotic process automation. Connects with her on Linkedin and Twitter.

Upcoming Tosca Training Online classes

Batch starts on 23rd Apr 2024
Mon & Tue (5 Days) Weekday Timings - 08:30 AM IST
Batch starts on 27th Apr 2024
Mon - Fri (18 Days) Weekend Timings - 10:30 AM IST
Batch starts on 1st May 2024
Mon & Tue (5 Days) Weekday Timings - 08:30 AM IST
To Top