
You are working on a new product that will provide an online pizza ordering service. Not everyone wants to
create a frequent-eater pizza account, so the user can either log in to their existing account, create an account
or proceed as a “guest" user. People with existing accounts have the option to update their accounts including
changing address, changing credit card information and changing phone number. New account creation
requires the user to enter their address, credit card information and phone number. This information Is
validated to be sure the address matches the credit card information.
Once the user logs in, they are able to order their pizza. They can request up to five different pizzas and can
select different ingredients on each. A user is allowed to pick up to 10 different ingredients per pizza. They can
also select from a pre-defined set of ingredients as follows: “meat lovers", “all veggie’, “cheese please’, and
“throw it all on".
The busiest day of the year for this product will be the day of the final football game of the professional
season. In addition to the normal high load, the company will also be running a special on the “cheese please" pizza (buy 3 get 2 more free). The new product will need to handle a load that Is expected to be twice as high
as the load on the old product last year. Given this information, what is an important item that should be
addressed In the architectural specification?
You are working on a project to develop an application that allows users to collaborate via bespoke, online
whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories
between testers, developers and the product owner during sprint development Since that release, the
developers have agreed to implement a TDD approach for future software development.
Creation of the product backlog for the second release is underway and you have recommended to the project
stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD
REASON for making this recommendation?
SELECT ONE OPTION
You are planning an exploratory test session for the current sprint which includes the following user stories:
User Story AA-008
As a booked customer of Alpha Airways
I want to access an open flight reservation
So that I can update the booking details
User Story AA-012
As a booking clerk for Alpha Airways I want to access a customer's flight reservation
So that i can view their reservation details
what three things should be considered when creating the session's test charter?
a)What are the user roles specified in the two user stories?
b)What level of coverage and efficiency was should be achieved by the session’
c)Will the session fit within a 60 to 120 minutes time box’
d)Do Will the findings from the exploratory sessions need to be documented?
e)What actions are performed by the user roles according to the acceptance criteria for these user stories’
f)Should the exploratory session be automated’
g)Has the Definition of Done been met for both user stories’
SELECT ONE OPTION
© Copyrights DumpsEngine 2026. All Rights Reserved
We use cookies to ensure your best experience. So we hope you are happy to receive all cookies on the DumpsEngine.
