Create Requirements


Objective

By the end of this exercise you will be able to create Requirements and link them to Releases.

Why is this important?

We need to identify the main goals of the Software’s functionality. Once identified, the new feature can be efficiently tested.

Project Perspective

Customers should be able to Login to the Web Shop as well as order any of the available books by adding it to the Shopping Cart.
The right item will have to be present in the Shopping Cart after the order.
As the tester, you have to create Requirements to define in detail the expected outcomes of the possible combinations of our variables.
The Requirements will have to cover the initial Login process, the ordering of the books and the verification that the right items have been added to the Shopping Cart.

Instructions

Within the project “qTest Exercise Training”, add a new Requirement Module and name it “Web Shop Requirements”.
Create the first Requirement and name it “Login” and fill in the following details.

Field Value
Status New
Priority Must Have
Type Functional
Assigned to Yourself
Description A user is able to log in to the Web Shop using a provided Username and Password

Save the Requirement

Create the second Requirement and name it “Order Books” and fill in the following details:

Field Value
Status New
Priority Must Have
Type Functional
Assigned to Yourself
Description A user should be able to order any of the books present in the Books section of the Web Shop.

Save the Requirement

Create the third Requirement and name it “Verify content of the Shopping Cart” and fill in the following details:

Field Value
Status New
Priority Must Have
Type Functional
Assigned to Yourself
Description A user should be able to verify that the Shopping Cart content is correct, and the Cart contains what was ordered.

Save the Requirement
Link all 3 new Requirements to the “Sprint 1” Release.