Testing- Fundamentals of Testing-Mazenet solution
Download as PPT, PDF1 like194 views
The document outlines the principles and processes of software testing, highlighting the necessity of testing due to human errors, the different types of testing, and the importance of prioritizing tests based on risk. It emphasizes understanding failures, managing testing efforts efficiently, and executing detailed test planning and specification. Key aspects include distinguishing between errors, faults, and failures, along with the roles of testers and the significance of maintaining independence in testing processes.
Testing- Fundamentals of Testing-Mazenet solution
- 1. Software Testing Presented by Baskaran E (Testing trainer)
- 2. Principles of Testing 1 Principles 2 Lifecycle 4 Dynamic test techniques 3 Static testing 5 Management 6 Tools Software Testing Chapter 1
- 3. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6
- 4. Testing terminology • No generally accepted set of testing definitions used world wide • New standard BS 7925-1 • Glossary of testing terms (emphasis on component testing) • most recent • developed by a working party of the BCS SIGIST • adopted by the ISEB / ISTQB
- 5. What is a “bug”? • Error: a human action that produces an incorrect result • Fault: a manifestation of an error in software • also known as a defect or bug • if executed, a fault may cause a failure • Failure: deviation of the software from its expected delivery or service • (found defect) Failure is an event; fault is a state of the software, caused by an error Failure is an event; fault is a state of the software, caused by an error
- 6. Error - Fault - Failure A person makes an error ... … that creates a fault in the software ... … that can cause a failure in operation
- 7. Reliability versus faults • Reliability: the probability that software will not cause the failure of the system for a specified time under specified conditions • Can a system be fault-free? (zero faults, right first time) • Can a software system be reliable but still have faults? • Is a “fault-free” software application always reliable?
- 8. Why do faults occur in software? • software is written by human beings • who know something, but not everything • who have skills, but aren’t perfect • who do make mistakes (errors) • under increasing pressure to deliver to strict deadlines • no time to check but assumptions may be wrong • systems may be incomplete • if you have ever written software ...
- 9. What do software faults cost? • huge sums • Ariane 5 ($7billion) • Mariner space probe to Venus ($250m) • American Airlines ($50m) • very little or nothing at all • minor inconvenience • no visible or physical detrimental impact • software is not “linear”: • small input may have very large effect
- 10. Safety-critical systems • software faults can cause death or injury • radiation treatment kills patients (Therac-25) • train driver killed • aircraft crashes (Airbus & Korean Airlines) • bank system overdraft letters cause suicide
- 11. So why is testing necessary? • because software is likely to have faults • to learn about the reliability of the software • to fill the time between delivery of the software and the release date • to prove that the software has no faults • because testing is included in the project plan • because failures can be very expensive • to avoid being sued by customers • to stay in business
- 12. Why not just "test everything"? system has 20 screens Average: 10 fields / screen 2 types input / field (date as Jan 3 or 3/1) (number as integer or decimal) Around 100 possible values Total for 'exhaustive' testing: 20 x 4 x 3 x 10 x 2 x 100 =20 x 4 x 3 x 10 x 2 x 100 = 480,000 tests480,000 tests If 1 second per test, 8000 mins, 133 hrs, 17.7 days (not counting finger trouble, faults or retest) Avr. 4 menus 3 options / menu 10 secs = 34 wks, 1 min = 4 yrs, 10 min = 40 yrs
- 13. Exhaustive testing? • What is exhaustive testing? • when all the testers are exhausted • when all the planned tests have been executed • exercising all combinations of inputs and preconditions • How much time will exhaustive testing take? • infinite time • not much time • impractical amount of time
- 14. How much testing is enough? • it’s never enough • when you have done what you planned • when your customer/user is happy • when you have proved that the system works correctly • when you are confident that the system works correctly • it depends on the risks for your system
- 15. How much testing? • It depends on RISKRISK • risk of missing important faults • risk of incurring failure costs • risk of releasing untested or under-tested software • risk of losing credibility and market share • risk of missing a market window • risk of over-testing, ineffective testing
- 16. - what not to test (this time)what not to test (this time) use RISKRISK to - allocate the time available for testing byallocate the time available for testing by prioritising testing ...prioritising testing ... So little time, so much to test .. • test time will always be limited • use RISKRISKto determine: • what to test first • what to test most • how thoroughly to test each item } i.e. where to place emphasis
- 17. Most important principle Prioritise tests so that, whenever you stop testing, you have done the best testing in the time available. Prioritise tests so that, whenever you stop testing, you have done the best testing in the time available.
- 18. Testing and quality • testing measures software quality • testing can find faults; when they are removed, software quality (and possibly reliability) is improved • what does testing test? • system function, correctness of operation • non-functional qualities: reliability, usability, maintainability, reusability, testability, etc.
- 19. Other factors that influence testing • contractual requirements • legal requirements • industry-specific requirements • e.g. pharmaceutical industry (FDA), compiler standard tests, safety-critical or safety-related such as railroad switching, air traffic control It is difficult to determine how much testing is enough but it is not impossible It is difficult to determine how much testing is enough but it is not impossible
- 20. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6
- 21. Test Planning - different levels Test Policy Test Strategy Company level High Level Test Plan High Level Test Plan Project level (IEEE 829) (one for each project) Detailed Test Plan Detailed Test Plan Detailed Test Plan Detailed Test Plan Test stage level (IEEE 829) (one for each stage within a project, e.g. Component, System, etc.)
- 22. The test process specification execution recording check completion Planning (detailed level)
- 23. Test planning • how the test strategy and project test plan apply to the software under test • document any exceptions to the test strategy • e.g. only one test case design technique needed for this functional area because it is less critical • other software needed for the tests, such as stubs and drivers, and environment details • set test completion criteria
- 24. Test specification specification execution recording check completion Identify conditions Design test cases Build tests Planning (detailed level)
- 25. A good test case • effective • exemplary • evolvable • economic Finds faults Represents others Easy to maintain Cheap to use
- 26. Test specification • test specification can be broken down into three distinct tasks: 1. identify: determine ‘what’ is to be tested (identify test conditions) and prioritise 2. design: determine ‘how’ the ‘what’ is to be tested (i.e. design test cases) 3. build: implement the tests (data, scripts, etc.)
- 27. Task 1: identify conditions • list the conditions that we would like to test: • use the test design techniques specified in the test plan • there may be many conditions for each system function or attribute • e.g. • “life assurance for a winter sportsman” • “number items ordered > 99” • “date = 29-Feb-2004” • prioritise the test conditions • must ensure most important conditions are covered (determine ‘what’ is to be tested and prioritise)
- 28. Selecting test conditions Importance Time Best set First set
- 29. Task 2: design test cases • design test input and test data • each test exercises one or more test conditions • determine expected results • predict the outcome of each test case, what is output, what is changed and what is not changed • design sets of tests • different test sets for different objectives such as regression, building confidence, and finding faults (determine ‘how’ the ‘what’ is to be tested)
- 30. Designing test cases Importance Time Most important test conditions Least important test conditions Test cases
- 31. Task 3: build test cases • prepare test scripts • less system knowledge tester has the more detailed the scripts will have to be • scripts for tools have to specify every detail • prepare test data • data that must exist in files and databases at the start of the tests • prepare expected results • should be defined before the test is executed (implement the test cases)
- 32. Test execution specification execution recording check completion Planning (detailed level)
- 33. Execution • Execute prescribed test cases • most important ones first • would not execute all test cases if • testing only fault fixes • too many faults found by early test cases • time pressure • can be performed manually or automated
- 34. Test recording specification execution recording check completion Planning (detailed level)
- 35. Test recording 1 • The test record contains: • identities and versions (unambiguously) of • software under test • test specifications • Follow the plan • mark off progress on test script • document actual outcomes from the test • capture any other ideas you have for new test cases • note that these records are used to establish that all test activities have been carried out as specified
- 36. Test recording 2 • Compare actual outcome with expected outcome. Log discrepancies accordingly: • software fault • test fault (e.g. expected results wrong) • environment or version fault • test run incorrectly • Log coverage levels achieved (for measures specified as test completion criteria) • After the fault has been fixed, repeat the required test activities (execute, design, plan)
- 37. Check test completion specification execution recording check completion Planning (detailed level)
- 38. Check test completion • Test completion criteria were specified in the test plan • If not met, need to repeat test activities, e.g. test specification to design more tests specification execution recording check completion Coverage too low Coverage OK
- 39. Test completion criteria • Completion or exit criteria apply to all levels of testing - to determine when to stop • coverage, using a measurement technique, e.g. • branch coverage for unit testing • user requirements • most frequently used transactions • faults found (e.g. versus expected) • cost or time
- 40. Comparison of tasks Clerical Intellectual one-off activity activity repeated many times Governs the quality of tests Good to automate Execute Recording Planning Specification
- 41. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6
- 42. Why test? • build confidence • prove that the software is correct • demonstrate conformance to requirements • find faults • reduce costs • show system meets user needs • assess the software quality
- 43. Fault foundFaults found Confidence Time Confidence No faults found = confidence?
- 44. Few Faults Many Faults Few Faults Few Faults Few Faults You may be here You think you are here Test Quality Low High Software Quality Low High Assessing software quality
- 45. A traditional testing approach • Show that the system: • does what it should • doesn't do what it shouldn't Fastest achievement: easy test cases Goal: show working Success: system works Goal: show working Success: system works Result: faults left inResult: faults left in
- 46. A better testing approach • Show that the system: • does what it shouldn't • doesn't do what it should Fastest achievement: difficult test cases Goal: find faults Success: system fails Goal: find faults Success: system fails Result: fewer faults left inResult: fewer faults left in
- 47. The testing paradox Purpose of testing: to find faults The best way to build confidence is to try to destroy it The best way to build confidence is to try to destroy it Purpose of testing: build confidence Finding faults destroys confidence Purpose of testing: destroy confidence
- 48. Who wants to be a tester? • A destructive process • Bring bad news (“your baby is ugly”) • Under worst time pressure (at the end) • Need to take a different view, a different mindset (“What if it isn’t?”, “What could go wrong?”) • How should fault information be communicated (to authors and managers?)
- 49. Tester’s have the right to: • accurate information about progress and changes • insight from developers about areas of the software • delivered code tested to an agreed standard • be regarded as a professional (no abuse!) • find faults! • challenge specifications and test plans • have reported faults taken seriously (non-reproducible) • make predictions about future fault levels • improve your own testing process
- 50. Testers have responsibility to: • follow the test plans, scripts etc. as documented • report faults objectively and factually (no abuse!) • check tests are correct before reporting s/w faults • remember it is the software, not the programmer, that you are testing • assess risk objectively • prioritise what you report • communicate the truth
- 51. Independence • Test your own work? • find 30% - 50% of your own faults • same assumptions and thought processes • see what you meant or want to see, not what is there • emotional attachment • don’t want to find faults • actively want NOT to find faults
- 52. Levels of independence • None: tests designed by the person who wrote the software • Tests designed by a different person • Tests designed by someone from a different department or team (e.g. test team) • Tests designed by someone from a different organisation (e.g. agency) • Tests generated by a tool (low quality tests?)
- 53. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6 Mazenet
- 54. Re-testing after faults are fixed • Run a test, it fails, fault reported • New version of software with fault “fixed” • Re-run the same test (i.e. re-test) • must be exactly repeatable • same environment, versions (except for the software which has been intentionally changed!) • same inputs and preconditions • If test now passes, fault has been fixed correctly - or has it?
- 55. Re-testing (re-running failed tests) x x x x New faults introduced by the first fault fix not found during re-testing Re-test to check Fault now fixed
- 56. Regression test • to look for any unexpected side-effects x x x x Can’t guarantee to find them all
- 57. Regression testing 1 • misnomer: "anti-regression" or "progression" • standard set of tests - regression test pack • at any level (unit, integration, system, acceptance) • well worth automating • a developing asset but needs to be maintained
- 58. Regression testing 2 • Regression tests are performed • after software changes, including faults fixed • when the environment changes, even if application functionality stays the same • for emergency fixes (possibly a subset) • Regression test suites • evolve over time • are run often • may become rather large
- 59. Regression testing 3 • Maintenance of the regression test pack • eliminate repetitive tests (tests which test the same test condition) • combine test cases (e.g. if they are always run together) • select a different subset of the full regression suite to run each time a regression test is needed • eliminate tests which have not found a fault for a long time (e.g. old fault fix tests)
- 60. Regression testing and automation • Test execution tools (e.g. capture replay) are regression testing tools - they re-execute tests which have already been executed • Once automated, regression tests can be run as often as desired (e.g. every night) • Automating tests is not trivial (generally takes 2 to 10 times longer to automate a test than to run it manually • Don’t automate everything - plan what to automate first, only automate if worthwhile
- 61. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6
- 62. Expected results • Should be predicted in advance as part of the test design process • ‘Oracle Assumption’ assumes that correct outcome can be predicted. • Why not just look at what the software does and assess it at the time? • subconscious desire for the test to pass - less work to do, no incident report to write up • it looks plausible, so it must be OK - less rigorous than calculating in advance and comparing
- 63. A test A Program: Source: Carsten Jorgensen, Delta, Denmark inputs expected outputs 3 8 6? 10? Read A IF (A = 8) THEN PRINT (“10”) ELSE PRINT (2*A)
- 64. Contents Why testing is necessary Fundamental test process Psychology of testing Re-testing and regression testing Expected results Prioritisation of tests Principles 1 2 3 4 5 6
- 65. Prioritising tests • We can’t test everything • There is never enough time to do all the testing you would like • So what testing should you do?
- 66. Most important principle Prioritise tests so that, whenever you stop testing, you have done the best testing in the time available. Prioritise tests so that, whenever you stop testing, you have done the best testing in the time available.
- 67. How to prioritise? • Possible ranking criteria (all risk based) • test where a failure would be most severe • test where failures would be most visible • test where failures are most likely • ask the customer to prioritise the requirements • what is most critical to the customer’s business • areas changed most often • areas with most problems in the past • most complex areas, or technically critical
- 68. Summary: Key Points Testing is necessary because people make errors The test process: planning, specification, execution, recording, checking completion Independence & relationships are important in testing Re-test fixes; regression test for the unexpected Expected results from a specification in advance Prioritise to do the best testing in the time you have Principles 1 2 3 4 5 6