1. An Object-Oriented Architecture Supporting Web Application Testing Presented By: Bhavdeep Singh

2. Structure Of The Presentation  Introduction  Constituents of Web Application  Architecture of Web Testing Environment  Application of the Architecture

3. Introduction  Available tools test syntax in HTML docs or the GUI components embedded in the browser.  Lack of tools for the overall web application testing.

4. Constituents of Web Application  Web application model is known as three-tier. The three major tiers are: Web Browser Web Server Database Server

5. Architecture of Web Testing Environment  Total of 6 subsystems Source Document Analysis Subsystem Test Management Subsystem Test Development Subsystem Test Execution Subsystem Test Failure Analysis Subsystem Test Measurement Subsystem

6. Source Document Analysis Subsystem  Source doc may contain HTML, server-side script and client-side script at the same time.  SDAS extracts information such as control flow from the source doc, and sends them to Test Management Subsystem.

7. Test Management Subsystem  Works as a warehouse of all the other subsystems to provide testing artifact management.  It has two repositories Application Information Repository: Contains control flow and data flow information Test Suite/Case Repository: Stores test data, execution path, execution result, test reports, etc.

8. Test Development Subsystem  Contains Five Tools: 1. Test Case Generator: Generates test cases automatically under a given testing criterion. (Has 2 Problems) 2. Test Suite/Case Maintenance Tool: Provides Functions to help tester editing, deleting and reviewing the test suite/case. (Solves 1 st prob.) 3. Test Case Recorder: Creates desired test cases manually. (Solves 2 nd prob.) 4. Test Case Composer: Editing tool to provide test case modification ( Another solution to 2 nd prob.) 5. Test Case Viewer: Provides a view of the test case generated for final review.

9. Problem

10. Test Execution Subsystem  Executes test cases by retrieving information from test suite/case repository.  Test data is filled in by Data Filler and GUI Event Generator.

11. Test Failure Analysis Subsystem  Test oracle analyzes the execution results of test cases and determines which of them are correct.  Generates a Test Failure Report.  Test Suite Summary Generator reads all test cases and results from one test suite and generates a Test Suite Summary.

12. Test Measurement Subsystem  Includes test coverage measurement and analysis  Designed to measure whether and how much of a test criterion is adequately satisfied.

13. Applying the Architecture  Test Case Recorder is used to create the test cases.  Test case Composer refines the existing test cases.  Test Case Executor interprets the designated test scripts.  Results are store in the testing log of Test suite/case repository.  Test Report Composer summarizes the test report.

14. Why is this model Object-Oriented ?  Reuse of Software Components.  Abstraction: Developing web- related domain components which help to describe web related operations.  Integration: Integrating domain components to perform specific tasks in the testing environment.

15. The End