1 / 15

7. Web Application Testing

7. Web Application Testing. Introduction. World Wide Web (WWW) exploitations: to offer services and to be reached by large numbers of customers . T he request is high-quality Web applications : satisfying security, scalability, reliability, and accessibility.

odessa
Download Presentation

7. Web Application Testing

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. 7. Web Application Testing Web Engineering, ITBK 2010 (Muhyi)

  2. Introduction • World Wide Web (WWW) exploitations: to offer services and to be reached by large numbers of customers. • Therequest is high-quality Web applications: satisfying security, scalability,reliability, and accessibility. • Testing Web applications’ quality  a crucialproblem. • Due to market pressure and very short time-to-market,the Web applications testing is often neglected  time-consuming and lack a significant payoff. Web Engineering, ITBK 2010 (Muhyi)

  3. Web Application Characteristics • A Web application can be considered as a distributed system, with a client–server or multi-tier architecture • Including the following characteristics: • wide number of users • heterogeneous execution environments: hardware, network, operating system, Webserver, browsers • heterogeneous/different software nature  (C)OTS: (commercially) of-the-shelf • software components at run time Web Engineering, ITBK 2010 (Muhyi)

  4. Web App Test Perspectives • Perspectives: • Non-fuctional requirements • Functional requirements • Terms: • Web application  the set of software components implementing thefunctionality and services the application provides to its users • Running environment the whole infrastructure (composedof hardware, software and middleware components) needed to executea Web application Web Engineering, ITBK 2010 (Muhyi)

  5. The Main Goal • Testing a Web application is to run the application usingcombinations of input and state to discover failures. • A failure is themanifested inability of a system / component to perform a required functionwithin specified performance requirements. • Failure is probably caused by: • The implementation • The application itself • The environment • The interface • Different types of testing have tobe executed to uncover these diverse types of failures. Web Engineering, ITBK 2010 (Muhyi)

  6. Non-Functional Requirements .. • Performance Testing  simulating hundreds, or even more, simultaneous user accesses over a defined time interval • Load Testing  measure the time needed to perform several tasks and functions under predefined conditions • Stress Testing  evaluate a system or component at or beyond the limits of its specified requirements • Compatibility Testing  the system runs as expected on a running environment that has various combinations of hardware, software, and middleware Web Engineering, ITBK 2010 (Muhyi)

  7. .. Non-Functional Requirements • Usability Testing  verify to what extent an application is easy to use (highly related with the interface of the application) • Accessibility Testing  verify that the access to an application’s content is allowed even in the presence of reduced hardware and software configurations on the client side • Security Testing  verify the effectiveness of the defences against undesired access of unauthorised users, its capabilityto preserve system resources from improper use, and grantingauthorised users access to authorised services and resources. Web Engineering, ITBK 2010 (Muhyi)

  8. Test Levels Unit Testing (Pages) Intregation Testing System Testing Acceptance Testing Test Strategies Black-Box Testing White-Box Testing Grey-Box Testing Test Models Behaviour Model  functionality Structural Model  implementation Test Processes: unit test  integration test  system test  acceptance test Functional Requirement Aspects Web Engineering, ITBK 2010 (Muhyi)

  9. Web Application Testing Tools • Main categories: • Load, performance and stress test tools. • Web site security test tools. • HTML/XML validators. • Link checkers. • Usability and accessibility test tools. • Web functional/regression test tools. Web Engineering, ITBK 2010 (Muhyi)

  10. Functionality Testing • Test Model Generation • Test Case Management • Driver and Stub Generation • Code Instrumentation • Test Result Analysis • Report Generation Web Engineering, ITBK 2010 (Muhyi)

  11. Example: Component Relationship Web Engineering, ITBK 2010 (Muhyi)

  12. Example: Use Case Model Web Engineering, ITBK 2010 (Muhyi)

  13. Example: Graphical Notation Web Engineering, ITBK 2010 (Muhyi)

  14. Example: Decision Table Web Engineering, ITBK 2010 (Muhyi)

  15. Thank you ... Discussion, Q & A Web Engineering, ITBK 2010 (Muhyi)

More Related