Chapter 3:Test Management

3.1 Test Planning:

Enlist any two activities involved in test planning.(2 marks)
Ans:
1. Scope Management: Deciding what features to be tested and not to
be
tested.
2. Deciding Test approach /strategy: Which type of testing shall be
done
like configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different phases of testing. The test strategies for the various
features and combinations determined how these features and
combinations would be tested.
4. Identifying responsibilities, staffing and training needs.
What is Test Plan? What is its need? List test planning activities.
Ans:
Test Plan:
i. Test plan is the project plan for the testing work to be done.
ii. It is not a test design specification, a collection of test cases or a set of
test procedures; in fact, most of our test plans do not address that level of
detail.
Need:
i. Test Plan Ensures all Functional and Design Requirements are
implemented as specified in the documentation.
ii. To provide a procedure for Unit and System Testing.
iii. To identify the documentation process for Unit and System Testing.
iv. To identify the test methods for Unit and System Testing.
Activities:
1. Scope Management: Deciding what features to be tested and not to be
tested.
2. Deciding Test approach /strategy: Which type of testing shall be done
like configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different phases of testing. The test strategies for the various
features and combinations determined how these features and
combinations would be tested.
4. Identifying responsibilities, staffing and training needs.
5. Identifying resource requirements.
6. Identifying test deliverables.
7. Testing tasks: size and effort estimation.

1.What is test plan? List test planning activities. (Test Plan-

1Mark, Listing Activities-3Marks)
Ans: Like any project, the testing also should be driven by a plan. The test
plan acts as the anchor for the execution, tracking and reporting of the
entire testing project. Activities of test plan: 1.Scope Management:
Deciding what features to be tested and not to be tested.
2.Deciding Test approach /strategy: Which type of testing shall be done
like configuration, integration, localization etc.
3.Setting up criteria for testing: There must be clear entry and exit criteria
for different phases of testing. The test strategies for the various features
and combinations determined how these features and combinations would
be tested.
4.Identifying responsibilities, staffing and training needs
5.Identifying resource requirements
6.Identifying test deliverables
7.Testing tasks: size and effort estimation.
2.Write steps to prepare test plan. Also write features to be
tested.
(Steps to prepare test plan, features to be tested - 4Marks)
Ans:
Steps to prepare test plan:
Like any project, the testing also should be driven by a plan. The test plan
acts as the anchor
for the execution, tracking and reporting of the entire testing project.
Activities of test plan:
1. Scope Management: Deciding what features to be tested and not to be
tested.
2. Deciding Test approach /strategy: Which type of testing shall be done
like configuration,
integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different phases
of testing. The test strategies for the various features and combinations
determined how these
features and combinations would be tested.
4. Identifying responsibilities, staffing and training needs.
5. Identifying resource requirements
6. Identifying test deliverables.
7. Testing tasks: size and effort estimation.
Features to be tested are:
1. Lists/tables: Files, features and functions, inputs and outputs, error
messages
2. Outlines :E.g., function list, top-level/user-visible functions, sub-
functions (options or
submenus), entry and exit conditions on fully parameterized methods
3. Matrices: List function/operation vs. test conditions, e.g., the save
operation with the
following conditions: disk full, almost full, write-protected
4. Notes : How to run test, expected results, special instructions, one-shot
or regression test,
what test is looking for, assumptions in the test

What is test planning?(2 marks)

Ans:
Test Planning: Like any project, the testing also should be driven by a
plan. The test plan acts as the anchor for the execution, tracking and
reporting of the entire testing project. Activities of test plan:
1. Scope Management: Deciding what features to be tested and not to be
tested.
2. Deciding Test approach /strategy: Which type of testing shall be done
like configuration, integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different phases of testing. The test strategies for the various
features and combinations determined how these features and
combinations would be tested.
4. Identifying responsibilities, staffing and training needs .

State the contets of standard template of a test plan.

(template contents of a test plan - 4 marks ) [**Note - any other
relevant template shall also be consider
Ans:
1. Introduction
1.1 Scope What features are to be tested and what features will not be
tested what combinations of environment are to be tested and what not.
2. References
3. Test Methodology and Strategy/Approach
4. Test Criteria
4.1 Entry Criteria
4.2 Exit Criteria
4.3 Suspension Criteria
4.4 Resumption Criteria
5. Assumptions, Dependencies, and Risks
5.1 Assumption
5.2 Dependencies
5.3 Risk and Risk Management Plans
6. Estimations
6.1 Size Estimate
6.2 Effort Estimate
6.3 Schedule Estimate
7. Test Deliverables and Milestones
8. Responsibilities
9. Resource Requirement
9.1 Hardware Resources
9.2 Software Resources
9.3 People Resources
9.4 Other Resources
10. Training Requirements
10.1 Detail of Training Require
10.2 Possible Attendees
10.3 Any Constrains
11. Defect Logging and Tracking Process
12. Metrics Plan
13. Product Release Criteria
What is test plan? Write its two advantages?
Ans:
Test planning is the first activity of test team. If a tester does not plan
for testing then it leads to failure. Test plans are defined in framework
created by test strategy and established by test policy Like any project,
the testing also should be driven by a plan. The test plan acts as the
anchor for the execution, tracking and reporting of the entire testing
project. The test plan acts as the anchor for the execution, tracking and
reporting of the entire testing project and covers.
Advantages of test planning:
It is strategic document describes how to perform a task in as effective,
efficient and optimized manner. It also specifies, the scope and objectives
for testing
Primary tasks in testing are :.( Explanation of followings related to):
1. Scope of testing
2. Set objectives of test planning
3. Methodology for testing
4. Requirement,
5. Entry and exit criteria
6. Develop Test matrix
7. Test estimation and administrative component
8. Write and execute test cases.
9. Deciding Criteria for test-to-pass, test-to-fail,
10. Schedule of testing
11. The main purpose of test planning is to show whether software is
correct as per requirement.

Explain in detail, how to prepare a test plan with suitable

example?
Ans:
The test plan acts as the anchor for the execution, tracking and reporting
of the entire
testing project and covers.
Preparing test plan:
 What needs to be tested – the scope of testing, including clear
identification
of what will be the tested & what will not be tested.
 How the testing is going to be performed – breaking down the testing
into
small and manageable tasks and identifying the strategies to be used for
carrying out the tasks.
 What resources are needed for testing- computer as well as human
resources.
 The time lines by which the testing activities will be performed.
 Risks that may be faced in all of the above, with appropriate mitigation
and
contingency plans.
1. Deciding Test approach/ strategy:
This includes identifying.
 What type of testing would use for testing functionality?
 What are the configurations for testing features?
 What integration testing would you do to ensure these features work
together?
 What “non-functional” tests would you need to do?
2. Setting up criteria for testing:
Some of the typical suspension criteria include:
 Encountering more than a certain numbers of defects, causing frequent
stoppage of testing activity.
 Hitting show stoppers that prevent further progress of testing.
3. Identifying responsibilities, staffing & Training needs:
 The next aspect of planning is who part of it. Identifying responsibilities,
staffing & training needs addresses this aspect.
4. Identifying Resource Requirement:
 As a part of planning for a testing project, the project manager should
provide estimate for the various h/w & s/w resources required.
5. Identifying Test Deliverables:
It includes:
 Test plan itself, test case design specification, test cases, test logs &
test
summary report
6. Testing task:
Size and Effort estimation:
 This gives estimation in terms of size, effort & schedule of testing
project.
Example:
1. Introduction
1.1 Scope What features are to be tested and what features will not be
tested what combinations of environment are to be tested and what not.
2. References
3. Test Methodology and Strategy/Approach
4. Test Criteria
4.1 Entry Criteria
4.2 Exit Criteria
4.3 Suspension Criteria
4.4 Resumption Criteria
5. Assumptions, Dependencies, and Risks
 5.1 Assumption
5.2 Dependencies
5.3 Risk and Risk Management Plans
6. Estimations
6.1 Size Estimate
6.2 Effort Estimate
6.3 Schedule Estimate
7. Test Deliverables and Milestones
8. Responsibilities
9. Resource Requirement
9.1 Hardware Resources
9.2 Software Resources
9.3 People Resources
9.4 Other Resources
10. Training Requirements
10.1 Detail of Training Required
10.2 Possible Attendees
10.3 Any Constrains
11. Defect Logging and Tracking Process
12. Metrics Plan
13. Product Release Criteria

3.1.2.Deciding Test Approach:

Which features are included in test approach while planning test?
Ans:
Like any project, the testing also should be driven by a plan. The test plan
acts as the anchor
for the execution, tracking and reporting of the entire testing project.
Activities of test plan:
1. Scope Management: Deciding what features to be tested and not to be
tested.
2. Deciding Test approach /strategy: Which type of testing shall be done
like configuration,
integration, localization etc.
3. Setting up criteria for testing: There must be clear entry and exit
criteria for different
phases of testing. The test strategies for the various features and
combinations determined
how these features and combinations would be tested.
4. Identifying responsibilities, staffing and training needs
5. Identifying resource requirements
6. Identifying test deliverables
7. Testing tasks: size and effort estimation

3.1.3.Setting Up Criteria For Testing:

Why is it essential to setup criteria for testing? List any three
criteria in different situations.
(Need to setup criteria for testing - 2 Marks, 3 criteria’s - 2
Marks)
Ans:
There is a need to setup criteria for testing because:
i. An early start to testing reduces the cost, time to rework and error free
software that is
delivered to the client.
ii. Software Development Life Cycle (SDLC) testing can be started from
the Requirements
Gathering phase and lasts till the deployment of the software.
iii. It also depends on the development model that is being used. For
example in Water fall
model formal testing is conducted in the Testing phase, but in incremental
model, testing is
performed at the end of every increment/iteration and at the end the
whole application is tested.
iv. Testing is done in different forms at every phase of SDLC like during
Requirement
gathering phase, the analysis and verification of requirements are also
considered testing.
v. Reviewing the design in the design phase with intent to improve the
design is also
considered as testing.
vi. Testing performed by a developer on completion of the code is also
categorized as Unit
type of testing.
Any 3 criteria’s in different situation are :
1. Start with the static white box testing procedure when the
specifications of the software to
be developed are ready.
2. Use the code coverage analyzer to test whether the whole code is
getting executed and
covered.
3. Perform unit testing as soon as one of the unit or sub module in the
software is ready.

3.1.5.Identifying Resource Requirements:

What factors shall be considered while selecting resource
requirements?
Ans:

1. Machine configuration (RAM, processor, disk, and so on) needed to run

the product under test.
2. Overheads required by the test automation tool, if any
3. Supporting tools such as compilers , test data generators configuration
management tools, and so on
4. The different configurations of the supporting software (for example,
OS) that must be present
5. Special requirements for running machine- intensive tests such as load
tests and performance tests
6. Appropriate number of license of all the software
OR
Factors to be considered while selecting the resource
requirements are :
People:
How many people are required?
How much experience they should posses?
What kind of experience is needed?
What should they be expertise in? Should they be full-time, part-time,
contract, students?
Equipment:
How many Computers are required?
What configuration computers will be required?
What kind of test hardware is needed?
Any other devices like printers, tools etc.
Office and lab space:
Where will they be located?
How big will they be?
How will they be arranged?
Software: Word processors, databases, custom tools. What will be
purchased, what needs to be written?
Outsource companies:
Will they be used?
What criteria will be used for choosing them?
How much will they cost?
Miscellaneous supplies: Disks, phones, reference books, training
material. What else might be necessary over the course of the project?
The specific resource requirements are very project-, team-, and
company-dependent, so the test plan effort will need to carefully evaluate
what will be needed to test the software.

3.1.6:Identifying Test Deliverables:

What is test deliverables?
Ans:
Test Deliverables are the artifacts which are given to the stakeholders of
software project during the software development lifecycle. There are
different test deliverables at every phase of the software development
lifecycle. Some test deliverables are provided before testing phase, some
are provided during the testing phase and some after the testing cycles is
over.
The different types of Test deliverables are:
Test cases Documents
Test Plan
Testing Strategy
Test Scripts
Test Data
Test Traceability Matrix
Test Results/reports
Test summary report
Install/config guides
Defect Reports Release notes
1. The test plan describes the overall method to be used to verify that the
software meets the product specification and the customer's needs. It
includes the quality objectives, resource needs, schedules, assignments,
methods, and so forth.
2. Test cases list the specific items that will be tested and describe the
detailed steps that will be followed to verify the software.
3. Bug reports describe the problems found as the test cases are followed.
These could be done on paper but are often tracked in a database.
4. Test tools and automation are listed and described which are used to
test the software. If the team is using automated methods to test
software, the tools used, either purchased or written in-house, must be
documented.
5. Metrics, statistics, and summaries convey the progress being made as
the test work progresses. They take the form of graphs, charts, and
written reports.
Milestones: milestones are the dates of completion given for various tasks
to be performed in testing. These are thoroughly tracked by the test
manager and are kept in the documents such as Gantt charts, etc.

Explain test deliverables in details?

Ans:
The test plan also identifies the deliverables that should come out of the
test cycle/testing activity. The Deliverables includes the following, all
reviewed and approved by the appropriate people.
1. The test plan itself(master test plan and previous other test plans for
the project)
2. Test case design specifications.
3. Test cases, including any automation that is specified in the plan.
4. Test logs produced by running the tests.
5. Test summary reports
OR
 Test deliverables identifies the deliverable documents from the
test process. Test input and output data should be identified as
deliverables.
 Testing report logs, test incident reports, test summary reports and
metrics reports must be considered testing deliverables.
 The deliverable include following:
1. Test plan document
2. Test cases
3. Test design specifications
4. Tools and their outputs
5. Simulators
6. Static and dynamic generators.
7. Error logs and execution logs.
8. Problem reports and corrective actions.
9. Test summary report.

Explain the need of test deliverables for test planning?

Ans:

What are test deliverables and milestones? Give any four types of
test deliverables.
Ans:
Test Deliverables are the artifacts which are given to the stakeholders of
software
project during the software development lifecycle. There are different test
deliverables at
every phase of the software development lifecycle. Some test deliverables
are provided
before testing phase, some are provided during the testing phase and
some after the
testing cycles is over.
The different types of Test deliverables are:
1.Test cases Documents
2.Test Plan
3.Testing Strategy
4.Test Scripts
5.Test Data
6.Test Traceability Matrix
7.Test Results/reports
8.Test summary report
9.Install/config guides
10.Defect Reports Release notes
1. The test plan describes the overall method to be used to verify that the
software meets
the product specification and the customer's needs. It includes the quality
objectives,
resource needs, schedules, assignments, methods, and so forth.
2. Test cases list the specific items that will be tested and describe the
detailed steps that
will be followed to verify the software.
3. Bug reports describe the problems found as the test cases are followed.
These couldbe done on paper but are often tracked in a database.
4. Test tools and automation are listed and described which are used to
test the
software. If the team is using automated methods to test software, the
tools used, either
purchased or written in-house, must be documented.
5. Metrics, statistics, and summaries convey the progress being made as
the test work
progresses. They take the form of graphs, charts, and written reports.
Milestones: Milestones are the dates of completion given for various
tasks to be
performed in testing. These are thoroughly tracked by the test manager
and are kept in
the documents such as Gantt charts, etc.
3.2 TEST MANAGEMENT:

What is test management?(2 marks)

Ans:
Test Management: It concerned with both test resource and test
environment management. It is the role of test management to ensure
that new or modified service products meet business requirements for
which they have been developed or enhanced.
Aspects In Test Management:
1.Test Infrastructure Management
2.Test People/Team Management

3.2.1.Test Infrastructure Management:

Explain the ‘Test infrastructure’ components with neat diagram.

(test infrastructure diagram - 2 marks ; description - 2 marks)
[**Note - any other relevant answer shall also be considered**]
Ans:
Test infrasturcture componets diagram :

The top, or project level, test plan, the process of creating it is more
important than the resulting document. The next three levels, the test
design specification, the test case specification, and the test procedure
specification are described in detail in the following sections. As you can
see in Figure, moving further away from the top-level test plan puts less
emphasis on the process of creation and more on the resulting written
document. The reason is that these plans become useful on a daily,
sometimes hourly, basis by the testers performing the testing. At the
lowest level they become step-by-step instructions for executing a test,
making it key that they‘re clear, concise, and organized how they got that
way isn‘t nearly as important. This standard is what many testing teams
have adopted as their test planning documentation intentional or not—
because it represents a logical and common-sense method for test
planning. The important thing to realize about this standard is that unless
tester is bound to follow it to the letter because of the type of software he
is testing or by your corporate or industry policy, tester should use it as a
guideline and not a standard.
Test Design The overall project test plan is written at a very high level. It
breaks out the software into specific features and testable items and
assigns them to individual testers, but it doesn‘t specify exactly how those
features will be tested. There may be a general mention of using
automation or black-box or white-box testing, but the test plan doesn‘t
get into the details of exactly where and how they will be used. This next
level of detail that defines the testing approach for individual software
features is the test design specification.
Test Cases Dissecting a specification, code, and software to derive the
minimal amount of test cases that would effectively test the software. The
test case specification ―documents the actual values used for input along
with the anticipated outputs. A test case also identifies any constraints on
the test procedure resulting from use of that specific test case.‖
Essentially, the details of a test case should explain exactly what values or
conditions will be sent to the software and what result is expected. It can
be referenced by one or more test design specs and may reference more
than one test procedure. The ANSI/IEEE 829 standard also lists some other
important information that should be included:
• Identifiers.
• Test item.
• Input specification.
• Output specification.
• Environmental needs.
• Special procedural requirements.
• Intercase dependencies. Test Procedures After tester documents the
test designs and test cases, what remains are the procedures that need to
be followed to execute the test cases. The test procedure specification
―identifies all the steps required to operate the system and exercise the
specified test cases in order to implement the associated test design.‖ The
test procedure or test script spec defines the step-by-step details of
exactly how to perform the test cases. Here‘s the information that needs
to be defined:
• Identifier. A unique identifier that ties the test procedure to the
associated test cases and test design.
• Purpose. The purpose of the procedure and reference to the test cases
that it will exe-cute.
• Special requirements. Other procedures, special testing skills, or
special equipment needed to run the procedure.
• Procedure steps. Detailed description of how the tests are to be run:
• Log. Tells how and by what method the results and observations will be
recorded.
• Setup. Explains how to prepare for the test.
• Start. Explains the steps used to start the test
• Procedure. Describes the steps used to run the tests.
• Measure. Describes how the results are to be determined for example,
with a stopwatch or visual determination.
• Shut down. Explains the steps for suspending the test for unexpected
reasons.
• Restart. Tells the tester how to pick up the test at a certain point if
there‘s a failure or after shutting down.
• Stop. Describes the steps for an orderly halt to the test.
• Wrap up. Explains how to restore the environment to its pre-test
condition.
• Contingencies. Explains what to do if things don‘t go as planned..

3.3.2.TEST CASE SPECIFICATION:

How test case specifications useful in designing test cases?
(Specifications (minimum 4) -4Marks, their justification -4Marks)
Ans:
phase of the test development life cycle. The test specification should
explain "how" to
implement the test cases described in the test plan. Test case
specifications are useful as it
enlists the specification details of the items.
Test Specification Items are must for each test specification should
contain the following
items:
1. Case No.: The test case number should be a three digit identifier of the
following form:
c.s.t, where: c- is the chapter number, s- is the section number, and t- is
the test case number.
2. Title: is the title of the test.
3. Programme: is the program name containing the test.
4. Author: is the person who wrote the test specification.
5. Date: is the date of the last revision to the test case.
6. Background: (Objectives, Assumptions, References, Success Criteria):
Describes in
words how to conduct the test.
7. Expected Error(s): Describes any errors expected
8. Reference(s): Lists reference documentation used to design the
specification.
9. Data: (Tx Data, Predicted Rx Data): Describes the data flows between
the Implementation
under Test (IUT) and the test engine.
10. Script: (Pseudo Code for Coding Tests): Pseudo code (or real code)
used to conduct the
test.

What are the things that test case specification shall identify?
Ans:
1. Test cases specify the inputs, predicted results and execution
conditions. Each test case should aim to evaluate the operation of a key
element or function of the system.
2. Failure of a test case, depending upon the severity of the failure, would
be catalogued as part of the overall evaluation of the suitability of the
system for its intended use.
3. Test cases can start with a specific ‗form‘ that allows operator entry of
data into the system. This needs to be mapped, if the architecture is
based upon an n-tier solution, through the business logic and rules into
the server systems with transactions being evaluated both in a ‗nominal‘
mode where the transaction is a success and for those occasions when
the transaction or ‗thread‘ fails.
4. Test design may also require one or more test cases and one or more
test cases may be executed by a test procedure.
Describe test case specification of test process.?
Ans:
Testing is a process rather than a single activity.
i. This process starts from test planning then designing test cases,
preparing for execution and evaluating status till the test closure.
ii. Divide the activities within the fundamental test process into the
following basic steps:
1. Planning and Control
Test planning has following major tasks:
i. To determine the scope and risks and identify the objectives of testing.
ii. To determine the test approach.
iii. To implement the test policy and/or the test strategy. (Test strategy is
an outline that describes the testing portion of the software development
cycle. It is created to inform PM, testers and developers about some key
issues of the testing process. This includes the testing objectives, method
of testing, total time and resources required for the project and the
testing environments.).
iv. To determine the required test resources like people, test
environments, PCs, etc.
v. To schedule test analysis and design tasks, test implementation,
execution and evaluation.
vi. To determine the Exit criteria we need to set criteria such as Coverage
criteria. (Coverage criteria are the percentage of statements in the
software that must be executed during testing. This will help us track
whether we are completing test activities correctly. They will show us
which tasks and checks we must complete for a particular level of testing
before we can say that testing is finished.)
Test control has the following major tasks:
i. To measure and analyze the results of reviews and testing.
ii. To monitor and document progress, test coverage and exit criteria.
iii. To provide information on testing.
iv. To initiate corrective actions.
v. To make decisions.
2. Analysis and Design
Test analysis and Test Design has the following major tasks:
i. To review the test basis. (The test basis is the information we need in
order to start the test analysis and create our own test cases. Basically it’s
a documentation on which test cases are based, such as requirements,
design specifications, product risk analysis, architecture and interfaces.
We can use the test basis documents to understand what the system
should do once built.)
ii. To identify test conditions.
iii. To design the tests.
iv. To evaluate testability of the requirements and system.
v. To design the test environment set-up and identify and required
infrastructure and tools.
3. Implementation and Execution
i. During test implementation and execution, take the test conditions into
test cases and procedures and other test ware such as scripts for
automation, the test environment and any other test infrastructure.
ii. (Test cases is a set of conditions under which a tester will determine
whether an application is working correctly or not.)
iii. (Test ware is a term for all utilities that serve in combination for testing
a software like scripts, the test environment and any other test
infrastructure for later reuse.)
Test implementation has the following major task:
i. To develop and prioritize our test cases by using techniques and create
test data for those tests.
ii. (In order to test a software application you need to enter some data for
testing most of the features.
iii. Any such specifically identified data which is used in tests is known as
test data.)
iv. We also write some instructions for carrying out the tests which is
known as test procedures.
v. We may also need to automate some tests using test harness and
automated tests scripts.
vi. (A test harness is a collection of software and test data for testing a
program unit by running it under different conditions and monitoring its
behavior and outputs.)
vii. To create test suites from the test cases for efficient test execution.
viii. (Test suite is a collection of test cases that are used to test a software
program to show that it has some specified set of behaviors.
ix. A test suite often contains detailed instructions and information for
each collection of test cases on the system configuration to be used
during testing.
x. Test suites are used to group similar test cases together.)
xi. To implement and verify the environment.

Test execution has the following major task:

i. To execute test suites and individual test cases following the test
procedures.
ii. To re-execute the tests that previously failed in order to confirm a fix.
This is known as confirmation testing or re-testing.
iii. To log the outcome of the test execution and record the identities and
versions of the software under tests.
iv. The test log is used for the audit trial.
v. (A test log is nothing but, what are the test cases that we executed, in
what order we executed, who executed that test cases and what is the
status of the test case (pass/fail).
vi. These descriptions are documented and called as test log.).
vii. To compare actual results with expected results.
viii. Where there are differences between actual and expected results, it
report discrepancies as Incidents.
4. Evaluating Exit criteria and Reporting
i. Based on the risk assessment of the project we will set the criteria for
each test level against which we will measure the “enough testing”. These
criteria vary from project to project and are known as exit criteria.
ii. Exit criteria come into picture, when:
1. Maximum test cases are executed with certain pass percentage.
2. Bug rate falls below certain level.
3. When achieved the deadlines.
iii. Evaluating exit criteria has the following major tasks
1. To check the test logs against the exit criteria specified in test planning.
2. To assess if more test are needed or if the exit criteria specified should
be changed.
3. To write a test summary report for stakeholders.
5. Test Closure activities:
Test closure activities are done when software is delivered. The testing
can be closed for the other reasons also like:
1. When all the information has been gathered which are needed for the
testing.
2. When a project is cancelled.
3. When some target is achieved.
4. When a maintenance release or update is done.
Test closure activities have the following major tasks:
1. To check which planned deliverables are actually delivered and to
ensure that all incident reports have been resolved.
2. To finalize and archive test ware such as scripts, test environments,
etc. for later reuse.
3. To handover the test ware to the maintenance organization. They will
give support to the software.
1. To evaluate how the testing went and learn lessons for future releases
and projects.
Describe test infrastructure management.
Ans:
Test infrastructure management
Testing requires a robust infrastructure to be planned upfront. This
infrastructure is made up of three essential elements.
1. A test case database (TCDB): A test case database captures all
the relevant information about the test cases in an organization.
Some of the entities and the attributes are given in following table

A test case database captures all the relevant information about

the test cases in an organization.
Some of the entities and attributes in each of the entities in such
a TCDB are:
 Test case
 Test case-product cross reference
 Test case run history
 Test case- defect cross reference
2. Defect repository:
It captures all the relevant information of defect repository for a
product. The
information that a defect repository includes
 Defect details
 Defect test detail
 Fix details
 Communication
3. Configuration Management (CM) repository and tool
Software Configuration Management is defined as a process to
systematically manage, organize, and control the changes in the
documents, codes, and other entities during the Software
Development Life Cycle.
It keeps track of change control and version control of all the
files/entities that make up a software product. Change control
ensures that
 Changes to test files are made in a controlled fashion and
only with proper approvals
 Change are made by one test engineer are not accidently
lost or overwritten by other changes
 Each change produces distinct version of the file that is
re-creatable at any point of time
 Everyone gets access to only the most recent version of
the test files.

3.3.3.TEST MANAGEMENT STANDRADS

Describe standards included in Test management.(4 MARKS)
Ans:
Internal standards are:
1. Naming and storage conventions for test artifacts.
2. Document standards
3. Test coding standards
4. Test reporting standards.
1. Naming and storage conventions for test artifacts: Every test
artifact (test specification, test case, test results and so on) have to
be named appropriately and meaningfully.
It enables
a) Easy identification of the product functionality.
b) Reverse mapping to identify the functionality corresponding to a
given set of tests.
E.g. modules shall be M01, M02. Files types can be .sh, .SQL.
2. Documentation standards:
a) Appropriate header level comments at the beginning of a file that
outlines the functions to be served by the test.
b) Sufficient inline comments, spread throughout the file
c) Up-to-Date change history information, reading all the changes
made to the test file.
3. Test coding standards:
a) Enforce right type of initialization
b) Stipulate ways of naming variables.
c) Encourage reusability of test artifacts
d) Provide standard interfaces to external entities like operating
system, hardware and so on.
4. Test reporting standard:
All the stakeholders must get a consistent and timely view of the
progress of tests. It provides guidelines on the level of details that
should be present in the test report, their standard formats and
contents.
5.External Standards:
These are the standards made by an entity external to an
organization. These standards are standards that a product should
comply with, are externally visible and are usually stipulated by
external parties.
The three types of external standards are:
1. Customer standard: refer to something defined by the
customer as per his/her business requirement for the given
product.
2. National Standard: refer to something defined by the
regulatory entities of the country where the supplier /
customer resides.
3. International Standard: are defined at international level and
these are applicable to all customers across the globe.
3.4.Executing test cases:
Design test cases for railway reservation system.
Test cases for railway reservation system:
Test case Test case Input Expected Actual Status
ID objective data result result

TC1 Login Any valid It should It Pass

field Login accept the accepted
name login the login
(abcxyz) name name

TC2 Password Valid It should It Pass

field password accept accepted
the valid the valid
password password;
successful
 login
message
TC3 Password Invalid It should Message Pass
field password not accept displayed
the valid as invalid
password login or
wrong
password.
TC4 Date of Date It should Accepted Pass
journey format accept the date
not before date
the
current
date

TC5 Date of Date It should Accepted Pass

return greater accept the the date
journey than the date
date of
journey
date
TC6 Boarding Valid It should Accepted Pass
station boarding accept the the
station valid boarding
boarding station
station
TC7 Train Valid train It should Train Pass
number number accept the number
valid train accepted
number

Prepare six test cases for marketing site www.flipkart.com

Ans:
Test Case -ID Steps Input Expect Actual Status
data ed Result Result
TC-1 Type correct user Abc123 It Should It accepts pass
name accept user name
user name
TC-2 Type correct and Co5i518 It Should It accepts pass
valid password accept password
password
TC-3 Click on login - Home Home Pass
 button page page is
should be displayed
displayed after login
after login and user
and user name
name should be
should be displayed
displayed on home
on home page
page
TC-4 Click on any - User User pass
product displayed should be redirected
on home page redirected to product
to product specificati
specificati on page
on page.
TC-5 Click on add to - The The Pass
cart for the product product
product. should be added to
added to cart
cart.
TC-6 Click on go to - The total The total pass
cart button. amount of amount of
all items in all items in
cart cart is
should be displayed.
displayed.
TC-7 Click on remove - The item The item pass
from cart button. should be is
removed removed
form cart. from the
cart.
TC-8 Click on - The The Pass
Checkout button. checkout checkout
page page is
should be displayed
displayed with
with payments
payments options.
options.
TC-9 Make payment - User User gets Pass
for the order. should get order
order details by
details by message
message or email.
or email.

Write important six test cases for the “Login Form” of the
Facebook website.
Ans:
Test Test step Test data Expected Actual Status
case no output output
1 Username - It will It displays Pass
filed is left display ‘Enter
blank ‘Enter Username
Username ’
2 Enter invalid abc It will It prompt Pass
user name prompt couldn’t
‘couldn’t find your
find your account.
account’
message
3 Enter valid Username- It will It displays Pass
user name abc123 display ‘wrong
and invalid Password – ‘Wrong password’
password 123 password’ message.
message.
4 Enter Valid Username- It will It displays Pass
username abc123 display ‘Enter
and no Password – ‘Enter password’
password password’. .
5 Enter Valid Username- It will It displays Pass
username abc123 display users
and Password Password – users’ account’s
co5i22518 account’s facebook
facebook page.
page.
6 Click on - It will go to It goes to Pass
‘Forgotten Find your Find your
password?’ account account
page. page.
Design test cases for ATM card operations.
Ans:
Test Test case Input Expected Actual Status
case ID objective data result result
TC1 Pin valid 4 It should It Pass
number digits accept the accepted
pin valid pin the pin
TC2 Withdraw Valid It should It Pass
al numeric accept the accepted
amount valid the
amount amount
TC3 TC3 Click on It should It Pass
Withdraw the ask for displayed
al withdrawa the the
l amount message
button as enter
the
amount
TC4 Mini Click on It should It issued Pass
 statement mini issue the the
statement receipt of receipt
last 3 of last 3
transactio transactio
ns ns
CAPITAL LETTERS”
ABCDEFGHIJKLMNOPQRSTUVWXYZ

SMALL LETTERS”
abcdefghIjklmnopqrstuvwxyz