• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
10+ Reasons to Use Static Testing
 

10+ Reasons to Use Static Testing

on

  • 374 views

This is a sequel of Forgotten? Ignored? Obsolete? presentation on static testing techniques. It is focused on key product and process risks mitigated by static testing.

This is a sequel of Forgotten? Ignored? Obsolete? presentation on static testing techniques. It is focused on key product and process risks mitigated by static testing.

Statistics

Views

Total Views
374
Views on SlideShare
370
Embed Views
4

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 4

http://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    10+ Reasons to Use Static Testing 10+ Reasons to Use Static Testing Presentation Transcript

    • 10+ Reasons To UseStatic Testing TechniquesRisk AnalysisMikhail PavlovTuesday, 30 April, 13
    • “Risk management is projectmanagement for adults.”Tom DeMarco “Waltzing With Bears”,20032Tuesday, 30 April, 13
    • Reason 1Static testing is moreefficient than otherapproaches3Tuesday, 30 April, 13
    • Reason 1 - RiskMitigationSchedule and efforts overrunProduct quality level is lower thanexpected4Tuesday, 30 April, 13
    • Reason 2Static testing can beconducted even if anobject of testing is notready to be executed5Tuesday, 30 April, 13
    • Reason 2 - RiskMitigationLater application-under-testreadiness for testingTime for test execution is notsufficient6Tuesday, 30 April, 13
    • Reason 3Static testing helps to finderrors early7Tuesday, 30 April, 13
    • Reason 3 - RiskMitigationInformation about application-under-test quality is not availablefor project stakeholders on timeTimeframes for fixing defects arenot sufficient8Tuesday, 30 April, 13
    • Reason 4Sometimes static testing isthe only approach to teston time9Tuesday, 30 April, 13
    • Reason 4 - RiskMitigationRequirements and design defects can leak outto subsequent SDLC phasesRequirements and design defects are harderto find and more expensive to fix later in SDLCTests executed are not enough to achieve acertain level of quality10Tuesday, 30 April, 13
    • Reason 5About half of defectsdetectable by dynamictesting techniques can befound using static testing11Tuesday, 30 April, 13
    • Reason 5 - RiskMitigationDefect leakage to productionLate defect detectionInefficient use of testing resources12Tuesday, 30 April, 13
    • Reason 6Static testing aims to findfailures directly13Tuesday, 30 April, 13
    • Reason 6 - RiskMitigationHigh debugging costsHigher testing costs14Tuesday, 30 April, 13
    • Reason 7The highest product qualitycan be delivered tocustomer when statictesting is used in synergywith other approaches15Tuesday, 30 April, 13
    • Reason 7 - RiskMitigationProduct quality level is lower thanexpected (esp. for mission-criticalsystems)Project execution discipline doesnot match project goals16Tuesday, 30 April, 13
    • Reason 8Static testing reduces totalcosts of a project17Tuesday, 30 April, 13
    • Reason 8 - RiskMitigationBudget overrunHigh rework efforts18Tuesday, 30 April, 13
    • Reason 9Static testing of testwareleads to its higher defectdetection power19Tuesday, 30 April, 13
    • Reason 9 - RiskMitigationInsufficient test coverageGoals of test scripts cannot be achievedUnreliable test automation frameworkDefects leakage to production20Tuesday, 30 April, 13
    • Reasons 10+What are your reasons to usestatic testing in your project?What risks do you mitigate?Tuesday, 30 April, 13