Versions Compared

Old Version 36

changes.mady.by.user Unknown User (lfir)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (tdda)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
UI Steps
UI Step

...

Creating a Manual Test


Info

Manual Tests are user-assisted tests, listing an assortment of guidelines the user must follow, and the results that such behavior is expected to accomplish. If the actual test result matches the expected test result, the test is considered as passed; otherwise, it is marked as failed.

"Manual" is the default Test Type in which Tests are specified with an ordered list of steps.

By default, each Test Step has the following fields:

  • Action* - the action to be reproduced by the tester.
  • Data - any data the related step requests (e.g., login credentials) to be used by the tester 
  • Expected Result - the behavior the step should accomplish. 
  • Attachments - external files that provide additional information related to the corresponding step. Attachments can only be added or removed in the Test Issue view page.

Only the Action field is mandatory. All other default fields are optional.

The order by which steps are defined is important. Users must start executing Test Steps in ascending order.



Click the Create Issue at the top of the screen to open the Create Issue dialog box / page.

Image Modified

Select the  Project and on Issue Type, select Test.

...

Image Added

...

On the Test Details tab, select the Test Type and complete all appropriate fields;

Select the Test Type as Manual and feel free to add

...

steps.


  

...

From the requirement issue screen

Info

To proceed as described below your admin as had to configure globally Requirements and Defects and Requirement coverage as been enabled for your project.

If you are not able to see it reach out your Jira admin as this needs to be set up by a Jira administrator.

Go to a requirement in your project (e.g Story) and click "Create new Test" just like highlighted in the picture below.

Image Removed

Select the  Project and on Issue Type make sure you have Test selected.

Image Removed

    And follow the same steps already described above to fully define your test.

Tip
titlePro Tip

The concept as you probably already figure it out is the same as  Epics and Stories.

Image Added 

Tip

If you want to understand all the details regarding Manual Steps and how to interact with them, visit Test Steps for Server/DC Xray Documentation

...

Clone

Info

Cloning a Test issue creates a new Test with all the information of the cloned Test, except its executions. Therefore, the cloned issue will not be associated with any Test Execution issue.

Select More > Clone. The Clone Issue screen will appear.

Image Removed

You can edit the clone Test's Summary if you wish.

  - If the test contains links to other issue(s), you can select whether or not to include the links in the new clone test.

  - If the test contains sub-tasks, you can select whether or not to create the sub-tasks in the new clone test.

  - If the test contains attachments, you can select whether or not to include the attachments in the new clone test.

Click Create.

Image Removed

UI Step

Extra

...