Published on

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Testing
  2. 2. Outline <ul><li>Terminology </li></ul><ul><li>Types of errors </li></ul><ul><li>Dealing with errors </li></ul><ul><li>Quality assurance vs Testing </li></ul><ul><li>Component Testing </li></ul><ul><ul><li>Unit testing </li></ul></ul><ul><ul><li>Integration testing </li></ul></ul><ul><li>Testing Strategy </li></ul><ul><li>Design Patterns & Testing </li></ul><ul><li>System testing </li></ul><ul><ul><li>Function testing </li></ul></ul><ul><ul><li>Structure Testing </li></ul></ul><ul><ul><li>Performance testing </li></ul></ul><ul><ul><li>Acceptance testing </li></ul></ul><ul><ul><li>Installation testing </li></ul></ul>
  3. 3. Quality of today’s software…. <ul><li>The average software product released on the market is not error free. </li></ul>
  4. 4. What is this? A failure? An error? A fault? Need to specify the desired behavior first!
  5. 5. Erroneous State (“Error”)
  6. 6. Algorithmic Fault
  7. 7. Mechanical Fault
  8. 8. Terminology <ul><li>Reliability: The measure of success with which the observed behavior of a system confirms to some specification of its behavior. </li></ul><ul><li>Failure: Any deviation of the observed behavior from the specified behavior. </li></ul><ul><li>Error: The system is in a state such that further processing by the system will lead to a failure. </li></ul><ul><li>Fault (Bug): The mechanical or algorithmic cause of an error. </li></ul><ul><li>There are many different types of errors and different ways how we can deal with them. </li></ul>
  9. 9. Errors, Faults, Bugs <ul><li>Defects are not free, somebody gets paid for making them, Deming </li></ul><ul><li>Failure : Incorrect behavior of a component – A symptom </li></ul><ul><li>Fault ( Bug, Defect ): Incorrect program or data object – Result of error </li></ul><ul><li>Error : Mistake made by human – omission or commission </li></ul>
  10. 10. Error Fault Failure Debug New Error Life Cycle of Problems
  11. 11. How do we deal with Errors and Faults?
  12. 12. Verification?
  13. 13. Modular Redundancy?
  14. 14. Declaring the Bug as a Feature?
  15. 15. Patching?
  16. 16. Testing?
  17. 17. Where does testing fit in? PHASE O: Testing == Debugging PHASE 1: Testing shows the software works PHASE 2: Testing shows the software doesn’t work PHASE 3: Testing doesn’t prove anything, it reduces risk of unacceptable software delivery. PHASE 4: Testing is not an act, a mental discipline of quality. Boris Biezer
  18. 18. “ The ” Testing Quote Testing cannot show the absence of defects, it can only show that software defects are present. We cannot test quality into a product, we have to design it in.
  19. 19. Test Objectives <ul><li>Tests intended to find errors </li></ul><ul><li>Good test cases have high p for finding a yet undiscovered error </li></ul><ul><li>Successful tests cause program failure, i.e. find an undiscovered error. </li></ul><ul><li>Minimal set of test cases needs to be developed because exhaustive testing not possible </li></ul>
  20. 20. What we have here… <ul><li>Developers do everything they can to make the software work. </li></ul><ul><li>Testers do everything they can to make the software fail. </li></ul>
  21. 21. Testing Paradox Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffective. Time Defects Found Cost
  22. 22. Testing Phases <ul><li>Programmer </li></ul><ul><li>Unit </li></ul><ul><li>Integration </li></ul><ul><li>Component </li></ul><ul><li>System </li></ul><ul><li>Usability </li></ul><ul><li>Regression </li></ul><ul><li>Validation (Acceptance) </li></ul><ul><li>Alpha/Beta (FUT/OT) </li></ul>
  23. 23. Vocabulary <ul><li>Test Case : a set of data/events provided for a specific test. </li></ul><ul><li>Test Suite: a set of test cases. </li></ul><ul><li>Test Driver: a program written to test a unit module </li></ul><ul><li>Test Stub: a module written to test a higher level component </li></ul><ul><li>Test Harness: a test environment to run the stubs and drivers and check the results. </li></ul>
  24. 24. Examples of Faults and Errors <ul><li>Faults in the Interface specification </li></ul><ul><ul><li>Mismatch between what the client needs and what the server offers </li></ul></ul><ul><ul><li>Mismatch between requirements and implementation </li></ul></ul><ul><li>Algorithmic Faults </li></ul><ul><ul><li>Missing initialization </li></ul></ul><ul><ul><li>Branching errors (too soon, too late) </li></ul></ul><ul><ul><li>Missing test for nil </li></ul></ul><ul><li>Mechanical Faults (very hard to find) </li></ul><ul><ul><li>Documentation does not match actual conditions or operating procedures </li></ul></ul><ul><li>Errors </li></ul><ul><ul><li>Stress or overload errors </li></ul></ul><ul><ul><li>Capacity or boundary errors </li></ul></ul><ul><ul><li>Timing errors </li></ul></ul><ul><ul><li>Throughput or performance errors </li></ul></ul>
  25. 25. Dealing with Errors <ul><li>Verification: </li></ul><ul><ul><li>Assumes hypothetical environment that does not match real environment </li></ul></ul><ul><ul><li>Proof might be buggy (omits important constraints; simply wrong) </li></ul></ul><ul><li>Modular redundancy: </li></ul><ul><ul><li>Expensive </li></ul></ul><ul><li>Declaring a bug to be a “feature” </li></ul><ul><ul><li>Bad practice </li></ul></ul><ul><li>Patching </li></ul><ul><ul><li>Slows down performance </li></ul></ul><ul><li>Testing (this lecture) </li></ul><ul><ul><li>Testing is never good enough </li></ul></ul>
  26. 26. Another View on How to Deal with Errors <ul><li>Error prevention (before the system is released): </li></ul><ul><ul><li>Use good programming methodology to reduce complexity </li></ul></ul><ul><ul><li>Use version control to prevent inconsistent system </li></ul></ul><ul><ul><li>Apply verification to prevent algorithmic bugs </li></ul></ul><ul><li>Error detection (while system is running): </li></ul><ul><ul><li>Testing: Create failures in a planned way </li></ul></ul><ul><ul><li>Debugging: Start with an unplanned failures </li></ul></ul><ul><ul><li>Monitoring: Deliver information about state. Find performance bugs </li></ul></ul><ul><li>Error recovery (recover from failure once the system is released): </li></ul><ul><ul><li>Data base systems (atomic transactions) </li></ul></ul><ul><ul><li>Modular redundancy </li></ul></ul><ul><ul><li>Recovery blocks </li></ul></ul>
  27. 27. Some Observations <ul><li>It is impossible to completely test any nontrivial module or any system </li></ul><ul><ul><li>Theoretical limitations: Halting problem </li></ul></ul><ul><ul><li>Practial limitations: Prohibitive in time and cost </li></ul></ul><ul><li>Testing can only show the presence of bugs, not their absence (Dijkstra) </li></ul>
  28. 28. Testing takes creativity <ul><li>Testing often viewed as dirty work. </li></ul><ul><li>To develop an effective test, one must have: </li></ul><ul><ul><ul><li>Detailed understanding of the system </li></ul></ul></ul><ul><ul><ul><li>Knowledge of the testing techniques </li></ul></ul></ul><ul><ul><ul><li>Skill to apply these techniques in an effective and efficient manner </li></ul></ul></ul><ul><li>Testing is done best by independent testers </li></ul><ul><ul><li>We often develop a certain mental attitude that the program should in a certain way when in fact it does not. </li></ul></ul><ul><li>Programmer often stick to the data set that makes the program work </li></ul><ul><ul><li>&quot;Don’t mess up my code!&quot; </li></ul></ul><ul><li>A program often does not work when tried by somebody else. </li></ul><ul><ul><li>Don't let this be the end-user. </li></ul></ul>
  29. 29. Testing Activities Tested Subsystem Subsystem Code Functional Integration Unit Tested Subsystem Requirements Analysis Document System Design Document Tested Subsystem Test Test T est Unit T est Unit T est User Manual Requirements Analysis Document Subsystem Code Subsystem Code All tests by developer Functioning System Integrated Subsystems
  30. 30. Testing Activities continued Global Requirements User’s understanding Tests by developer Performance Acceptance Client’s Understanding of Requirements Test Functioning System Test Installation User Environment Test System in Use Usable System Validated System Accepted System Tests (?) by user Tests by client
  31. 31. Fault Handling Techniques Testing Fault Handling Fault Avoidance Fault Tolerance Fault Detection Debugging Unit Testing Integration Testing System Testing Verification Configuration Management Atomic Transactions Modular Redundancy Correctness Debugging Performance Debugging Reviews Design Methodology
  32. 32. Quality Assurance encompasses Testing Usability Testing Quality Assurance Testing Prototype Testing Scenario Testing Product Testing Fault Avoidance Fault Tolerance Fault Detection Debugging Unit Testing Integration Testing System Testing Verification Configuration Management Atomic Transactions Modular Redundancy Correctness Debugging Performance Debugging Reviews Walkthrough Inspection
  33. 33. Types of Unit Testing <ul><li>Structural (Whitebox) </li></ul><ul><li>Functional (Blackbox) </li></ul><ul><li>Statistical (Random) </li></ul><ul><li>Mutation </li></ul><ul><li>Object Oriented (State-based) </li></ul><ul><li>Insert latest PhD thesis topic here </li></ul>
  34. 34. Return of the Vocabulary <ul><li>Coverage: a measure of the amount of testing to be achieved. Normally spoken of in standard criteria based upon test technique for a subset of test cases. </li></ul><ul><li>Adequacy: a measure of the overall efficiency and effectiveness of the test suite. </li></ul>
  35. 35. Writing a test plan (Simple Version) <ul><li>Introduction: </li></ul><ul><ul><li>Purpose </li></ul></ul><ul><ul><li>Program Description </li></ul></ul><ul><li>Test Environment </li></ul><ul><li>Test Case Descriptions: </li></ul><ul><ul><li>Coverage Criteria </li></ul></ul><ul><ul><li>Details </li></ul></ul>4. Summary Test # Test Purpose/Setup Test Case Expected Result Actual Result Priority 1 Check Square 4 16 8 Critical
  36. 36. Sample Test Plan <ul><li>Introduction </li></ul><ul><li>a. Purpose: This test plan describes procedures for testing the Zap-O-Matic 3000 version 1.0. It specifies </li></ul><ul><li>unit, component and system-level testing requirements. </li></ul><ul><li>b. Program Description: The Zap-O-Matic 3000 is a program that wipes a hard drive clean of all information. It meets NSA requirements for B1 security. </li></ul>
  37. 37. Test Plan cont’d <ul><li>Test Environment: The tests in this plan were carried </li></ul><ul><li>out on the following configurations: </li></ul><ul><li>a. Pentium 4 PC with 512MB RAM and 10 GB free disk </li></ul><ul><li>space, Windows XP with SP2, Java JRE 1.4.2_05. </li></ul><ul><li>b. Pentium 4 PC with 1GB RAM and 3 GB free disk </li></ul><ul><li>space, LINUX Fedora Core 3 all patches applied, </li></ul><ul><li>JAVA JRE 1.3.1_09. </li></ul>
  38. 38. Test Plan cont’d <ul><li>Test Case Descriptions: </li></ul><ul><li>a. Coverage Criteria: For unit level tests, we attempted to achieve branch coverage for all whitebox tests, and all boundary conditions for blackbox tests. For system-level testing, we covered all input equivalence partitions. </li></ul>
  39. 39. Test Plan cont’d b. Details: Frodo Baggins (Developer 1), Method getData(int, int, string) Test #1 Purpose: check that when HDD signal is true, the GUI displays a RED light in main monitor panel. Test Case: 5,4,”HIGH” Expected: RED light in main monitor panel Actual: YELLOW light in main monitor panel Priority: HIGH, must be fixed before release, assigned to Frodo for action.
  40. 40. Test Plan (cont’d) Arnold Ziffel (Developer 2), System test, Paragraph 15a, Test server login Test #23 Purpose: Check that server rejects invalid login. Test Case: a. “Bobbo” (valid user), “grtda1” (invalid password). b. “Freda” (invalid user), “grtda1” (valid password). Expected: a,b both rejected Actual: a accepted, b rejected Priority: Critical, unsecure operation allowed
  41. 41. Test Plan cont’d <ul><li>Summary: </li></ul><ul><li>Unit Level: 100 tests executed, 95 passed </li></ul><ul><li>Failures: 3 critical, 2 urgent </li></ul><ul><li>System Level: 250 tests executed, 150 passed </li></ul><ul><li>Failures: 10 critical, 35 urgent, 50 routine, </li></ul><ul><li>5 minor </li></ul><ul><li>All critical and urgent failures are assigned for action. </li></ul>
  42. 42. Stubbing Functions int main (int argc, char **argv) { if (argc<4) usage(); double x = f(argv[1],argv[2]); … } void usage() { return; } double f(char *arg1, char *arg2) { return 3.0 }
  43. 43. Writing Drivers int main( int argc, char **argv) { int i; for (i=0; i<10;i++) { printf(“SQR of %i is %i”, i, square(i)); } }
  44. 44. Why does testing go bad? <ul><li>Schedule compression/ Waterfall </li></ul><ul><li>Writing harnesses, suites,stubs and drivers doesn’t relate directly to LOC. </li></ul><ul><li>Different philosophy’s </li></ul><ul><li>Overconfidence in “silver bullets” </li></ul>
  45. 45. Types of Testing <ul><li>Unit Testing: </li></ul><ul><ul><li>Individual subsystem </li></ul></ul><ul><ul><li>Carried out by developers </li></ul></ul><ul><ul><li>Goal: Confirm that subsystems is correctly coded and carries out the intended functionality </li></ul></ul><ul><li>Integration Testing: </li></ul><ul><ul><li>Groups of subsystems (collection of classes) and eventually the entire system </li></ul></ul><ul><ul><li>Carried out by developers </li></ul></ul><ul><ul><li>Goal: Test the interface among the subsystem </li></ul></ul>
  46. 46. System Testing <ul><li>System Testing: </li></ul><ul><ul><li>The entire system </li></ul></ul><ul><ul><li>Carried out by developers </li></ul></ul><ul><ul><li>Goal: Determine if the system meets the requirements (functional and global) </li></ul></ul><ul><li>Acceptance Testing: </li></ul><ul><ul><li>Evaluates the system delivered by developers </li></ul></ul><ul><ul><li>Carried out by the client. May involve executing typical transactions on site on a trial basis </li></ul></ul><ul><ul><li>Goal: Demonstrate that the system meets customer requirements and is ready to use </li></ul></ul><ul><li>Implementation (Coding) and testing go hand in hand </li></ul>
  47. 47. Unit Testing <ul><li>Informal: </li></ul><ul><ul><li>Incremental coding </li></ul></ul><ul><li>Static Analysis: </li></ul><ul><ul><li>Hand execution: Reading the source code </li></ul></ul><ul><ul><li>Walk-Through (informal presentation to others) </li></ul></ul><ul><ul><li>Code Inspection (formal presentation to others) </li></ul></ul><ul><ul><li>Automated Tools checking for </li></ul></ul><ul><ul><ul><li>syntactic and semantic errors </li></ul></ul></ul><ul><ul><ul><li>departure from coding standards </li></ul></ul></ul><ul><li>Dynamic Analysis: </li></ul><ul><ul><li>Black-box testing (Test the input/output behavior) </li></ul></ul><ul><ul><li>White-box testing (Test the internal logic of the subsystem or object) </li></ul></ul><ul><ul><li>Data-structure based testing (Data types determine test cases) </li></ul></ul>
  48. 48. Black-box Testing <ul><li>Focus: I/O behavior. If for any given input, we can predict the output, then the module passes the test. </li></ul><ul><ul><li>Almost always impossible to generate all possible inputs (&quot;test cases&quot;) </li></ul></ul><ul><li>Goal: Reduce number of test cases by equivalence partitioning: </li></ul><ul><ul><li>Divide input conditions into equivalence classes </li></ul></ul><ul><ul><li>Choose test cases for each equivalence class. (Example: If an object is supposed to accept a negative number, testing one negative number is enough) </li></ul></ul>
  49. 49. Black-box Testing (Continued) <ul><li>Selection of equivalence classes (No rules, only guidelines): </li></ul><ul><ul><li>Input is valid across range of values. Select test cases from 3 equivalence classes: </li></ul></ul><ul><ul><ul><li>Below the range </li></ul></ul></ul><ul><ul><ul><li>Within the range </li></ul></ul></ul><ul><ul><ul><li>Above the range </li></ul></ul></ul><ul><ul><li>Input is valid if it is from a discrete set. Select test cases from 2 equivalence classes: </li></ul></ul><ul><ul><ul><li>Valid discrete value </li></ul></ul></ul><ul><ul><ul><li>Invalid discrete value </li></ul></ul></ul><ul><li>Another solution to select only a limited amount of test cases: </li></ul><ul><ul><li>Get knowledge about the inner workings of the unit being tested => white-box testing </li></ul></ul>
  50. 50. White-box Testing <ul><li>Focus: Thoroughness (Coverage). Every statement in the component is executed at least once. </li></ul><ul><li>Four types of white-box testing </li></ul><ul><ul><li>Statement Testing </li></ul></ul><ul><ul><li>Loop Testing </li></ul></ul><ul><ul><li>Path Testing </li></ul></ul><ul><ul><li>Branch Testing </li></ul></ul>
  51. 51. White-box Testing (Continued) <ul><li>Statement Testing (Algebraic Testing): Test single statements (Choice of operators in polynomials, etc) </li></ul><ul><li>Loop Testing: </li></ul><ul><ul><li>Cause execution of the loop to be skipped completely. (Exception: Repeat loops) </li></ul></ul><ul><ul><li>Loop to be executed exactly once </li></ul></ul><ul><ul><li>Loop to be executed more than once </li></ul></ul><ul><li>Path testing: </li></ul><ul><ul><li>Make sure all paths in the program are executed </li></ul></ul><ul><li>Branch Testing (Conditional Testing): Make sure that each possible outcome from a condition is tested at least once </li></ul>if ( i = TRUE) printf(&quot;YES &quot;); else printf(&quot;NO &quot;); Test cases: 1) i = TRUE; 2) i = FALSE
  52. 52. White-box Testing Example /*Read in and sum the scores*/ FindMean(float Mean, FILE ScoreFile) { SumOfScores = 0.0; NumberOfScores = 0; Mean = 0; Read(Scor eFile, Score); while (! EOF(ScoreFile) { if ( Score > 0.0 ) { SumOfScores = SumOfScores + Score; NumberOfScores++; } Read(ScoreFile, Score); } /* Compute the mean and print the result */ if (NumberOfScores > 0 ) { Mean = SumOfScores/NumberOfScores; printf(&quot;The mean score is %f &quot;, Mean); } else printf(&quot;No scores found in file &quot;); }
  53. 53. White-box Testing Example: Determining the Paths <ul><li>FindMean (FILE ScoreFile) </li></ul><ul><li>{ float SumOfScores = 0.0; </li></ul><ul><ul><li>int NumberOfScores = 0; </li></ul></ul><ul><ul><li>float Mean=0.0; float Score; </li></ul></ul><ul><ul><li>Read(ScoreFile, Score); </li></ul></ul><ul><ul><li>while (! EOF(ScoreFile) { </li></ul></ul><ul><ul><ul><li>if (Score > 0.0 ) { </li></ul></ul></ul><ul><ul><ul><ul><ul><li>SumOfScores = SumOfScores + Score; </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>NumberOfScores++; </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>} </li></ul></ul></ul></ul></ul><ul><ul><ul><li>Read(ScoreFile, Score); </li></ul></ul></ul><ul><ul><li>} </li></ul></ul><ul><ul><li>/* Compute the mean and print the result */ </li></ul></ul><ul><ul><li>if (NumberOfScores > 0) { </li></ul></ul><ul><ul><ul><ul><li>Mean = SumOfScores / NumberOfScores; </li></ul></ul></ul></ul><ul><ul><ul><ul><li>printf(“ The mean score is %f ”, Mean); </li></ul></ul></ul></ul><ul><ul><li>} else </li></ul></ul><ul><ul><ul><ul><li>printf (“No scores found in file ”); </li></ul></ul></ul></ul><ul><li>} </li></ul>1 2 3 4 5 7 6 8 9
  54. 54. Constructing the Logic Flow Diagram
  55. 55. Finding the Test Cases Start 2 3 4 5 6 7 8 9 Exit 1 b d e g f i j h c k l a (Covered by any data) (Data set must (Data set must contain at least one value) be empty) (Total score > 0.0) (Total score < 0.0) (Positive score) (Negative score) (Reached if either f or e is reached)
  56. 56. Test Cases <ul><li>Test case 1 : ? (To execute loop exactly once) </li></ul><ul><li>Test case 2 : ? (To skip loop body) </li></ul><ul><li>Test case 3: ?,? (to execute loop more than once) </li></ul><ul><li>These 3 test cases cover all control flow paths </li></ul>
  57. 57. Comparison of White & Black-box Testing 25.1.2002 <ul><li>White-box Testing: </li></ul><ul><ul><li>Potentially infinite number of paths have to be tested </li></ul></ul><ul><ul><li>White-box testing often tests what is done, instead of what should be done </li></ul></ul><ul><ul><li>Cannot detect missing use cases </li></ul></ul><ul><li>Black-box Testing: </li></ul><ul><ul><li>Potential combinatorical explosion of test cases (valid & invalid data) </li></ul></ul><ul><ul><li>Often not clear whether the selected test cases uncover a particular error </li></ul></ul><ul><ul><li>Does not discover extraneous use cases (&quot;features&quot;) </li></ul></ul><ul><li>Both types of testing are needed </li></ul><ul><li>White-box testing and black box testing are the extreme ends of a testing continuum. </li></ul><ul><li>Any choice of test case lies in between and depends on the following: </li></ul><ul><ul><li>Number of possible logical paths </li></ul></ul><ul><ul><li>Nature of input data </li></ul></ul><ul><ul><li>Amount of computation </li></ul></ul><ul><ul><li>Complexity of algorithms and data structures </li></ul></ul>
  58. 58. The 4 Testing Steps <ul><li>1. Select what has to be measured </li></ul><ul><ul><li>Analysis: Completeness of requirements </li></ul></ul><ul><ul><li>Design: tested for cohesion </li></ul></ul><ul><ul><li>Implementation: Code tests </li></ul></ul><ul><li>2. Decide how the testing is done </li></ul><ul><ul><li>Code inspection </li></ul></ul><ul><ul><li>Proofs (Design by Contract) </li></ul></ul><ul><ul><li>Black-box, white box, </li></ul></ul><ul><ul><li>Select integration testing strategy (big bang, bottom up, top down, sandwich) </li></ul></ul><ul><li>3. Develop test cases </li></ul><ul><ul><li>A test case is a set of test data or situations that will be used to exercise the unit (code, module, system) being tested or about the attribute being measured </li></ul></ul><ul><li>4. Create the test oracle </li></ul><ul><ul><li>An oracle contains of the predicted results for a set of test cases </li></ul></ul><ul><ul><li>The test oracle has to be written down before the actual testing takes place </li></ul></ul>
  59. 59. Guidance for Test Case Selection <ul><li>Use analysis knowledge about functional requirements (black-box testing): </li></ul><ul><ul><li>Use cases </li></ul></ul><ul><ul><li>Expected input data </li></ul></ul><ul><ul><li>Invalid input data </li></ul></ul><ul><li>Use design knowledge about system structure, algorithms, data structures (white-box testing): </li></ul><ul><ul><li>Control structures </li></ul></ul><ul><ul><ul><li>Test branches, loops, ... </li></ul></ul></ul><ul><ul><li>Data structures </li></ul></ul><ul><ul><ul><li>Test records fields, arrays, ... </li></ul></ul></ul><ul><li>Use implementation knowledge about algorithms: </li></ul><ul><ul><li>Examples: </li></ul></ul><ul><ul><li>Force division by zero </li></ul></ul><ul><ul><li>Use sequence of test cases for interrupt handler </li></ul></ul>
  60. 60. Unit-testing Heuristics <ul><li>1. Create unit tests as soon as object design is completed: </li></ul><ul><ul><li>Black-box test: Test the use cases & functional model </li></ul></ul><ul><ul><li>White-box test: Test the dynamic model </li></ul></ul><ul><ul><li>Data-structure test: Test the object model </li></ul></ul><ul><li>2. Develop the test cases </li></ul><ul><ul><li>Goal: Find the minimal number of test cases to cover as many paths as possible </li></ul></ul><ul><li>3. Cross-check the test cases to eliminate duplicates </li></ul><ul><ul><li>Don't waste your time! </li></ul></ul><ul><li>4. Desk check your source code </li></ul><ul><ul><li>Reduces testing time </li></ul></ul><ul><li>5. Create a test harness </li></ul><ul><ul><li>Test drivers and test stubs are needed for integration testing </li></ul></ul><ul><li>6. Describe the test oracle </li></ul><ul><ul><li>Often the result of the first successfully executed test </li></ul></ul><ul><li>7. Execute the test cases </li></ul><ul><ul><li>Don’t forget regression testing </li></ul></ul><ul><ul><li>Re-execute test cases every time a change is made. </li></ul></ul><ul><li>8. Compare the results of the test with the test oracle </li></ul><ul><ul><li>Automate as much as possible </li></ul></ul>
  61. 61. Integration Testing <ul><li>Big Bang </li></ul><ul><li>Top-Down </li></ul><ul><li>Bottom-Up </li></ul><ul><li>Sandwich </li></ul><ul><li>Feature Set </li></ul><ul><li>Call Graph/Sequence Diagram </li></ul><ul><li>Continuous </li></ul>
  62. 62. Top-Down Strategy Breadth-First Depth-First Start with Main and Stubs Replace stubs incrementally Test at each step Regression Test Suite DISADVANTAGE: A lot of stub writing M1 M4 M3 M2 M5
  63. 63. Bottom-Up Strategy M1 M3 M2 M4 M5 Start with driver and atomic module Replace upper drivers with modules Test each integration Build-up clusters DISADVANTAGE: No program till integration complete
  64. 64. Feature-Set M1 M3 M2 Load/Save Game M5 M4 Board Display Select Key Features Organize into clusters Integrate/Test Feature DISADVANTAGE: May be hard to isolate features/ Feature Interaction Problem
  65. 65. Call Graph / Sequence Diagram <ul><li>Pick neighbors, strongly connected classes and integrate by pairs. </li></ul><ul><li>Reduces the stub/driver effort </li></ul>main scanner getnoblank usage parser insertsymbol getsymbol Student aClass: Class Register :Scheduler adjustRoom checkRooms
  66. 66. Pulling Testing Together (V&V) <ul><li>Validation: </li></ul><ul><ul><li>Customer review of use cases (Requirements validation) </li></ul></ul><ul><ul><li>Traceability (match phases to requirements) </li></ul></ul><ul><ul><li>Validation test suite </li></ul></ul><ul><ul><li>Prototypes </li></ul></ul><ul><ul><li>Alpha/Beta Tests </li></ul></ul>
  67. 67. V&V Continued <ul><li>Verification: </li></ul><ul><ul><li>Reviews/Inspections </li></ul></ul><ul><ul><li>Process Monitoring </li></ul></ul><ul><ul><li>Unit Test Standards </li></ul></ul><ul><ul><li>Integration Test Strategy </li></ul></ul><ul><ul><li>Regression Testing </li></ul></ul><ul><ul><li>System Testing </li></ul></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.