02 test planning

32
Module 01 Test Planning

description

Testing with Visual Studio 2012 Agile TMap

Transcript of 02 test planning

Page 1: 02   test planning

Module 01Test Planning

Page 2: 02   test planning

Topics

Page 3: 02   test planning

Formulating a cohesive and broadly supported approach with which the test assignment can be successfully executed. An important part of the planning phase is the creation of the test plan, for the purpose of informing the client and other stakeholders concerning the approach, schedule, budget, activities and the (end) products to be delivered in relation to the test process. If an overall master test plan exists, the test plan should be derived from it.

http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/planning-phase

The Planning Phase

Page 4: 02   test planning

The Master Test Plan

Page 5: 02   test planning

What exactly will be tested?

Based on business aspects:Result, Risks, Time and Cost

Managing the Test Process

Unit Test

Load Test

Performance Test

Coded UI Test

Page 6: 02   test planning

Business- orTechnology-facing

Supporting the team,Critiquing the product

Agile Testing Quadrants

Performance &

Load Tests

Security Tests

‘ility’ Tests

Page 7: 02   test planning

Test Levels, Phases and Types

Every test must rely on previous testsTest goals/depth of coverage per phase are coordinated with each other using a Master Test Plan.

All test types are supported by Visual StudioFunctional Testing, Examples, Story Tests, Prototypes, Simulations, Exploratory Testing, Scenarios, Usability Testing, User Acceptance Testing, Alpha/Beta, Unit Tests, Component Tests, Performance & Load Testing, Security Testing, ‘ility’ testing.

Page 8: 02   test planning

Software Testing with Visual Studio

Page 9: 02   test planning

Demo

Visual Studio Test Types:Overview

Page 10: 02   test planning

Don‘t Test Twice!Save Effort and Money with agood Master Test Plan!

Page 11: 02   test planning

The Product Backlog

Page 12: 02   test planning

Value, Risk, Priority, Necessity

Grooming the

Backlog

Risk Classification

and

Business Value

Acceptance

Criteria

Logical Test

Cases

Page 13: 02   test planning

Acceptance Test Planning

Business goalsActionable

requirementsAcceptance criteria Acceptance test plan

Acceptance test driven

development w/ full

lifecycle traceability

Page 14: 02   test planning

Title/Description(describing the story)

Narrative: As a [role] I want [feature] so that [benefit].

Acceptance Criteria(presented as scenarios)

Given [context]and [some more context]...

When [event]

then [outcome] and [another outcome]...

Acceptance Criteria

Page 15: 02   test planning

Business ValueProduct Backlog items have the attributes of a description, order, and estimate and are often ordered by value, risk, priority, and necessity.

Risk Classificationhttp://www.tmap.net/sites/tmap.net/files/attachments/Checklist__Risk_factors_per_quality_characteristic_.doc

Ordering the Backlog

Page 16: 02   test planning

Logical Test CasesLogical test cases are a combination of test situations derived from scenarios and data.

Test CoverageA test design technique that is used to derive the necessary test cases to achieve required coverage from a specific test basis.

Acceptance Test Driven

Page 17: 02   test planning

"Are you done yet?“Development Teams deliver an increment of a product functionality every Sprint. This increment is useable, so a Product Owner may choose to immediately release it.

Shared UnderstandingEveryone must understand what “Done” means.

Definition of “Done”

Page 18: 02   test planning

Demo

Planning the Project andTesting Effort

Page 19: 02   test planning

Groom the Backlog!

Page 20: 02   test planning

Testing in a Sprint

Page 21: 02   test planning

It’s a team effort!Do not forget to include testers in Sprint planning/execution.

Get Testing knowledgeThis is a must have for proper estimation and effort planning!

Define Test TasksTesting should be an integral part of the “Definition of Done”!

Testing in a Sprint

Page 22: 02   test planning

To obtain, with the client’s agreement, a test basis that is of sufficient quality for designing the test cases. In order to determine this, a testability review of the test basis is carried out during this phase, which will provide insight into the testability of the system.

http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/preparation-phase

The Preparation Phase

Page 23: 02   test planning

Define test tasks during the sprint planning meeting.

Page 24: 02   test planning

“Define Test Cases based on thePCT2 Test Design Technique”

Activity Type: Testing.

Example: Test Specification Tasks

Page 25: 02   test planning

Every phase has specific test tasks.

Planning, Control,Preparing, Specification, Execution, Complet-ion, Infrastructure.

Test Lifecycle

Page 26: 02   test planning

Team Capacity Planning

Page 27: 02   test planning

Demo

Planning the Sprint.

Page 28: 02   test planning

SCRUM Boards

Page 29: 02   test planning

Always Read theSCRUM Board!

Page 30: 02   test planning

Put TestTasks on theSCRUM Board

Page 31: 02   test planning

The PBI isn’t ready to be tested until coding is done.

Finish one item after another.

Implementation Sequence

Page 32: 02   test planning