1 / 19

Chapter 20 Testing For WebApps

Chapter 20 Testing For WebApps. 20.1 Testing Concepts for WebApps. Dimensions of Quality Content: syntactic and semantic level Function: correctness, instability, standards Structure: proper delivery, extensible, supported extension

skyler
Download Presentation

Chapter 20 Testing For WebApps

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. Chapter 20Testing For WebApps

  2. 20.1 Testing Concepts for WebApps • Dimensions of Quality • Content: syntactic and semantic level • Function: correctness, instability, standards • Structure: proper delivery, extensible, supported extension • Usability: each actor can learn and apply all required navigation syntax and semantics of the interface • Navigability: navigation syntax and semantics • Performance: operating conditions, configurations, and loading • Compatibility: different host configurations on both the client and server sides • Interoperability:interfaces with other applications and/or databases • Security: potential vulnerabilities 1/18

  3. 20.1 Testing Concepts for WebApps • The Difficulties • A symptom on the client side is not the error itself • Almost impossible to reproduce an error outside the environment • Many errors are due to the configuration • Difficult to trace across the client, the server, and the network layers • Static (configuration) and dynamic (instantaneous resource loading or time-related errors) operating environments both generate errors Environment plays an important role in the diagnosis of errors. 2/18

  4. 20.1 Testing Concepts for WebApps • Testing Strategy • The content model for the WebApp is reviewed to uncover errors. • The interface model is reviewed to ensure that all use-cases can be accommodated. • The design model for the WebApp is reviewed to uncover navigation errors. • The user interface is tested to uncover errors in presentation and/or navigation mechanics. • Selected functional components are unit tested. 3/18

  5. 20.1 Testing Concepts for WebApps • Testing Strategy • Navigation throughout the architecture is tested. • The WebApp is implemented in a variety of different environmental configurations and is tested for compatibility with each configuration. • Security tests are conducted in an attempt to exploit vulnerabilities in the WebApp or within its environment. • Performance tests are conducted. • The WebApp is tested by a controlled and monitored population of end-users 4/18

  6. Content Testing Interface Testing User Navigation Testing Interface design Component Testing Aesthetic design Content design Navigation design Configuration Testing Architecture design Component design Performance Testing Security Testing technology 20.2 The Testing Process – An Overview 5/18

  7. 20.3 Content Testing • Objectives • to uncover syntactic errors (e.g., typos, grammar mistakes) in text-based documents, graphical representations, and other media • to uncover semantic errors (i.e., errors in the accuracy or completeness of information) in any content object presented as navigation occurs • to find errors in the organization or structure of content that is presented to the end-user. 6/18

  8. 20.3 Content Testing • Database Testing – why complicated? • The original client-side request is rarely presented in the form (e.g., SQL) for DBMS => translation • The DB may be remote to the WebApp server => server communication • Raw data from DB must be transmitted to the WebApp server and then to the client => raw data and transformations • The dynamic content object(s) must be in proper format for display => format and compatibility Layers of interaction 7/18

  9. Client layer – user interface HTML scripts Server layer – WebApp User data Tests are designed for each layer Server layer – data transformation User data SQL Server layer – data management Raw data SQL Database layer – data access Database 20.3 Content Testing • Layers of interaction 8/18

  10. 20.4 User Interface Testing • Testing Strategy: to uncover errors • related to specific interface mechanisms • in the way the interface implements the semantics of navigation, functionality or content display • Objectives • Test interface features => design rules, aesthetics, and related visual content • Test individual interface mechanisms (unit testing) • Test each interface mechanism => use-case or NSU for a specific user category • Test the complete interface against selected use-cases and NSUs => semantics of the interface • The interface is tested within a variety of environments (e.g., browsers) => compatible 9/18

  11. 20.4 User Interface Testing • Testing Interface Mechanisms Links Forms Client-side scripting Dynamic HTML Pop-up windows CGI scripts Streaming content Cookies Application specific interface mechanisms 10/18

  12. 20.4 User Interface Testing • Usability Tests:designed by a WebE team … executed by end-users • Define a set of usability testing categories and identify goals for each • Interactivity, layout, readability, aesthetics, display characteristics, time sensitivity, personalization, accessiblity • Design tests that will enable each goal to be evaluated • Select participants who will conduct the tests • Instrument participants’ interaction with the WebApp while testing is conducted • Develop a mechanism for assessing the usability of the WebApp 11/18

  13. 20.5 Component-Level Testing • Focuses on a set of tests that attempt to uncover errors in WebApp functions • Conventional black-box and white-box test case design methods can be used • Database testing is often an integral part of the component-testing regime 12/18

  14. 20.6 Navigation Testing • Objectives: • Syntax • Navigation links • Redirects • Bookmarks • Frames and framesets • Site maps • Internal search engines • Semantics Please read 20.6.2 for the testing questions 13/18

  15. 20.7 Configuration Testing • Server-side • Is the WebApp fully compatible with the server OS? • Are system files, directories, and related system data created correctly when the WebApp is operational? • Do system security measures (e.g., firewalls or encryption) allow the WebApp to execute and service users without interference or performance degradation? • Has the WebApp been tested with the distributed server configuration (if one exists) that has been chosen? • Is the WebApp properly integrated with database software? Is the WebApp sensitive to different versions of database software? • Do server-side WebApp scripts execute properly? • Have system administrator errors been examined for their affect on WebApp operations? • If proxy servers are used, have differences in their configuration been addressed with on-site testing? 14/18

  16. 20.7 Configuration Testing • Client-side • Hardware —CPU, memory, storage and printing devices • Operating systems —Linux, Macintosh OS, Microsoft Windows, a mobile-based OS • Browser software —Internet Explorer, Mozilla/Netscape, Opera, Safari, and others • User interface components —Active X, Java applets and others • Plug-ins —QuickTime, RealPlayer, and many others • Connectivity —cable, DSL, regular modem, T1 15/18

  17. 20.8 Security Testing • Designed to probe vulnerabilities of • the client-side environment • the network communications that occur as data are passed from client to server and back again • the server-side environment • On the client-side, vulnerabilities can often be traced to pre-existing bugs in browsers, e-mail programs, or communication software. • On the server-side, vulnerabilities include denial-of-service attacks and malicious scripts that can be passed along to the client-side or used to disable server operations 16/18

  18. 20.9 Performance Testing • Objectives: to simulate real-world loading situations • Does the server response time degrade to a point where it is noticeable and unacceptable? • At what point (in terms of users, transactions or data loading) does performance become unacceptable? • What system components are responsible for performance degradation? • What is the average response time for users under a variety of loading conditions? • Does performance degradation have an impact on system security? • Is WebApp reliability or accuracy affected as the load on the system grows? • What happens when loads that are greater than maximum server capacity are applied? 17/18

  19. 20.9 Performance Testing • Load Testing:how the WebApp and its server-side environment will respond to various loading conditions • N, the number of concurrent users • T, the number of on-line transactions per user per unit time • D, the data load processed by the server per transaction • Overall throughput P = N x T x D • Stress Testing: a continuation of load testing, but forces the variables to meet and then exceed operational limits Please read 20.9.3 for the testing questions 18/18

More Related