What is a Control?

What is a Control?

• A. A test script
• B. A browser setting
• C. An element in your application that the test can interact with
• D. A report template

Answer: (C)

A Control is the element in your application that the test can interact with—things like a button, an input field, a checkbox, or a link. It’s the actual UI piece you drive with actions such as click, type, select, or verify, so the test can operate the application in a way a user would. By focusing on these UI elements, Tosca can reliably locate and manipulate the app across runs and data sets. This is why the correct idea is that a Control is an element in your application that the test can interact with. The other options aren’t about interacting with the UI: a test script is the sequence of steps, a browser setting is an environment configuration, and a report template defines how results are shown.

A Control is the element in your application that the test can interact with—things like a button, an input field, a checkbox, or a link. It’s the actual UI piece you drive with actions such as click, type, select, or verify, so the test can operate the application in a way a user would. By focusing on these UI elements, Tosca can reliably locate and manipulate the app across runs and data sets. This is why the correct idea is that a Control is an element in your application that the test can interact with. The other options aren’t about interacting with the UI: a test script is the sequence of steps, a browser setting is an environment configuration, and a report template defines how results are shown.