Web Testing in simple terms is checking your web application for potential bugs before it’s made life or before code is moved into the production environment.
During this stage issues such as that of web application security, the functioning of the site, its access to handicapped as well as regular users, and its ability to handle traffic are checked.
Web Application Testing Checklist:
1. Functionality Testing :
- Outgoing links
- Internal links
- Anchor Links
- MailTo Links
- Scripting checks on the form are working as expected. For example- if a user does not fill a mandatory field in a form an error message is shown.
- Check default values are being populated
- Once submitted, the data in the forms are submitted to a live database or is linked to a working email address
- Forms are optimally formatted for better readability
- Testing cookies (sessions) are deleted either when the cache is cleared or when they reach their expiry.
- Delete cookies (sessions) and test that login credentials are asked for when you next visit the site.
- Checking for Syntax Errors
- Readable Color Schemas
- Standard Compliance. Ensure standards such as W3C, OASIS, IETF, ISO, ECMA, or WS-I are followed.
- Testing your end-to-end workflow/ business scenarios takes the user through a series of webpage’s to complete.
- Test negative scenarios as well, such that when a user executes an unexpected step, an appropriate error message or help is shown in your web application.
2. Usability testing:
- Menus, buttons, or links to different pages on your site should be easily visible and consistent on all webpages
- Content should be legible with no spelling or grammatical errors.
- Images if present should contain an “alt” text
- Application: Test requests are sent correctly to the Database and output at the client side is displayed correctly. Errors if any must be caught by the application and must be only shown to the administrator and not the end-user.
- Web Server: Test Web server is handling all application requests without any service denial.
- Database Server: Make sure queries sent to the database give expected results.
- Test if any errors are shown while executing queries.
- Data Integrity is maintained while creating, updating, or deleting data in the database.
- Check response time of queries and fine-tune them if necessary.
- Test data retrieved from your database is shown accurately in your web application.
5. Compatibility testing.
- Website application response times at different connection speeds
- Load test your web application to determine its behavior under normal and peak loads
- Stress-test your website to determine its breakpoint when pushed to beyond normal loads at peak time.
- Test if a crash occurs due to peak load, how does the site recover from such an event
- Make sure optimization techniques like gzip compression, browser, and server-side cache enabled to reduce load times
7. Security testing:
- Test unauthorized access to secure pages should not be permitted
- Restricted files should not be downloadable without appropriate access
- Check sessions are automatically killed after prolonged user inactivity
- On the use of SSL certificates, a website should redirect to encrypted SSL pages.