Scribd
Upload
79 views

Laboratory Work Nr.3 Theme: Creating Testcases

This document describes a laboratory work on creating test cases in Jira. It provides tips for writing test cases in Jira, including keeping test cases as open issues and adding a "Testing" status. The document then details the steps taken to create 7 test cases for a website's homepage, including describing test steps and expected results. Images are included of some test cases documenting found bugs. In conclusion, the author notes improving testing skills from reviewing previous work and identifying additional bugs.

Uploaded by

Vasilica Boaghi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
79 views

Laboratory Work Nr.3 Theme: Creating Testcases

This document describes a laboratory work on creating test cases in Jira. It provides tips for writing test cases in Jira, including keeping test cases as open issues and adding a "Testing" status. The document then details the steps taken to create 7 test cases for a website's homepage, including describing test steps and expected results. Images are included of some test cases documenting found bugs. In conclusion, the author notes improving testing skills from reviewing previous work and identifying additional bugs.

Uploaded by

Vasilica Boaghi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 8

Technical University of the Moldova

Software Engeneering and Automation Department

Software Testing
Laboratory work nr.3

Theme: Creating TestCases


.

Report

Done By: Verified by:


Vasile Boaghi Mihai Lungu

Chisinau 2020
Laboratory scope: Create 4-6 testcases with will have number of steps
between 3-6. (test sequence) 
How the goal was achieved:

1. Documentation process:

Test cases are a fundamental part of the software testing process. They
effectively answer the “what” and “how” of testing. That being, what needs
to be tested? And how exactly does the test need to be performed? Writing
them takes time, but if done well, test cases become extremely valuable
artifacts.

Once test cases are written, they need to be stored in an organized way
where they can be referenced and updated in a timely manner. In this
article, we’re going to look at how to write test cases in Jira. This tutorial
will walk you through how to configure Jira to handle test cases and their
results, along with how to view lists of both cases and runs which are
filtered by release. We’ll also look at some of the advantages and
disadvantages of using Jira as a test case management tool.

Tips for Writing Test Cases in Jira

Step 1. Create a “Test Case” Issue — and Keep It Open.

But Jira issues are meant to be pushed to done. That makes it challenging to
rerun or reuse tests. Plus, it’s hard to keep track of all of your testing if
you’re managing test cases as Jira issues. Trying to create test coverage
reports from disparate sources will be difficult.

Step 2. Tweak a User Story to Be a Test Case.

Jira user stories have the same problems that Jira issues have. So, you’ll
still have a challenge if you want to reuse tests. That’s made all the more
difficult by the fact that Jira doesn’t have built-in testing functionality.

2
Step 3. Add a “Testing” Status to Your Jira Workflow.

But you might find yourself moving to a “done” status before you’re
actually done with that test. After all, completing a test is not the same as
being done with a test. 

You could configure a workflow, so a test isn’t “done” before you’re


actually done. But that will add more steps to an already manual process.

1.2 Software used

Zephyr is the #1 selling testing solution. 18,000 customers and 5 million


users across 100 countries rely on Zephyr's feature-rich solutions every
day. Globally, Zephyr's customers benefit from improved productivity,
faster time to market, and dramatic cost savings.

Zephyr for JIRA is a native application that exists in JIRA and brings
quality test management capabilities to any JIRA project. When Zephyr is
used with JIRA, the test can be created, viewed in any JIRA project, and
executed immediately or as part of a testing cycle that may be linked to
other issues. The detailed testing metrics can be tracked via customizable
Zephyr gadgets.

2. Steps for creating a simple test-case

- To create a test case (issue with type 'test'), simply click on the
'Create' button located in the top menu navigation.
- The 'Create Issue' module will appear with the following fields
when creating a test case. The required fields for a test case are
the following:
o Project – The name of the project that the test case is
being placed after creation.
o Issue Type – The issue type for the test case (in this
case, we'll select 'Test').
o Summary – The name/title for the test case.
o Reporter – The name of the individual creating the test
case.
3
- Once the required fields are filled out, users can scroll to the
bottom of the interface and create test steps for the test case
which includes the following information for each test step:
o Test Step – Description of the test step/action that needs
to be performed for this individual step.
o Test Data – Any data that is required for the test step to
be performed.
o Expected Result – The expected result after performing
the actions for this individual step.

3. Creating testcases

First of all, I choosed the HOME PAGE to do the test on it.

And the most obscure bug I saw, was searching functionality.

4
As you can see, in the first image I defined 4 steps in order to reach the
bug, first three steps had status as passed one, but the last one gave an error.
And in the second image, I linked the bug which is related to this test-case.
The second bug is related to flickr post redirection.

5
In the second test-case I practically had done the same actions I did in the
first one, but I added some pictures to some steps.

The third bug, related to facebook/Instagram/twitter/linkedin redirection


fail.

Something I hadn’t done to the previous task, but to this I done, I added a
new bug wich I didn’t find in the first and second lab.

The fourth bug, related to the shopping card label which doesn’t hide
some UI components from the bottom of the page.

6
The fifth bug, wrong redirection from the advertisements.

The sixth bug, related to the men’s accessories and men’s clothing, the fact
that they have different URLs, but one contains the same items as other.

7
The seventh bug, related to scroll problem, it doesn’t work so smoothly.

Conclusion: After this laboratory work, I improved my analyzing skill, also


after I review the first laboratory and second one, I found some bugs that I
missed from the first glance. I found a lot of information about Zephyr,
quick tips to do good test-cases, why they are important, steps for test-
cases.

Webography:
https://www.guru99.com/zephyr-agile-jira.html
https://blog.testlodge.com/how-to-write-test-cases-in-jira/
https://confluence.atlassian.com/jirakb/using-jira-software-for-test-case-
management-136872198.html

You might also like