09 high level test planning (v2.4)

22
© SIM Group Ltd., SQS Group AG, 2002 ISEB Foundation Certificate in Software Testing High Level Test Planning High Level Test Planning

Upload: rana-gaballah

Post on 23-Apr-2017

220 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

ISEB Foundation Certificate in Software Testing

High Level Test PlanningHigh Level Test Planning

Page 2: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

High Level Test Planning

In this session we willIn this session we will

Look at how a test plan is put togetherLook at how a test plan is put together

Understand how it should be used and maintainedUnderstand how it should be used and maintained

Understand why they are so important to a testing projectUnderstand why they are so important to a testing project

Page 3: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

High Level Test Planning

What is a test plan?What is a test plan?

A project plan for testingA project plan for testing

Covering all aspects of testingCovering all aspects of testing

Page 4: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

High Level Test Planning

Before you planBefore you plan

A test strategy must be in placeA test strategy must be in place

Page 5: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

The Different Sections of a Test Plan

Test plan identifierTest plan identifier

IntroductionIntroduction

Test itemsTest items

Features to be testedFeatures to be tested

Features not to be testedFeatures not to be tested

ApproachApproach

Item pass / fail criteriaItem pass / fail criteria

Suspension criteria & Suspension criteria & resumption criteriaresumption criteria

Test deliverablesTest deliverables Testing tasksTesting tasks EnvironmentEnvironment ResponsibilitiesResponsibilities Staffing and training needsStaffing and training needs SchedulesSchedules Risks and contingenciesRisks and contingencies ApprovalsApprovals

Based upon IEEE 829-1998 standard for Based upon IEEE 829-1998 standard for software test documentationsoftware test documentation

Page 6: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Test Plan Identifier

A unique identifier for the test planA unique identifier for the test plan

Page 7: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Introduction

The introduction shouldThe introduction should

Give an overview of the planGive an overview of the plan A summary of the requirementsA summary of the requirements Discuss what needs to be achievedDiscuss what needs to be achieved Detail why testing is neededDetail why testing is needed

Reference to other documentsReference to other documents Quality assurance and configuration managementQuality assurance and configuration management

Page 8: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Test Items

The various items to be used in the testsThe various items to be used in the tests

The software itemsThe software items

Their versions numbers / identifiersTheir versions numbers / identifiers

How they will be handed over to testingHow they will be handed over to testing

References to relevant documentsReferences to relevant documents

Page 9: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Features to Be Tested

List all features of the SUT that will be tested under this List all features of the SUT that will be tested under this planplan

Page 10: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Features Not to Be Tested

List all features of the SUT that will not be tested under List all features of the SUT that will not be tested under this planthis plan

Between the test items, features to be tested and features not to be Between the test items, features to be tested and features not to be tested we have scope of the projecttested we have scope of the project

Page 11: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Approach

Describes the approach to testing the SUTDescribes the approach to testing the SUT

This should be high level, but sufficient to estimate the time This should be high level, but sufficient to estimate the time and resources requiredand resources required

What this approach will achieveWhat this approach will achieve Specify major activitiesSpecify major activities Testing techniquesTesting techniques Testing tools / aidsTesting tools / aids Constraints to testingConstraints to testing Support required - environment & staffingSupport required - environment & staffing

Page 12: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Item Pass / Fail Criteria

How to judge whether a test item has passedHow to judge whether a test item has passed

Expected vs. Actual resultsExpected vs. Actual results

Certain % of tests passCertain % of tests pass

Number of faults remaining (known and estimated)Number of faults remaining (known and estimated)

Should be defined for each test itemShould be defined for each test item

Page 13: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Suspension criteria & resumption requirements

Reasons that would cause testing to be suspendedReasons that would cause testing to be suspended

Steps necessary to resume testingSteps necessary to resume testing

Page 14: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Test Deliverables

Everything that goes to make up the testsEverything that goes to make up the tests

All documentationAll documentation e.g. Specification, test plans, procedures, reportse.g. Specification, test plans, procedures, reports

Code releasesCode releases

Testing toolsTesting tools Test management tools, automation tools, excel, word etcTest management tools, automation tools, excel, word etc

Test systemsTest systems Manual and automated test casesManual and automated test cases

Page 15: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Testing Tasks

Preparation to perform testingPreparation to perform testing Test case identificationTest case identification Test case designTest case design Test data storageTest data storage Baseline applicationBaseline application

Special skills neededSpecial skills needed Spreadsheet skills, test analysis, automation etcSpreadsheet skills, test analysis, automation etc

Inter-dependenciesInter-dependencies

Page 16: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Environment

Requirements for test environmentRequirements for test environment

Hardware & softwareHardware & software PCs, servers, routers etcPCs, servers, routers etc SUT, interfaced applications, databasesSUT, interfaced applications, databases

ConfigurationConfiguration Maybe operating systems or middleware to test againstMaybe operating systems or middleware to test against

FacilitiesFacilities Office space, desks, internet accessOffice space, desks, internet access

Page 17: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Responsibilities

Who is responsible?Who is responsible?

For which activitiesFor which activities

For which deliverablesFor which deliverables

For the environmentFor the environment

Page 18: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Staffing and Training Needs

Staff requiredStaff required Test managers, team leaders, testers, test analystsTest managers, team leaders, testers, test analysts

Skill levels requiredSkill levels required Automation experienceAutomation experience Spreadsheet skills, etcSpreadsheet skills, etc

Training requirementsTraining requirements Tools specific trainingTools specific training Refresher courses, etc. Refresher courses, etc. Overall project resource requirementsOverall project resource requirements

Page 19: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Schedule

Timescales, dates and milestonesTimescales, dates and milestones

Resources required to meet milestonesResources required to meet milestones

Availability of software and environmentAvailability of software and environment

DeliverablesDeliverables

Page 20: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Risks and Contingencies

What might go wrong?What might go wrong?

Actions for minimising impact on testing should things go Actions for minimising impact on testing should things go wrongwrong

Page 21: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

Approvals

Who has approved the test planWho has approved the test plan

Names and dates of approvalNames and dates of approval

Why is it so importantWhy is it so important Evidence that the document has been viewedEvidence that the document has been viewed Shows that the approach has been agreed and has the backing Shows that the approach has been agreed and has the backing

of those who matterof those who matter You have commitment, now make them stick to it!You have commitment, now make them stick to it!

Page 22: 09 High Level Test Planning (v2.4)

© SIM Group Ltd., SQS Group AG, 2002

High Level Test Planning

SummarySummary

Test plans are created to ensure that the requirements are Test plans are created to ensure that the requirements are understoodunderstood

To ensure that maximum test coverage is achievedTo ensure that maximum test coverage is achieved

To identify all items that will form the testTo identify all items that will form the test