What is the primary way Tosca supports data-driven testing?

• A. Binding steps to Data Sheets or external data sources.
• B. Hard-coding values in the test steps.
• C. Relying on manual data entry for each run.
• D. Using only static assertions.

Answer: (A)

Data-driven testing is about running the same test with different input data without changing the test logic. In Tosca, this is implemented by binding test steps to Data Sheets or external data sources. You map each parameter or input in a test step to a column in a data sheet, and each row becomes a separate test run. This separation of data from the test steps lets you reuse the same test with many data values, making it easy to validate how the system behaves under various inputs and scenarios.

Hard-coding values locks you into a single set of inputs, so you lose the ability to test multiple data combinations without editing the test. Relying on manual data entry defeats automation, and static assertions don’t provide varying inputs to exercise different paths. Binding to data sheets or external sources is what enables scalable, automated data-driven testing in Tosca.