...
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 criterion 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 article Linking in Jira. The "Parent Jira" field is not required immediately upon Test Case creation, so it can be left blank for the time being. It does, however, need to be filled out prior to the Test Case being passed, failed, or assigned to another user. |
|---|
...
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
...