Test Tooling in Visual Studio 2012 an overview

  • 3,102 views
Uploaded on

Test Tooling in Visual Studio 2012 an overview.

Test Tooling in Visual Studio 2012 an overview.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,102
On Slideshare
0
From Embeds
0
Number of Embeds
8

Actions

Shares
Downloads
44
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Show a master test plan
  • http://en.wikipedia.org/wiki/Unit_testing
  • Everything under analyseCode Clone tooArchitecturalanalysers
  • Everything under analyseCode Clone tooArchitecturalanalysers
  • Everything under analyseCode Clone tooArchitecturalanalysers
  • Everything under analyseCode Clone tooArchitecturalanalysers
  • http://en.wikipedia.org/wiki/Unit_testing
  • http://dannorth.net/whats-in-a-storyhttp://www.specflow.org/specflow/screencast.aspx
  • http://www.scrumalliance.org/articles/107-how-do-we-know-when-we-are-done
  • UMLModel Demo http://clemensreijnen.nl/post/2010/07/01/Visual-Studio-Architecture-Guidance-Use-UML-Models-for-Testing.aspx

Transcript

  • 1. TechNight Clemens Reijnen
  • 2. Continuous Quality
  • 3. ‘ility’ testingAlpha/ BetaComponent TestsExamplesExploratory TestingFunctional TestingLoad TestingPerformancePrototypesScenariosSecurity TestingSimulationsStory TestsUnit TestsUsability TestingUser Acceptance Testing
  • 4. Every test must be able to rely on previous tests All test types are supported by Visual Studio 2012http://www.tmap.net/en/tmap/4-essentials/structured-test-process/master-test-plan
  • 5. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
  • 6. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
  • 7. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
  • 8. Unit TestsComponent Tests
  • 9. Isolate each part of the program and show that theindividual parts are correct.Crafted during the sprint, executed continuously.
  • 10. Developer FocusedTestingRed Green RefactorPluggable testframeworksRun test after build
  • 11. Run from Unit TestExplorer
  • 12. Isolating code for better testing Shims – run-time interception lets you replace call Stubs – concrete implementations of interfaces or abstract classesStrive to refactor the code so you don’t need the Shims anymo
  • 13. Unit TestsComponent Tests
  • 14. Find semanticallysimilar code
  • 15. UnderstandingClass Coupling
  • 16. Check codingrules
  • 17. Functional TestingExamplesStory TestsPrototypesSimulations
  • 18. PrototypesSimulationsBeginning of the sprintmake pbi’s clear.
  • 19. Test RunnerAction Recording
  • 20. Test Automation Levels 0 No automation 1 Shared Steps with action recording 2 Test Cases with action recording 3 Generated Coded UI 4 Customized Coded UI
  • 21. Test Automation Levels Number of test cases per level in a sprint.
  • 22. Performance &Load TestingSecurity Testing‘ility’ testing
  • 23. Performance test:To determine or validatespeed, scalability, and/or proof businessstability. needsLoad test:To verify applicationbehavior under normal Supporting the Productand peak load conditions.
  • 24. Exploratory TestingScenariosUsability TestingUser AcceptanceTestingAlpha/ Beta
  • 25. Simultaneoustest design andexecution. Supporting the ProductTest workingsoftware. support the implementation
  • 26. http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/planning-phase
  • 27. Title / Description(describing the story)Acceptance Criteria:(presented as scenarios)
  • 28. Logical Test CasesTest Coverage
  • 29. "Are you done yet?“Shared Understanding
  • 30. Get a TeamGet Testing knowledgeHave Test Tasks
  • 31. Define Test Cases based on the PCT2 Test DesignTechnique
  • 32. Every phase has it’s specific test tasksPlanning, Control, Preparing, Specification, Execution, Completion, Control, Infrastructure.
  • 33. The PBI isn’t ready to be tested till coding is done.