CSTM Course

Workshop Exercises

2007

STQC IT Services
Department of Information Technology
Government of India
ETDC, Bangalore
 STQC IT SERVICES

Contents

Workshop I Software Inspection of Software Bus Reservation System 01

Workshop II Black Box Testing of program 16

Workshop III Cause-Effect Graph 17

Workshop IV Functional Testing of Software Bus Reservation System 18

Workshop V State Transition Testing 19

Workshop VI Application of orthogonal arrays to GUI testing 20

Workshop VII Integration / System Testing 22

Workshop VIII Application of Risk Analysis to a Testing Project 25

Workshop IX Software Test Project Management 26

CSTM Workshop Exercises Aug 2007 2

 STQC IT SERVICES

Workshop I (Software Inspection of Software Requirement Specification)

The SRS of a program 'Bus Reservation System' is given in the following pages. The
exercise is to carry out a software inspection. The participants have to study the SRS
and look for major non-trivial defects. All trivial defects may be listed and given directly
to the author, as they do not merit discussion. The 'logging meeting' will be held
facilitated by an Inspection Leader (IL). The IL will present the defects logged by the
group in the format given.

Bus Reservation System - Software Requirements specification

Released on 28 July, 2007
Version 1.0

1 Introduction

1.1 Purpose

The purpose of the Software Requirements Specification document is to define the

software functional requirements for reservation at a bus station. The document shall
be used as a baseline for development of the system. The SRS will describe the
requirements for the client portion of the system. In addition the document will describe
how the clients will be connected to the server.

1.2 Product perspective

Bangalore has found its growth is rapid phase. As the city grows, the requirement of the
people also increases in every aspect of their life. The requirement may be big or small
but Technology has provided solutions to every requirements. For example reserving a
bus ticket with ease is a crucial task in busy cities like Bangalore, but Bus Reservation
System makes the task even simpler than imagined.

Bus Reservation System is a generalised software application, where the customers

can easily reserve tickets at different reservation centres commissioned in Bangalore.
The system also provides a smooth interface to Booking Clerks and dynamic
information’s are found with ease. Administrator can easily configure and maintain the
system.

1.3 Project Scope

The bus reservation system shall be a multi-user client / server application designed for
booking tickets by clerks of KSRTC, running buses to all the major destinations around
Bangalore. Using the BRS, Administrator can configure the Reservation system and
each booking clerk including Administrator can provide reservation services to
customers.

The system supports Up to 91 users including the Administrator. They can make
reservations, update it, delete it and prepare various types of reports.

CSTM Workshop Exercises Aug 2007 3

 STQC IT SERVICES

1.4 Definitions, acronyms and abbreviations

BRS - Bus Reservation System

SRS - Software Requirements Specifications
KSRTC – Karnataka State Road Transport Corporation

1.5 References

1. IEEE Std 830 –1998 recommended practice for Software Requirement

Specification

1.6 Overview

The remaining portion of this document contains an overall description of Administrator

functions and system requirement of BRS.

2 General Description

2.1 Context

The Bus Reservation System is a multi-user client / server application designed for the
booking tickets by clerks of KSRTC, running buses to all the major destinations around
Bangalore.

2.2 User Interfaces

1. Each form should have a unique title

2. All error messages should have the same title 'Bus Reservation Message' and an
"OK" button.
3. The user interface shall be in English

2.3 Hardware Interface

2.3.1 Server Hardware

Hardware requirements are Intel dual processor based Xeon system, 2Gz or above with
at least 1.2 BG RAM, 5 X 36GB SCSI.

2.3.2 Client Hardware

Hardware requirements are Pentium 4 with Intel® server chipset 2GHz with 512 MB
RAM, 1 X 80GB IDE HDD.

2.4 Software Interfaces

The front-end application will interact with the BRS communication framework and this
framework will use the server side components to interact with database

CSTM Workshop Exercises Aug 2007 4

 STQC IT SERVICES

2.4.1 Server System Software

The system software required is Windows 2003, Oracle server 10G.

2.4.2 Client System Software

The system software required are Windows XP professional, .Net framework

2.5 Communication Interfaces

LAN Administrator

WAN

Central Server

Booking Office Server 1 Booking Office Server 2 Booking Office Server 9

Booking Booking Booking Booking Booking Booking

Clerk 1 Clerk 10 Clerk 1 Clerk 10 Clerk 1 Clerk 10

LAN 1 LAN 2 LAN 9

(Block diagram of network connectivity)

• Data transfer between the Central Server and Booking Office Server would be
done over WAN
• Data transfer between the Booking Office Server and Booking clerk would be
done over LAN
• Administrator will be monitoring the Central server and he can also book the
tickets like a Booking clerk.

CSTM Workshop Exercises Aug 2007 5

 STQC IT SERVICES

3 Product Functions

3.1 Security

The application is secured by password. The entrance to the BRS is through the screen
shown below. The entry can be as a booking clerk or as an administrator. The activity
can be a booking activity by the clerk or an activity of booking or route modification by
the admin. For Booking Clerk Route Modification option will be disabled. Status of login
either successful or not:

Administrator (Booking Incorrect password “Invalid Password”

activity)
Administrator (Route Incorrect Password “Invalid Password”
Modification)
Administrator Correct Password Logging in
Booking Clerk (Booking Correct password Logging in
activity)
Booking Clerk (Route Deactivated for this activity ----
modification)
Booking clerk (booking Incorrect password “Invalid Password”
activity)

CSTM Workshop Exercises Aug 2007 6

 STQC IT SERVICES
The list of valid users created by the Administrator is viewed in a list box.
3.2 Create a New order

The booking clerk or the administrator, when they are in the booking mode, create a
new reservation for the customer as follows:

CSTM Workshop Exercises Aug 2007 7

 STQC IT SERVICES

CSTM Workshop Exercises Aug 2007 8

 STQC IT SERVICES
The customer gives the date, destination and bus type (ordinary/express). The clerk
selects the date from the given calendar, routes from the routes table and fills the
passenger name and number of tickets. The total fare is automatically accounted. The
route number appears and the reservation code appears automatically on pressing the
reserve option.

NOTE: The reservation screen is divided into bus schedule section containing the
calendar and the route table and the Reservation Information section containing
reservation information.

3.3 ERROR MESSAGES

(1) If number of tickets is more than 10 then message "Cannot reserve ticket(s) more
than 10"
(2) If date of journey before current date then message " Valid date of journey dates
must be on or after..."
(3) If Date/time of bus schedule is prior to current date/time then message "The
reservation date must be greater than the current date and current time"

3.4 Delete Order

To delete current order just press " delete" in Reservation information section. On
Confirmation of request the particular reservation with Reserve code id is deleted

3.5 Update Order

After reservation, the order can be updated by editing information’s like schedule and
name, number of tickets etc.

3.6 Open an Existing order

An existing order can be opened, updated or deleted.

To open an order, press open from main menu, then a search engine appears and you
can search the record by passenger name, date of journey or reservation code.

You can select the order or cancel the search .The process of update and deletes can
be done as before.

If a search is requested for an Invalid passenger then, error message "Record is not
found' ' appears.

If no record is found for a particular date of journey, message "Record is not found". If
reservation code is not existing then message" Record is not found".

3.7 Administrator Functions

CSTM Workshop Exercises Aug 2007 9

 STQC IT SERVICES

• Administrator’s security validation is done through Admin validation Form

3.7.1 Add User

CSTM Workshop Exercises Aug 2007 10

 STQC IT SERVICES
The Administrator screen appears first and the administrator has to validate using his
password. Once validated, he can add new user with User name and password .On
successful user addition the message-" New user is successfully created" appears. The
new user is added to list on right.

3.7.2 Delete User

The administrator security is first verified. Then the delete user screen appears and a
user can be deleted. Confirmation is required before final deletion.

3.7.3 Edit User

This option shows list of existing users and only their name can be edited.

3.7.4 Change Password

The administrator can change the password for himself or any of the users after security
validation. The user list appears on the right side. The administrator password must be
alphanumeric and at least 5 characters long.

3.7.5 MODIFY & ADD NEW ROUTES

CSTM Workshop Exercises Aug 2007 11

 STQC IT SERVICES
On security validation, the administrator can modify and add new routes. The route
entry screen appears. The route number can be selected from a list box. On 'browse'
all the trips on this route for type ordinary/Express with fare will appear. The cost of
ticket also appears. The departure time and fare can be modified and updated on
confirmation. Any particular route can be selected and with proper departure time and
route id, can be deleted. A new route can be added by writing a route number,
Departure time, from/to travel type and price.

3.8 REPORTS

(1) Current year reservation report can be obtained on printer.

(2) Period wise reservation report can be obtained on giving starting date and ending
date. The reports will be Route NO wise, date wise or give total amount at end of
report.

4 Non-functional Requirements

4.1 Performance
4.1.1 Response time of the Bus Reservation System should be less than 2 second.
Response time refers to the waiting time while the system accesses, queries and
retrieves the information from the databases (DB-user, DB-schedule etc) (A local
CSTM Workshop Exercises Aug 2007 12
 STQC IT SERVICES
copy of Bus schedule database is maintained as DB-schedule to reduce this
access time)
4.1.2 The server must be able to handle 10 simultaneous requests.
4.1.3 BRS shall show no visible deterioration in response time as the number of users
or bus schedule data increases

4.2 Reliability
4.2.1 BRS shall be available 24 hours a day, 7 days a week
4.2.2 BRS shall always provide real time information about bus availability information.
4.2.3 BRS shall be robust enough to have a high degree of fault tolerance. For
example, if the user enters a negative number of passengers or a value too
large, the system should not crash and shall identify the invalid input and
produce a suitable error message.
4.2.4 BRS shall be able to recover from hardware failures, power failures and other
natural catastrophes and rollback the databases to their most recent valid state.

4.3 Usability
4.3.1 BRS shall provide a easy-to-use graphical interface similar to other existing
reservation system so that the users do not have to learn a new style of
interaction.
4.3.2 The WAN interface should be intuitive and easily navigable Users should be able
to understand the menu and options provided by BRS.
4.3.3 Any notification or error messages generated by BRS shall be clear, succinct,
polite and free of jargon.

4.4 Integrity

4.4.1 Only system administer has the right to change system parameters, such as bus
routes and pricing policy etc. The system should be secure and must use
encryption to protect the databases.
4.4.2 Users need to be authenticated before having access to any personal data.

5 Other requirements

5.1 Main Reservation Form

CSTM Workshop Exercises Aug 2007 13
 STQC IT SERVICES

The main reservation window is divided into two sections:

1. Bus schedule; and

2. Order information

5.2 Description of fields

All read only fields are filled automatically from the route database after a particular
journey detail is selected.

5.3 Routes Table

Pressing the Routes button in the main window can assess the route table. It contains
all the routes with from and to destinations, cost per ticket, and timings. The selected
information will appear in the reservation read only edit fields.

6 Future Requirements
6.1 Support for waiting list functionality
6.2 BRS shall be made more flexible in ticket reservation handling, and shall accept
waiting list for reservation.
6.3 BRS shall be made more dynamic and helpful to the users by enabling it to send
instant messages to the passengers, of a cancelled or rescheduled bus, through
email, phone, fax etc., informing them about the change, and providing them with
other feasible alternatives.

6.4 Provide service integration with auto rental agencies and hotel chains.
6.5 Interface for the travel agents shall be provided in the future versions with
additional features like informing them of any availability of seats on a bus
which was earlier booked to capacity.
6.6 Choices like aisle or window seats shall be provided to the users.
6.7 The BRS shall be able to handle the situation where bus services are available
to multiple bus-stations in a single city.

CSTM Workshop Exercises Aug 2007 14

 STQC IT SERVICES

Specification Review Check List

• Do stated goals and objectives for software remain consistent will system goals and
objectives.
• Have important interfaces to all system elements been described?
• " Is information flow and structure adequately defined for the problem?
• Are diagrams clear? Can each stand alone without supplementary text?
• Do major functions remain within scope and has each been adequately described?
• Is the behaviour of the software consistent with the information it must process and
the functions it must perform?
• Are design constraints realistic?
• Have the technological risks of development been considered?
• Have alternative software requirements been considered?
• Have validation criteria been stated in detail? Are they adequate to describe a
successful system?
• Do inconsistencies, omissions, or redundancies exist?
• Is the customer contact complete?
• Has the user reviewed the preliminary user's manual or prototype?
• How are planning estimates affected?
• Be on the lookout for persuasive connectors (e.g., certainly, therefore, clearly,
obviously, it follows that), and ask 'why?"
• Watch out for vague terms (e.g., some, sometimes, often, usually,
ordinarily, most, mostly); ask for clarification.
• Watch lists are given, but not completed, be sure all items are understood. Keys to
look for: 'etc., and so forth, and so on, such as."
• Be sure stated ranges don't contain unstated assumptions (e.g., Valid codes range
from 10 to 100. Integer? Real? Hex?).
• Beware of vague verbs such as "Handled, rejected, processed, skipped, eliminated.'
They can be interpreted in many ways.
• Beware ambiguous pronouns (e.g., The I/O module communicates with the data
validation module and its control flag is set. Whose control flag?)
• Look for statements that imply certainty (e.g., always, every, all, none, never), then
ask fur proof.
• When a term is explicitly defined in one place, try substituting the definition for other
occurrences of the term.
• When a structure is described in words, draw a picture to aid in understanding.
• When a calculation is specified, work at least two examples.

CSTM Workshop Exercises Aug 2007 15

 STQC IT SERVICES

Workshop II (Black Box Testing)

Bookman & Co offers trade discount to established booksellers and others for a newly
released best seller. The specification for discounts is as follows:
For private customers or libraries:
if mode of payment is cash, then, discount 20%;
if mode of payment is credit card then, discount is 10%,
If order quantity is less than 6 and greater than 60 then there is no sale and
appropriate messages are displayed for all types of customers.

For Book sellers

If order quantity is >= 6 and <= 20 and mode of payment is cash, then, discount 5% and
if mode of payment is credit card, then discount 4%.
If order quantity >20 and <=60 and mode of payment is cash, then discount 15%; if
mode of payment is credit card, then discount 13%.

For this specification write test cases for:

Equivalence partitioning and boundary value testing.

16
 STQC IT SERVICES

Workshop III : Cause-Effect Graph.

A database management system requires that each file in the database have its
name listed in a master index which identifies the location of each file. The index
is divided into ten sections. A small system is being developed which will allow the
user to interactively enter a command to display any section of the index at his
terminal. Cause – effect graphing is used to develop a set of test cases for the
system.

The specification for this system is as follows:

To display one of the ten possible index sections, a command must be entered
consisting of a letter and digit. The first character entered must be a D (for display)
or an L (for list) and it must be in column 1. The second character entered must be a
digit (0 –9) in column 2. If this command occurs, the index section identified by the
digit is displayed on the terminal. If the first character is incorrect, error message A is
printed. If the second character is incorrect, error message B is printed. The error
messages are:

A: INVALID COMMAND
B: INVALID INDEX NUMBER

The causes and effects have been identified as follows. Each has
been assigned a unique number.

Causes
1. Character in column 1 is D.
2. Character in column 1 is L.
3. Character in column 2 is a digit.

Effects
50. Index section is displayed/listed.
51. Error message A is displayed.
52. Error message B is displayed.

17
 STQC IT SERVICES

Workshop IV (Functional Testing of Software Bus Reservation System)

1.0 Aim
To design test cases for the software Bus Reservation System using black box
testing strategy.

2.0 Documents available

SRS Document
User Interfaces
3.0 Scope
Prepare the black box test cases as per the given SRS and UI diagrams

Hint: Make the following Test Clusters

Login Tests
DB Operations
Administrator functions
Modify & Add new routes
Report Generation

18
 STQC IT SERVICES

Workshop V : State Transition Testing

Write Test cases for the following State Transition Diagram.

Stop, reset
Start
Start
// Time=increasing value
Initial state //Time=0
Idle reset Running
Reset
// Time=0

Start
// Time=increasing value stop
Reset // Time=last value
// Time=0

Paused

Stop

19
 STQC IT SERVICES

Workshop VI : Application of Orthogonal Arrays to configuration testing

The testing of a web site requires that it must operate correctly with:
• Different browsers-Internet Explorer 5.0, 5.5, and 6.0. Netscape 6.0, 6.1,
7.0, Mozilla 1.1 and opera 7 ( 8 choices)
• Different plug-ins-Real player, media Player or AV Rack (3 choices)
• Running on different client operating system-Windows 95, 98, ME, NT,
2000, and XP (6 Choices)
• Receiving pages from different servers-IIS, Apache and Web Logic (3
Choices)
• Running on different server operating system-Windows NT, 2000 and
Linux.(3 choices)
Given the following array how would you map the requirements to it. Give a
sample of 2-3 test configurations for this project.

Factor1 Factor2 Factor3 Factor4 Factor5

Run1 1 1 1 1 1
Run2 1 4 3 4 4
Run3 1 4 2 4 4
Run4 1 1 4 1 1
Run5 1 3 5 3 3
Run6 1 2 7 2 2
Run7 1 2 6 2 2
Run8 1 3 8 3 3
Run9 3 4 1 3 3
Run10 3 1 3 2 2
Run11 3 1 2 2 2
Run12 3 4 4 3 3
Run13 3 2 5 1 1
Run14 3 3 7 4 4
Run15 3 3 6 4 4
Run16 3 2 8 1 1
Run17 2 3 1 2 1
Run18 2 2 3 3 4
Run19 2 2 2 3 4
Run20 2 3 4 2 1
Run21 2 1 5 4 3
Run22 2 4 7 1 2
Run23 2 4 6 1 2
Run24 2 1 8 4 3
Run25 4 2 1 4 3
Run26 4 3 3 1 2
Run27 4 3 2 1 2
Run28 4 2 4 4 3
Run29 4 4 5 2 1
Run30 4 1 7 3 4
20
 STQC IT SERVICES
Run31 4 1 6 3 4
Run32 4 4 8 2 1
Run33 5 2 1 4 2
Run34 5 3 3 1 3
Run35 5 3 2 1 3
Run36 5 2 4 4 2
Run37 5 4 5 2 4
Run38 5 1 7 3 1
Run39 5 1 6 3 1
Run40 5 4 8 2 4
Run41 6 3 1 2 4
Run42 6 2 3 3 1
Run43 6 2 2 3 1
Run44 6 3 4 2 4
Run45 6 1 5 4 2
Run46 6 4 7 1 3
Run47 6 4 6 1 3

21
 STQC IT SERVICES

Workshop VII Integration / System Testing

People’s Bank of India (PBI) is a commercial bank giving a varied services to

the customers both in India and abroad. Their services include Fixed
Deposits, Loans,
Savings account and current account, Demand Drafts, Clearing of Local
Cheques/drafts, and clearing of outstation cheques , to mention a few. Their
auxiliary services include safe Deposit Lockers, Standing instructions, Money
transfers etc.

Salient Features:

A group in your company develops the SAVINGS BANK (Called SB) module
of the Banking package. Following modules are to be made in SB:

• Master Creation of SB accounts.

• Cheque Book Master Maintenance.
• SB Transactions
• Reports.

Other modules under preparation are current account, loan and deposits.

As a Software Test Professional, please provide the solution that you feel will
be the most appropriate for the following:

1.Your Project Manager asks you to test the functionality of the current
account module developed by others, without explaining the internal structure
of the module. What type of test will you do, Black box or White Box?

2. You are asked to check the functionality of savings Bank Transactions

screen. What type of test will you do? Black Box or White Box?

3. For availing cheque book facility in the current account, a customer must
maintain a minimum balance of Rs 5000. In the Black box testing, which
optimization technique will you use to check the minimum balance?

4. In the cheque book maintenance problem referred above, the program

works well for the values of 1, 2500 and 5000 but not for a value of 5001.
Which particular range of the boundary value analysis is throwing the
error here?.

5. After fixing the problem of cheque books, that particular path works well,
but a unknown problem has crept in suddenly. Will you be testing some of
the already tested paths of this module after a defect has been fixed or
only that particular path which was giving error?.

6. Customer complains that while accessing the cheque book module from SB
transactions, errors are thrown. But, transaction module and cheque book
22
 STQC IT SERVICES
maintenance are working fine Individually. Which test would have detected
this problem?

7. SB transaction module is designed to handle about 20 users at a time. Client

wants to know what will happen when 20 users handle SB. Client says that
time is a criteria. Which test to be performed?

8. The client says that if the users are 52 at a time against the stipulated 50,
the first 50 transactions must run smoothly and a report must be generated
about the excess of 2 transactions and that the system should not crash,
which test is to be conducted?

9. The client wants to generate the report of all SB Transactions for the last
one month. Client says even if there is a delay in doing that, it is ok. But the
report must be generated . Which test is to be performed?

10. Client complains that during backup of data, the screen goes blank and that
they do not know whether the intended operations are performed or not.
Which test would have detected this problem?

11. You have provided only the SB transactions module to the client and asked
for a feed back. The client is in the process of computerization and has only
one stand-alone system, while others are awaited. Will it be possible for you
to accept to the client’s request to test the software for load?

12. The client complains that while initially the user password was accepted as a
8 character string, the modification of password is allowing only a maximum
of 6 characters. Which test would have detected this problem?

13. The SB package has been so designed that any transaction will be
successful only after the transaction log is printed, giving all details about the
transactions carried out. There have been frequent complains that a “Run
time errors” occurs whenever the printer is not ready and update command
is given. Which test would have detected this problem?

14. A particular problem occurs only during the last day of the month, when
special reports are generated and specified procedures with respect to
interest calculations are executed. Which test would have detected this
defect/?

15. The banking software was running smoothly till an external “Address Book”
package was bought by the client and installed at the server/machine. Which
test would have detected this defect?

16. While the previous version was working fine, an updated version of the SB
module was not working properly. Suggest a Test.

17. Certain modules are behaving in a different way from the examples given in
the user Manuals and documentation. Suggest a Test.
23
 STQC IT SERVICES

18. The client was planning to go for a P IV with 60 GB hard disk and 256 MB
RAM, at the time of placement of the order and the software development is
proceeding under that assumption. Client now asks whether he can go for a
P III with 20 GB hard disk and 64 MB RAM? Which test should the software
pass to accept to this request?

19. You have completed all the modules in SB and want the customer’s feed
back. Since, banking is a general product, you may like more than one
banker to look into that and get back to you, so that depending on the
feedback you expect to improve on the performance of the product. What is
the particular test called.?

20. Customers are invited to come to Developer’s site to test the product, before
it is released. What is the particular test called.?

21. Client complains that whenever the system crashes, they are not able to
recover the system and the data. Which test would have detected this
defect/?

**********************************

24
 STQC IT SERVICES
Workshop VIII : Application of Risk Analysis to a testing Project
A company had to test a retail banking software before delivery to a large bank.
A risk-based approach was followed. A set of functions that were to be delivered
early in the project was Interest calculation, penalty calculation and profitability
analysis. The following is an indication of cost of a fault (scale of 1-3 where 1 is
minimum and 3 is maximum):
Function Maintenance Legal Economic Consequences
name resource consequences loss of reputation
allocation in of faults
case of fault
Interest 3 2 3 3
Calculation
Penalty 2 2 3 2
calculation
Profitability 1 1 1 2
analysis
Consider the probability of failure (scale 1-3, where 1 is minimum and 3 is
maximum) from the perspective of the following observations:
1.0 The project was mainly a re engineering effort and the three functions
were re written with varying degrees of change/creation of new
functionality:
1.1 Interest calculation = 10%
1.2 Penalty calculation = 15%
1.3 Profitability analysis = 20 %
2.0 The number of change requests given for design of software was of the
following ratios:
2.1 Interest calculation = 5
2.2 Penalty calculation = 4
2.3 Profitability analysis = 11
3.0 The size of the different functions was of the order of:
3.1 Interest calculation = 30FP
3.2 Penalty calculation = 25FP
3.3 Profitability analysis = 43 FP
4.0 The complexity of the software in terms of v (g) were:
4.1 Interest calculation = 15
4.2 Penalty calculation = 20
4.3 Profitability analysis = 7
The indicator weights (1-5 where 1 is minimum and 5 is maximum) is used for
each risk attribute is as follows:
Changed or new functionality – 5
Design Quality – 5
Size – 2
Complexity – 4
Based on your understanding of Risk exposure as Probability of failure * Cost of
failure rank the functions in order of decreasing risk.
Hints:
1.0 Take the average cost for each module
2.0 Scale the functions based on the probability of failure and obtain product
of probability of failure and weights)

25
 STQC IT SERVICES

Workshop IX : Software Test Project management

M/s Cybersec is a software company who has signed a contract for the
development of a software project for an MNC. It is a very prestigious project and
the client is very strict about maintaining the shipping schedule and will give
awards if project is ready before time.
Assume that you are the Test Manager of that company in charge of running
System Tests and your team comprises the following persons:
1. Test engineers: 2
2. Automation Expert: 1
3. Trainees: 5
As a test manager, you have created a WBS and assigned efforts & duration to
each task using Delphic Oracle or Three point Method. You have also identified
dependencies & the critical path.
Write the best possible solutions for the following scenarios with
justification:
1. Your most experienced automation expert goes on a fortnight long urgent
medical leave, and no one else in your organization knows how to do
scripting. You have only 3 weeks to go before D-day and as a Test Manager
what will you do?
2. The time taken for fixing the defects after test pass 1 is found to exceed the
estimated time of 2 weeks. What could be the contingency plan?
3. The top management is keen on pre-poning the release date and your testing
team require another 2 weeks for completion.
1. Relax your entry criteria
2. Adding more staff
3. Arbitrary reduction in test execution time
4. Relax your exit criteria by way of cutting testing of some features in
the product
5. Putting staff on overtime
6. Removing the safety margins in estimation and setting a tight
schedule
7. Forecasting of latent defects in the product
8. Pressurize the management not to prepone
Of the options mentioned above, which is the best and for what reason? As
a Test Manager, can you think of any other option?

26