| Anchor | ||||
|---|---|---|---|---|
|
| Center |
|---|
|
...
Before creating an OLETS Test Case, it is recommended that you review the Acceptance Criteria section 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 article Linking in Jira). This is only very rarely the case.
| Anchor | ||||
|---|---|---|---|---|
|
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.
...
List of Fields
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 Version/s | This field |
|---|
...
is for the version of OLE in which the functionality to be tested will be established (e.g., "OLE 1.0", "OLE 1.5", "OLE 2.0"). Although this field can contain multiple values, Test Cases should only ever receive one value in this field. This field should generally be the same as on the Enhancement (PP) the Test Case was created from. | |
Parent Jira | This field will contain a link to the |
|---|
...
Enhancement (PP) which serves as the Parent Issue for this Test Case. |
...
Assignee
...
Assignee | The "Assignee" field is used to assign the Test Case to a Jira user. This field will default to the user who created the Test Case, and is generally only used by the QA Team and Testing Coordinators. |
|---|---|
| Co-Assignee/s | This field allows additional assignees to be designated, and is only rarely used. It can safely be ignored during test creation. |
Description | The "Description" field is the main body of the OLETS Test Case. This is where you will enter the statement of purpose and descriptive testing steps. |
Attachment | This field allows you to add attachments, and can generally be disregarded. You will not need to add attachments to a Test Case immediately upon creation. For instructions on using this field, please see the article Attaching Files in Jira. |
Description
...
Components
Acceptance Criteria Statement
...
The detailed steps for the testing process will also be included in the "Description" field. The steps you include should be detailed enough for another user to follow. It is best to write out general steps, try them yourself in the OLE Test Environment, take notes, then come back and modify the steps accordingly.
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 the article Attaching Files in Jira.
Reporter
This field reflects which Jira user created the Test Case. It will default to your own username, and requires no editing.
| Center |
|---|