An Action may define Input parameters to avoid hard-coded data in the logic. For example, Login to QBank Action may define Username and password as parameters, rather than hard-coding these values in the logic statements.
When this Action is used in a Scenario (as a Step), the Scenario provides values for these Parameters.
A Scenario, in fact, consolidates the input parameter requirements for all the steps involved in the flow.
Scenario steps may require inputs, in the form of parameters.
You provide values for these input parameters in Test Cases tagged for the Scenario. Each Test Case is one full collection of data values for all the parameters that a Scenario’s steps need.
For a given Scenario, you may create multiple Test Cases with different data permutations.
Examples of test cases for "Verify Funds Transfer" Scenario could be:
- Verify transfer with maximum transaction value
- Verify transfer to an external account
- Verify transfer with a future date
A Scenario can define multiple test cases, each test case providing values for all step parameters in the Scenario. Scenario effectively achieves data-driven testing.
Comments
0 comments
Please sign in to leave a comment.