Log in to the site

1. Open a browser, and go to https://metainfdemo.atlassian.net

2. Your login credentials are:

• Username: minfdemo.developer@gmail.com
• Password: devdem789

Navigate to your Jira project

Once you logged in, navigate to your Website development project, or simply click on this link

Create a Bug

1. Click on the Create button on the top navigation bar.

2. Select Bug.

3. Fill out the fields:

• Summary is required, you can’t create an issue without a “name”.
• We suggest to fill out the other fields like Component, Epic link.
• Eg. if you add the component Frontend, your user will be the Assignee of the issue automatically!

View issues

1. On the left side, click on the Kanban board, or simply click on this link

2. Your newly created bu will be on the Backlog

• If you click on it, you can see more details about your issue
• Feel free to drag & drop the bug to any other statuses.
• You can check the issues in the timeline view. On the left navigation bar, click on the Roadmap icon, or simply click on this link
• If you haven’t filled out the Epic link, you won’t see it!

You can learn more about Kanban projects here

Create a test case

1. On the Kanban board, click on your card/issue.

2. At the Zephyr scale section, click on the Create a new test case, or simply click on the + sign.

3. When you create a new test case, you can work on different tabs.

• Details tab: here you can add some details about your test. You have to give it a name, so click there and add a name for your test case! You can add more details like priority or estimation time about your test case.
• Test script tab: Here you can set up the steps that you have to follow and check when you execute the test. There will be three columns for every step:
• STEP: You can add description here what needs to be done
• TEST DATA: if the step requires a test data like credentials to login, or a query to run in your database, you can add it here.
• EXPECTED RESULT: you can add what should be happening. Depending on the result, that step could pass or fail.

4. Create a three-step process, something easy like:

STEP

TEST DATA

EXPECTED RESULT

Open login page

Login page loads

Fill out fields

Username: minfdemo.developer@gmail.com

Password: devdem789

Password should transform to * characters

Click on the login button

The user logged in!

Also, you can check two other tabs:

• Execution: right now it’s empty, but we will get back to that after the first execution!
• Traceability: you can see, the “original” Bug is already linked to this test case.

Execute a test

1. Go back to your Bug on the Kanban board.

2. Click on the Start a new Text Execution (on the little “play” icon)

3. Click on start

4. Follow the test script. You can add a result at the right end of every step with the different icons:

• the first icon is PASS
• the second icon is FAIL
• the third icon is BLOCKED

5. Check the overall result at the top of the page!

• If anything fails, the test result will be fail.
• If anything blocked, but there are now fails, it will be blocked.
• If everything passes, it will be pass.

Re-do the tests in different ways! So follow these steps from 1-4., and at 4, try different outcomes!

After you have done some re-executions:

1. Go back to your bug on the Kanban board.

2. Click on your test case.

3. You can check the execution history!

Click here to learn more about test cases

Create a bug right from the test step

If your imaginary test failed, you have the option to create a bug directly from the affected step, and it will be linked already with the new issue.

1. Navigate to your failed test step.

• You can do it via the “original” ticket
• Navigate to your ticket (eg. by Search, Kanban board)
• Click on the test in the Zephyr section
• Click on the failed test execution’s key (first column)
• Navigate to your failed test step.
• via Zehpyr Scale on the left navigation bar.
• Navigate to your failed test.
• Click on the Execution tab.
• Click on the failed test execution’s Key (first column)

2. At the affected step, at the right end (where you set the step failed), you have the last icon, a little cog.

3. Click on the cog icon, than click Create issue

4. Select the issue type Bug, fill out the create form.

5. Go back to your Kanban board. And you will see, your new bug is already in the backlog!

6. If you click on the newly created bug, you can see that the test has been already linked to this issue.

Run a test cycle

1. Click on Zephyr Scale at the left navigation bar, or simply click here

2. On the right-hand corner, click on Cycles, or simply click here

3. Click on the + New test cycle button.

4. On the Details tab, type a Name for the cycle.

5. On the Test Cases tab, click on the + Add test cases

6. Here, add some test cases. Select them and click on Add

• what you have created in the previous steps and/or
• any previously created test case
• Click on Save
• Click on Back

Your new test cycle is ready to go!

1. Simply select it, and click on Run

2. On the left side, you can select the different test cases. Select the first one!

3. Execute the test steps. You can try different results here as well.

4. Select the next one, execute the test, next one, execute test,… till every test has a result.

• On the right-hand corner, click on Back
• You can check the overview results of the test cycle.

Of course, you can re-run the test cycle any time!

You can learn more about test cycles here

Reports about tests

1. Click on Zephyr Scale at the left navigation bar, or simply click here

2. On the right-hand corner, click on Reports, or simply click here

3. Click on Test Execution on the mid-left side of the page

4. Click on Test execution results (summary)

5. Click on Generate button

You can see that the report is generated about the test executions.

You can generate almost 30 different reports with Zephry scale, feel free to try them. More on reports here