Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
C L I C K<br />
E<br />T<br />W<br />A<br />T<br />R<br />E<br />S<br />I<br />N<br />G<br />T<br />O<br />F<br />S<br />3<br />2<br />1<b...
Testing Policy<br />Only exhaustive testing can show a program is free from defects. However, exhaustive testing is imposs...
Software Testing & Development Life Cycle<br />
Unit Testing<br />module<br />to be<br />tested<br />Result<br />Software Engineer<br />Test Cases<br />
Unit Testing<br />module<br />to be<br />tested<br />Interface<br />Local Data Structures<br />Boundary Conditions<br />In...
Interface<br />Module<br />Local Data Structures<br />Boundary Conditions<br />Driver<br />Independent paths<br />Error Ha...
Integration Testing<br /> Involves building a system from its components and      testing it for problems that arise from ...
Integration Testing<br /><ul><li>The Big-bang Approach.
Incremental Approach.</li></li></ul><li>What is mean by stub <br />A Stub is a special code arrangement when called by any...
Top-Down Integration<br />A<br />Top module is tested with Stub<br />B<br />F<br />G<br />Stubs are all Replaced one at a ...
Bottom-Up Integration<br />A<br />B<br />F<br />G<br />Drivers are replaced one at a time, Depth First.<br />C<br />Worker...
Thread-Based Integration<br />A<br />Top Modules are tested with stubs<br />B<br />F<br />G<br />C<br />Worker modules are...
Systems testing<br />
Trivial example<br />Scenario-based Testing<br />
Trivial Example-System Testing<br />
Regression Testing<br /><ul><li>Change do not always effect the entire program.
After each change
Entire test suite of a system must be run again.</li></ul>Need for an automatic test suite execution.<br />
Test activities<br />Expected results when the inputs are executed; and <br />Execution conditions or execution environmen...
Test  Case selection<br />
Test Oracles<br /><ul><li>A test oracle is
    A program
    A process
    A body of data
Upcoming SlideShare
Loading in …5
×

Software testing and_quality_assurance_powerpoint_presentation

932 views

Published on

Published in: Education, Technology, Business
  • Login to see the comments

Software testing and_quality_assurance_powerpoint_presentation

  1. 1. C L I C K<br />
  2. 2. E<br />T<br />W<br />A<br />T<br />R<br />E<br />S<br />I<br />N<br />G<br />T<br />O<br />F<br />S<br />3<br />2<br />1<br /> E<br />D<br />N<br />A<br />M<br />V<br />A<br />R<br />I<br />C<br />C<br />N<br />E<br />A<br />R<br />U<br />A<br />S<br />Y<br />T<br />I<br />S<br />Q<br />A<br />U<br />L<br />
  3. 3. Testing Policy<br />Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible;<br />Testing policies define the approach to be used in selecting system tests; For example,<br />All functions accessed through menus should be tested;<br />Combinations of functions accessed through the same menu should be tested;<br />Where user input is required, all functions must be tested with correct and incorrect input.<br />3<br />
  4. 4. Software Testing & Development Life Cycle<br />
  5. 5. Unit Testing<br />module<br />to be<br />tested<br />Result<br />Software Engineer<br />Test Cases<br />
  6. 6. Unit Testing<br />module<br />to be<br />tested<br />Interface<br />Local Data Structures<br />Boundary Conditions<br />Independent paths<br />Error Handling Paths<br />Test <br />Cases<br />
  7. 7. Interface<br />Module<br />Local Data Structures<br />Boundary Conditions<br />Driver<br />Independent paths<br />Error Handling Paths<br />stub<br />stub<br />Test <br />Cases<br />Result<br />
  8. 8. Integration Testing<br /> Involves building a system from its components and testing it for problems that arise from component interactions.<br />Top-down integration<br /> Develop the skeleton of the system and populate it with components.<br />Bottom-up integration<br />Integrate infrastructure components then add functional components.<br />To simplify error localisation, systems <br />should be incrementally integrated.<br />
  9. 9. Integration Testing<br /><ul><li>The Big-bang Approach.
  10. 10. Incremental Approach.</li></li></ul><li>What is mean by stub <br />A Stub is a special code arrangement when called by any other module, stimulates the behaviour of an well designed and existing module which is not yet constructed or developed.<br />
  11. 11. Top-Down Integration<br />A<br />Top module is tested with Stub<br />B<br />F<br />G<br />Stubs are all Replaced one at a time, Depth first<br />C<br />As new modules are integrated, <br />some subset of tests is re-run<br />D<br />E<br />
  12. 12. Bottom-Up Integration<br />A<br />B<br />F<br />G<br />Drivers are replaced one at a time, Depth First.<br />C<br />Worker modules are grouped into builds <br />and Integrated<br />D<br />E<br />Cluster<br />
  13. 13. Thread-Based Integration<br />A<br />Top Modules are tested with stubs<br />B<br />F<br />G<br />C<br />Worker modules are grouped into builds <br />and Integrated<br />D<br />E<br />Cluster<br />
  14. 14. Systems testing<br />
  15. 15. Trivial example<br />Scenario-based Testing<br />
  16. 16. Trivial Example-System Testing<br />
  17. 17. Regression Testing<br /><ul><li>Change do not always effect the entire program.
  18. 18. After each change
  19. 19. Entire test suite of a system must be run again.</li></ul>Need for an automatic test suite execution.<br />
  20. 20. Test activities<br />Expected results when the inputs are executed; and <br />Execution conditions or execution environment in which the inputs are to be executed. <br />Boils down to selecting and executing test cases. Test case consists of……<br />Set of test inputs, of if the program is non-terminating, a sequence of test inputs.<br />These steps generally remain same from <br />unit testing to system testing.<br />
  21. 21. Test Case selection<br />
  22. 22. Test Oracles<br /><ul><li>A test oracle is
  23. 23. A program
  24. 24. A process
  25. 25. A body of data
  26. 26. In many cases - directly form the requirements.
  27. 27. For example, a test case assessing performance - performance threshold.
  28. 28. Determines whether or not the program has passed or failed the test case.</li></li></ul><li>Text Execution<br /><ul><li>Test inputs on the </li></ul> ‘program-under-test’<br /><ul><li> Record the actual</li></ul> behavior.<br />Generally can be automated to an extend !!!!<br />
  29. 29. Test Evaluation<br />Compare the actual behavior with the expected behavior. <br />Generally can be automated to an extend !!!!<br />
  30. 30. Test Reporting<br /><ul><li> Report the outcome of the testing.
  31. 31. Developers
  32. 32. Project Mangers etc. </li></ul>Generally can be automated to an extend !!!!<br />
  33. 33. Key points<br />A system typically undergoes a range of testing types.<br />Each type of testing is aimed at detecting different kinds of failures<br />Testing boils down to the selection and execution of test cases. <br />
  34. 34. The ability to convert ideas to things is the secret of outward success.<br />Created By<br />Srivignesh<br />

×