1 / 18

Introduction to Testing

Learn about the definition and goals of software testing, as well as the importance of early bug detection. Discover the common causes of software problems and the cost of fixing bugs. Understand the role of professionalism in testing and when to stop testing. Get insights into test system designs and the usage of test processes and testware.

wmh
Download Presentation

Introduction to Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Testing

  2. Topics • Who are we? • Software Testing Definition and Goals • Facts and Numbers

  3. Quality Time Cost The Software Quality Dilemma

  4. Topics • Who are we? • Software Testing Definition and Goals • Facts and Numbers

  5. Software Testing - Definition “The process of exercising or evaluating a system by manual or automated means to verify that it satisfies specified requirements or to identify differences between expected and actual results.” (IEEE Standard Glossary, 1983)

  6. Software Testing • Software testing is not a phase • It is a process that should be integrated into the entire software life-cycle • There are testing deliverables associated with every phase of development

  7. What are the Goals of Testing? • To locate and prevent bugs as early as possible • To perform all Tests according to the Requirements, in the most effective and economic way • To bring the software product to a level of quality that is appropriate for the client We perform all of the above through Methodology Implementation

  8. Why Does Software Have Bugs? • Miscommunication or Lack of Communication • Misunderstandings • Time Pressure • Programmer’s Skill Level is Low

  9. Bad Communication

  10. Bad Communication - Requirements

  11. Topics • Who are we? • Software Testing Definition and Goals • Facts and Numbers

  12. Where do Software Problems Come From? • Insufficiently defined requirements 50% • Ambiguous or insufficient design 30% • Programming errors 20%

  13. Cost of Fixing Bugs Req Design Coding Int. test Sys. test Operation

  14. Remember The later a bug is found, the higher the cost of fixing it

  15. Errors? Fix Them as Early as Possible SOW DPD CODING TESTING OGS

  16. Professional Testing Professionalism in testing is the ability to select the minimum number of efficient test cases that will verify the maximum number of system functions.

  17. When to Stop Testing ? • Never • When the number of detected defects in one cycle is less than the agreed upon number • When no critical or highly severe defects are detected • When the time has expired

  18. Picturing the Test System Test Environment DesignsAcquiresConfiguresUtilizesSupport Provides a Platform for the operation of Determine the usage of TestTeam DesignsAcquiresConfiguresUtilizesSupport CreateArticulatesTrainsAppliesInternalize TestProcesses Testware

More Related