TechNight   Clemens Reijnen
Continuous Quality
‘ility’ testingAlpha/ BetaComponent TestsExamplesExploratory TestingFunctional TestingLoad TestingPerformancePrototypesSce...
Every test must be able to rely on previous                                    tests                                    Al...
Exploratory TestingFunctional Testing   ScenariosExamples             Usability TestingStory Tests          User Acceptanc...
Exploratory TestingFunctional Testing   ScenariosExamples             Usability TestingStory Tests          User Acceptanc...
Exploratory TestingFunctional Testing   ScenariosExamples             Usability TestingStory Tests          User Acceptanc...
Unit TestsComponent Tests
Isolate each part of the program and show that theindividual parts are correct.Crafted during the sprint, executed continu...
Developer FocusedTestingRed Green RefactorPluggable testframeworksRun test after build
Run from Unit TestExplorer
Isolating code for better testing       Shims – run-time interception lets you replace call       Stubs – concrete impleme...
Unit TestsComponent Tests
Find semanticallysimilar code
UnderstandingClass Coupling
Check codingrules
Functional TestingExamplesStory TestsPrototypesSimulations
PrototypesSimulationsBeginning of the sprintmake pbi’s clear.
Test RunnerAction Recording
Test Automation Levels   0   No automation                         1   Shared Steps with action                           ...
Test Automation Levels                  Number of test cases per level in a                  sprint.
Performance &Load TestingSecurity Testing‘ility’ testing
Performance test:To determine or validatespeed, scalability, and/or                             proof businessstability.  ...
Exploratory TestingScenariosUsability TestingUser AcceptanceTestingAlpha/ Beta
Simultaneoustest design andexecution.        Supporting the                  ProductTest workingsoftware.                 ...
http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/planning-phase
Title / Description(describing the story)Acceptance Criteria:(presented as scenarios)
Logical Test CasesTest Coverage
"Are you done yet?“Shared Understanding
Get a TeamGet Testing knowledgeHave Test Tasks
Define Test Cases based on the PCT2 Test DesignTechnique
Every phase has it’s specific test tasksPlanning, Control, Preparing, Specification, Execution, Completion, Control, Infra...
The PBI isn’t ready to be tested till coding is done.
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Test Tooling in Visual Studio 2012 an overview
Upcoming SlideShare
Loading in...5
×

Test Tooling in Visual Studio 2012 an overview

3,395

Published on

Test Tooling in Visual Studio 2012 an overview.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,395
On Slideshare
0
From Embeds
0
Number of Embeds
9
Actions
Shares
0
Downloads
52
Comments
0
Likes
1
Embeds 0
No embeds

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
  • Test Tooling in Visual Studio 2012 an overview

    1. 1. TechNight Clemens Reijnen
    2. 2. Continuous Quality
    3. 3. ‘ility’ testingAlpha/ BetaComponent TestsExamplesExploratory TestingFunctional TestingLoad TestingPerformancePrototypesScenariosSecurity TestingSimulationsStory TestsUnit TestsUsability TestingUser Acceptance Testing
    4. 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. 5. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
    6. 6. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
    7. 7. Exploratory TestingFunctional Testing ScenariosExamples Usability TestingStory Tests User AcceptancePrototypes TestingSimulations Alpha/ Beta Performance & Load TestingUnit Tests Security TestingComponent Tests ‘ility’ testing
    8. 8. Unit TestsComponent Tests
    9. 9. Isolate each part of the program and show that theindividual parts are correct.Crafted during the sprint, executed continuously.
    10. 10. Developer FocusedTestingRed Green RefactorPluggable testframeworksRun test after build
    11. 11. Run from Unit TestExplorer
    12. 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. 13. Unit TestsComponent Tests
    14. 14. Find semanticallysimilar code
    15. 15. UnderstandingClass Coupling
    16. 16. Check codingrules
    17. 17. Functional TestingExamplesStory TestsPrototypesSimulations
    18. 18. PrototypesSimulationsBeginning of the sprintmake pbi’s clear.
    19. 19. Test RunnerAction Recording
    20. 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. 21. Test Automation Levels Number of test cases per level in a sprint.
    22. 22. Performance &Load TestingSecurity Testing‘ility’ testing
    23. 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. 24. Exploratory TestingScenariosUsability TestingUser AcceptanceTestingAlpha/ Beta
    25. 25. Simultaneoustest design andexecution. Supporting the ProductTest workingsoftware. support the implementation
    26. 26. http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/planning-phase
    27. 27. Title / Description(describing the story)Acceptance Criteria:(presented as scenarios)
    28. 28. Logical Test CasesTest Coverage
    29. 29. "Are you done yet?“Shared Understanding
    30. 30. Get a TeamGet Testing knowledgeHave Test Tasks
    31. 31. Define Test Cases based on the PCT2 Test DesignTechnique
    32. 32. Every phase has it’s specific test tasksPlanning, Control, Preparing, Specification, Execution, Completion, Control, Infrastructure.
    33. 33. The PBI isn’t ready to be tested till coding is done.
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×