Sample Questions Of STE -22518

CHAPTER 1
2 marks
1. State any four basic principles of writing good test cases.
Ans: Basic principles of writing a good test case are:
 Test case must be testable.
 Tester should know what is to be done when to wait for system to do it.
 Inform tester each transaction displayed/ replied by the system on screen at each
step. And wait for user response.
 Use simple conversational language for writing test case, which improves clarity
and avoid communication losses.
 Use consistent names of fields must be used in place of generic names. Any
change in field name must be incorporated in test cases.
 Tester should be aware of windows basics.
 Order of the test cases must follow business scenario. Avoid time wastage,
Common Mistakes in writing test cases:
 Making test cases too long and combining two or more test cases in single test
should be avoided
 Incomplete, incorrect, and incoherent test cases can create confusion and
frustrate testers.
 Steps should be made very clear in test case steps.
 Test case changes must be updated in software user interface.
 Define pass/fail criteria correctly, i.e. test are successful or not, there is a defect
or not?

2. Define following terms-Failure, Error, Defect and Bug.

Ans: Fault: It is a condition that causes the software to fail to perform its required
function. 
Error: Refers to difference between Actual Output and Expected output. 
Failure: It is the inability of a system or component to perform required
function according to its specification. 
IEEE Definitions 
Failure: When the External behavior is incorrect, it is called as a failure
Fault: Discrepancy in code that causes a failure is called as a fault.
Error: Human mistake that caused fault is called as a fault.
Defect : A defect is an error in coding that causes a program to fail or to produce
incorrect /unexpected results.

3. Enlist any four skills for software tester.

Ans :
Skills of a software tester are :
 1. He should possess Communication & listening Skill
2. He should be a Troubleshooter ,explorer and relentless
3. He should have Knowledge of SDLC and Domain knowledge
4. He should have knowledge of Risk assessment and management
5. He should be Innovative in testing skill
6. He should be Tactful, diplomatic and persuasive
7. He should posses Knowledge of selecting & using testing tools

4. Enlist objectives of software testing.

Ans : Objectives of software testing are
1. Finding error: Finding defects which may get created by the programmer while
developing the software.
2. Quality improvement: Gaining confidence in and providing information about
the level of quality.
3. Creating good test cases: Good test case is one that has a high probability of
finding undiscovered error.
4. Meets users requirements : To make sure that the end result meets the business
and user requirements.
5. Satisfying Requirements: To ensure that it satisfies the BRS that is Business
Requirement Specification and SRS that is System Requirement Specifications.
6. To gain the confidence of the customers by providing them a quality product

4 marks
1. Differentiate between Verification and Validation.(any 6 points)
Ans :
Verification   Validation

Are we building the system right? Are we building the right system?

Verification is the process of evaluating Validation is the process of evaluating

products of a development phase to find out software at the end of the development
whether they meet the specified process to determine whether software meets
requirements. the customer expectations and requirements.

The objective of Verification is to make sure The objective of Validation is to make sure
that the product being develop is as per the that the product actually meet up the user’s
requirements and design specifications. requirements, and check whether the
specifications were correct in the first place.

Following activities are involved Following activities are involved

in Verification: Reviews, Meetings and in Validation: Testing like black box testing,
Inspections. white box testing, gray box testing etc.
Verification is carried out by QA team to
check whether implementation software is as
per specification document or not.
Execution of code is not comes
under Verification.
Verification process explains whether the
outputs are according to inputs or not.
Verification is carried out before the
Validation.
Following items are evaluated
during Verification: Plans, Requirement
Specifications, Design Specifications, Code,
Test Cases etc,
Cost of errors caught in Verification is less
than errors found in Validation.
It is basically manually checking the of
documents and files like requirement
specifications etc.
2. Differentiate between Quality Assurance and Quality Control.
Ans :
Quality Assurance
Ensures quality in processes by
which product are developed.
Identifies weaknesses in processes
and improves them. It is a proactive
quality process
QA is the responsibility of the entire
team.
Prevents the introduction of issues or
defects
QA personnel should not perform
quality control unless doing it to
Validation is carried out by testing team.
Execution of code is comes
under Validation.
Validation process describes whether the
software is accepted by the user or not.
Validation activity is carried out just after
the Verification.
Following item is evaluated
during Validation: Actual product or
Software under test.
Cost of errors caught in Validation is more
than errors found in Verification.
It is basically checking of developed program
based on the requirement specifications
documents & files.
Quality Control
Ensures quality in products by focus on identifying
defects in actual products
Identifies defects for the primary purpose of
correcting defects. It is a reactive quality process
QC is the responsibility of the specific team that
tests for defects.
Detects, reports and corrects defects
QC personnel may perform quality assurance tasks
if and when required.
 validate quality control is working.
QA is a managerial tool QC is a corrective tool

3. Design test cases for railway reservation system.

Tes
t Specif Expecte
Objectiv Prerequi Input Actual Stat
Cas icatio Steps d
e sites data Output us
e ns Output
ID
The On Click
Login
To
"login" Click on Event.Page Login
validate
TC Home button the Click on
should Page is Pas
the
_01 Screen should "login" the be displaye s
"login"
be button. "login"
displaye d.
button.
present. button. d.
The user
The On Click The user
To should
"logout" Click on Event. is
validate be
TC Home button the Click on successf Pas
the successf
_02 Screen should "logout" the ully s
"logout" ully
be button. "logout" logged
button. logged
present. button. out
out
The
userid The
The 1) Click Enter
should userid is
"userid" on the valid
To be accepted
field "userid" username
validate accepted and
TC Login should field. consisting Pas
the and displaye
_03 Page be 2)Enter of s
"userid" displaye d on
present valid alphabets.
field. d on screen.
and usernam Eg.
screen. Eg.User_
active. e. User_01
Eg. 01
User_01
TC Login To The 1) Click Enter The The Pas
_04 Page validate password on the valid password password s
the field password password should is
"passwor should field. consisting be accepted.
d" field. be 2)Enter of accepted.
present valid alphabets,
and usernam min 8 ,
active. e. max 15
 and atleast
one
uppercase,
lowercase
and a
numeric
character
Eg.
User_011
2
The
To "forgot Forgot
Click on On Click
validate usernam userid Forgot
the Event.
the e" button page userid
TC Login "forgot Click on Pas
"forgot should should page is
_05 Page usernam "Forget s
usernam be be displaye
e" Username
e" present displaye d.
button. " button
button. and d.
active.
Valid
Source
1)Click Click on Station is
The on the "From" Valid selected
"From" "From Field and Source and list
To
field Field" type any Station of station
Reser validate
TC should 2)Type valid should names Pas
vation the
_06 be or Select source be are s
Form "From"
present on the station selected. displaye
field
and valid name. Eg. d for
active. source Eg Mumbai choice.
station. "Mumbai" Eg.
"MMCT
","BCT"
TC Reser To The 1)Click On Click The The Pas
_07 vation validate "Flexible on the Event. Flexible Flexible s
Form the with flexible Click on with with
"Flexible Dates" with date Flexible Dates Dates
with checkbo checkbo with date checkbo checkbo
Dates" x should x. checkbox x should x has
checkbo be be checked.
x. present checked.
and
 active.
1)Click
on the
the Select
journey
journey appropriat Selected
class
To check class e class class Selected
field.
Reser the field from the should class is
TC 2)Select Pas
vation journey should drop be accepted.
_08 appropri s
form class be down accepted. Eg.All
ate class
field present menu. Eg.All Classes
from the
and Eg. All Classes
drop
active Classes
down
menu.
TC Check To Fields 1)Click 1)Click on List of List of Pas
_09 ing validate like on the the trains trains s
availa that the "From"," "From "From" available available
bility available To","Dat Field" Field. from from
of trains are e" and 2)Type 2)Type or Source Source
trains displaye "Search" or Select Select on to to
d from button on the the valid Destinati Destinati
source to etc valid source on on
destinati should source station.Eg. Station Station
on be station. "BVI" for next for next
station. available 3)Click 3)Click on five days five days
and on the the "To" should is
active. "To" Field be displaye
Field 4)Type or displaye d on
4)Type Select on d on screen.
or Select the valid screen. Eg.NDL
on the destinatio S RAJ
valid n SPL
destinati station.Eg. (02951),
on "DLI" NZM
station. 5)Click on RAJDH
5)Click the "Date" ANI SPL
on the Field. (02953)
"Date" 6)Select etc.
Field. the
6)Select appropriat
the e the date
appropri of
ate the journey.
 Eg.
date of
27/10/202
journey.
1
7)Click
7)Click on
on
search
search
button.
button.
8)Select
8)Select
the class
the class.
Eg. AC 2
9)Click
tier
on
9)Click on
"Other
"Other
Dates"
Dates"
button.
button.
Enter
The
1)Click valid
"Passeng email-id
on the email-id
To er Email- The is not
"Passeng that
Passen validate Id" email-id accepted
er Email- contains a
TC ger the should should and error Pas
Id" valid
_10 Detail "Passeng be not be message s
Field. domain
s er Email- present accepted "Email is
2)Enter name.
Id" field. and . invalid is
the valid Eg.
active. displaye
email-id User_01g
d" .
mail.com
Enter
The The
1)Click valid
"name" name The
To on the name
Passen field should name is
validate "name" consisting
TC ger should be accepted. Pas
the field. of
_11 Detail be accepted. Eg. s
"name" 2)Enter alphabets
s present Eg. User_01
field valid only. Eg.
and User_01 Vora
name User_01
active. Vora
Vora
1. Click
The OTP
on the The
field The
Passen OTP received The
To check should system
TC ger field. 8-digit system Pas
the OTP be should
_12 Detail 2. Enter OTP accepts s
field. present accept
s the eg. the OTP.
and the OTP
received 12345678
active.
OTP.
 1)Click
on the
Select
"Occupat
"Occupat appropriat Selected
ion"
To check ion" e Occupati Selected
dropdow
Passen the dropdow occupatio on Occupati
n.
TC ger "Occupat n should n from the should on is Pas
2)Select
_13 Detail ion" be drop be accepted. s
the
s dropdow present down accepted. Eg.Stude
appropri
n and menu. Eg.Stude nt
ate
active. Eg. nt
occupati
Student
on from
the list.
The
passenge
r Mobile
Enter Number
1)Click The
valid is not
Mobile on the passenge
To mobile accepted
Number "Mobile r Mobile
Passen validate numbers and error
should Number" Number
TC ger the in message Pas
be Field. should
_14 Detail Mobile numeric "Indian s
present 2)Enter not be
s Number characters Mobile
and the valid accepted.
field. . Number
active. mobile Eg
Eg is
number 8828356
8828356 Invalid"
is not.
Eg
8828356
1)Click
on the
"Prefere Select
"Prefere
To check d appropriat
d" Selected
the Languag e Selected
dropdow Languag
Passen "Prefere e" language Languag
n. e should
TC ger d dropdow from the e is Pas
2)Select be
_15 Detail Languag n should drop accepted. s
the accepted.
s e" be down Eg.Engli
appropri Eg.Engli
dropdow present menu. sh
ate sh
n and Eg.
language
active. English
from the
list.
 4. Apply equivalence partitioning on application which display result on basis of
percentage obtained in exam.
Ans :
Equivalence partitioning on application which display result on basis of
percentage obtained in exam.
Assume that the application accepts an integer and decimal number as marks in the
range 0 to 100 and display the result accordingly as :
If marks are between 0-39 fail
If marks are between 40-59 second class
If marks are between 60-74 first class
If marks are between 75-100 Distinction
For rest of any numbers it should display Invalid marks
So ,
Valid Equivalence Class partition: 0 to 100 inclusive of decimal numbers.
Non-valid Equivalence Class partitions: less than 0, more than 100, alphabets/non-
numeric characters.
The equivalence partitioning with reference to the result display can be given as :
Inputs as marks Expected output (Display result as )

Numbers less than 0 Invalid

Marks 0-39 ( >= 0 and <=39 ) Fail

Marks 40-59 ( >= 40 and <=59) Second class

Marks 60-74 ( >= 60 and <=74) First class

Marks equal to or more than 75 and Distinction

less than or equal to 100 (>=75 and
<=100)

Alphabets or special characters Invalid marks

Marks >100 Invalid marks

CHAPTER 2
2 MARKS
1. State any two examples of Security testing.
Ans : examples of security testing are :
Privilege Escalation.
It’s an act of exploiting a bug, design flaw or a misconfiguration in the web application to
gain direct access to the reserved resources.
SQL Injection.
It is a technique which takes undue advantage of ambiguities present in the web
application and bypasses ambient security checks. The input fields (text boxes) are the
prime targets for implanting SQL injection. To prevent such attacks, the application
should either not allow Special characters or use them properly.
Unauthorized Data Access.
It is a technique which proposes to gain unauthorized access to data within an application.
Such data leaks take place on servers or launched via networks.
URL Manipulation.
This method modifies the website URL and steals important information. It happens
when the application uses the HTTP GET method to exchange data between the client
and the server. The information is passed in parameters in the query string. The tester can
change a parameter value in the query string to check if the server accepts it.
Denial Of Service.
It is a method to prepare conditions that make a machine or network resource unavailable
to its legitimate users.
Identity Spoofing.
Identity spoofing is a method where the tester uses the credentials of a user or device to
launch attacks against network hosts, steal data or bypass access controls.
Cross-Site Scripting (XSS)
Cross-site scripting is a computer security flaw found in web applications. It enables
attackers to inject client-side script into Web pages viewed by other users.
2. Describe the need of stub and driver in Unit testing?
Ans :
Unit is the smallest testable part of the software system.
Unit testing is done to verify that the lowest independent entities in any software are
working fine. The smallest testable part is isolated from the remainder code and tested to
determine whether it works correctly.
When developer is coding the software it may happen that the dependent modules are not
completed for testing, in such cases developers use stubs and drivers to simulate the
called (stub) and caller (driver) units.
Unit testing requires stubs and drivers, stubs simulates the called unit and driver
simulates the calling unit.
Stubs provide the downward functionality for the module under test while drivers provide
the upward functionality for the module under test.

3. Define Load testing and Stress testing.

Ans : Load testing and Stress testing :

Load testing - It is the simplest form of testing conducted to understand the behaviour of
the system under a specific load. Load testing will result in measuring important business
critical transactions and load on the database, application server, etc. are also monitored.
 Stress testing - It is performed to find the upper limit capacity of the system and also to
determine how the system performs if the current load goes well above the expected
maximum.

4. Define regression testing.

Ans : Regression Testing is defined as a type of software testing to confirm that a recent
program or code change has not adversely affected existing features.
Regression Testing is nothing but a full or partial selection of already executed test cases
which are re-executed to ensure existing functionalities work fine.
This testing is done to make sure that new code changes should not have side effects on
the existing functionalities. It ensures that the old code still works once the new code
changes are done.
5. State the process of performance testing.
Ans : Process of performance testing involves steps given as follows :

1. Identify your testing environment

2. Identify the performance acceptance criteria
3. Plan & design performance tests
4. Configuring the test environment
5. Create the performance tests according to your test design.
6. Run the tests
7. Analyze, tune and retest

6. State any two examples of integration testing.

Ans : example of integration testing are:
1. top down integration testing
2. bottom up integration testing
3. Hybrid/ sandwich/ bi-directional integration testing.

4 marks
1. Describe the Integration Testing.
Ans :
The testing of combined parts of an application to determine if they function correctly
together is Integration testing. There are two methods of doing Integration Testing
Bottom-up Integration testing and Top Down Integration testing and bidirectional testing.
Bottom-up integration testing begins with unit testing, followed by tests of
progressively higher-level combinations of units called modules or builds.
Top-Down integration testing, the highest-level modules are tested first and
progressively lower-level modules are tested after that. In a comprehensive software
development environment, bottom-up testing is usually done first, followed by top-down
testing.
Bidirectional or Sandwich integration testing, the testing is done in both the ways top
down and bottom up approach. Generally applicable for larger types of software testing.
Eg .

1. Bottom-up Integration
In the bottom-up strategy, each module at lower levels is tested with higher modules until
all modules are tested. It takes help of Drivers for testing
Diagrammatic Representation:

Here the testing starts from lowest level.

Module 4 and 5 re tested first and the cluster of module 4 and 5 is tested with a driver
software which simulates the module 2.

Advantages:
 Fault localization is easier.
 No time is wasted waiting for all modules to be developed unlike Big-bang approach
 In this approach development and testing can be done together so that the product or
application will be efficient and as per the customer specifications.

Disadvantages:

Critical modules (at the top level of software architecture) which control the flow of
application are tested last and may be prone to defects.
 An early prototype is not possible
 The key interface defects are caught at the end of the cycle.
 Test drivers are required to be created for modules at all levels except the top control.
 The critical modules, which control the flow of the application are tested last and may
be prone to defects.

2. State the testing approaches that are considered during Client- Server Testing.

Ans :

Component Testing: One need to define the approach and test plan for testing client
and server individually. When server is tested there is need of a client simulator, whereas
testing client a server simulator, and to test network both simulators are used at a time.
 Integration testing: After successful testing of server, client and network, they are
brought together to form system testing.
 Performance testing: System performance is tested when number of clients is
communicating with server at a time. Volume testing and stress testing may be used for
testing, to test under maximum load as well as normal load expected. Various interactions
may be used for stress testing.
 Concurrency Testing: It is very important testing for client-server architecture. It may
be possible that multiple users may be accessing same record at a time, and concurrency
testing is required to understand the behavior of a system in this situation.
 Disaster Recovery /Business continuity testing: When the client server are
communicating with each other , there exit a possibility of breaking of the
communication due to various reasons or failure of either client or server or link
connecting them. The requirement specifications must describe the possible expectations
in case of any failure.
 Testing for extended periods: In case of client server applications generally server is
never shutdown unless there is some agreed Service Level Agreement (SLA) where
server may be shut down for maintenance. It may be expected that server is running 24X7
for extended period. One needs to conduct testing over an extended period to understand
if service level of network and server deteriorates over time due to some reasons like
memory leakage.
 Compatibility Testing: Client server may be put in different environments when the
users are using them in production. Servers may be in different hardware, software, or
operating system environment than the recommended. Other testing such as security
testing and compliance testing may be involved if needed, as per testing and type of
system.

3. Explain Top Down integration testing.

Ans :
Top-down Integration:
In Top to down approach, testing takes place from top to down following the control flow
of the software system.
Takes help of stubs for testing.
Diagrammatic Representation:
Advantages:
 Fault Localization is easier.
 Possibility to obtain an early prototype.
 Critical Modules are tested on priority; major design flaws could be found and fixed
first.
 The tested product is extremely consistent in this approach as the integration testing is
performed in an environment that is similar to the real world environment.
 The stubs in top-down approach can be written in lesser time compared to drivers as
they are simpler to author.
 Here, fault localization is easier.
 In top-down approach the critical modules are tested on priority, which further helps
testers in finding major design flaws as early as possible.
Disadvantages:
 Needs many Stubs.
 Modules at a lower level are tested inadequately.
 The basic functionality of the software is tested at the end of the cycle.

2. Explain need of Regression Testing.

Ans : Regression Testing is required when there is a
 Change in requirements and code is modified according to the requirement
 New feature is added to the software
 Defect fixing
 Performance issue fix
 3. Explain beta testing . also write 2 advantages and 2 disadvantages of beta testing.
Ans :

This test is performed after alpha testing has been successfully performed, in beta testing
a sample of the intended audience tests the application.
Beta testing is also known as pre-release testing. Beta testing takes place at customers
site and involves testing by a group of customers who use the system at their own
locations and provide feedback, before the system is released to other customers.
Beta testing is considered to be the last step in software testing and QA process. The
software is delivered to end users and they check the functionality of the software.
The main features of Beta testing are:
 outside users are involved;
 black box practices are used.

Both alpha and beta testings are very important while checking the software functionality
and are necessary to make sure that all users’ requirements are met in the most efficient
way.
In Beta Testing, the software is distributed as a beta version to a limited set of users
outside the company. This helps to get the software tested by end-users in a real
environment.
These users are called beta testers; they test the software in a real-world scenario.
They provide feedback to the developers to help them fix any issues before the software
is released to the market.
The beta testers check and validate the functionality, usability, reliability, security, and
compatibility of the software.
Beta Testing helps to ensure there is a lesser number of faults and bugs in the
software. Beta testing helps to increase end-user satisfaction from the software.

Advantages of Beta Testing

 Reduces product failure risk via customer validation.
 Beta Testing allows a company to test post-launch infrastructure.
 Improves product quality via customer feedback
 Cost effective to detect errors compared to similar data gathering methods
 Creates goodwill with customers and increases customer satisfaction
 The software is tested by the end-users before releasing it in the market. It allows the
development team to know what end users like in the software.
 Customers can easily test software at their end to provide feedback.
 Beta testers detect bugs and issues which were missed by the testing team which
ensures high performance.
 High quality of the software is released to the market.
 Early users generate interest before the launch of the software.
Disadvantages of Beta Testing
 Test Management is an issue. As compared to other testing types which are usually
executed inside a company in a controlled environment, beta testing is executed out in the
real world where you seldom have control.
 Finding the right beta users and maintaining their participation could be a challenge

4. Describe Unit Testing.

Ans: This type of testing is performed by the developers before the setup is handed over
to the testing team to formally execute the test cases. Unit testing is performed by the
respective developers on the individual units of source code assigned areas. The
developers use test data that is separate from the test data of the quality assurance team.
The goal of unit testing is to isolate each part of the program and show that individual
parts are correct in terms of requirements and functionality.

Above figure shows the Unit test environment.

the test cases are written considering an interface , local data structures,boundary
conditions, etc.
If the upper module of the unit under test is not ready, then the driver is written and unit
is tested with the unit. Driver drives the functionality of the module under test. It acts as a
calling unit for the module under test.

If the lower modules of the unit under test is not ready, then the stub is written and unit is
tested with the stub .The unit under test will drive the functionality of the Stub. It acts as a
called unit for the module under test.
Advantages of Unit testing :

 It helps catch bugs earlier.

 It helps detect regression bugs.
 It makes code easy to refactor.
 It makes more efficient at writing code.

Disadvantages of Unit testing :

1. Testing cannot catch each and every bug in an application.
2. It is impossible to evaluate every execution path in every software application. The
same is the case with unit testing.
3. There is a limit to the number of scenarios and test data that the developer can use
to verify the source code. So after he has exhausted all options there is no choice
but to stop unit testing and merge the code segment with other units.

5. With respect to client-server testing design test cases for Online Payment Transfer
at banking system.
6. With respect to GUI testing, write test cases for Flipkart login form.
Ans : Refer to the answer of Question 8
7. State the testing approaches that are considered during client-server testing.
Ans : given above
8. With respect to GUI testing write the test cases for Amazon login form
Tes
t Spec Expecte
Objectiv Prerequi Input Actual
Cas ificat Steps d Status
e sites data Output
e ions Output
ID
To Mobile
validate number
the field
position of should
cursor on On Click Cursor Cursor is
be Click on
Regi mobile Event. should be be placed
present the
TC strati number Click on placed on on the
field and mobile Pass
_01 on the mobile the mobile mobile
active number number number
form number
and field field field
field
cursor
should
be
available
TC Logi To login Click on On Click Cursor Cursor is Pass
_02 n validate field the login Event. should be be placed
page the should field Click on placed on on the
position of be the login the login login
cursor on field field
present field
Login field
and
active
 and
cursor
should
be
available
To Continue Click on the On Click Continue Continue
validate should be continue Event. Click button button is
the present button on the should be clicked and
Logi and active. Continue clicked and it
TC Continue
n button button it should redirected Pass
_03 redirect to to the
Page
the password
password page
page
Readabilit Open the
y of Login
login
contents page The
page and Contents
Logi on login should Open the contents
TC try to read should
n page be login on login Pass
_04 the be
page opened page page are
contents if readable
and readable
they are
visible
readable
Testing of Read the
spelling of Word
word “ Spelling
mobile mobile Spelling
Mobile ” of
Logi should Read the of
TC on the Mobile
n be word Mobile Pass
_05 login page should
Page present mobile is
and check be
and correct
the correct
readable
spelling
Testing of It should Changed
hyperlink change the
The
the cursor on
"From"
cursor hovering
field
Logi Hover the Hover the and the
TC should mouse on
n mouse on should mouse Pass
_06 be hyperlink. hyperlink
page redirect and
present
to redirecte
and
respectiv d to the
active.
e page another
on click page

Chapter 3
2 marks
 1. Enlist any four benefits of Test Plan.
Ans : benefits of Test Plan are :
1. Test Plan helps us determine the effort needed to validate the quality of the
application under test
2. Help people outside the test team such as developers, business managers,
customers understand the details of testing.
3. Test Plan guides our thinking. It is like a rule book, which needs to be
followed.
4. Important aspects like test estimation, test scope, Test Strategy are
documented in Test Plan, so it can be reviewed by Management Team and reused
for other projects.

2. Enlist any two activities involved in test planning

Ans : Activities involved in test planning are :
1. determining the scope and risks that need to be tested and that are not to be
tested.
2. Documenting Test Strategy.
3. Making sure that the testing activities have been included.
4. Deciding Entry and Exit criteria.
5. Evaluating the test estimate.

3. enlist the different types of test deliverables.

Ans :
Different types of test deliverables are:
1. Test strategy
2. test plan
3. test secenarios
4. test cases
5. test data
6. requirement traceability matrix
7. test metrics
8. test incident report
9. test status report
10. test summary report
11. release note
12. test closure report

4 marks
1. Write the contents of Test plan and explain.
Ans : Test Plan Template consists of

• Test Plan Identifier:

 Provide a unique identifier for the document. (Adhere to
the Configuration Management System if you have one.)
• Introduction:
 Provide an overview of the test plan.

 Specify the goals/objectives. Specify any constraints.

• References:
 List the related documents, with links to them if available, including the
following:

 Project Plan
 Configuration Management Plan
• Test Items:
 List the test items (software/products) and their versions.
• Features to be Tested:
 List the features of the software/product to be tested.
 Provide references to the Requirements and/or Design
specifications of the features to be tested
• Features Not to Be Tested:
 List the features of the software/product which will not be tested.
 Specify the reasons these features won’t be tested.
• Approach:
 Mention the overall approach to testing.
 Specify the testing levels [if it’s a Master Test Plan], the testing types, and
the testing methods [Manual/Automated; White Box/Black Box/Gray Box]
• Item Pass/Fail Criteria:
 Specify the criteria that will be used to determine whether each
test item (software/product) has passed or failed testing.
• Suspension Criteria and Resumption Requirements:
 Specify criteria to be used to suspend the testing activity.
 Specify testing activities which must be redone when testing
is resumed.
• Test Deliverables:
 List test deliverables, and links to them if available, including the
following:

 Test Plan (this document itself)

 Test Cases
  Test Scripts
 Defect/Enhancement Logs
 Test Reports
• Test Environment:
 Specify the properties of test environment: hardware, software, network
etc.
 List any testing or related tools.
• Estimate:
 Provide a summary of test estimates (cost or effort) and/or provide a
link to the detailed estimation.
• Schedule:
 Provide a summary of the schedule, specifying key test milestones,
and/or provide a link to the detailed schedule.
• Staffing and Training Needs:
 Specify staffing needs by role and required skills.
 Identify training that is necessary to provide those skills, if not already
acquired.
• Responsibilities:
 List the responsibilities of each team/role/individual.
• Risks:
 List the risks that have been identified.
 Specify the mitigation plan and the contingency plan for each risk.
 Test Plan Template : contd..

• Assumptions and Dependencies:

List the assumptions that have been made during the
preparation of this plan.
 List the dependencies.
• Approvals:

Specify the names and roles of all persons who must

approve the plan.

Provide space for signatures and dates. (If the document is

to be printed.)
• Glossary :
 Summary or the definitions used in testing