03 test specification and execution


Published on

Testing with Visual Studio 2012 Agile TMap

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

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

No notes for slide

03 test specification and execution

  1. 1. Module 02Test Specificationand Execution
  2. 2. Topics
  3. 3. During the Specification phase, the required tests and starting points are specified. The aim is to have as much aspossible prepared, in order to be able to run the test as quickly as possiblewhen the developers deliver the test object.http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/specification-phaseThe Specification Phase
  4. 4. Tests in the top quadrantsvalidate business needs.Tests in the bottom quadrantsvalidate the implementation.Agile Testing QuadrantsPerformance &Load TestsSecurity Tests‘ility’ Tests
  5. 5. Tests in the right-handquadrants help the product.Tests in the left-hand quadrantshelp the team.Agile Testing QuadrantsPerformance &Load TestsSecurity Tests‘ility’ Tests
  6. 6. To obtain insight into the quality of the test object through the execution of the agreed tests.http://www.tmap.net/en/tmap/4-essentials/structured-test-process/acceptance-and-system/execution-phaseThe Execution Phase
  7. 7. Test Types
  8. 8. Acceptance TestsBusiness-facingCritique ProductA test script that checksif a feature behaves asexpected.Defined during backloggrooming and early inthe sprint.
  9. 9. Requirements and bugs linkdirectly to related test casesIntegrated Storyboarding withPowerPoint keeps stakeholders andall team members in syncMeasurable acceptancecriteria, visible to all teammembers, aligns with tests
  10. 10. ResultUser Story Test Status Report
  11. 11. DemoCreating a Test Plan withLogical Acceptance Tests
  12. 12. Unit TestsSupportingthe teamTechnologyfacingIsolate each part of theprogram and show thatthe individual parts arecorrect.Created in the sprint,Executed continuously.
  13. 13. Unit testing is a method by which individual units of source code, sets of one or more computer program modules togetherwith associated control data, usage procedures, and operating procedures, are tested to determine if they are fit for use.Intuitively, one can view a unit as the smallest testable part of an application.Definition of DoneAll unit tests are written and have been successfully executed.Code CoverageCode coverage records for each package are available and whatever the team has decided as the minimum benchmarkhas been achieved.Unit Tests
  14. 14. Use the testing frameworkyou’re familiar with to writeyour unit testsQuickly run all unit tests, ortarget specific tests orgroups of testsQuickly examine results of eachtest during the previous test runwith the Test Explorer
  15. 15. Developer-focusedTestingRed Green RefactorPluggable testframeworksRun tests after buildUnit Test Explorer
  16. 16. Shims can be used to fake almostany method call, rendering yourlegacy code testableCreate a “fake” reference to any .dllreferenced by your testing project
  17. 17. The Fakes Framework allows youto shim SharePoint web parts,improving testabilityExplore and execute tests usingthe same first-class Test ExplorerManage the unit testproject directly alongsideyour SharePoint projectsUse familiar SharePoint codeto create your unit tests
  18. 18. Group unit tests by project,traits, duration, results and moreCode coverage analysis determinesthe portion of your code covered byunit tests, down to the method levelResults can be exported andsaved for future analysis
  19. 19. Code CoverageCode Clone AnalysisStatic Code AnalysisCode ReviewsTest Impact Analysis*Developer-focused Code Quality Tools
  20. 20. DemoCode Quality Tools
  21. 21. Functional TestingSupportingthe teamTechnologyfacingValidates thefunctionality qualitycharacteristic, with thefunctional design as thetest basis.Specified and executedduring the sprint.
  22. 22. Specified and executed during the sprintAll functionality created during a sprint is tested during the same sprint.Test coverageLinked work items are used for test coverage.Definition of DoneAll priority 1 test cases are executed.All high risk backlog items have a test coverage of 80%.Test Case promotion to regression setsSome test cases will be part of regression testing efforts.Functional Tests
  23. 23. Test StepsShared StepsTest Data ParametersSpecify Test Cases
  24. 24. Organize testing in multipleconfigurationsPlayback a prior recording to savetime with frequently-repeatedsetup steps and prerequisitesBind data to controls, tosupport multiple iterationsand future automationPause, save, close, return, andpick up where you left off
  25. 25. Test RunnerAction RecordingExecute Test Cases
  26. 26. IntelliTrace LogsSystem logs & configurationDetailed status and historyvisible to all team membersAudio & Video recordings
  27. 27. Get an overview of the test runwith summary pie charts, or drillinto the details for each test.Analyze code coverage for manualtests to determine which specificparts of your code were tested .Associate manual test runswith builds and environments.
  28. 28. Recommended TestsShows passed Tests withchanged source codeTest Impact Analysis
  29. 29. Exploratory TestingSupportingthe productSupports theImplementationSimultaneous testdesign and execution.Tests working software.
  30. 30. Create rich text commentswith screenshots whileexploringExploratory sessions canbe recorded to increasereproducibilityExplore your application touncover new defectsThe Test Runner docks on the leftside of the screen and automaticallyrecords your steps as you explore
  31. 31. Time spent duringexploratory testingCourtesy of Jon BachTest SetupBug FilingTestingThe 3 Components of Testing
  32. 32. Comments and steps areautomatically addedThe exploratory test sessionis paused while you create abug reportFile new bugs without ending theexploratory test sessionAttach the video recorded duringthe exploratory test session formaximum reproducibilityQuickly create anautomatically linked testcase for this bug
  33. 33. Add verification values toindicate the expected resultSession is paused while creatingtest casesTest steps are addedautomatically
  34. 34. Comment block reflectsthe added bugs and testsContinue exploratory testingright from where you left offQuick access to bugs and testcases created during the session
  35. 35. DemoExploratory Testing
  36. 36. Performance and Load TestingSupportingthe productSupports theImplementationPerformance TestTo determine or validate speed, scalability, and/or stability.Load TestTo verify application behavior under normal andpeakload conditions.
  37. 37. Web Performance Test
  38. 38. Load Test
  39. 39. DemoWeb Performance TestLoad Test
  40. 40. Test Automation
  41. 41. Test AutomationPerformance &Load TestsSecurity Tests‘ility’ TestsAutomatedand ManualManualAutomatedToolsAutomated
  42. 42. Visual Studio SupportPerformance &Load TestsSecurity Tests‘ility’ Tests
  43. 43. Convert the test case tocode for enhancedflexibilityGenerate your Coded UI test froman existing recording, or record anew test case on the fly
  44. 44. Test Automation with CodedUI Tests
  45. 45. CodedUI tests interactdirectly with your app’s UITests can be run and monitoredon the local machine, or furtherautomated on a virtual machineCross-browser testing supportallows automated testing onmultiple browsers
  46. 46. Coded UI tests run as part of yourunit testing suite, enablingdevelopers to detect defects earlyEven if the look & feel changes, theautomated test still executes properlyCoded UI tests are part ofsource control formaximum visibility
  47. 47. DemoEnd-to-end Test Workflowwith Coded UI Automation