02 test planning


Published on

Testing with Visual Studio 2012 Agile TMap

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

02 test planning

  1. 1. Module 01Test Planning
  2. 2. Topics
  3. 3. Formulating a cohesiveand 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 andother stakeholdersconcerning the approach, schedule, budget, activities and the (end) products to be delivered inrelation 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-phaseThe Planning Phase
  4. 4. The Master Test Plan
  5. 5. What exactly will be tested?Based on business aspects:Result, Risks, Time and CostManaging the Test ProcessUnit TestLoad TestPerformance TestCoded UI Test
  6. 6. Business- orTechnology-facingSupporting the team,Critiquing the productAgile Testing QuadrantsPerformance &Load TestsSecurity Tests‘ility’ Tests
  7. 7. Test Levels, Phases and TypesEvery 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.
  8. 8. Software Testing with Visual Studio
  9. 9. DemoVisual Studio Test Types:Overview
  10. 10. Don‘t Test Twice!Save Effort and Money with agood Master Test Plan!
  11. 11. The Product Backlog
  12. 12. Value, Risk, Priority, NecessityGrooming theBacklogRisk ClassificationandBusiness ValueAcceptanceCriteriaLogical TestCases
  13. 13. Acceptance Test PlanningBusiness goalsActionablerequirementsAcceptance criteria Acceptance test planAcceptance test drivendevelopment w/ fulllifecycle traceability
  14. 14. 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
  15. 15. Business ValueProduct Backlog items have the attributes of adescription, order, and estimate and are often orderedby value, risk, priority, and necessity.Risk Classificationhttp://www.tmap.net/sites/tmap.net/files/attachments/Checklist__Risk_factors_per_quality_characteristic_.docOrdering the Backlog
  16. 16. Logical Test CasesLogical test cases are a combination of test situationsderived from scenarios and data.Test CoverageA test design technique that is used to derive thenecessary test cases to achieve required coverage froma specific test basis.Acceptance Test Driven
  17. 17. "Are you done yet?“Development Teams deliver an increment of a productfunctionality every Sprint. This increment is useable, soa Product Owner may choose to immediately release it.Shared UnderstandingEveryone must understand what “Done” means.Definition of “Done”
  18. 18. DemoPlanning the Project andTesting Effort
  19. 19. Groom the Backlog!
  20. 20. Testing in a Sprint
  21. 21. 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
  22. 22. To obtain, with the client’s agreement, a test basis that is of sufficient quality for designing the test cases. In order todetermine this, a testability review of the test basis is carried out during this phase, which will provide insight into thetestability of the system.http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/preparation-phaseThe Preparation Phase
  23. 23. Define test tasksduring the sprintplanning meeting.
  24. 24. “Define Test Cases based on thePCT2 Test Design Technique”Activity Type: Testing.Example: Test Specification Tasks
  25. 25. Every phase has specific test tasks.Planning, Control,Preparing, Specification,Execution, Complet-ion, Infrastructure.Test Lifecycle
  26. 26. Team Capacity Planning
  27. 27. DemoPlanning the Sprint.
  28. 28. SCRUM Boards
  29. 29. Always Read theSCRUM Board!
  30. 30. Put TestTasks on theSCRUM Board
  31. 31. The PBI isn’t ready to be tested until coding is done.Finish one item after another.Implementation Sequence