It is important to know how a Test Case is structured so that you can use it efficiently. It is advisable to get used to the following terms for easier understanding of future articles.
Test Case Key: Once a Test Case is created it is automatically assigned a unique ID number commonly referred to as a Test Case key.
Step ID: The first column you will find in the Test Script tab is Step# known as a Step ID. A Step ID is allocated to each Test Step by default.
Headline: The Headline summarises the purpose of the Test Case.
A Test Case is structured into 3 parts, i.e. Main, Test Script and Test Run.
Clicking on a Test Case Key or the Headline will open it in a new tab.
Main: Your Test Case will always open in the first tab which is Main. On top of the page, you can see the user’s journey to the page in the form of breadcrumb. However, the main purpose of this tab is to capture the Description of the scenario. You can add additional details related to the Test Case in the Description box below the Headline.
Moreover, you can also manage all your Test Case Properties such as Type, Priority, Sprint, Labels, Assignee.
Any changes made to the Test Case Properties will prompt the user to save changes at the top right of the screen before proceeding.
You can also Link Test Folders and Jira Issues and add Attachments from the Main tab.
Test Script: The second and the most important tab within the Test Case. This is where you add your Test Script by breaking it down into Test Steps. Add Step wise details, Test Data and Expected Results to articulate your Test Case as accurately you can. These steps are crucial for your Test Execution.
Test Runs: The third and the final tab is the Test Runs tab. You will find all the Test Runs associated with the given Test Case here along with the Date and Time of Execution and the Test Result. You can filter the Test Runs based upon the Test Results, Release versions as well as Test Environments.
You can directly navigate to the desired Test Runs by clicking on the respective Test Run Key.