Test Steps
Defining test steps ensure that test cases are well-defined and instructions are clear. Let's dive into this feature - details below.
Test steps, a vital part of test cases, allow QA teams to define what aspects make up a whole test case. They help break down the whole item into manageable sections, which ensures that test case covers all of the requirements linked.
Each Test Step in ATM consist of 3 specific text fields that can be filled out by testers - Actions, Data and Expected Results. Each text within the fields can be formatted to user's likings. Additional items such as action items, links or tables can also be added.

The users can also create versions of Test Steps - details can be found here.
Customizing Test Steps

The layout and visibility of Test Steps can be managed through the Testing hub. This allows administrators to align the step structure with the specific needs of the testing team.
This option is visible only for the Administrators. If users do not see it within the Testing hub, they may not have sufficient permissions within the app.
In order to access the configuration settings, go to Apps> Testing hub> Test steps. There, administrators can manage the three default fields: Action, Data, and Expected results. Users can change the field visibility or order:
Each field features a toggle to show or hide it.
To ensure data can still be recorded, at least one field must remain visible at all times.
The display order of fields can be modified using a drag-and-drop interface.
Display consistency
Changes made in the Test Steps configuration are applied consistently across three primary areas:
Test Case Panel: The Test Steps section within the Test Case issue view.
Full Screen View: The expanded editor for Test Steps.
Test Case Execution (TCE): The execution view where steps are marked as passed or failed.
Hiding a field does not delete the underlying data. If a field containing information is toggled "OFF" and later re-enabled, all previously entered data will remain intact and visible.
Creating and editing Test Steps
In the work item view
Test steps can be added by users directly in the Test Case work item view. In the Test Case of choice, the user can add the steps in the Test Management panel by clicking Add step. Every new added step is listed beneath the previous one and gets assigned a number respective to the order of steps in the list. The steps can be edited directly in the work item view.

In the expanded Edit view
There is also a possibility to add and edit steps in an expanded window, if that's user's preference. In order to access it, click on the expand window button. The outlook and functionalities are the same as in the work item view.

Duplicating Test Steps
Users can duplicate steps by selecting the duplicate button at the bottom of each step. The button is accessible in the expanded step view.

Deleting Test Steps
Test Steps can be deleted individually or in bulk. In order to delete an individual step, click on the More actions menu (three dots) and select Delete. To delete steps in bulk, click on the trash icon at the top of the steps list.
Any modifications of Test Steps do not affect already existing Test Case Executions, as they are a snapshot in time of a Test Case.
Test Steps views
Within the steps, the fields can be configured to be viewed either as a list, where fields become rows, or a grid, where each field is a column.

Whether the user prefers to view all of the details at once or look at the specifications one step at the time, the Test Steps view overall can be adjusted. Details of steps can be collapsed or expanded individually with arrows in the right corner. If the expansion or the collapse needs to happen in bulk - the arrows in the Test Management section can help with doing so.

The order of the steps can also always be changed - the users can either use the arrows at the bottom of each step to switch them individually, or drag the step of choice and drop it in the needed order.

Not seeing our Panel? Select Apps, on the left-side menu, and choose Testing Hub.
Last updated
Was this helpful?
