...
- Header: This displays the project to which this test belongs, the issue key of the test and its one-line Summary
- Toolbar: This toolbar allows you to access often used functionality
- Edit: This button takes you to the edit mode of a test where many of the fields can be edited. This is very similar to creating an issue. Please note that Test Details have to be edited from this View Issue screen.
- Clone: 'Cloning' (copying) a test allows you to quickly create a duplicate of the test within the same project. The clone test is a replica of the original test, containing the same information stored in the original test— e.g. Summary, Labels, Components, Test Details, etc. except for Test Execution details.
A clone issue is a separate entity from the original issue. Operations on the original issue have no effect on the clone issue and vice versa.
Link: Allows you to link another issue or a web link to this test, typically a requirement or a story or an epic.
Add to Test Cycle(s): Under the "More Actions" drop-down, this allows you to add this test to an existing Test Cycle. That then also shows in the Test Executions section below.
- Create sub-task: You can create a new sub-task issue for the test case by using the "More Actions" drop-down.
- Attach Files: You can attach one or more files to a test (Note: Your JIRA Administrator must have enabled file attachments. You will also need "Create Attachments" permission in the appropriate projects).
- Attach Screenshots: You can attach a screenshot to a test if your Administrator has configured JIRA and your permissions correctly.
- Comment: Adding a comment to a test is a useful way to record additional details about a test, and collaborate with team members. Comments are shown in the Comments tab of the Activity section.
- Execute: This button allows you to immediately execute this test, either in an ad hoc manner or as part of a Test Cycle.
- Details: This section is almost exactly like the one for any other issue-type but note the following:
- Fix Version/s: This field is the one that is used to organize tests i.e. make it belong to a Version.
- Status: By default, the workflow statuses for tests are turned off. Modify workflow options to turn it on.
- Resolution: Just like Status, these do not apply until workflow is turned on
- Description: this section is exactly like the one for any other issue-type and can be useful for adding a high level description or pre-conditions for the test.
- Test Details: This section allows you to enter detailed test steps, any accompanying test data and expected results. Test steps can be reordered, cloned or deleted.
- Test Executions: This section shows the details of all scheduled and previous executions of this test. It also allows you to execute a test.
- Attachments: This section is exactly like the one for any other issue-type
- Issue Links: This section is exactly like the one for any other issue-type
- Activity: This section has a Test Details History tab that shows all the changes made to the test with respect to its step, test data and expected results.
...