1. What is Web Application Testing?
Web application testing is the process of validating a web-based system to ensure that each web page functions correctly, displays properly, performs efficiently, and remains secure across browsers, devices, and user conditions.
When interviewers ask about web page testing, they expect knowledge of:
- Page-level functionality (links, forms, validations)
- UI rendering and layout
- Client–server interaction
- Session, cookies, and caching
- Security vulnerabilities
- Performance behavior
- Browser compatibility
Unlike a single-page check, web page testing validates how individual pages behave independently and as part of an end-to-end flow.
2. Functional Testing Scenarios for Web Pages
Core Web Page Functional Scenarios
- Page loads successfully (HTTP 200)
- Correct content displayed based on user role
- All links navigate to expected pages
- Forms submit data correctly
- Mandatory field validations
- Error messages displayed for invalid actions
- Page refresh does not lose critical data
- Bookmarking page behavior
Login Page Test Scenarios
- Valid username and password login
- Invalid credentials error handling
- Blank username/password validation
- Password masking
- Case sensitivity check
- Login button disabled until mandatory fields filled
- Login via bookmarked URL
- Multiple login attempts handling
Session Timeout Page Scenarios
- Session expires after configured idle time
- User redirected to login page
- Back button does not show secured page
- Page reload after timeout redirects correctly
- Multiple tabs behavior after session expiry
Cookies & Caching Page Scenarios
- Cookies created after login
- Cookies contain no sensitive data
- Secure and HttpOnly flags enabled
- Pages not cached after logout
- Browser refresh does not expose secured content
- CDN caches only static pages
3. UI + UX + Responsive + Accessibility Test Cases
UI Test Cases for Web Pages
- Page layout alignment
- Proper spacing between elements
- Fonts and colors as per design
- Broken images or icons
- Consistent header/footer across pages
- Error messages positioned near fields
UX Test Cases
- Clear page purpose
- Minimal clicks to complete tasks
- Logical navigation flow
- Helpful validation messages
- Predictable page behavior
Responsive Web Page Testing
- Layout adapts on mobile, tablet, desktop
- No horizontal scrolling
- Menus collapse properly
- Buttons are touch-friendly
- Orientation change handled correctly
Accessibility Test Cases
- Keyboard-only navigation
- Tab order correctness
- Screen reader compatibility
- Alt text for images
- ARIA labels for dynamic elements
- Color contrast compliance (WCAG)
4. Web Page Testing Interview Questions & Answers
Q1. What is web page testing?
Answer:
Web page testing focuses on validating the functionality, UI, performance, security, and compatibility of individual web pages within a web application.
Q2. Difference between web page testing and web application testing?
Answer:
Web page testing validates individual pages, while web application testing validates complete workflows and system behavior.
Q3. What checks do you perform when a page loads?
Answer:
HTTP status, content accuracy, layout rendering, script errors, images, and load time.
Q4. How do you test links on a web page?
Answer:
Verify navigation, broken links, target behavior, and access control.
Q5. What is statelessness in web pages?
Answer:
Each HTTP request is independent; sessions and cookies maintain user state.
Q6. How do you test form validations?
Answer:
Check mandatory fields, format validation, boundary values, error messages, and server-side validation.
Q7. What is deep link testing?
Answer:
Accessing internal pages directly without authentication to check security.
Q8. How do you test page refresh behavior?
Answer:
Verify data persistence, duplicate submission prevention, and correct reload handling.
Q9. What is pagination testing?
Answer:
Validating navigation, record count consistency, sorting, filtering, and performance.
Q10. How do you test search functionality on a page?
Answer:
Validate keyword matching, case sensitivity, special characters, empty results, and performance.
Q11. What is client-side validation?
Answer:
Validation performed using JavaScript before sending data to server.
Q12. Why is server-side validation mandatory?
Answer:
Client-side validation can be bypassed, but server-side ensures data integrity and security.
Q13. How do you test error handling on a page?
Answer:
Trigger invalid actions and verify user-friendly, non-technical error messages.
Q14. How do you test logout functionality?
Answer:
Verify session destruction, cookie deletion, and back button behavior.
Q15. What are common web page UI defects?
Answer:
Misalignment, overlapping elements, broken images, unreadable text, missing messages.
Q16. What is cross-browser testing?
Answer:
Testing page behavior across different browsers and versions.
Q17. How do you test JavaScript errors?
Answer:
Check browser console for errors during page load and interactions.
Example:
Uncaught TypeError: Cannot read property ‘value’ of null
Q18. How do you test broken images?
Answer:
Verify image URLs, alt text, and network response codes.
Q19. How do you test role-based page access?
Answer:
Login with different roles and attempt unauthorized page access.
Q20. What is exploratory testing?
Answer:
Experience-based testing without predefined test cases.
5. Security & Penetration-Based Questions (Web Pages)
Q21. What is XSS?
Answer:
Cross-Site Scripting allows attackers to inject malicious scripts into web pages.
HTML Example:
<script>alert(‘XSS’)</script>
Q22. How do you test XSS on a page?
Answer:
Inject scripts into inputs and check if they execute or are encoded.
Q23. What is SQL Injection?
Answer:
Manipulating backend SQL queries via malicious input.
Example:
‘ OR ‘1’=’1
Q24. How do you test SQL Injection manually?
Answer:
Enter SQL characters in input fields and observe errors or data leakage.
Q25. What is CSRF?
Answer:
Forcing authenticated users to perform unwanted actions.
Q26. How do you test CSRF protection?
Answer:
Remove or modify CSRF tokens and submit requests.
Q27. What is authentication abuse?
Answer:
Misusing login features like brute force or credential stuffing.
Q28. How do you test brute force protection?
Answer:
Perform multiple failed login attempts and verify CAPTCHA or lockout.
Q29. What is session fixation?
Answer:
Forcing a known session ID and hijacking it after login.
Q30. What security headers should be validated?
Answer:
CSP, HSTS, X-Frame-Options, X-Content-Type-Options.
6. API + Web Services Validation Examples
API Scenarios for Web Pages
- Page triggers correct API calls
- Validate request payload
- Validate response structure
- Error handling validation
Common HTTP Status Codes
- 200 OK
- 201 Created
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 500 Internal Server Error
Sample JSON Request
{
“email”: “user@test.com”,
“password”: “Test@123”
}
Sample XML Request
<login>
<email>user@test.com</email>
<password>Test@123</password>
</login>
Postman / SOAPUI Usage
- Trigger APIs manually
- Validate headers and tokens
- Verify response time
- Validate schema
7. Web Page Performance Checkpoints
Key Performance Metrics
- TTFB (Time to First Byte)
- Page load time
- API response time
- DOM load time
- Concurrent user handling
CDN & Caching Validation
- Static resources served via CDN
- Cache-control headers configured
- Sensitive pages not cached
- Compression enabled
8. Browser & Device Compatibility Scenarios
- Chrome, Firefox, Edge, Safari
- Different browser versions
- Android vs iOS
- Different resolutions
- JavaScript compatibility issues
9. Real-Time Defects with RCA
Defect 1: Page Accessible After Logout
- Severity: High
- Priority: High
- Root Cause: Session not invalidated on server
- Fix: Destroy session token on logout
Defect 2: XSS in Comment Field
- Root Cause: Missing output encoding
- Fix: Encode user input before rendering
Defect 3: Slow Page Load
- Root Cause: Large images without compression
- Fix: Image optimization and CDN usage
10. Defect Logging Format + RCA
Defect Template
- Defect ID
- Summary
- Steps to Reproduce
- Expected Result
- Actual Result
- Severity
- Priority
- Root Cause
- Environment
Severity vs Priority
- Severity: Business impact
- Priority: Fix urgency
11. Quick Revision Sheet
- Validate page load and navigation
- Test login and session handling
- Check cookies and cache behavior
- Validate UI and responsiveness
- Perform security checks
- Validate APIs behind pages
- Test across browsers and devices
- Perform RCA for critical defects
12. FAQs + CTA
FAQ 1: Is web page testing different from UI testing?
Yes. Web page testing includes UI, functionality, security, and performance aspects.
FAQ 2: Do manual testers need API knowledge?
Yes. Understanding APIs helps validate backend behavior triggered by pages.