Automation

TOSCA Interview Questions

4.9 (1296)10,496 learners20 lessons40m

Curriculum

Topic

01 - What is Tricentis Tosca, and what does model-based, scriptless test automation mean1:54
02 - What are the main components of Tosca (Commander, XScanModules, TestCase-Design, Execution, API Scan)1:46
03 - What is Tosca Commander, and what is it used for1:56
04 - What are the standard sectionsfolders in a Tosca workspace (Modules, TestCases, Execution, Requirements, TestC2:00
05 - What is the difference between a single-user and a multi-user (common repository) workspace1:47
06 - Why do enterprises choose Tosca over script-based tools like Selenium — what's the maintenance advantage at sc2:02
07 - What is Tosca's risk-based testing, and how does it help when you can't run every test case2:02
08 - What is a Module in Tosca, and how is it created by scanning an application1:54
09 - What is the relationship between Modules, ModuleAttributes, and TestSteps1:56
10 - Why is the model-based approach low-maintenance — if a UI screen changes, what do you update2:07
11 - What is XScan, and how does Tosca identify and steer UI controls2:09
12 - What is the difference between a TestCase, a TestStep, and a TestStepValue1:53
13 - What are the ActionModes in a TestStepValue (Input, Verify, Buffer, WaitOn, Constraint), and what does each do2:06
14 - How does Tosca handle API testing with its codeless, model-based approach2:04
15 - What is the ScratchBook, and why should it only be used for temporarydebug execution1:50
16 - What is an ExecutionList, and how does it differ from the ScratchBook1:55
17 - Where are execution results stored permanently, and how do you view logs and reports2:11
18 - What is the difference between the Execute and Debug run options1:57
19 - What are the error types Tosca reports (verification failure, dialogdialogue failure, user abort)2:00
20 - What is a Buffer (and XBuffer), and how do you pass a value captured in one TestStep into a later one2:10