Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
• Test planning is the most important activity undertaken by a test leader in any test project.
• Ensures there is a list of tasks and milestones in a baseline plan to track progress .
• Defining the shape and size of the test effort.
WHEN IS TEST PLANNING USED?
• Used in development and implementation projects as well as maintenance (Change and fix) activities.
DOCUMENTS IN TEST PLANNING
• The main document produced in test planning is called a master test plan or project test plan.
• This document defines the high level of test activities being planned.
• Normally produced in early stages of project.
• Provides sufficient information to enable a test project to be established.
• The details of the test-level activities are documented within test-level plans.
WAIT… THERE IS AN ACRONYM??? SPACEDIRT
• Determine the scope and risks that need testing, involve the Project Manager and Subject
Manager.
• Identify and agree on the objectives of testing, with a focus on TIME, QUALITY and COST.
• Objectives assist Manager’s to know when the Test Project is finished.
• A Test Strategy (Overall Approach) ensures that test levels, entry criteria and exit criteria are
defined.
• Liaise with the Project Manager ensuring testing activities have been included within the
Software Life Cycle activities such as:
Design – the development of Software Design
Development – the building of the code
Implementation – the activities surrounding implementation into a live environment
TEST PLANNING ACTIVITIES
The following are required activities for Test Planning, for both whole or part systems: Part 2
• Identifying what needs to be tested, who will be performing the testing and in which roles.
• How and when the test activities should take place .
• Deciding on test result evaluation and when to stop testing (Exit Criteria).
• Create a Plan to identify when and who will undertake the test analysis and design activities along
with the documentation of the schedule for test implementation, test execution and test evaluation.
• Sourcing and delegating resources for each defined activity.
• Decide on the format of test project documentation, and which plans and test cases will be
documented.
• Define Management information including the metrics required, establishing processes to monitor
and control test preparation and execution along with defect resolution and risk issues.
• Ensure that test documentation generates test assets i.e. test cases.
ENTRY CRITERIA
• There are two very different Test Estimation approaches. They are:
• The Metrics based approach – data based.
• The Expert based approach – subjective based.
TEST ESTIMATION
• The Metrics-based approach
• Relies upon data collected from previous or similar projects. Data collected might included the
following:
Number of Test Conditions.
Number of Test Cases written.
Number of Test Cases executed.
Time taken to develop Test Cases.
Time taken to run Test Cases.
Number of defects found.
Number of environment outages and average length as to how long each one lasted.
• It is essential for this approach to be a success is that actual costs and time for testing is
accurately recorded.
• The record cards from one project can be used for the metrics for the next project.
TEST ESTIMATION
Expert estimating can be done individually or collectively using either or both the examples given above.
CONCLUSION
• Many things affect the level of effort required to fulfil the test requirements of a project.
These can be split into three main categories, as listed below.
1. Product characteristics
2. Development process characteristics
3. Expected outcome of testing
CONCLUSION
• Product characteristics:
Size of the test basis
Complexity of the final product
The amount of non-functional requirements
The security requirements (perhaps meeting BS 7799, the security standard)
How much documentation is required (e.g. some legislation-driven changes demand a certain
level of documentation that may be more than an organisation would normally produce)
The availability and quality of the test basis (e.g. requirements and specifications)
CONCLUSION
• Taking all of this into account, once the estimate is developed and agreed the test leader can set about
identifying the required resources and building the detailed plan.