Scribd
Upload
37 views7 pages

Laboratory Work nr.4 Theme: Creating Test Cycles

The document describes creating test cycles for laboratory work. Two test cycles were created: a regression cycle including main site features and a smoke cycle for basic features. Tests were added to the appropriate cycles and an CSV file with test execution data was generated. Creating test cycles allows tests to be logically grouped and executed in a structured manner to track progress.

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
37 views7 pages

Laboratory Work nr.4 Theme: Creating Test Cycles

The document describes creating test cycles for laboratory work. Two test cycles were created: a regression cycle including main site features and a smoke cycle for basic features. Tests were added to the appropriate cycles and an CSV file with test execution data was generated. Creating test cycles allows tests to be logically grouped and executed in a structured manner to track progress.

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/ 7

Technical University of the Moldova

Software Engeneering and Automation Department

Software Testing
Laboratory work nr.4

Theme: Creating Test Cycles


.

Report

Done By: Verified by:


Vasile Boaghi Mihai Lungu

Chisinau 2020
Laboratory scope: Create and divide previously created tests (lab 3), in test
cycles. Create at least 2 cycles (regression and smoke). Execute all test
inside created cycles. All tests should have corresponding statuses with
comments and screenshots attached. Generate an .csv file with test
execution cycles. Attach generated .csv file to same email with report.
 
How the goal was achieved:

1. Documentation process:

Planning Test Cycles and executing tests as part of those cycles is very
powerful yet easy to set up.
Based on your Test Process, you could have a very simple flow where you
could create and execute tests in an ad hoc manner, but if you have any
basic execution planning in place or have a more elaborate structured test
process, then planning your test execution ahead of time is important. Test
Cycles are used to set up and execute tests in a structured manner. This
allows tests to be grouped logically and executed in a structured fashion. It
also allows for the tracking of progress and reporting of quality metrics.
The "Ad hoc" cycle is default in every version. If no version exists for the
project, then it is listed as "Unscheduled", and will also have an "Ad hoc"
cycle.
The progress tracking status bar provides a quick view on how many tests
have been executed, what % of the overall testing has been completed for a
test cycle and on hovering over the different status colors, the # and % of
tests in that status (e.g. PASSED, FAILED etc.)
Clicking on any test cycle displays a list of tests for that cycle, which can
then be executed or viewed. You can also expand the Test Cycle to view
the folders in that cycle by clicking on the arrow located next to the cycle.
Each folder can have its' own set of executions as part of the overall cycle.

2
Creating a Test Cycle
A new test cycle can be created for a selected version by clicking on
the '+' button in the context menu:

 Version: Shows the list of versions that exist for this project
 Name: Name of the test cycle - this is mandatory
 Description: A description of the cycle
 Build: This is informational only
 Environment: This is informational only
 From: The start date of this test cycle
 To: The end date of this test cycle. The end date is not enforced (i.e.
you can continue adding tests to the test cycle and executing them
beyond this date)

Once a test cycle has been created, it can be edited or deleted via contextual
menu options, as below. You can also add tests to it.

3
Use the "Delete Cycle" option carefully. Once deleted, all the test
executions, comments, attachments and bug linkages are deleted. Test
Execution metrics are affected too. This does not delete the actual tests.

Viewing a Test Cycle and adding Tests


Clicking on any test cycle displays a list of tests for that cycle that can then
be executed or viewed. The Fixed Version/s field of a test does not
automatically bring it into a test cycle for that version. It still has to be
explicitly added to a test cycle for execution.
Once a test has been added to a cycle - either for future execution or as part
of the execution - it is displayed under the cycle. It can be executed from
there by clicking on it.

4
2. Creating test cycles

From the beginning I analyzed what’s the difference between regression


testing and smoke testing.

So, I’ve decided to add the following test cases in the regression test cycle:
adding to shopping card feature, search bar feature, social links redirection
feature, because these features are the main on this site, in my opinion, and
they are most likely to suffer from a change in code, supposing the search
feature may be affected by changing the search algorithm, redirection may
be affected by changing the group from a specific social link.

5
In the smoke test cycle, I added test cases like: quick view feature, very
men’s wear category, verify quantity in shopping card pop-up, shoping card
closing when clicking outside. These are related to smoke testing, because
these are the basic features which don’t get affected usually after a period
of time, for example, if from the beginning the shopping card is closing
when clicking outside, it won’t be affected soon, because it is not related to
some big features that may be updated-changed, the same happens with
veryfing quantity, ones it works from the early stages, there is no point to
put it in the regression testing cycle.

Conclusion
During this laboratory, I’ve learned the difference between smoke testing
and regression testing, learned how to create a test cycle and what’s the
importance of it, how to export a test cycle to .csv.

Webography:
https://professionalqa.com/smoke-vs-regression-testing
https://www.qed42.com/blog/zephyr-jira-features
https://zephyrdocs.atlassian.net/wiki/spaces/ZFJCLOUD/pages/21757979/
Creating+Cloning+and+Viewing+Test+Cycles

6
https://www.getzephyr.com/insights/how-to-start-testing-in-agile-scrum-
the-right-way

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy