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
Tests in the top quadrantsvalidate business needs.Tests in the bottom quadrantsvalidate the implementation.Agile Testing QuadrantsPerformance &Load TestsSecurity Tests‘ility’ Tests
Tests in the right-handquadrants help the product.Tests in the left-hand quadrantshelp the team.Agile Testing QuadrantsPerformance &Load TestsSecurity Tests‘ility’ Tests
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
Acceptance TestsBusiness-facingCritique ProductA test script that checksif a feature behaves asexpected.Defined during backloggrooming and early inthe sprint.
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
DemoCreating a Test Plan withLogical Acceptance Tests
Unit TestsSupportingthe teamTechnologyfacingIsolate each part of theprogram and show thatthe individual parts arecorrect.Created in the sprint,Executed continuously.
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
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
Developer-focusedTestingRed Green RefactorPluggable testframeworksRun tests after buildUnit Test Explorer
Shims can be used to fake almostany method call, rendering yourlegacy code testableCreate a “fake” reference to any .dllreferenced by your testing project
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
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
Functional TestingSupportingthe teamTechnologyfacingValidates thefunctionality qualitycharacteristic, with thefunctional design as thetest basis.Specified and executedduring the sprint.
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
Test StepsShared StepsTest Data ParametersSpecify Test Cases
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
IntelliTrace LogsSystem logs & configurationDetailed status and historyvisible to all team membersAudio & Video recordings
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.
Exploratory TestingSupportingthe productSupports theImplementationSimultaneous testdesign and execution.Tests working software.
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
Time spent duringexploratory testingCourtesy of Jon BachTest SetupBug FilingTestingThe 3 Components of Testing
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
Add verification values toindicate the expected resultSession is paused while creatingtest casesTest steps are addedautomatically
Comment block reflectsthe added bugs and testsContinue exploratory testingright from where you left offQuick access to bugs and testcases created during the session
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
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
DemoEnd-to-end Test Workflowwith Coded UI Automation