Download as PPSX, PPTX
Software testing and_quality_assurance_powerpoint_presentation
- 1. C L IC K
- 2. ETWATRESINGTOFS321 EDNAMVARICCNEARUASYTISQAUL
- 3. Testing PolicyOnly exhaustivetesting can show a program is free from defects. However, exhaustive testing is impossible;Testing policies define the approach to be used in selecting system tests; For example,All functions accessed through menus should be tested;Combinations of functions accessed through the same menu should be tested;Where user input is required, all functions must be tested with correct and incorrect input.3
- 4. Software Testing &Development Life Cycle
- 5. Unit Testingmoduleto betestedResultSoftwareEngineerTest Cases
- 6. Unit Testingmoduleto betestedInterfaceLocalData StructuresBoundary ConditionsIndependent pathsError Handling PathsTest Cases
- 7. InterfaceModuleLocal Data StructuresBoundaryConditionsDriverIndependent pathsError Handling PathsstubstubTest CasesResult
- 8. Integration Testing Involvesbuilding a system from its components and testing it for problems that arise from component interactions.Top-down integration Develop the skeleton of the system and populate it with components.Bottom-up integrationIntegrate infrastructure components then add functional components.To simplify error localisation, systems should be incrementally integrated.
- 9. Integration TestingThe Big-bangApproach.
- 10. Incremental Approach.What ismean by stub 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.
- 11. Top-Down IntegrationATop moduleis tested with StubBFGStubs are all Replaced one at a time, Depth firstCAs new modules are integrated, some subset of tests is re-runDE
- 12. Bottom-Up IntegrationABFGDrivers arereplaced one at a time, Depth First.CWorker modules are grouped into builds and IntegratedDECluster
- 13. Thread-Based IntegrationATop Modulesare tested with stubsBFGCWorker modules are grouped into builds and IntegratedDECluster
- 14.
- 15.
- 16.
- 17. Regression TestingChange donot always effect the entire program.
- 18.
- 19. Entire test suiteof a system must be run again.Need for an automatic test suite execution.
- 20. Test activitiesExpected resultswhen the inputs are executed; and Execution conditions or execution environment in which the inputs are to be executed. Boils down to selecting and executing test cases. Test case consists of……Set of test inputs, of if the program is non-terminating, a sequence of test inputs.These steps generally remain same from unit testing to system testing.
- 21. Test Caseselection
- 22. Test OraclesA testoracle is
- 23.
- 24.
- 25.
- 26. In many cases- directly form the requirements.
- 27. For example,a test case assessing performance - performance threshold.
- 28. Determines whether ornot the program has passed or failed the test case.Text ExecutionTest inputs on the ‘program-under-test’ Record the actual behavior.Generally can be automated to an extend !!!!
- 29. Test EvaluationCompare theactual behavior with the expected behavior. Generally can be automated to an extend !!!!
- 30. Test Reporting Report the outcome of the testing.
- 31.
- 32. Project Mangers etc.Generally can be automated to an extend !!!!
- 33. Key pointsA systemtypically undergoes a range of testing types.Each type of testing is aimed at detecting different kinds of failuresTesting boils down to the selection and execution of test cases.
- 34. The ability toconvert ideas to things is the secret of outward success.Created BySrivignesh