ECE 453 CS 447 SE 465 Software Testing

ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis 1

Overview èFunctional Testing èStructural Testing èIntegration and System Testing èProcess Models and Software Testing èIntegration Testing èSystem Testing 2

Testing in the V-Model te te Wri sts Detailed Design Module implementation Customer Developer System test Integration test Unit tests Architectural Design Acceptance test Run Requirements Functional (BB) Structural (WB) 3

Testing stages • Unit testing – Testing of individual components • Integration testing – Testing to expose problems arising from the combination of components • System testing – Testing the complete system prior to delivery • Acceptance testing – Testing by users to check that the system satisfies requirements. Sometimes called alpha testing 4

Layered Tests http: //www-128. ibm. com/developerworks/java/library/j-aopwork 11 / 5

Integration Testing • Objectives: • To expose problems arising from the combination • To quickly obtain a working solution from components. • Problem areas – Internal: between components • Invocation: call/message passing/… • Parameters: type, number, order, value • Invocation return: identity (who? ), type, sequence – External: • Interrupts (wrong handler? ) • I/O timing – Interaction 6

Integration Testing • Types of integration – Structural • “Big bang” no error localization • Bottom-up: terminal, driver/module, (driver module) • Top-down: top, stubs, (stub module), early demo – Behavioral 7

System Testing • Concerns with the app’s externals • Much more than functional – Load/stress testing – Usability testing – Performance testing – Resource testing 8

Waterfall Model and Integration Testing • • • The Waterfall model is closely associated with top-down development and functional decomposition Top down integration testing will start from the main and use stubs Bottom up integration testing will start from lower level functions and use drivers Big-bang integration testing will test all components at once Traditional integration testing integrates previously tested units with respect to the functional decomposition tree 9

Incremental Models and Integration Testing Each release adds more functionality, i. e. , a new increment Release 1 Requirements Design Coding Test Deployment Release 2 Design Coding Test Deployment Coding Test Release 3 Design Deployment • Incremental Builds: • Regression Testing • Progression Testing 10

Evolutionary Models and Integration Testing New versions implement new and evolving requirements Version 1 Requirements Design Coding Test Deployment Version 1 Requirements Design Version 1 Requirements Coding Design Test Deployment Feedback Coding Test Deployment • Incremental Builds: • Regression Testing • Progression Testing 11

Spiral Model and Integration Testing • Rapid prototyping brings the operational / behavioral profile of the system in the requirements phase 12