1 / 13

Testing Processes of Web Applications

Testing Processes of Web Applications. Susan Cohen. Agenda . Brief introduction Web Application Testing Aspects of Web application testing Architectural styles Levels of testing An approach to integration testing Capture/replay Implicit/explicit states Test case generation.

mei
Download Presentation

Testing Processes of Web Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Testing Processes of Web Applications Susan Cohen

  2. Agenda • Brief introduction • Web Application Testing • Aspects of Web application testing • Architectural styles • Levels of testing • An approach to integration testing • Capture/replay • Implicit/explicit states • Test case generation

  3. Introduction • Web applications could benefit from formalized processes, better techniques, and defined methodologies • Process model for development of Web applications • UML model of Web applications

  4. Web Application Testing • Thin Web Client • Thick Web Client • Web Delivery Thin Web Client: Web applications, Http protocol for message exchange Thick Web Client Web Delivery: Traditional Client/Server, Own communication protocol

  5. Non-functional requirements • Response time • Load testing • Computation resources • Client • server

  6. Functional Requirements – Application as black box • Partition legal inputs into equivalence classes • Define one or more test cases for each of these classes • Use test cases and inputs to generate output pages • Deviations considered errors

  7. Functional Requirements:Application as white-box • HTML pages and messages exchanged via HTTP are known and drive the definition of test cases • Example: Link validation • Exploit knowledge of systems organization • Server programs, dynamic pages, forms, links, etc

  8. Levels of Testing • Unit Test • Integration Test • System Test • Acceptance Test • Regression Test • Integration and regression test dependent on type of web application

  9. Capture/Recapture of graphical events versus HTTP messages

  10. Approaching Integration Testing of Web Applications • Starting point: UML model for the Web application • Implicit and Explicit state models • Operations cannot be fully automated and user intervention is unavoidable • White box testing criteria • Page testing • Hyperlink testing • Definition use testing • All-uses testing • All paths testing • Disregard testing static pages with no forms

  11. Test Case Generation • Satisfying white box criteria means selecting a set of paths in the Web application graph • Provides input values • Explicit state model path selection is independent from input values • Can automate path and variable selection • Lots more info, but no more time • See article for further details

  12. Conclusions • Much of the Web application testing process cannot be automated and requires user intervention • Much work is still needed in Web application testing tools and techniques

  13. Questions:

More Related