Test Execution Schedule Exercise
The high-level process followed in
an order entry system to be tested is:
1.Login
2.Enter/View
customer information
3.Enter
order
4.Confirm
items on hand
5.Process
payment
6.Ship
the product
The following sets of tests have
been defined:
Security
- Priority 1 – No other tests can be performed until authentication and
authorization tests have passed. (SEC1 – SEC35)
Add
New Customers – Must be consistent with existing customer data. (AC1 - AC40)
Add
Orders – This must be accessible by the customer as well as by the company’s
sales staff. (AO1 – AO20)
Fulfill
orders – This requires integration with the warehouse as well as the inventory
system. (FO1 – FO20)
Query
and View Customers – Must include older converted customer data. (QC1 – QC15)
Query
and View Orders – This must be accessible by the customer as well as by the
company’s sales staff. (VO1 – VO18)
Payment
processing – Must be able to process checks, purchase orders, all major credit
cards and PayPal. (PP1 – PP45)
The following responsibilities have
been assigned:
SEC –
Team A
AC,
AO, QC1 – Team B
FO,
VO – Team C
PP –
Team D
Your task in this exercise is to
create a test execution schedule that follows the priorities reflected in the
main order entry process. You can assign projected dates to the
tests as you choose to define them.
Your test execution schedule
should:
- Contain a logical sequence of events that follows the main order entry process to be tested
- Show a timeline of events
- Show responsibilities
- Reflect priorities and pre-requisites in the sequence
Please record your work on the test execution template and submit your response when complete.
- 28 January 2019, 1:15 PM