Creating Test Cases in OLETS
Before creating an OLETS Test Case, it is recommended that you review the Acceptance Criteria from the Functional Specification you will be testing. You want to ensure first that the Acceptance Criteria statement is fully covered by the individual Test Case, or by the group of Test Cases you wish to create. Second, you may want to use the Acceptance Criteria section of the Functional Specification document as a checklist for creating Test Cases, crossing through each acceptance criterion as you create the Test Case. This will help to ensure that all the criteria are fully covered by your OLETS Test Cases.
If you are only testing Bug/Defect items, you will create as many Test Cases as there are Bug/Defect issues to test. As with an individual acceptance criterion, it may be the that a single Bug/Defect necessitates more than one test. If so, a Bug/Defect will receive as many Test Cases as necessary, all linked by the "Tests/Tested By" link (covered in detail in the Linking section below). This is only very rarely the case.
Fields
In this section, you will find an explanation of all the fields currently in use on an OLETS Test Case, in the order in which they appear on the screen.
Summary
The "Summary" field contains the title of the Test Case itself. It allows for a fairly lengthy statement, but it's generally better not to use all the space given, as a long title can result in hard-to-read search results. The title of each Test Case should be a very brief explanation of what is to be tested, usually a contraction of the Acceptance Criteria statement upon which the Test Case is built.
Components
The "Components" field will contain the name of your Functional Specification team. If you are not a member of a Functional Specification team, you will enter the name of the FSPEC team whose issue you are testing. If you have any difficulty identifying the appropriate FSPEC component to enter here, your Team Lead or the QA Team will be able to help you figure out which option to select.
Fix Versions
This field was intended to contain the Milestone Release version to which the Test Case belongs, but is no longer being used and has been marked for removal.
Parent Jira
This field will contain a link to the Story which serves as the Parent Issue for this Test Case. For more information on how to use this field, see the "Linking" section below.
Assignee
The "Assignee" field is used to assign the Test Case to a Jira user. Unless you are the lead tester for a team and need to delegate Test Cases to other members, you will enter your own name here.
Description
The "Description" field is the main body of the OLETS Test Case.
Acceptance Criteria Statement
The first thing to be added to the "Description" field will be the Acceptance Criteria statement that will be tested by this Test Case. Briefly summarize what functionality this Test Case is meant to evaluate; for example, "The purpose of this test is to ensure that a user can fully receive a single, non-serial item-in-hand."
Steps
The detailed steps for the testing process will also be included in the "Description" field. For detailed instructions on creating accurate, reliable test steps, please see (Wiki Article...)
Attachment
This field allows you to add attachments, and can be disregarded. You will not need to add attachments to a Test Case immediately upon creation. For instructions on using this field, please see How to Attach Files to Jira Issues.
Reporter
This field reflects which Jira user created the Test Case. It will default to your own username, and requires no editing.
Linking
There are two main linking methods, detailed below, which will be used in OLE QA testing: linking to the Story issue which serves as the parent Jira issue, and linking to the specific issue - Task or Bug/Defect - to be tested.
Parent Jira Field
This field should contain the Jira issue ID of the Story issue to which the Functional Specification being tested is attached. The Jira issue ID will have the format OLE-###, where ### is the issue's ID number. You can find the issue ID in the title info, displayed at the top of a given Jira issue, or by examining the URL for that issue. The Jira issue ID is highlighted in blue in the screenshot below.
Tests/Tested By Link
The "Tests/Tested By" link cannot be established until after Test Case creation. Once you do create the "Tests" link, the "Tested By" link will also be established on the Task or Bug/Defect to which the Test Case is linked.
In the menu bar near the top of the Test Case, click the "More Actions" drop-down, and select "Link" in the menu that appears (pictured below).
The Link dialogue box will open (pictured below). You should select "Tests" from the drop-down menu immediately to the right of the words "This issue." In the next box down, you should enter the issue id of the Task or Bug/Defect you will be testing. You can use the "Comment" box to include a comment, but it is not necessary at this point. The last thing to do is click the "Link" button. The Link dialogue box will disappear, and a two-way link will be created between the Test Case and the target issue.
