Explore topic-wise InterviewSolutions in .

Tosca allows us to verify a file's existence in any directory by using the TBox File Existence. It includes the following ATTRIBUTES:  

• Directory: Location of the file to be verified.
• File: Name of the file that needs to be verified.

Tricentis Tosca is one of the best automation testing tools currently available on the market, which simplifies the work of software testers. Tosca automation tool automates software testing and makes it easier to find and FIX bugs efficiently. Since then, it has developed into one of the biggest players in the automation field. So, securing a job as a Tosca specialist/expert is sure to guarantee you a SUCCESSFUL career. Here is your chance if you are looking for Tosca Interview QUESTIONS and Answers for Freshers and Experienced.

Useful Resources:

• Automation Testing
• Manual Testing
• Automation Testing Tools
• Manual Testing Tools

In order to integrate Tosca Connect with HP ALM, follow these STEPS: 

• Download and install ALM Rest API.
• Install Tasktop on a test system using a license key.
• Synchronize testcases from Tosca to HP ALM's Test Plan Module.
• Sync Tosca execution lists with HP ALM's test lab MODULES.
• Sync Tosca execution entry and latest test results with HP ALM's Test Lab/Test Run modules.

When you instantiate a template, you CONVERT a single testcase template into several test cases using the test DATA that you supply as input to the template. You MUST follow the STEPS below to instantiate TestCases in Excel: 

• The TestCase that is needed to be instantiated must be viewed as a template.
• Parameters (values to be transferred from a template) must be linked to template attributes by specified syntax.
• To create a TemplateInstance, right-click on the TestCase template and select Create TemplateInstance from the context menu.
• You must specify the Excel file with the corresponding spreadsheet in the subsequent dialog box.
• Click the OK button to confirm your inputs.
• Once you click Yes in the subsequent dialog, the INSTANTIATION process will begin.

In this way, Tosca creates a TestCase in the TemplateInstance for every TestCase defined in the template. The structure of the TestCase is the same as that of the corresponding TestCase in the template. 

Tosca BI (Business Intelligence) modules can be used to create a TestCase TEMPLATE MANUALLY. In order to create and utilize your own TestCase templates, perform the FOLLOWING steps:  

• Step 1: BUILD a TestCase that meets your needs.
• Step 2: Right-click on the TestCase and CHOOSE "Convert to Template" from the context menu to convert it to a Template.
• Step 3: Drag and drop the appropriate TestSheet onto your TestCase Template.

There are two ways to fetch test data from Excel as follows:  

• In order to test a TestCase scenario on multiple datasets, TOSCA provides a TemplateInstance feature. We can create as many test cases as necessary from a data SET by using it. We can then IMPORT the data from Excel and embed it into the Test Case steps.
• For different TestCases and to import data from EXTERNAL sources, the Excel Engine module can be used.

With Tosca CI (Continuous Integration), test cases can be executed directly from the build server without the USER having to perform/run them themselves (manually). Examples of CI TOOLS include Jenkins, Bamboo, etc. It is used to minimize testing time and effort for Continuous Integration & Delivery. The following ways can be used to implement Tosca CI:  

• Use a remote service to run the test EXECUTION, i.e., on a separate workspace.
• Use Tosca Continuous Integration along with Tosca Distributed Execution. Your tests will be executed by several Distribution Agents, thereby speeding up the PROCESS.

As its name implies, RECOVERY scenarios are used to recover from the failure of a testcase/teststep. During test execution, if for some reason your test case fails (this could be any reason), the Recovery scenario ENSURES that the NEXT test case after that failed test case will proceed normally. This will ensure that the following test case runs correctly, without any impact from the previous test case. There are two conditions in which recovery is possible i.e., dialog failure and verification failure. When a recovery scenario fails, Tosca then tries the next higher level recovery scenario, and if all recovery scenarios fail, it REPORTS the test case as failed.   

As its name implies, Test Data Management involves managing test data necessary for the execution of TESTCASES. In addition to viewing all records within your test data repository, it allows you to modify and/or delete SELECTED ones. During Tricentis Tosca Server setup, it is automatically installed as part of the Test Data SERVICE component. It COMBINES Test Data Service (TDS) and test data management to allow teams to design, locate, MANAGE, and provide test data, even in complex and hard-to-manage scenarios. 

In TOSCA Rescan, the module that has already been SCANNED is scanned again. Assume you have already scanned the page, but there have been a few changes and two new FIELDS have been added which you need to include in your TEST case. For the two fields to appear in your scanned modules and your test case, you need to rescan your module. 

TC PDF Compare is the STANDARD module OFFERED by TOSCA for comparing PDF FILES. This TC PDF Compare feature from Tosca Exchange Portal allows the comparison of two PDF files. After the test is executed, any differences found appear in the ExecutionLog. 

The Tosca Query Language (TQL) is a POWERFUL way to search within your project. The tool gives you the ability to perform search QUERIES on your project through objects, object relations, and object properties to find/search anything you need. Simply type your query into a language the computer understands and the system will do the rest. It gives you the ability to take control of a project at any time. In its most basic form, this is similar to SQL, which enables us to search based on conditions. 

Example: Suppose the diagram below represents our CURRENT situation, in which we want to search for all TestCases with the name DATA Source Excel in the TestCases folder.

Solution:

In Tosca, objects can be identified in four different ways as LISTED below: 

• Identify by properties: By DEFAULT, Tosca XScan IDENTIFIES objects by their properties. All technical information and the properties of an object can be found in the Identify by Properties window.
• Identify by Anchor: The technical properties of objects can be used in Tricentis Tosca to identify other objects.
• Identify by image: Tosca can identify objects by capturing a screenshot of the object.
• Identify by index: In this case, the object is identified by its index. If an object SELECTED does not have a UNIQUE ID, you can specify an index to be used to identify the object at test execution.

In Tosca, we are not able to TRIGGER multiple browsers at once, but we can perform cross-browser execution. In order to automate TestCases with applications that have to RUN on different browsers, buffers can be used. The test configuration parameter can be changed at runtime using buffers, and the browser to be used can be specified using the TBox Set Buffer. The following STEPS need to be followed in order to perform cross-browser execution:   

• Design a Test Configuration Parameter “Browser”.
• Using the buffer, change the value of the Test Configuration Parameter to [B[Browser]].
• Specify which browser should be used using the TBOX Set Buffer. Users have the option of selecting Internet Explorer, Firefox, CHROME, etc.
• Executions will be TRIGGERED by individual browsers.

Tricentis Tosca's integration with Application Lifecycle Management (ALM) tools enables development and QA (Quality Assurance) teams to better collaborate and meet customer expectations. This integration serves as a means of managing TEST executions and defect management. In general, ALM is a test management tool used to manage the testing process, including test development, EXECUTING them, and tracking defects. ALM allows developers to MONITOR quality parameters and test results at any time, and the QA (Quality Assurance) team will have real-time insight into all development phases. 

The above shows Tosca integration with ALM tool. Thus, Tricentis Tosca will SYNC all requirements from the ALM tools, and all defects reported by the QA team will appear in the ALM tool.

In TOSCA, templates are structured/conventional formats that can be reused to create CONCRETE TestCases. It is possible to convert test cases that have very similar steps into templates so that they can be used for a variety of data combinations. Data from test datasheets are used in the template. When you INSTANTIATE a template, you convert a SINGLE test case template into several test cases USING the test data that you supply as input to the template.

To CONFIGURE your tests, you can set configuration VALUES through test configuration parameters. The test configuration parameters give you the ability to set parameters for TOSCA objects. You can simplify the maintenance of your tests and reduce repetitive tasks by setting specific values to test configuration parameters. For example:  

• VERSIONS of test objects, such as RELEASE numbers.
• Various test environment identifiers, for instance Windows 7.
• Connection identifiers, such as URLs and parameters.
• Identifiers of business process chains.

Test configuration parameters can be created for the following Tricentis Tosca objects:

• Project root element
• ExecutionList
• Component folder
• ExecutionEntry folder
• Configuration's folder
• ExecutionEntry
• TestCase folder
• Scratchbook
• TestCase
• TestCase-Design folder
• ExecutionList folder

Tosca's synchronization functionality allows automated test cases to be executed in accordance with the APPLICATION SPEED using processes and events. Synchronization is when the automation tool speed synchronizes with the application speed. You can achieve sync in Tosca using ActionMode WaitOn. Synchronization settings can be modified via the settings - "GO to settings->TBox->synchronization". 

The reusable TestStepBlock usually consists of TestSteps that can be reused in a number of TestCases, meaning you don't have to rewrite as much code. In Reusable TestStepBlocks, business parameters display an OVERVIEW of crucial business information. Business parameters can be USED to set or pass dynamic values in test step blocks. You can create it simply by right-clicking on Reusable TestStep Block and choosing business parameters from the CONTEXT menu. Business parameters can also be manually defined within the module in the following ways:  

• XML elements and attributes in the Payload tab.
• JSON data in the Payload tab.
• Headers in the Headers list.
• Parameters in the PARAMS tab.
• Transport information in requests.
• Response TIME and Status code and in responses.

Model-based testing and risk-based testing are two of the most commonly used technologies in Tricentis Tosca. 

• Model-based testing: Tricentis Tosca uses model-based testing instead of scripting for automation testing. This involves creating a model of the AUI (Application Under Test). A model (the lego blocks can be combined and reused across your tests)  can be used to represent the intended behaviour of an AUT, as well as the testing STRATEGY and the test environment.   It is a simple and codeless approach that is easy for anyone to understand and use.  Whenever a change is made to an application (e.g., adding or removing a field), you need only update the module once. These changes will be synchronized across all of the IMPACTED test cases, saving you time and effort. 
• Risk-based testing: In the BLINK of an eye, defect-filled product releases can disrupt your business processes and damage your brand and customer trust. The problem is, traditional test approaches don't measure business risk as much as they focus on checking the total number of test cases run. The problem can be solved with Toca's risk-based test optimization, which maximizes the risk coverage while minimizing effort. Using this approach, you can reduce the number of tests you don't need by 40%, while increasing your application's risk coverage by 90% or more. In addition, you are able to identify which business-critical functions were successful or failed, enabling you to make faster and better decisions THROUGHOUT the release cycle. 
  As you can SEE in the below diagram, traditional testing approaches only cover 20% of risks and focus on the overall number of test cases run. In contrast, with risk-based testing, the goal is to maximize risk coverage and minimize testing and therefore risk coverage is 80%.