book

Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems, Second Edition

Name: Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems, Second Edition
ISBN: 9780471201007

by Hung Q. Nguyen, Bob Johnson, Michael Hackett

June 2003

Intermediate to advanced

672 pages

14h 25m

English

Wiley

Read now

Unlock full access

Copyright
Preface
Foreword
Acknowledgments
About the Authors
1. Introduction
1. Welcome to Web Testing
1.1. Why Read This Chapter?1.2. Introduction1.3. The Evolution of Software Testing1.4. The Gray-Box Testing Approach1.5. Real-World Software Testing1.6. Themes of This Book1.7. What's New in the Second Edition1.7.1. New Contents and Significant Updates1.7.2. What Remains from the First Edition
2. Web Testing versus Traditional Testing
2.1. Why Read This Chapter?2.2. Introduction2.3. The Application Model2.4. Hardware and Software Differences2.5. The Differences between Web and Traditional Client-Server Systems2.5.1. Client-Side Applications2.5.2. Event Handling2.5.3. Application Instance and Windows Handling2.5.4. UI Controls2.6. Web Systems2.6.1. Hardware Mix2.6.2. Software Mix2.6.3. Server-Based Applications2.6.4. Distributed Server Configurations2.6.5. The Network2.7. Bug Inheritance2.8. Back-End Data Accessing2.9. Thin-Client versus Thick-Client Processing2.10. Interoperability Issues2.11. Testing Considerations2.12. Bibliography
2. Methodology and Technology
3. Software Testing Basics
3.1. Why Read This Chapter?3.2. Introduction3.3. Basic Planning and Documentation3.4. Common Terminology and Concepts3.4.1. Test Conditions3.4.1.1. Static Operating Environments3.4.1.2. Dynamic Operating Environments3.4.1.2.1. Resource Contention Example3.4.2. Test Types3.4.2.1. Acceptance Testing3.4.2.1.1. Development Acceptance Test3.4.2.1.2. Release Acceptance Test3.4.2.1.3. Functional Acceptance Simple Test3.4.2.1.4. Deployment Acceptance Test3.4.2.2. Feature-Level Testing3.4.2.2.1. Task-Oriented Functional Test3.4.2.2.2. Forced-Error Test3.4.2.2.3. Boundary Test3.4.2.2.4. System-Level Test3.4.2.2.5. Real-World User-Level Test3.4.2.2.6. Exploratory Test3.4.2.2.7. Load/Volume Test3.4.2.2.8. Stress Test3.4.2.2.9. Performance Test3.4.2.2.10. Fail-over Test3.4.2.2.11. Availability Test3.4.2.2.12. Reliability Test3.4.2.2.13. Scalability Testing3.4.2.2.14. API Test3.4.2.2.15. Regression Test3.4.2.2.16. Compatibility and Configuration Test3.4.2.2.17. Documentation Test3.4.2.2.18. Online Help Test3.4.2.2.19. Utilities/Toolkits and Collateral Test3.4.2.2.20. Install/Uninstall Test3.4.2.2.21. User Interface Tests3.4.2.2.22. Usability Tests3.4.2.2.23. Accessibility Tests3.4.2.2.24. External Beta Testing3.4.2.2.25. Dates Testing3.4.2.2.26. Security Tests3.4.2.2.27. Unit Tests3.4.3. Phases of Development3.5. Test-Case Development3.5.1. Equivalence Class Partitioning and Boundary Condition Analysis3.5.2. State Transition3.5.3. Use Cases3.5.3.1. Example Test Cases from Use Cases3.5.3.2. Test Cases Built from Use Cases3.5.3.3. Templates for Use-Case Diagram, Text, and Test Case3.5.4. Condition Combination3.5.5. The Combinatorial Method3.6. Bibliography

4. Networking Basics
4.1. Why Read This Chapter?4.2. Introduction4.3. The Basics4.3.1. The Networks4.3.2. The Internet4.3.2.1. Local Area Networks (LANs)4.3.2.2. Wide Area Networks (WANs)4.3.2.3. Connecting Networks4.3.2.4. Connectivity Services4.3.2.4.1. Dial-Up Connection4.3.2.5. Direct Connection4.3.2.5.1. Internet Connection Hardware4.3.2.6. Other Network Connectivity Devices4.3.3. TCP/IP Protocols4.3.3.1. The TCP/IP Architecture4.3.3.1.1. The Application Layer4.3.3.1.2. The Transport Layer4.3.3.1.3. The Internet Layer4.3.3.1.4. The Data Link Layer4.3.3.1.5. The Physical Layer4.3.4. Testing Scenarios4.3.4.1. Connection Type Testing4.3.4.1.1. Potential Modem Compatibility Issues4.3.4.1.2. Potential Dialer Compatibility Issues4.3.4.2. Connectivity Device Testing4.4. Other Useful Information4.4.1. IP Addresses and DNS4.4.1.1. IP Address4.4.1.2. Network Classes4.4.1.3. Domain Name System (DNS)4.4.2. Subnet4.4.2.1. Subnet Masks4.4.2.2. Custom Subnets4.4.3. A Testing Example4.4.3.1. Host Name and IP Resolution Tests4.5. Testing Considerations4.6. Bibliography
5. Web Application Components
5.1. Why Read This Chapter?5.2. Introduction5.3. Overview5.3.1. Distributed Application Architecture5.3.1.1. Traditional Client-Server Systems5.3.1.2. Thin- versus Thick-Client Systems5.3.1.3. Web-Based Client-Server Systems5.3.2. Software Components5.3.2.1. Operating Systems5.3.2.2. Application Service Components5.3.2.3. Third-Party Components5.3.2.4. Integrated Application Components5.3.3. Dynamic Link Library (DLL)5.3.3.1. Potential DLL-Related Errors5.3.3.2. Scripts5.4. Web Application Component Architecture5.4.1. Server-Side Components5.4.1.1. Core Application Service Components5.4.1.1.1. Web Servers5.4.1.1.2. Database Servers5.4.1.1.3. Application Servers5.4.1.2. Markup Language Pages5.4.1.3. XML with SOAP5.4.1.4. Web-to-Database Connectivity5.4.1.4.1. Common Gateway Interface (CGI)5.4.1.4.2. Web Server Extension-Based Programs5.4.1.4.3. Web Server Extension-Based Scripts5.4.1.4.4. ASP/JSP versus CGI5.4.1.4.5. ASP/JSP versus Web Server Extension-Based Programs5.4.1.5. Other Application Service Components5.4.1.5.1. Search Servers5.4.1.5.2. Proxy Servers and Firewalls5.4.1.5.3. Communication-Related Servers5.4.1.5.4. E-Commerce-Related Servers5.4.1.5.5. Multimedia-Related Servers5.4.2. Client-Side Components5.4.2.1. Web Browsers5.4.2.2. Add-on/Plug-in Components5.4.2.2.1. Communication-Related Components5.5. Testing Discussion5.5.1. Test-Case Design Analysis5.5.2. Test Partitioning5.6. Testing Considerations5.6.1. DLL Testing Issues5.6.2. Script Testing Issues5.6.2.1. Characteristics of a Script5.6.2.2. Use of Scripts in Web Applications5.6.2.3. Testing Scripts in Web Applications5.6.2.4. Coding-Related Problems5.6.2.5. Script Configuration Testing5.7. Bibliography
6. Mobile Web Application Platform
6.1. Why Read This Chapter?6.2. Introduction6.3. What Is a Mobile Web Application?6.4. Various Types of Mobile Web Client6.4.1. Palm-Sized PDA Devices6.4.2. Data Synchronizing6.4.3. Web Connectivity6.4.4. Various Types of Palm-Sized PDA Devices6.4.5. Handheld PCs6.5. WAP-Based Phones6.5.1. i-Mode Devices6.5.2. Smart Phones or Mobile Phone/PDA Combos6.6. Mobile Web Application Platform Test Planning Issues6.6.1. Microbrowsers6.6.2. Web Clipping Application: How Does It Work?6.6.3. Handheld Device Hardware Restrictions6.6.4. Software-Related Issues6.6.5. Wireless Network Issues6.6.5.1. Wireless Network Standards6.6.5.1.1. 1G6.6.5.1.2. 2G6.6.5.1.3. 3G/2.5G6.6.5.1.4. Ready for 4G?6.6.5.2. Wireless Modem6.6.5.3. Wireless LAN and Bluetooth6.6.6. Other Software Development Platforms and Support Infrastructures6.7. The Device Technology Converging Game: Who Is the Winner?6.8. Bibliography and Additional Resources6.8.1. Bibliography6.8.2. Additional Resources
7. Test Planning Fundamentals
7.1. Why Read This Chapter?7.2. Introduction7.3. Test Plans7.3.1. Test-Plan Documentation7.3.2. Test-Plan Templates7.3.3. Test-Plan Section Definitions7.4. LogiGear One-Page Test Plan7.4.1. Developing a One-Page Test Plan7.4.1.1. Step 1: Test Task Definition7.4.1.2. Step 2: Task Completion Time7.4.1.3. Step 3: Placing the Test Tasks into Context7.4.1.4. Step 4: Table Completion7.4.1.5. Step 5: Resource Estimation7.4.2. Using the LogiGear One-Page Test Plan7.5. Testing Considerations7.5.1. Issue Reports7.5.2. Weekly Status Reports7.5.3. Automated Testing7.5.4. Milestone Criteria and Milestone Tests7.6. Bibliography
8. Sample Application
8.1. Why Read This Chapter?8.2. Introduction8.3. Application Description8.4. Technical Overview8.5. System Requirements8.6. Functionality of the Sample Application8.6.1. Installing the Sample Application8.6.2. Getting Started8.6.3. Division Databases8.6.4. Importing Report Data8.6.5. System Setup8.6.6. Project Setup8.6.7. E-Mail Notification8.6.8. Submitting Defect Reports8.6.9. Generating Metrics8.6.10. Documentation8.7. Bibliography
9. Sample Test Plan
9.1. Why Read This Chapter?9.2. Introduction9.3. Gathering Information9.3.1. Step 1: Testing-Task Definitions for the Sample Application9.3.2. Step 2: Task Completion Time9.3.3. Step 3: Placing Test Tasks into the Project Plan9.3.4. Step 4: Calculate Hours and Resource Estimates9.4. Sample One-Page Test Plan9.5. Bibliography
3. Testing Practice
10. User Interface Tests
10.1. Why Read This Chapter?10.2. Introduction10.3. User Interface Design Testing10.3.1. Profiling the Target User10.3.1.1. Computer Experience10.3.1.2. Web Experience10.3.1.3. Domain Knowledge10.3.1.4. Application-Specific Experience10.3.2. Considering the Design10.3.2.1. Design Approach10.3.2.2. User Interaction (Data Input)10.3.2.2.1. User Interface Controls10.3.2.2.2. Dynamic User Interface Controls10.3.2.2.3. Navigation Methods10.3.2.2.4. Mouse/Keyboard Action Matrices10.3.2.2.5. Action Commands10.3.2.2.6. Feedback and Error Messages10.3.2.3. Data Presentation (Data Output)10.4. User Interface Implementation Testing10.4.1. Miscellaneous User Interface Elements10.4.1.1. Display Compatibility Matrix10.5. Usability and Accessibility Testing10.5.1. Accessibility Testing10.6. Testing Considerations10.7. Bibliography and Additional Resources10.7.1. Bibliography10.7.2. Recommended Reading10.7.3. Useful Links
11. Functional Tests
11.1. Why Read This Chapter?11.2. Introduction11.3. An Example of Cataloging Features in Preparation for Functional Tests11.3.1. Testing the Sample Application11.4. Testing Methods11.4.1. Functional Acceptance Simple Tests11.4.2. Task-Oriented Functional Tests11.4.3. Forced-Error Tests11.4.4. Boundary Condition Tests and Equivalent Class Analysis11.4.5. Exploratory Testing11.4.6. Software Attacks11.4.7. Which Method Is It?11.5. Bibliography
12. Server-Side Testing
12.1. Why Read This Chapter?12.2. Introduction12.3. Common Server-Side Testing Issues12.3.1. Connectivity Issues12.3.1.1. Time-Out Issues12.3.1.2. Maintaining State12.3.2. Resource Issues12.3.3. Backup and Restore Issues12.3.4. Fail-over Issues12.3.5. Multithreading Issues12.4. Server Side Testing Tips12.4.1. Using Log Files12.4.2. Using Monitoring Tools12.4.3. Creating Test Interfaces or Test Drivers12.4.4. The Testing Environment12.4.4.1. Working with Live Systems12.4.4.2. Resetting the Server12.4.5. Using Scripts in Server-Side Testing12.5. Bibliography12.5.1. Additional Resources12.5.1.1. Testing Tools for Run-Time Testing
13. Using Scripts to Test
13.1. Why Read This Chapter?13.2. Introduction13.3. Batch or Shell Commands13.3.1. Batch Files and Shell Scripts13.4. Scripting Languages13.4.1. Why Not Just Use a Compiled Program Language?13.4.2. What Should You Script?13.5. Application of Scripting to Testing Tasks13.5.1. System Administration: Automating Tasks13.5.2. Discovering Information about the System13.5.3. Testing the Server Directly: Making Server-Side Requests13.5.4. Working with the Application Independent of the UI13.5.5. Examining Data: Log Files and Reports13.5.6. Using Scripts to Understand Test Rexssults13.5.7. Using Scripts to Improve Productivity13.5.7.1. A Script to Test Many Files13.5.7.2. A Set of Scripts That Run Many Times13.5.8. Executing Tests That Cannot Be Run Manually13.6. Scripting Project Good Practice13.7. Scripting Good Practice13.8. Resource Lists13.8.1. General Resources for Learning More about Scripting13.8.2. Windows Script Host (WSH)13.8.3. Batch and Shell13.8.4. Perl13.8.5. Tcl13.8.6. AWK13.8.7. Learn SQL13.8.8. Where to Find Tools and Download Scripts13.9. Bibliography and Useful Reading
14. Database Tests
14.1. Why Read This Chapter?14.2. Introduction14.3. Relational Database Servers14.3.1. Structured Query Language14.3.1.1. Database Producers and Standards14.3.1.2. Database Extensions14.3.1.3. Example of SQL14.4. Client/SQL Interfacing14.4.1. Microsoft Approach to CLI14.4.2. Java Approach to CLI14.5. Testing Methods14.5.1. Common Types of Errors to Look For14.5.2. Database Stored Procedures and Triggers14.5.3. White-Box Methods14.5.3.1. Code Walk-through14.5.3.2. Redundancy Coding Error Example14.5.3.3. Inefficiency Coding Error Example14.5.3.4. Executing the SQL Statements One at a Time14.5.3.5. Executing the Stored Procedures One at a Time14.5.3.6. Testing Triggers14.5.3.7. External Interfacing14.5.4. Black-Box Methods14.5.4.1. Designing Test Cases14.5.4.2. Testing for Transaction Logic14.5.4.3. Testing for Concurrency Issues14.5.4.4. Preparation for Database Testing14.5.4.5. Setup/Installation Issues14.5.4.6. Testing with a Clean Database14.6. Database Testing Considerations14.7. Bibliography and Additional Resources14.7.1. Bibliography14.7.2. Additional Resources
15. Help Tests
15.1. Why Read This Chapter?15.2. Introduction15.3. Help System Analysis15.3.1. Types of Help Systems15.3.1.1. Application Help Systems15.3.1.2. Reference Help Systems15.3.1.3. Tutorial Help Systems15.3.1.4. Sales and Marketing Help Systems15.3.2. Evaluating the Target User15.3.3. Evaluating the Design Approach15.3.4. Evaluating the Technologies15.3.4.1. Standard HTML (W3 Standard)15.3.4.2. Java Applets15.3.4.3. Netscape NetHelp15.3.4.4. ActiveX Controls15.3.4.5. Help Elements15.4. Approaching Help Testing15.4.1. Two-Tiered Testing15.4.1.1. Stand-alone Testing15.4.1.2. Interaction between the Application and the Help System15.4.2. Types of Help Errors15.5. Testing Considerations15.6. Bibliography
16. Installation Tests
16.1. Why Read This Chapter?16.2. Introduction16.3. The Roles of Installation/Uninstallation Programs16.3.1. Installer16.3.2. Uninstaller16.4. Common Features and Options16.4.1. User Setup Options16.4.2. Installation Sources and Destinations16.4.2.1. Server Distribution Configurations16.4.2.2. Server-Side Installation Example16.4.2.3. Media Types16.4.3. Branching Options16.5. Common Server-Side-Specific Installation Issues16.6. Installer/Uninstaller Testing Utilities16.6.1. Comparison-Based Testing Tools16.6.2. InControl4 and InControl516.6.3. Norton Utilities' Registry Tracker and File Compare16.7. Testing Considerations16.8. Bibliography and Additional Resources16.8.1. Additional Resources
17. Configuration and Compatibility Tests
17.1. Why Read This Chapter?17.2. Introduction17.3. The Test Cases17.4. Approaching Configuration and Compatibility Testing17.4.1. Considering Target Users17.4.2. When to Run Compatibility and Configuration Testing17.4.3. Potential Outsourcing17.5. Comparing Configuration Testing with Compatibility Testing17.6. Configuration/Compatibility Testing Issues17.6.1. COTS Products versus Hosted Systems17.6.2. Distributed Server Configurations17.6.3. Client-Side Issues17.6.4. Web Browsers17.7. Testing Considerations17.8. Bibliography17.9. Additional Resources
18. Web Security Testing
18.1. Why Read This Chapter?18.2. Introduction18.2.1. What Is Computer Security?18.3. Security Goals18.3.1. From Which Threats Are We Protecting Ourselves?18.3.2. Common Sources of Security Threats18.3.3. What Is the Potential Damage?18.4. Anatomy of an Attack18.4.1. Information Gathering18.4.2. Network Scanning18.4.3. Attacking18.5. Attacking Intents18.6. Security Solution Basics18.6.1. Strategies, People, and Processes18.6.1.1. Education18.6.1.2. Corporate Security Policies18.6.1.3. Corporate Responses18.6.2. Authentication and Authorization18.6.2.1. Passwords18.6.2.2. Authentication between Software Applications or Components18.6.2.3. Cryptography18.6.2.3.1. Public Key Cryptography Basics18.6.2.3.2. Digital Certificates18.6.2.3.3. Pretty Good Privacy18.6.2.3.4. Secure Multipurpose Internet Mail Extensions (S/MIME)18.6.2.4. Other Web Security Technologies18.6.3. Perimeter-Based Security: Firewalls, DMZs, and Intrusion Detection Systems18.6.3.1. Firewalls18.6.3.1.1. Packet-Screening Firewalls (Routers)18.6.3.1.2. Proxy-Based Firewalls (Gateways)18.6.3.2. Setting Up a DMZ18.6.3.3. Intrusion Detection Systems (IDS)18.7. Common Vulnerabilities and Attacks18.7.1. Software Bugs, Poor Design, and Programming Practice18.7.1.1. Buffer Overflows18.7.1.2. Malicious Input Data18.7.1.3. Command-Line (Shell) Execution18.7.1.4. Backdoors18.7.1.5. JavaScript18.7.1.6. CGI Programs18.7.1.7. Java18.7.1.8. ActiveX18.7.2. Cookies18.7.3. Spoofing18.7.4. Malicious Programs18.7.4.1. Virus and Worm18.7.4.2. Trojan Horses18.7.5. Misuse Access Privilege Attacks18.7.6. Password Cracking18.7.7. Denial-of-Service Attacks18.7.8. Physical Attacks18.7.9. Exploiting the Trust Computational Base18.7.10. Information Leaks18.7.10.1. Social Engineering18.7.10.2. Keystroke Capturing18.7.10.3. Garbage Rummaging18.7.10.4. Packet Sniffing18.7.10.5. Scanning and Probing18.7.10.6. Network Mapping18.7.11. Network Attacks18.8. Testing Goals and Responsibilities18.8.1. Functionality Side Effect: An Error-Handling Bug Example18.9. Testing for Security18.9.1. Testing the Requirements and Design18.9.1.1. Requirements Are Key18.9.1.2. Trusted Computational Base (TCB)18.9.1.3. Access Control18.9.1.4. Which Resources Need to Be Protected?18.9.1.5. Client Privacy Issues: What Information Needs to Be Private?18.9.2. Testing the Application Code18.9.2.1. Backdoors18.9.2.2. Exception Handling and Failure Notification18.9.2.3. ID and Password Testing18.9.2.4. Testing for Information Leaks18.9.2.5. Random Numbers versus Unique Numbers18.9.2.6. Testing the Use of GET and POST18.9.2.7. Parameter-Tampering Attacks18.9.3. SQL Injection Attacks18.9.3.1. Cookie Attacks18.9.3.2. Testing for Buffer Overflows18.9.3.3. Testing for Bad Data18.9.3.4. Reliance on Client-Side Scripting18.9.3.5. When Input Becomes Output18.9.4. Testing Third-Party Code18.9.4.1. Known Vulnerabilities18.9.4.2. Race Conditions18.9.5. Testing the Deployment18.9.5.1. Installation Defaults18.9.5.2. Default Passwords18.9.5.3. Internationalization18.9.5.4. Program Forensics18.9.5.5. Working with Customer Support Folks18.9.6. Penetration Testing18.9.7. Testing with User Protection via Browser Settings18.9.7.1. Testing with Firewalls18.9.8. The Challenges Testers Face18.10. Other Testing Considerations18.11. Bibliography and Additional Resources18.11.1. Bibliography18.11.2. Additional Resources18.11.3. Useful Net Resources18.11.4. Tools
19. Performance Testing
19.1. Why Read This Chapter?19.2. Introduction19.3. Performance Testing Concepts19.3.1. Determining Acceptable Response Time or Acceptable User Experience19.3.2. Response Time Definition19.3.3. Performance and Load Stress Testing Definitions19.3.4. Searching for Answers19.3.5. A Simple Example19.4. Performance Testing Key Factors19.4.1. Workload19.4.2. System Environment and Available Resources19.4.3. Response Time19.4.4. Key Factors Affecting Response Time or Performance19.5. Three Phases of Performance Testing19.6. Setting Goals and Expectations and Defining Deliverables19.7. Gathering Requirements19.7.1. What Are You Up Against?19.7.2. What If Written Requirements Don't Exist?19.8. Defining the Workload19.9. Sizing the Workload19.9.1. Server-Based Profile19.9.2. User-Based Profile19.10. Problems Concerning Workloads19.11. Selecting Performance Metrics19.11.1. Throughput Calculation Example19.12. Which Tests to Run and When to Start19.13. Tool Options and Generating Loads19.13.1. Tool Options19.13.2. Analyzing and Reporting Collected Data19.13.3. Generating Loads19.14. Writing the Test Plan19.14.1. Identifying Baseline Configuration and Performance Requirements19.14.2. Determining the Workload19.14.3. Determining When to Begin Testing19.14.4. Determine Whether the Testing Process Will Be Hardware-Intensive or Software-Intensive19.14.5. Developing Test Cases19.15. Testing Phase19.15.1. Generating Test Data19.15.2. Setting Up the Test Bed19.15.3. Setting Up the Test Suite Parameters19.15.4. Performance Test Run Example19.16. Analysis Phase19.17. Other Testing Considerations19.18. Bibliography
20. Testing Mobile Web Applications
20.1. Why Read This Chapter?20.2. Introduction20.3. Testing Mobile versus Desktop Web Applications20.4. Various Types of Tests20.4.1. Add-on Installation Tests20.4.2. Data Synchronization-Related Tests20.4.3. UI Implementation and Limited Usability Tests20.4.3.1. UI Guideline References20.4.4. Browser-Specific Tests20.4.5. Platform-Specific Tests20.4.5.1. Platform or Logo Compliance Tests20.4.6. Configuration and Compatibility Tests20.4.7. Connectivity Tests20.4.7.1. Devices with Peripheral Network Connections20.4.7.2. Latency20.4.7.3. Transmission Errors20.4.7.4. Transitions from Coverage to No-Coverage Areas20.4.7.5. Transitions between Data and Voice20.4.7.6. Data or Message Race Condition20.4.7.7. Performance Tests20.4.8. Security Tests20.4.9. Testing Web Applications Using an Emulation Environment20.4.10. Testing Web Applications Using the Physical Environment20.5. Survey of Mobile Testing Support Tools20.5.1. Device and Browser Emulators20.5.1.1. Palm Computing20.5.1.2. OpenWave20.5.1.3. Nokia20.5.1.4. YoSpace20.5.1.5. Microsoft20.5.2. Web-Based Mobile Phone Emulators and WML Validators20.5.3. Desktop WAP Browsers20.6. Other Testing Considerations20.7. Bibliography and Additional Resources20.7.1. Bibliography20.7.2. Additional Resources
21. Web Testing Tools
21.1. Why Read This Chapter?21.2. Introduction21.3. Types of Tools21.3.1. Rule-Based Analyzers21.3.1.1. Sample List of Link Checkers and HTML Validators21.3.1.2. Sample List of Rule-Based Analyzers for C/C++, Java, Visual Basic, and Other Programming and Scripting Languages21.3.2. Load/Performance Testing Tools21.3.2.1. Web Load and Performance Testing Tools21.3.3. GUI Capture (Recording/Scripting) and Playback Tools21.3.3.1. Sample List of Automated GUI Functional and Regression Testing Tools21.3.4. Runtime Error Detectors21.3.4.1. Sample List of Runtime Error-Detection Tools21.3.5. Sample List of Web Security Testing Tools21.3.6. Java-Specific Testing Tools21.3.7. Other Types of Useful Tools21.3.8. Database Testing Tools21.3.9. Defect Management Tool Vendors21.3.9.1. QACity.Com Comprehensive List of DEFECT TRACKING Tool Vendors21.4. Additional Resources21.4.1. On the Internet21.4.2. Development and Testing Tool Mail-Order Catalogs
22. Finding Additional Information
22.1. Why Read This Chapter?22.2. Introduction22.3. Textbooks22.4. Web Resources22.4.1. Useful Links22.4.2. Useful Magazines and Newsletters22.4.3. Miscellaneous Papers on the Web from Carnegie Mellon University's Software Engineering Institute22.5. Professional Societies
A. LogiGear Test Plan Template
A.1. I. OverviewA.1.1. 1. Test Plan IdentifierA.1.2. 2. IntroductionA.1.3. 3. ObjectiveA.1.4. 4. ApproachA.2. II. Testing SynopsisA.2.1. 1. Test ItemsA.2.1.1. 1.1.1. Main Application ExecutablesA.2.1.2. 1.2. Software Collateral ItemsA.2.1.3. 1.3. Publishing ItemsA.2.2. 2. Features to Be TestedA.2.3. 3. Features Not to Be TestedA.2.4. 4. System RequirementsA.2.5. 5. Product Entrance/ExitA.2.6. 6. Standard/ReferenceA.2.7. 7. Test DeliverablesA.2.8. 7.1. Test PlanA.2.8.1. 7.1.1. The Original Approved Development Test PlanA.2.8.2. 7.1.2. The Executed Development Test PlanA.2.8.3. 7.1.3. The Original Approved Final Test PlanA.2.8.4. 7.1.4. The Executed Final Test PlanA.2.9. 7.2. Bug-Tracking SystemA.2.9.1. 7.2.1. Bug ReportsA.2.9.2. 7.2.2. Bug DatabaseA.2.10. 7.3. Final Release ReportA.3. III. Testing Project ManagementA.3.1. 1. The Product TeamA.3.2. 2. Testing ResponsibilitiesA.3.3. 3. Testing TasksA.3.4. 4. Development Plan and ScheduleA.3.5. 5. Milestone Entrance/Exit CriteriaA.3.6. 6. Test Schedule and ResourceA.3.6.1. 6.1. ScheduleA.3.6.2. 6.2. Resource EstimateA.3.7. 7. Training NeedsA.3.8. 8. Environmental NeedsA.3.8.1. 8.1. Test ComponentsA.3.8.2. 8.2. Test ToolsA.3.8.3. 8.3. FacilitiesA.3.9. 9. Integration PlanA.3.10. 10. Test Suspension and ResumptionA.3.11. 11. Test Completion CriteriaA.3.12. 12. The Problem-Tracking ProcessA.3.12.1. 12.1. The ProcessA.3.12.2. 12.2. The Bug-Tracking Tool (database)A.3.12.3. 12.3. Definition of Bug SeverityA.3.12.3.1. 12.3.1. 1—CriticalA.3.12.3.2. 12.3.2. 2—SeriousA.3.12.3.3. 12.3.3. 3—NoncriticalA.3.13. 13. Status Tracking and ReportingA.3.14. 14. Risks and ContingenciesA.3.15. 15. The Approval ProcessA.3.15.1. 15.1. Test Plan ApprovalA.3.15.2. 15.2. Final Release ApprovalA.4. Appendix 1: Setup/Installation Test CaseA.5. Appendix 2: Test Case for Application ShellA.6. Appendix 3: Test Matrix for XXXXXA.7. Appendix 4: Compatibility Test Systems
B. Weekly Status Report Template
B.1. I. Testing Project ManagementB.1.1. 1. Project Schedule*B.1.2. 2. Progress and Changes Since Last WeekB.1.3. 3. Urgent ItemsB.1.4. 4. Issue BinB.1.5. 5. To-do Tasks by Next ReportB.2. II. Problem Report StatusB.2.1. 1. Bug Report TabulationB.2.2. 2. Summary List of Open BugsB.3. III. Trend Analysis ReportB.3.1. Stability Trend ChartB.3.2. Quality Trend Chart
C. Error Analysis Checklist: Web Error Examples
C.1. Check for the Existence of DNS EntryC.1.1. SymptomsC.1.2. Possible ProblemsC.1.3. ExamplesC.1.4. TipsC.2. Check for Proper Configuration of the Client Machine and Browser SettingsC.2.1. SymptomsC.2.2. Possible ProblemsC.2.3. ExamplesC.2.4. TipsC.3. Check the HTTP Settings on the BrowserC.3.1. SymptomsC.3.2. Possible ProblemsC.3.3. ExamplesC.3.4. TipsC.4. Check the JIT Compiler-Enabled Setting on the BrowserC.4.1. SymptomsC.4.2. Possible ProblemsC.4.3. ExamplesC.4.4. TipC.5. Check the Multimedia Settings on the BrowserC.5.1. SymptomsC.5.2. Possible ProblemsC.5.3. ExamplesC.5.4. TipC.6. Check the Security Settings on the BrowserC.6.1. SymptomsC.6.2. Possible ProblemsC.6.3. ExamplesC.6.4. TipC.7. Check for a Slow ConnectionC.7.1. SymptomsC.7.2. Possible ProblemsC.7.3. ExamplesC.7.4. TipsC.8. Check for Proper Configuration on the Web ServerC.8.1. SymptomsC.8.2. Possible ProblemsC.8.3. ExamplesC.8.4. TipsC.9. Check for the Deletion of Your Browser Cache (Temporary Internet Files)C.9.1. SymptomsC.9.2. Possible ProblemsC.9.3. ExamplesC.9.4. Tip
D. UI Test-Case Design Guideline: Common Keyboard Navigation and Shortcut Matrix
E. UI Test-Case Design Guideline: Mouse Action Matrix
F. Web Test-Case Design Guideline: Input Boundary and Validation Matrix I
G. Display Compatibility Test Matrix
H. Browser OS Configuration Matrix

Content preview from Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems, Second Edition

Chapter 14. Database Tests

Why Read This Chapter?

All Web-based data access applications require database servers. To effectively plan for database testing and the analysis of database-related errors, it is useful to understand key database technology concepts, how Web server components interact with the database components, and other testing issues.

Introduction

This chapter offers an introduction to database components, application- database interaction, data warehouses, and data marts. Technical terms and examples that are useful in improving test planning and bug-report communication are also discussed. Databases play an important role in Web application technology. They house the content that Web applications manage—fulfilling user requests for data storage and record queries. Understanding how databases operate within Web applications is essential to effective database testing. Databases are repositories that are organized in such a way that makes it easy to manage and update the data they contain. One of the database technologies commonly used in Web-based applications is the relational database. Relational databases are tabular databases that can be easily reorganized and queried. Additionally, in a Web environment, the term distributed database is used to refer to databases that are dispersed over multiple ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9780471201007Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design