A TestStep is the smallest unit used to build a Tosca test. It represents one discrete operation you perform in the application, which can be an action (like clicking a button or entering text), a verification (such as checking that a value is displayed or a condition is met), or a data operation (like reading or writing data). Because it captures a single, focused operation, it’s the most precise description of what a TestStep is. Tests are composed by arranging multiple of these steps in sequence to model a complete scenario. The other concepts describe larger ideas: a collection of TestCases is a higher-level grouping, a data sheet supplies input data for data-driven tests, and a module is a reusable component that steps can invoke but is not itself a single operation.

Dynamic data sources are values resolved at run time, so each execution can receive different input. Static data sources store fixed values in the data set that do not change from one run to the next. This distinction means the correct description is that dynamic data changes per run, while static data remains fixed in a data set. Use static data for repeatable, reproducible tests and dynamic data when you want to test with varying inputs across runs (like unique IDs or time-based values).

ActionMode Constraint is used to pinpoint a single item within a list by providing a combination of values that uniquely identifies that item. When you’re working with dynamic lists or grids where many rows share the same structure, applying a constraint based on fields within the item (for example, a product name and code) lets Tosca target the exact row you want. This ensures actions are performed on the correct item during an ActionMode interaction, rather than relying on position or generic locators. It isn’t about inserting data, verifying a value, or waiting for a property; those tasks are handled separately, while the Constraint guarantees you’re addressing the right item by the content values.

The concept being tested is knowing the exact name of Tosca’s Chrome integration. The correct name is the Tricentis Automation Extension for Chrome. This is the official Chrome extension provided by Tricentis to enable Tosca to automate web tests in the Chrome browser. The other options do not match the actual product name used by Tosca for this plug-in, so they aren’t the recognized extension you install and use with Tosca.