TOSCA Interview Questions

 TOSCA:

Q1) What is Tosca.

Ans. Tosca is one of the widespread continuous testing platforms established by Tricentis. It facilitates testing with a no-code approach and script-less for end-to-end automation. Tricentis Tosca combines multiple aspects of software testing (test case design, test automation, test data design and generation, and analytics, it also supports graphical user interface, application programming interface, and command-line interface. 

It helps you to:

1. Deliver fast feedback for DevOps and AgileReduces regression testing time
2. Maximizes maintainability and reusability
3. Integrates and extends existing test assets

Q2) Tell me the major components of Tosca?

Ans. The significant components available in Tosca are:

1. Tosca Commander.
2. Tosca Executor.
3. Tosca XScan (Tosca Wizard)
4. Test Repository.
5. Tosca ARA (Automation Recording Assistant)

Q3) What are the advantages of the Tosca Automation tool.

Ans. The benefits provided by Tosca automation tool mentioned below:

1. Multiple Features in One Tool
2. Scriptless automation
3. Suitable for large scale operations
4. Test management
5. Mass updates
6. Reusability of assets
7. Supports Multiple Platforms
8. Quality Vendor Support
9. Easy to use interface
10. Model-based automation

Q4) What is TOSCA Commander?

Tosca commander is the IDE, which facilitates the user to create, execute, manage, and analyze the test scripts. Commander is the core part of Tricentis Tosca. Commander compacted with different sections like modules, Test Case, Requirement, Test script Design, Execution list, and Reporting, etc.

Q5) Discuss the process of executing scripts from Tosca ExecutionLists?

Ans. Test scripts can be executed in many ways:

1. Test Scripts in Tosca can be executed either by pressing the F6 key in the execution section.
2. Select the scripts and right-click over there and Run the scripts. 
3. Choose the ExecutionLists and trigger the execution. (Select Ctrl + left mouse button to run more than one ExecutionList)

Q6) What are the different modules in TOSCA?

 Ans: There are four different modules in Tosca

1. Tosca Commander
2. Tosca Executor
3. Tosca Wizard
4. Test Repository

Q7) What are the different processes to run scripts from Tosca ScratchBook?

Ans. The ScratchBook permits the user to perform trial runs for test cases. Objects like scripts and test steps can be executed from scratchBook.

Below two options to execute tests from the ScratchBook:

1. Execute objects right away.
2. Append or organize objects in the ScratchBook and then run them. 

Q8) How Tosca can be integrated with Jira?

Ans:

TOSCA Can be integrated with JIRA for issue tracking. We can submit issues from TOSCA to JIRA & if you want to change the status, then we can resolve the issue in TOSCA so that that will get reflected in JIRA.

Q9) What are the benefits of Tosca Jira Integration?

Ans. Tosca Jira integration enhances the standard and accountability of software products. Some of the advantages of this integration are:

1. Synchronizes failed tests from Tosca.
2. Automatically reports defects.
3. Supports cross-tool traceability.

Q10) Which kind of errors occurs in Tosca?

Ans. Usually, three types of errors in Tosca.

1. Verification-Failure: This error occurs when verification does not provide the expected results. 
2. User Abort: Terminate of the test run by the tester.
3. Dialog-Failure: The application desires to get the authority of either that doesn’t obtain or is not in a working state.

Q11) What is Tosca Testsuite?

 Ans:

Tosca Testsuite is a tool for the automated execution of functional and regression software testing. Also, to test automation functions, TOSCA includes integrated test management, a graphical user interface (GUI), a command-line interface (CLI), and an application programming interface (API).

Q12) How to extract data from Excel using Tricentis Tosca?

Ans. Any user can extract data from excel by the below process:

1. For a single test schema that has to be tested on different datasets, Tosca provides a feature of “TemplateInstances” to create any number of test cases from your data set to import your excel data and set it in Test Case steps.
2. To import data from an outside source, the user can utilize the “Excel Engine.”

Q13) Can we launch multiple browsers in TOSCA?

 Ans:

Multiple Browsers cannot be launched with TOSCA. But we can achieve cross-browser execution. For using cross-browser execution

 A Test configuration Parameter “Browser” should be design either at testcase or its Parent Levels.

 We can select the value as InternetExplorer, Firefox, Chrome.

 The respective browsers will trigger executions.

Q14) How is Data-Driven testing achieved in Tosca testsuite?

Ans:

Data-driven testing in TOSCA testsuite can be gained by using the test sheet in TestCaseDesign Section. There user can create attributes (Parameters which require to cover for data-driven testing) & Create various instances (possibilities) for each attribute. Finally, generate instances. Design a template from your test case, attach the test data sheet to template & then instantiate the template.

Q15) Is it possible to launch more than one browser in Tricentis TOSCA?

 Ans: Launching multiple browsers is not possible in TOSCA. But the user can achieve cross-browser execution. 

To perform cross-browser execution, users need to follow the below steps: 

1. A Test Configuration Parameter “Browser” should be designed either at TestCase or its Parent Levels.
2. Users can choose the value as InternetExplorer, Firefox, Chrome.
3. The individual browsers will trigger executions. 

Q16) What types of test status available for post-execution in Tosca?

Ans: For each execution, there are four states available:

1. Passed
2. Failed
3. No result
4.  Error

Q17) What are the limitations of the TOSCA ScratchBook?

Ans: ScratchBook is a debugging window of Tosca.

The limitation is it will not display detailed action steps if the action is performed repetitively.

Q18) What are the benefits of linking test cases to requirements in Tosca Testsuite?

Ans. To keep track of the prerequisites, a user links the test cases in Tosca. Which track the number of conditions covered, and how many more are pending and also to check for how many requirements the test cases are passed successfully. This assists users in providing a high-level picture of requirement analysis.

Q19) What is Template? How to Create a Template?

Ans: Generally, the template is nothing but something in a conventional format. In TOSCA TestSuite, user can convert test cases to the template so that it can be used for various data combinations. The template can use test data from the test datasheet.

Q20) What is the advantage of associating test scripts to specifications in Tosca Testsuite?

Ans: The user links the scripts to specifications to track of the requirements. This will let the user know that how many conditions are covered, how many are yet to be covered, for which requirements test cases are successfully passed, So basically, this will give a high-level picture of requirement coverage.

Q21) Explain Test Data Management.

Ans. Test data management enables you to deal with the test data necessary for test execution. It is the component of this Tricentis Tosca Testsuite standard installation. It gives you the ability to manage, use, and reuse check information. Testers can get the specific test data required seamlessly for much more complex situations, with on-demand ingress to stateful test data.

Q22) What is String Operations in Tosca?

Ans. String operations are utilized for verifying or changing the strings with regular expressions. It features count specific character/word from the announcement, aligning a word with another word, confirming the structure of a number, etc. You ought to have a module AidPack downloaded and downloaded on your endeavor to execute String operations.

Q23) Why SratchBook is required in Tricentis TOSCA?

 Ans: ScratchBook in TOSCA provides temporary aid to come up with Test Cases while executing the scripts. ScratchBook also enables temporary arrangement and execution of TestCases. Therefore, several TestCases, TestSteps, or test connections may be arranged together in any required order and could be executed in ScratchBook.

Q24) What is exploratory testing Tosca?

Ans. Exploratory testing is a method of designing and executing tests and interpreting test results all at one time. It’s a plan-as-you-test strategy. The purpose of this testing would be to explore the unknown to prevent unexpected results.

Tosca Interview Questions for Intermediate level

25) Describe the organizational units of the testing procedures in Tricentis Tosca?

Ans: A testing process is sketched within a software testing project, and it contains the following organizational units.

1. Test planning.
2. Test specification.
3. Test execution.
4. Test logging.
5. Test analysis.

Q26) Describe the purpose of “Tosca Query Language”(TQL)?

Ans: TQL stands for Tosca Query Language, a strong search process that allows you to control the project at any time. TQL exploration is condition dependent.

Q27) Is it possible to compare pdf using Tricentis Tosca?

Ans. Tosca allows users with a standard module to perform a comparison of pdf files. This activity recommends two pdf files to differentiate automatically with each other. If any deviations are found, they are shown in ExecutionLog after the test completion.

Q28) What is Tosca CI? How does the user execute test scripts using CI Tool?

Ans: TOSCA CI is a Continuous Integration concept braced by TOSCA TestSuite. Users can execute test cases from CI tools like Jenkins, Bamboo, etc. So, this TOSCA CI makes a bridge with TOSCA TestSuite workspace as an Integration tool like Jenkins.

Q29) What are the loop-statements used in Tosca?

Ans. To run TestSteps with branches, Tosca supports IF, DO, and WHILE Statements.

Q30) What do you mean by Tosca WebAccess?

Ans: Tosca Commander WebAccess is a web application designed by Tricentis, which permits Tosca Commander workspaces to be accessed/edited in a web browser without installing Tricentis Tosca Testsuite on the local system.

The host system stores the TOSCA workspaces, and browser clients access the host’s workspaces using WebAccess application hosted in a web server.

Q31) What is the purpose of Tosca API Scan?

Ans. Tosca API Scan assists you to design testcases for Tosca Orchestrated Service Virtualization or Web Services. User can scan API definitions, validate messages, and save them in TestCases.

Q32) What is Tosca QC / ALM Integration?

Ans: HP Quality Center is an application that permits test scripts, Pre-requisites, ExecutionLists, and defects to be supervised. This synchronization happens via Tosca Commander with the help of the Tosca Quality Center Integration.

Q33) Explain the Tosca test configuration parameters.

Ans. Test configuration parameters help users to design tests to set values. User can create test configuration parameters for the following Tricentis Tosca objects: 

1. Project root element
2.  ExecutionList
3. Component folder
4. ExecutionEntry folder
5. Configurations folder
6. ExecutionEntry
7. TestCase folder
8. ScratchBook
9. TestCase
10. TestCase-Design folder
11. ExecutionList folder

It is used for diverse functions and assertion in Tricentis Tosca.

Q34) How to integrate Tosca Connect with HP ALM? 

Ans.

1. Install Rest API.  
2. Install Tasktop in the test system with the License.
3. Do test script synchronization with Test Plan Module in HP ALM from TOSCA. 
4. Synchronize the execution list with the test lab module in HP ALM from TOSCA. 
5. Sync with execution Entry and Latest Test Result from TOSCA to Test Lab/Test Runs Modules in HP ALM.

Q35) Explain the different modes of TC Shell.

Ans: The TOSCA commander administrator uses TC shell, and there are two different methods of starting TC Shell.

1. Interactive mode: The interactive mode favor by new and intermediate users, assists the user with help and options. The user has ingress to the full range of functionalities of the GUI version in the Tosca Commander.
2. The script mode: The Script mode involved minimal interaction and meant for running the scripts in automated mode.

Q36) What is Synchronization in Tricentis Tosca? 

Ans. Synchronization is a process that matches the application momentum with automation tool momentum. It can be accomplished in Tosca using ActionMode “WaitOn” method. User will find the Synchronization settings using below steps:

Go to settings->TBox->synchronization.

Q37) How do users validate existing files in a specific directory in Tosca?

Ans. Using “TBox File Existence,” the user can validate if the file exists in a specific directory or not. It contains the following attributes:

1. Directory: Path of the file to be verified.

2. File: Name of the file to be confirmed. Users can apply ActionModes like “Verify” or “WaitOn.”

Q38) How many types of logs available in Tosca?

Ans: There are two types of logs available post-execution.

1. ActualLog: Contains all current execution results, including their history. Each execution list and TestMandate has an ActualLog with them.
2. ExecutionLog: It is generated with the option “Archive actual ExecutionLog” 

Q39) What is Behavior Driven Development (BDD) in TOSCA?

Ans: BDD is an agile methodology grounded software development process that is based on Test Driven Development.

BDD does not generate workable test cases but workable documentation. In BDD, behavior, and actions are described as texts. This permits them to be tested as workable documentation. Requirements are depicted as user stories.

TOSCA carries the BDD in a specific way that,

1. A clear difference is made between user stories (Requirements), scenarios (TestCase-Design Instances), and test cases.

2. Methods are drafted in an easily readable format.
3. All processes and actions are visible.

Q40) What is the purpose of ActionMode Constraint?

Ans. Action mode constraint is applicable for limiting the search. If a condition is specified along with verifying, it will ascertain only those items where the limitation is confirmed. User can use this if he or she knows which elements uniquely identify a list item.

Q41) What are the Default object components in TOSCA?

When a workspace is designed in the TOSCA test suite, the default objects could be automatically introduced or manually using the import subset feature.

The Default objects are saved in the file standard.tce and is located under %TRICENTIS_PROJECT%\Toscacommander folder.

The components of the Default objects are,

1. Standard modules that include TBox XEngines and TBox Automation Tools.
2. Virtual folders.
3. Standard Reports.

Q42) What is Damage class?

Ans: Damage class indicates the estimated damage value of an event, i.e. for instance, a single functional requirement in a question should be evaluated that how much damage it can cause in term of cost? 

 This value can be set with numeric values ranging between 0 (min) and 10 (max).   

Q43) What is Frequency class?

Ans: Frequency class indicates the estimated damage value of an event, i.e., for instance, a single function requirement in a question should be evaluated that how much frequency this is going to be?

This value can be set with numeric values ranging between 0 (min) and 10 (max).   

Q44) Discuss the manual test case template creation steps in Tosca?

Ans. Users can design the TestCase templates using the anticipated sections of Tosca BI Modules and Samples.tce subset.

Follow the mentioned steps to create and use your TestCase templates:

1. Create a TestCase according to the user’s requirements. 

2. Right-click on the TestCase and choose the option Convert to Template from the context menu to convert the TestCase to a Template.

3. Drag and drop the appropriate TestSheet onto the desired TestCase Template.

4. Use XL paths to manually allocate the TestSheet values to the essential TestStepValues express the Testcase Template. 

Tosca Interview Questions for Advanced level

Q45) What are the advantages of using Tosca Testsuite?

 Ans: The Advantages of using Tosca are as follows-

1. Scripless automation.
2. Easy to learn so that tester can train their team within significantly less time compared to QTP/UFT and selenium. So you can start automation very early.
3. Model-based automation, user does not need to design a new framework for testing. 
4. Reusability of assets and copy-paste property for test cases and modules.
5. Test management and manual testing are also present.
6. It can be integrated with HP ALM, can run selenium scripts.
7. Mass updates – Tosca provides its query language the same as SQL called TQL. User can change many tests cased together using this.

Q46) Is it possible to do API testing using Tricentis Tosca?

Ans: Yes, API Testing can be done by Tosca using TOSCA TestSuite. TOSCA API Scan is to accomplish this. We can either specify the url or file path where the JSON or XML file (API) is placed. We can send the request, verify the response, XML structure automatically.

Q47) How to use multiple web browsers within the same test case using Tosca?

Ans. Users want to automate a test script pass over different applications that execute on other browsers. Using buffers, changing the Test Configuration Parameters at execution time by the below methods.

1. Alternating the value of test ordering Parameter to {B[Browser]} or any other Buffer Name user prefers. 

2. Using a TBOX Set Buffer to specify which Browser needs to be used.

Q48) What is TOSCA Classic Engine?

Ans: Classic Engine or Base Engine is used for executing each of the automated test scripts. Base Engine obeys an architecture according to which the test cases are managed as business-based objects. The Classic engine receives the business-based object information about the test scripts and activities the steering of the object. The steering is achieved by the corresponding engines which understand and formulate the technology in question. 

Q49) What are the steps required in Object Steering in Tosca?

Ans: There are two steps involved in Object Steering:

1. Object access.
2. Object steering.

Q50) Discuss Tosca Model-Based and Risk-Based Testing?

Ans. Tosca describes test cases by scanning the applications. The automation model comprises automation logic for decoupling the test logic, as stated as a test case. When the required models are defined, they may be used to execute automated and manual test cases with entering & verification information.

Q51) What do you mean by Distributed Execution in TOSCA?

Ans: When any user or Test wants to execute a large set of test scripts in multiple machines, the tester must create TestEvents in Tosca commander. Once this is finished, he can then use the option “Execute now” to address the request to Tosca Distribution server, which then assigns the events on designated machines or virtual machines etc.     

Q52) Describe Test Data Management (tdm)?

Ans: Test data management is used to control the test data required for test scripts execution. Test Data Management (TDM) is a segment of the Tricentis Tosca Testsuite standard installation process. Tosca uses the same database as the regular repository does for test data management for DB2, Oracle, and MS SQL Server depositories. For SQLite repositories, a deferent TDM repository is designed.

Q54) How to run Tests using ScratchBook?

Ans: Unlike the attention of an ExecutionList, the attention of the ScratchBook is a temporary arrangement and execution of TestCases while creating TestCases. Additionally, you can even perform partial test executions by running only individual TestSteps. The ScratchBook allows you to combine various TestCases, TestSteps, or examine folders and execute them. On the other hand, the TestCases compilation and the execution results won’t be saved. The ScratchBook should, therefore, only be regarded as a temporary aid for executing TestCase parts while constructing TestCases.

Q55) What is the use of TestMandates?

Ans: There are many scenarios like banking, insurance, etc. domain projects; we required a batch to be run at a specific time. This requirement can be fulfilled using TestMandates. So other testers can execute different parts of the ExecutionList simultaneously without any dependency. Of course, the results are consolidated in ExecutionList itself.    

Q56) Discuss the steps to instantiate TestCases using Excel?

Ans. Instantiating means converting one template test case into multiple test cases based on the test data provided to a template.

Below are the steps to instantiate TestCases with excel:

1. The TestCase to be instantiated must be inspected as a template.

2. The values required to be transferred from the template (parameters) must be linked by specified syntax with attributes of the template.

3. Select Create TemplateInstance from the context menu of the TestCase template.

4. The Excel file with the respective spreadsheet must be identified in the subsequent dialog. 

5. Authenticate user’s inputs by clicking on the OK button.

6. Click on Yes in the following dialog, and the instantiation process will start.

Q57) Describe Instantiating Template?

Ans: Instantiating template is a method to convert one template test case into multiple test cases based on the test data, which is supplied to the template. This is how we can achieve data-driven testing using TOSCA TestSuite.

Q58) What do you mean by business parameters in Tosca?

Ans. Business parameters permit you to steer the values you want in your test scripts.

Business parameters can be declared manually within the module by the below process:

1. ML elements and attributes in the Payload tab
2. JSON data in the Payload tab
3. Headers in the Headers list
4. Parameters in the Params tab
5. Transport information in requests
6. Status code and response time in responses

Q59) Explain about TC-Shell?

Ans. TC-Shell is the command-line control of this Tosca commander. It can be launched in two unique manners using interactive and script.

1. The script mode allows Shell to operate with a set of commands from the script data document. This mode is acceptable for automation processes. The user cannot interfere at any part of this procedure. 
2. Users may use the comprehensive selection of purposes of the GUI version from the Tosca commander.

Q60) Discuss the naming protocol of the Tosca Execution Framework?

Ans: Any project name should follow the below naming conventions in TOSCA.

1. No special characters, including _ (underscore), $.
2. The project name should not exceed 16 characters.
3. CamelCase naming should follow.
4. Finishes with “Engine.”

Any “Namespaces” must have to follow below naming conventions in TOSCA.

1. Root namespace must be the project name.
2. As there is no namespaces support in COM, project-root must be visible for COM.
3. Namespaces can be selected freely for .Net internal classes.

Q61) What are the different ways to identify objects in Tosca Testsuite?

Ans: Objects are identified in Tosca by mentioned ways

1. Identify by properties
2. Identify by Anchor
3. Identify by image
4. Identify by index

Q62) What is DokuSnapper in Tosca? 

Ans: The DokuSnapper function enables to an archive of the progress of automated tests in a document. Tosca creates a Microsoft Word document for every test script upon each execution. The document name consists of the test script name and the timestamp of the execution time. 

User can enable Dokusnapper from Settings 

Configure options and settings > Settings Dialog > Settings – Engine > Settings – DokuSnapper

Q63) What is TDS?

Ans: TDS stands for Test Data Service, which is used for test data management in Tosca. Using TDS, we can store the dynamic test data in a shared location which is easy to read/ update by the test case. As the data stored in a shared location, it is useful to share the same dynamic data across multiple test cases. Also, we can update it without opening Tosca as it’s treated as a separate component.

Q64) Explain the API Testing using TOSCA? Explain the advantages.

Ans: API stands for Application Interface. In a multi-application environment where one application is interacting other application through API, we have to wait for the completion of development of all the application for testing. So the testing is going to be a time-consuming process. Instead of that, we can start the testing of APIs once any of the application is ready to reduce the execution cycle time. So API testing is an approach to test the interface through API before integration of the entire application. Tosca provides an API scanning wizard; through this, we can scan the API and creates API modules. Later based on the module, we can create test cases to perform Tosca API Testing.

The advantages are –

• Fast execution.
• Reduce execution cycle time.
• Testing can be initiated before system integration.

Q65) What is exploratory testing in Tosca? Explain the purposes?

Ans: It’s an approach to record test scenarios as a document for functional analysis, verification/ testing of training purpose.

Q66) How can we change the value of any Test Configuration Parameter during the execution?

Ans: We need to assign a buffer as the value of Test Configuration Parameter (TCP). By changing the buffer value using “Tbox Set Buffer”, we will be able to change the TCP value during execution.

Q67) Is it possible to automate mobile apps in Tosca?

Ans: Yes, Tosca supports mobile automation using engine ME3.0 for mobile testing.

Q68) Explain the approach of mobile testing?

Ans: We need to follow the below steps to perform mobile automation.

• We need to connect the physical or simulator mobile device with our system or Appium server. For an iOS device, we need to connect the device in Appium configured Mac system.
• Select the Scan->Mobile option while scanning mobile devices.
• In the scan window, we need to provide basic details such as Connection type as Local or Appium Server, Name of the device, Device Id and device type as Android or iOS.
• We need to select the checkbox for “Run Live View” to replicate mobile screen in the device.
• Click on Connect button to establish the connection with mobile devices.
• Select the desire mobile screen and scan to create nodule.
• Create the mobile test cases based on the created modules and some standard modules such as an open mobile app.
• Execute the test case.

Q69) What kinds of mobile apps are supported by Tosca?

Ans: Only Android or iOS mobile devices are supported by Tosca. Also, it can automate mobile web, native and hybrid apps.

Q70) What are the different engine available for mobile automation?

Ans: There is two engines are available –

1. Tosca Mobile + – It’s used for old devices.
2. Mobile Engine 3.0 (ME 3.0) – It’s used for the latest devices.

Q71) What is the basic configuration required to execute any test case in mobile Chrome browser?

Ans: We need to set the value as “CromeAndroid” for TCP Browser.

Q72) What is ARA? 

Ans:  ARA stands for Automation Recording Assistant. This is an advanced recording feature of TOSCA. With the help of ARA, we can record any scenario with the verification and generate the test cases instantly. After recording ARA generates a .ara file which needs to be imported in TOSCA to generate the instant test case. This is very useful for the business user who does not have any bits of knowledge about Tosca.

Q73) Explain the advantages of ARA?

Ans: The major advantages are –

• Standalone recording wizard

• Intuitive recording

• On-the-fly remarks & verifications

• No duplicate modules in a single recording

• Easy clean-up

• Fast playback

• Easy to export & import recordings

Q74) Explain the limitations of ARA?

Ans: The limitations of ARA are –

• Compatible with Tosca 13.1 & above

• Linear recording

• License required for standalone installation

• Duplicate modules get created in multiple recordings

• Challenging to modify existing tests

• Yet to be compatible with Android/iOS

Q75) Explain the steps that create test cases through ARA?

Ans: The process steps are –

• Record any scenario using ARA Wizard.
• Add verification points during recording and perform clean up on the recorded scenario.
• Export the recording.
• Import recording in Tosca.
• Execute test cases which are auto-created during recording.