Writing Cases

AIO Tests allows you to create a test case with the click of a button. Whether you want to test a specific functionality or feature or want to verify compliance with a specific requirement, the test management tool lets you do it effortlessly.

In this documentation, you’ll understand:

Steps to Create a Case 

Step 1: To create a case, simply click on the Create option in the top bar menu and select Case from the drop-down list. 

Step 2: Once you click on the Case option, the Create Case modal window will appear on the screen where you can enter the below details under the Details tab. 

Details

  • Title: It is a mandatory field where the user needs to give a relevant name to the Test Case.

  • Description: The user can use this field to describe the objective of the case.

  • Pre-conditions: Users should mention the prerequisites that must be fulfilled before executing the test. They can also specify the setup needed for a Case to be executed successfully.

  • Folder: The folder drop-down shows the folder structure for cases.

If the user clicks ‘Create Case’ from All Cases or from any other screen then it will pre-populate with “Not Assigned”. However, if the user clicks “Create Case” from within a folder then it will pre-populate with the selected folder’s name. The test case will then be created in the selected folder.

  • Owner: The logged-in user’s name is pre-populated as Owner.

Users can change owner only if the status is other than Draft.

  • Priority: Prioritization ensures that the most important test cases are executed first. By default, priority is Not Assigned.

  • Status: AIO Tests has 4 default statuses for Test cases- Draft, Under Review, Published and Deprecated. 

  • By default, Draft is selected which means a case is a “work-in-progress”.

  • The Test cases in Draft (Status) cannot be owned by other users.

  • Type: AIO Tests supports - Unit, Integration, Functional, API, Performance and Security types. Users can use these to categorize the cases.

  • Component: With AIO Tests, components that were created in the Jira project, become available while creating a case. This feature helps to categorize and organize cases.

  • Release: Releases that were created (based on the delivery dates) in the Jira project become available while creating a case.

  • Estimated Effort: The expected time to complete the execution of the case can be entered in the given format Xh Ym.

  • Tags: Tags are keywords that let you classify cases in a more flexible and informal manner. They help you in searching.

Jira Requirements

AIO Tests allows you to map cases to Jira requirements for creating traceability while creating a case. 

Attachments

While creating a case, users have the option to attach any necessary files that may help the case review, automation or the steps to be written.

Automation

Currently, there are three attributes that support Automation.

  • Status: Users can specify the automation status- Manual, To be Automated, In Progress, and Automated. It can be used as a workflow too.

  • Owner: The user responsible for automating the case can be specified here. This field can be different from the Case Owner field.

  • Automation Key: The automation key helps to match AIO Tests cases with an automated case. 

Step 3: Click on the Add Steps option located at the top right corner of the Create Case modal window.

Step 4: On the Steps tab, users have the option to create a Classic case (step-by-step) or a BDD case (Gherkin).

Steps

  • Classic Case: This method allows users to add Steps along with Data and Expected Results to the case. Steps are necessary for the execution of a case. 

While writing steps, a few functions can be done like: 

  1. Add new step: Clicking the plus (+) symbol or clicking the ‘Tab’ key while on the ‘Expected Results’ field adds a new line below the current step, allowing the user to enter steps to execute the case. 

  2. Attach File: By clicking on the vertical ellipsis button, the user gets an option to add attachments at the step level (in addition to the case level). Users can either paste an image or upload documents. Click here to find more details. 

  3. Duplicate a step: Clicking on the vertical ellipsis button gives the user an option to duplicate a step, which copies the data from the step above into the step being created. Click here to find more details. 

  4. Copy Steps: By clicking on the vertical ellipsis button, the user gets an option to copy steps already written for other cases into the case they are on. Users can also add steps from cases of other projects that they have access to. Find more details on the Copy steps.

  5. Link another case: Clicking on the vertical ellipsis button and then clicking the link symbol changes the current step into a step with a linked case allowing the user to search for an existing case by key or title and link it to the case being created. Users can also link cases from other projects that they have access to. This promotes reusability across cases and projects and saves time and effort. Find more details here.

  6. Delete a step: Clicking the delete symbol will allow the user to delete a particular step. The step isn’t deleted permanently but is marked for deletion. The actual deletion takes place with the click of Save Steps. 

  • BDD Case: By clicking on the BDD/Gherkin option, users can add Steps in the Gherkin language using keywords such as Given, When, And, Then, But, and *. Find more details on BDD cases

Step 5: Once you complete the steps, click on the Save and Close button. 

Data Parameterization/Examples-Based Cases

Users can choose to parameterize their cases and run them with several datasets by clicking on the Datasets icon while editing a Case.

Creating Datasets/Examples

In BDD cases, Scenario Outlines can map to such Example Based cases.

Click on the Plus icon to Add New Parameters.

Once the required parameters have been created, datasets can be created by clicking on the row cells.

Using Parameters in Steps

To use parameters in steps, the parameter names need to be enclosed in angular brackets: <>

For classic cases, the user will be shown a prompt with a list of parameter names.

For BDD cases, the user can use the parameter in a similar way. However, there will be no prompt for parameter names due to an auto-complete dropdown coming for existing steps.

Data Sets in Linked Cases

If a case is linked to another case, datasets cannot be created for such cases.

Cases that have datasets defined cannot be linked to cases and would show the linking button as disabled.

For further queries and suggestions, feel free to reach out to our customer support service via help@aiotests.com