Scribd
Upload
11 views3 pages

QA Challenge 1

The document outlines a QA challenge consisting of an exercise to write test cases for the Sign in and Shop products screens, along with theoretical questions regarding testing strategies and defect management. It includes user stories, acceptance criteria, and prompts for critical thinking about testing practices. The challenge must be completed and submitted to a recruiter within 24-48 hours.

Uploaded by

Luis Pérez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views3 pages

QA Challenge 1

The document outlines a QA challenge consisting of an exercise to write test cases for the Sign in and Shop products screens, along with theoretical questions regarding testing strategies and defect management. It includes user stories, acceptance criteria, and prompts for critical thinking about testing practices. The challenge must be completed and submitted to a recruiter within 24-48 hours.

Uploaded by

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

Welcome to the QA challenge!

The challenge below contains an exercise and some theoretical questions. Please read the
entire test before answering and once completed, send it back to your K+C recruiter in a
new document, including your first and last name in the header. We ask that you please
submit your project at your earliest convenience (within 24-48 hours).

Exercise
For the first exercise you should write the most important test cases, for the Sign in and Shop products
screens, in order to ensure best quality in an efficient way. Those test cases have to have all information you
consider mandatory in order to be executed by another QA.

User Story: Sign in


As the user with existing credentials
I want to be able to sign in to the website,
So that I can start using the website

Acceptance Criteria

GIVEN the user enters their username and password


WHEN the user taps Log in
AND their credentials are verified and are correct
THEN they will be logged in and brought to the homescreen

GIVEN the user doesn’t enter any characters


WHEN the user attempts to enter
THEN Log in button is displayed disable

Given: the user enters their username and password incorrectly


When the user taps Log in
Then: they will see the field turn red
And: an error message will be displayed

Given: the user write only their password


And: the user doesn’t enter their username
When: the user tries to enter
Then: the username field turn red
And: the Log in button will be disable CONTINUES →
User Story Shop products:
As a user looking into the website
I want to see all the products that are available on the store,
So that I can choose which product I would like to buy

Acceptance Criteria

Given: the user is looking for a product


When: the user taps on “View more” button
Then: the product details screen is displayed

Given: the user wants to order the products by price order


When: the users taps on the filter button
And: select price filter
Then: the page is reload
And: display all the products by price order

Given: the user wants to order the products by Alphabetical order


When: the users taps on the filter button
And: select Alphabetical filter
Then: the page is reload
And: display all the products by Alphabetical order

Now it is your turn to write the test cases (There isn’t any restriction of how to write them)

CONTINUES →
Theoretical test
Now it’s time to answer some questions:

1. You see a field which only allows years of birth between 1900 and 2004. The boundary values for testing
this field are:

2. Knowing the dev team is going to deliver you 4 stories tomorrow and the sprint is going to finish in two
days and considering you don’t have enough time to test the whole suite: How would you manage this
situation? What would be the criteria to use to cover all the stories?

3. A user story to be tested is ongoing (development process) and your scrum master informs the team the
app graphic interface will be the last to be deployed, being the delivery order: Business rule, API and then UI.
What kind of tests would you perform in order to reach quality early?

4. What kind of severity can a defect have and depending on which qualities you would choose each of those
severities?

5. For the test cases you have already created, what would be their critical path?

6. What information is necessary to include when you are loading a defect?

7. A daily radiation recorder for plants produces a sunshine score based on a combination of the number of
hours a plant is exposed to the sun (below 3 hours, 3 to 6 hours or above 6 hours) and the average intensity
of the sunshine (very low, low, medium, high).

Hours Intensity Score


T1 1.5 v. low 10
T2 7.0 medium 60
T3 0.5 v. low 10

What is the minimum number of additional test cases that are needed to ensure full coverage of ALL VALID
INPUT equivalence partitions?

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