0% found this document useful (0 votes)
19 views2 pages

Web Application Testing Report

Uploaded by

cavdxbdbtb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views2 pages

Web Application Testing Report

Uploaded by

cavdxbdbtb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Web Application Testing Report

This report documents the results of testing performed on three web application pages hosted at
[Link]. Testing includes Usability, Functional, Compatibility, and Security evaluations.
The findings are based on the given assignment details and actual observations from the testing
process.

Category Observations / Findings


Usability Testing • Page layout and content are visible but some image assets are missing (logo, favicon).
• Login page is clean and centered; however, placeholder text could be more descriptive.
• Known issue: Login button not working (Test1).
• All pages should be checked for mobile/tablet responsiveness.
Functional Testing • Test1: Login button does not work (known defect).
• Test2: Form fields and next button present, but no dynamic functionality as expected.
• Test3: Signup/Registration/Login buttons present; need to ensure click actions navigate corr
• 404 errors for image/logo assets observed in DevTools:
- [Link]
- [Link]
- [Link]
• Console Error: 'Promised response from onMessage listener went out of scope'.
Compatibility Testing • Pages load on desktop Chrome without crash.
• Recommend testing on:
- Chrome, Firefox, Edge (latest versions)
- iOS Safari, Android Chrome
• Test responsive layouts for all device sizes (desktop, tablet, mobile).
Security Testing • Password field hides user input as expected.
• No HTTPS security warnings found; site uses HTTPS.
• Since this is a static HTML template, no server-side validation is tested.
• Recommend implementing CSRF protection, secure session handling, and input sanitization

Evidence from DevTools

Below is an example screenshot showing missing assets (404 errors) and console error.

You might also like