Testing in TFS involves managing the test process to improve quality and customer satisfaction. Key aspects of testing in TFS include: test planning, authoring test cases and scenarios, executing tests in test suites, tracking and reporting results, and managing bugs. Test cases go through various states like design, ready, pass, fail, and more to track progress and ensure quality.

1. Testing in TFS
Quality Assurance (QA): QA is a way of preventing mistakes or defects in manufactured products
and avoiding problems when delivering solutions or services to customers.
Testing: Testing is the process of evaluating a system or its component(s) with the intent to find that
whether it satisfies the specified requirements or not. System executed in order to identify any gaps, errors
or missing requirement in contrary to the actual desire or requirement.
Who - In most cases testing done by Tester, Developer, and Project Lead/Manage and End user.
When – Started from requirement gathering and lasts till deployment of software.
Test Management:
Managing the testprocessto shiphighqualityproduct whichincrease customersatisfaction&leadto
smoother& consistentquality.
Test Preparation:
 TestPlanning– Developingthe testpurpose,when&environment basedonspecification. Whatneedstobe
testingisbrokendownintomultiple TestScenario/Case.
 TestAuthoring– Definingthe generictestcase whichare thenbrokendownintodetailedteststeps. Test
Stepsare defined&order.
TestCase,Test Scenario andTestdata preparation.
Test Execution:
 TestExecution – Run testcase in logical setsreferredasTestSuite. Runinspecifiedconfiguration&
recorded.
 TestTracking – TestResultsare logged&tracked.
 TestReporting– Evaluate testingeffortsandcommunicate testresultstoothers.
TestSuite, Execute Test, andBugReportingandRetesting.

2. Testing in TFS
Test activity in TFS
Test plan: We can define test scope basedtestsuite canbe created, resources,testenvironmentandschedule of
intendedtestactivities. Itisa record of the test planningprocess.
Test Suite:Clubof Test Case/Scenario.TestSuitebasedonSprinttoidentifythe sprint testscope &quality.
Test Case/Scenario preparation:Setof conditionsorvariables/situationorscene underwhichatesterwill
determine whetheranapplication,software systemorone of itsfeaturesisworkingasit was originallyestablished
for itto do. Prerequisite defines whatshouldbe available before startingatestexecution.

3. Testing in TFS
Test State:
 Design – Test case/Scenario in preparation (designing) not yet ready for test execution.
 Ready – Test case/Scenario preparation is completed & it is ready for test execution.
Test Priority:
It is a test classification variable, where it’s classified based Risk, Visibility & Threat. In simple terms
Priority = Severity + Frequency
 Risk – Probability of failure
 Visibility – Where the test visible (i.e: Occurrence is high the priority should be high)
 Threat – How much damage could be caused if there was an error in this area
Smoke Testing: Teststhat aimat ensuringthatthe most importantfunctionswork.The resultsof thistestingis
usedto decide if abuildisstable enoughtoproceedwithfurthertesting.
Test Case/Scenario execution:Testare Ran to evaluate actual result&compare actual resultwithexpectedresult
to specifywhere the steppassorfail. Whenall the stepswhere pass,thenthe testcase ismarkedas pass.Whena
stepfailedthenit’smarkedasfailed&testcase savedas testfailed.

4. Testing in TFS
Test Case/Scenario Status:
 PassTest – All the teststepspass
 Fail Test – Atleastone stepfail
 Pause Test – Testkepton hold
 BlockTest – Unable toexecute the testdue todependentrequirementnotworking
 Notapplicable – Outof Scope
Bug Reporting:Thena bugis raisedwhenateststepfailedusingcreate bug& itsID is specifiedincomments. Bug
Title representsthe failure clearly.WhereStepstoreproduce explainthe stepstoreproduce the bug& itsAssigned
to the developerwhoworkedonthatarea. Bug can be raisedapart fromtestcase too withoutlinking.
Severity:It isthe extenttowhichthe defectcan affectthe software.Itdefinesthe impactthata givendefecthason
the system.Severityispurelybasedonusercontext
Critical – It is impossible tocontinue testingbecause of the defect.Testingcancontinue butthe applicationcannot
be releasedintoproductionuntil thisdefectisfixed.
High – Testingcancontinue butthisdefectwill resultinasevere departure fromthe businessrequirementsif
releasedforproduction.
Medium– Testingcan continue andthe defectwill cause onlyminimal departure fromthe businessrequirements
wheninproduction.
Minor – Testingcan continue andthe defectwill notaffectthe releaseintoproduction.The defectshouldbe
correctedbut little ornochangesto businessrequirementsare envisaged.Minorcosmeticissueslikecolors,fonts,

5. Testing in TFS
and pitchsize thatdo not affecttestingorproductionrelease.If,however,these featuresare importantbusiness
requirementsthentheywill receive ahigherseveritylevel.
Our Agile Bug Life Cycle in TFS:
RemovedReason:
 Removedfromthe backlog – KnownIssue orDeferred
 Duplicate – Same bugraisedtwice
 Notan Issue – Asrequirementreversedormisunderstood&wronglyraised
New
(QA)
Committed
(Dev)
Done
(QA)
Removed
(QA)
Approved
(Dev)

6. Testing in TFS
Re-testing: Conformation testing for a specific bug after it has been fixed & Re-run of failed to test case.
Pair testing: Two team members work together at one keyboard to test the software application. One does
the testing and the other analyses or reviews the testing.
Sprint Test Summary Report:
Overall Summary - Sprint Name
Test Case Execution Ratio
Sprint Planned Executed Pending Completion %
SprintName 90 90 0 100%
Test Case Success Ratio
Sprint Total Pass Fail Pass %
SprintName 90 59 31 66%
Active Test Case Priority Ratio
Sprint Priority 1 Priority 2 Priority 3 Priority 4
SprintName 0 31 0 0
Overall Bug Severity
Sprint Critical High Medium Low
SprintName 26 13 41 2
Active Bug Severity
Sprint Critical High Medium Low
SprintName 4 2 19 2
Bug Fix Ratio by Severity
Sprint Bug Done Pending Bug Fixing %
SprintName 227 165 62 73%
Bug Fix Ratio
Sprint Bug Done Pending Bug Fixing %
SprintName 82 55 27 67%

7. Testing in TFS
Project Quality Track Report: