UNIT II TEST PLANNING
The Goal of Test Planning, High Level Expectations, Intergroup Responsibilities, Test Phases, Test
Strategy, Resource Requirements, Tester Assignments, Test Schedule, Test Cases, Bug Reporting,
Metrics and Statistics
The Goal of Test Planning
The primary goal of test planning is to define the scope, objectives, approach, resources,
and schedule for testing activities in a structured and organized manner.
The goal of test planning is to establish a comprehensive framework for testing that encompasses
defining the scope, objectives, strategies, resources, and schedules. This not only ensures
systematic and well-organized testing but also aids in early defect identification and reduction of
rework, thus saving time and costs. Furthermore, it aligns the testing process with the project's
overall objectives and helps in delivering a high-quality, reliable software product.
High-level expectations
High-level expectations serve as the quality benchmarks and desired outcomes for a software
testing project. They are crucial because they provide a clear vision of what the stakeholders
expect in terms of software quality and functionality. Effective communication of these
expectations involves regular collaboration with stakeholders, setting specific quality standards,
and using visual aids, such as graphs or charts, to ensure a common understanding of what is
expected from the testing process.
Intergroup responsibilities can be intricate due to the need for effective coordination and
collaboration between various teams, such as development, testing, and quality assurance. For
instance, if there is a lack of clarity regarding who is responsible for maintaining test
environments, it can lead to delays in testing, resource conflicts, and,
ultimately, project delays. Clear delineation of responsibilities and collaboration protocols are vital
to avoid such issues.
Roles and responsibilities
Test manager responsibilities
• Control the testing division
• Distribute resources among projects.
• Examine weekly status report.
• Prepare budget ,buy software tools for the company.
• Provide technical assistance.
• Participate in weekly project meetings.
• Make sure the procedures are carried out as specified.
Responsibilities of test lead
• Analyse the requirements.
• Keep check on any fresh project needs.
• Set up hardware/software requirements.
• Inform the client of the severity of the applications problems.
• Assign task to every member of the testing team and make sure everyone have work in the
project.
• Create meeting agends,attend client call, send the client the status report.
• Examine reports that test engineers have created.
• Check soft skill training and technical needs and send to project manager.
Responsibilities of a tester
• Recognize project needs.
• Setup the test environment.
• Update the document with the test results
• Check for flaws.
• Discuss concerns/doubts with the client or development team.
• Hold internal product-specific training
Test phases in the software testing life cycle
The key test phases in the software testing life cycle typically include unit testing,
integration testing, system testing, and acceptance testing.
A test strategy outlines the approach, scope, objectives, and resources for testing. It
provides a high-level plan that guides the testing process, ensuring that it aligns with
project goals and requirements.
Defining resource requirements is crucial to ensure that the testing process has the necessary
people, tools, and environments. Resources to consider include test engineers,
testing tools, test data, and testing environments.
Test phases evolve in a progressive manner. Unit testing focuses on individual components to
verify their correctness. Integration testing examines the interactions between these components.
System testing evaluates the entire software system's functionality and performance. Finally,
acceptance testing ensures that the software
meets user requirements and is ready for production deployment.
Test strategy in a software testing project,
A test strategy is a critical document that defines the overall approach, scope, and objectives of the
testing effort. It guides test planning by specifying what to test and how to test it. Test design is
influenced by the strategy, ensuring that test cases align with project goals. A well-defined test
strategy enhances the chances of project success by providing a structured and organized
approach to software testing.
The selection of testing tools can significantly affect testing efficiency and automation capabilities.
Skilled test engineers can maximize the value derived from these tools through effective usage.
Resource requirements also encompass test data, which should
be representative of real-world scenarios, and testing environments, which should mimic the
production environment as closely as possible.
Structured and organized test cases ensure thorough testing coverage, help in replicating
scenarios, and enable efficient defect tracking. They act as a blueprint for validating software
functionality and are vital for achieving a high level of software quality.
Well-defined tester assignments ensure that each tester knows their responsibilities and areas
of focus within the testing project. It optimizes efficiency, enhances accountability, and facilitates
better collaboration among the testing team.
Well-structured test cases contribute to comprehensive test coverage by providing clarity on
what to test and how to test it. They enable efficient test execution and defect tracking. In
managing a large repository of test cases, strategies like categorization, test case management
tools, and regular reviews can be employed to ensure efficient maintenance, execution, and
continuous improvement of the test case repository
Bug Reporting
A well-structured bug report should include components like a clear title, detailed description,
steps to reproduce, expected and actual results, and system environment information. A detailed
bug report benefits the software development process by providing developers with precise
insights into the issue, making it easier to locate,
understand, and fix the problem efficiently
Metrics and statistics
Metrics and statistics help in quantifying testing progress, identifying trends, and making
data-driven decisions. Examples of key testing metrics include defect density, test
coverage, and mean time to failure (MTTF).
Testing metrics, like pass-fail ratios, can be used to optimize resource allocation by
identifying areas with a high density of defects. Test efforts can then be concentrated on
these areas, improving testing efficiency and directing resources where they are most needed.
Mean time to failure" (MTTF) .
MTTF is a metric that measures the average time between the occurrence of failures or defects in
a software system. It's significant for measuring software stability as it provides an estimate of
how long the system is expected to operate without critical
issues. A higher MTTF indicates greater stability and reliability.
In agile development, metrics and statistics can be integrated by using tools like burndown charts
and velocity charts to track progress. Teams can conduct regular retrospectives to discuss
performance metrics and identify areas for improvement. This approach ensures transparency
and facilitates continuous improvement.
Relying solely on metrics and statistics can lead to a tunnel vision approach. Challenges
include ignoring subjective aspects and overlooking user feedback. It's essential to consider
qualitative factors like user experience and feedback alongside quantitative data
to achieve a holistic assessment of testing effectiveness
