TEST MANAGEMENT

TEST PLAN
 Test plan is a detailed document which describes software testing areas and
activity.
 It outlines test strategy objectives test schedule required resources test
Estimation and test deliverables.
 Test plan is a base of every software testing.
 Test plan is the project plan required to perform testing of an application or a
system.
 Test plan is prepared by the test lead 60% test manager 20% and by the test
engineer 20%
 TEST PLANNING ACTIVITIES
 To determine the scope and the risk that need to be tested and that are not to
be tested.
 documenting test strategy
 Making sure that the testing activities have been included
 Deciding entry and exit criteria.
 Evaluating the test estimate
 planning when and how to test and deciding how the test results will be
evaluated and defining test exit criteria.
 ensuring that the test documentation generates repeatable test assets
 ADVANTAGES OF TEST
PLANNING
 Better coverage
 Generate more bugs
 We only need to define test points during the testing phase
 The entire test plan can be reused if regression testing is done later on.
 PREPARING A TEST PLAN HOW TO
WRITE A TEST PLAN

 Writing a test plan is one of the primary task in testing.

 Analyze the product
 developed a strategy :This is critical step in making a test plan
 A test strategy document is a high level document which is usually developed by test manager.
 Define objective of testing
 Define test criteria
 Planning the resources
 Plan test environment
 Schedule and cost
 Test deliverables.
 STANDARD TEMPLATE OF TEST
PLAN
Standard template of test plan contains:
 Test plan identifier
 References
 Introduction
 Test items
 Software risk issues
 Feature to be tested
 Feature not to be tested
 Approach
 Test pass/ fail criteria
 STANDARD TEMPLATE OF TEST
PLAN
 Suspension criteria and resumption requirement
 Test deliverables.
 Remaining test task
 Environment needs
 Staffing and training needs
 Responsibility
 Schedule
 Planning risks
 Aapprovals
 Glossary
 RISK MANAGEMENT
 Risk management is done during test planning and test execution
 Risk management is an integral part of software Project to make sure we handle risks and
prevent/ reduce losses
 1)Risk identification: This phase involves making a list of everything that might potentially
come up and disrupt the normal flow of events.
 2) Risk impact analysis: This phase quantified and prioritized all the risk every risk
probability and impact and determined systematically
 high medium and low values are assigned to both the probability and impact for each risk
 3) Risk mitigation: This is final phase to find solution to all listed risk and plan to handle
each one of these situations.
 TEST APPROACH
 A test approach is the strategy implementation of a project which defines how testing would be carried out
 Define the strategy which needs to be implemented and executed to carry out a particular task
 Type or features of test strategy/approach
 1)analytical: Focusing testing on the most critical functionality that is risk based.
 2) Model based: During requirement and design phase of project some formal and informal models are created
 3) Methodical: It involves strategies that are pre-planned developed in-house or outside all industries are
trying to confirm the quality standard Defined by ISO 9126
 4) Process or standard compliant: Process strategies involves externally developed approach to testing
 5) Dynamic: Dynamic strategies such as exploratory testing concentrating on finding as many defects as
possible during test execution
 6) Regression averase: Regression averase strategy is having common a set of procedures usually automated
that allowed them to detect regression defects.
 SETTING UP CRITERIA FOR
TESTING
 Pass or fail criteria: Specify the criteria that will be used to determine
whether each test item has passed or failed testing
 Suspend criteria: Specify criteria to be used to suspend the testing activity
 Resume criteria: Specify testing activities which must be redone when testing
is resumed
 RESOURCE REQUIREMENT
 Resource plan is a detailed summary of all types of resources required to complete project
task
 Resource could be human equipment and materials needed to complete a project

 Some resources required are as follows

1. To run the process machine with required configuration include Ram processor hard disk etc
2. Supporting software and output must be available
3. Required number of license copies of all software
4. Supporting tools like configuration management tools test generators, compilers etc
5. Special testing tools for load test and performance test
 TEST DELIVERABLES AND
MILESTONE
 Different types of documents are given to the stakeholders of software
project during the SDLC.
 There are different types of test deliverables generated at every phase of
the SDLC
 Some of the test deliverables are provided before testing phase or during the
testing phase or after the testing cycle is over.
 TYPES OF TEST DELIVERABLES
1. Test case documents
2. Test plan
3. Testing strategy
4. Test scripts
5. Test data
6. Test traceability matrix
7. Test results or reports
8. Test summary reports
9. Install or configuration guide
10. Defect report
11. Release notes
 Milestone
Milestone are nothing but the target that must be completed in order to
process within any given testing activity or completing testing activity as per
plan.
 TEST MANAGEMENT
 Test management is a process of managing the testing
activities in order to ensure high quality and high end
testing of the software application
 Organizing and controlling the testing process
 Ensuring visibility traceability and control of testing
process to deliver high quality software.
 It managing the software testing activities from start to
end.
 It provides planning controlling tracking and monitoring
facilities throughout the whole project cycle.
 TYPES OF STANDARD
External standard
1. Customer standards
2. National Standards
3. International standards
Internal standards

Standards are defined to provide exact meaning to any subject

In software development and testing field standards are define and used for coding testing
reviewing designing and requirement analysis phases
Testing standards are mainly used to control activities that are come under this phase
 TYPES OF STANDARD
External standard
It is made by any entity other than the organization.
These standards are defined by the regulatory authorities
These standards can be treated as legal requirement for a product.
Types of external standard
1. Customer standards: These standards are defined by the customer the aim in defining the standards
lies in the business requirement of certain product. This standard then enforced by the customer to
supplier who are working on customers product development process
2. National standards: These standards are defined by regulatory authorities. This standards are
applicable to both producer and customers who reside in the specific area
3. International standards: This standards are globally define and applicable to all producers and
customers organizations like ISO, IEEE etc Prescribes such standards
 TYPES OF STANDARD
Internal standards:
This standards are developed by the software development organization for their internal use purpose
Use of internal standards:
Reason for which internal standards are used:
1. Simplified communication
2. Provides continuity
3. Promote consistency and uniformity
4. Eliminates the need to invent the another solution to the same problem
5. Present a way of prescribing proven practices
6. Supplies Benchmarks and framework.
 IEEE STANDARDS

1. 730 -1998 IEEE standard for software quality assurance plan

2. 828 -1998 IEEE standards for software configuration management plan
3. 829- 1998 IEEE standard for software test documentation
4. 1008 -1987 (R 1993 )IEEE standard for software unit testing
5. 1012 -1998 IEEE standard for software verification and validation
6. 1028 -1997 IEEE standard for software reviews
 TEST INFRASTRUCTURE MANAGEMENT

The testing infrastructure is used to support automated and Manual software

testing
Component of testing infrastructure: Testing infrastructure has three
component
1. H/W infrastructure : This is main component of testing infrastructure
Efficient and high configuration as well as old configuration dedicated
infrastructure must available for testing.
2. S/W infrastructure: This is another component of testing infrastructure.
latest as well as previous software should be available for testing
3. Automated testing tool infrastructure: Different testing tools for different
type of testing is required to improve quality of software product.
 TEST CASE SPECIFICATION
It specifies the purpose of a specific test identifies the required Input and
expected result provides step-by-step procedures for executing the taste and
outlines the pass/ fail criteria for determining acceptance.
Test case specification has to be done separately for each unit
Writing good test cases that reveal every single part of a unit is a very creative
task. success of a product is depending upon the quality of a test cases
through which it was passed. these specified test cases must be reviewed to
confirm to its quality
Test case specification gives idea to test what scenarios will be tasted how
they will be tested how often they will be tested
 TEST REPORTING
Once testing is completed tester generate Matrix and make final reports on their test
effort and concluded whether or not to the software tested is ready for release.
Preparing test summary report:

Step 1. Purpose of the document it gives the short description about the objective
behind preparation of the document Ex document explaining various activities
performed as a part of testing
Step 2. Overview of an application in this step brief description about the application
to be tested is mentioned
Step 3. Testing scope 1.In scope 2.out of scope 3. item not tested
In this step it gives an explanation about the functions modules in scope and out of
scope for testing along with this.it also gives information about any item which is not
tested due to any restriction.
 TEST REPORTING
Step 4. Metrics: In this section it gives information about Metrics these metrics will
help to understand the test execution results status of test cases and defects etc
Ex number of test cases plan versus executed and number of test cases passed or
failed
Step 5. Types of testing performed 1. Smoke testing 2. System integration testing 3.
Regression testing
Step 6. Information of test environment and tools detail of test environment in which
the testing is carried out is given
Information about server database and application URL
Step 7. Lessons learned: This section describes the crucial issues occurred and faced
also gives detailed solution
Step 8. Recommendation suggestions about different activities can be mentioned here
Step 9. Best practices save time good and efficient.
 TEST REPORTING
Step 9. Best practices save time good and efficient.
Step 10. Exit criteria
A) all planned test cases are executed.
B)All critical defects are closed etc
Step 11. conclusion/ sign of
 TEST REPORTING
Types of test report:
1. Test incident report
A test incident report is communication that happens through the testing cycle as
and when defects are encountered a test incident report is nothing but an entry
made in the defect repository each defect has a unique ID and this is used to
identify the incident defects are highlighted in the test summary report
2. Test summary report
A summary of the activities carried out during that cycle
Defect that were uncovered during that cycle based on their severity and impact
Progress from the previous cycle to the current cycle in terms of defect fixed
Outstanding defects that are yet to be fixed in this cycle.
Any variations observed in effort or schedule