A Test Case consists of steps and may contain single or multiple tasks. Each step contains an action along with its associated objects and parameters. Define the sequence of the steps in a test case that resemble the flow of a test scenario. You can add test data as per the requirements.
A test case determines whether the application under test meets the defined specifications under the given set of conditions or variables. Test cases are also created to validate if an application meets the business and functional requirements.
Before you create a test case, create a test scenario or select from available test scenarios.
A Test Case consists of steps, where each step contains the following:
- Object: If a step executes on an UI object, then the object name is added.
- Action: Qualitia has defined action which you can use.
- Parameters: The input and output values associated with actions.
A Test Case Editor screen contains buttons that you can use to add steps or execute a test case.
The following table shows the description of each button.
| Button | Button Name | Description |
|---|---|---|
| To import a task. Select a step in which you want to add a task. | ||
| To remove a task from the test case | ||
| To add a step that is not part of any task. | ||
| To remove a step from the test case. Select the consecutive steps and click | ||
| To insert a conditional statement. | ||
| To move up a selected step. | ||
| To move down the selected step. | ||
| To start web recording on a web application under test. Note: If you have already dry run a test case, you cannot record in the same session. You need to close the browser, open the test case, and then do the recording. | ||
| To start web recording on a mobile application under test. Note: If you have already dry run a test case, you cannot record in the same session. You need to close the browser, open the test case, and then do the recording. | ||
| To insert test data. For more information, refer to Adding a Test Data. | ||
| To dry run the test case. For more information, refer to Dry Running a Test Case. | ||
| To debug a test case. For more information, refer to Debugging a Test Case. | ||
Related topics
| Child pages (Children Display) |
|---|