Test Case Management
The heavy lifting is already done by creating reusable web elements, actions, and assertions. Now all you need to do is create a test case by combining these elements, actions, and assertions. The test case builder is a simple and intuitive interface that allows you to create and manage test cases with ease.
Test Cases
Test Cases are structured sequences of actions and assertions that verify the expected behavior of a web application. Each test case represents a unique scenario to validate functionality, ensuring that critical workflows function as intended. Test cases can include interactions like filling forms, clicking buttons, selecting options, and more, with assertions to perform validation where necessary.
Creating a Test Case
To create a test case in tacl.io:
- Navigate to the Test Cases section.
- Click on Create Test Case.
- Define the test case Name and Description to outline the purpose and context.
- Click Create to add the test case to your project.
This will take you to the test case builder, where you can add actions and assertions to build the test case.
Editing a Test Case
You can edit existing test cases to add, remove, or modify actions and assertions:
- Navigate to the Test Cases section.
- Select the dropdown menu next to the test case you want to edit and choose Update Testcase.
- This will open the test case builder, where you can adjust the steps, update assertions, or modify settings as needed.
Test Case Builder
The Test Case Builder provides a user-friendly, visual interface for creating and managing test cases in tacl.io. It includes the following components:
- Workflow Builder: Define and structure the steps in your test case.
- Step Configuration: Configure details for each step, including:
- Start URL
- Action Configuration
- Assertion Configuration
Workflow Builder
The Workflow Builder allows you to add, configure, and remove steps in your test case. Each step can include actions and assertions that define the behavior and validations of the test.
- Adding Actions: To add an action, click the + button and select Add Element Action. Configure the action settings by selecting the element and specifying the action.
- Adding Assertions: To add an assertion, click the + button and select Add Element Assertion. Configure the assertion by selecting the element and setting the expected outcome.
- Removing Steps: To remove a step, click the trash icon on the step card.
Step Configuration
Each step in the workflow can be customized with the following configurations:
-
Start URL
- Define the starting URL for the test case. The test execution will begin at this URL.
-
Action Configuration
- Action: Choose the element and action to be performed at this step.
- Continue on Failure: Decide whether to continue to the next step if this action fails.
- Timeout: Set a custom timeout for this action, overriding the default.
- Save: Apply the action settings to save changes.
-
Assertion Configuration
- Assertion: Select the element and the assertion to validate at this step.
- Continue on Failure: Choose whether to proceed to the next step if this assertion fails.
- Timeout: Set a custom timeout for this assertion, overriding the default.
- Save: Save the assertion settings.
Additional Configuration
- Editing Test Case Details: To edit the test case’s name or description, click the Edit icon next to the test case name.
- Saving the Test Case: After making changes, click the Save Test Case button to apply updates.
Elements, actions and assertions are reusable components that can be shared across multiple test cases. This allows you to create a library of common interactions and validations that can be easily added to new test cases. When you edit an element, action, or assertion, the changes will be reflected in all test cases that use that component.
The Test Case Builder simplifies test case management, allowing you to structure, customize, and execute complex workflows with ease.
Once you have created or updated a test case, you can are ready to spin up a test run to verify the application functionality. To learn more about running test cases, refer to the Run Test Case guide.
Best Practices for Test Cases
- Define Clear Actions and Assertions: Ensure each step has a clear purpose and validation.
- Use Stable Identifiers: Use identifiers like Test Ids, Name, or Role whenever possible to make tests resilient to page changes.
- Limit Test Case Scope: Keep test cases focused on specific scenarios to make troubleshooting easier and execution faster.
Test cases in tacl.io provide a flexible and powerful framework for creating end-to-end automation, with customization options to match various testing needs.