5 TH
5 TH
Check if all the interactions between these servers are executed and errors are
handled properly. If the database or web server returns an error message for any
query by application server then the application server should catch and display
these error messages appropriately to the users.
Check what happens if the user interrupts any transaction in-between? Check
what happens if the connection to the webserver is reset in between?
Compatibility Testing
Browser compatibility
Operating system compatibility
Mobile browsing
Printing options
Browser Compatibility
Performance Testing
The web application should sustain to heavy load. Web performance testing include:
need to test if many users are accessing or requesting the same page. Can the system
sustain in peak load times? The site should handle many simultaneous user requests, large
input data from users, simultaneous connection to DB, heavy load on specific pages, etc.
Generally stress means stretching the system beyond its specified limits. Web stress
testing is performed to break the site by giving stress and it’s checked as to how the
system reacts to stress and how it recovers from crashes. Stress is generally given on
input fields, login and sign up areas.
Security Testing
Following are some of the test cases for web security testing:
Test by pasting the internal URL directly into the browser address bar without
login. Internal pages should not open.
If we are logged in using username and password and browsing internal pages
then try changing URL options directly. I.e. If we are checking some publisher
site statistics with publisher site ID= 123. Try directly changing the URL site ID
parameter to different site ID which is not related to the logged-in user. Access
should be denied for this user to view other’s stats.
Try some invalid inputs in input fields like login username, password, input text
boxes, etc. Check the system’s reaction to all invalid inputs.
Web directories or files should not be accessible directly unless they are given
download option.
Test if SSL is used for security measures. If it is used, the proper message should
get displayed when users switch from non-secure HTTP:// pages to secure
HTTPS:// pages and vice versa.
All transactions, error messages, security breach attempts should get logged in log
files somewhere on the webserver.
5.1 Snapshots
CHAPTER 6
Conclusion and Future Scope
6.1 Conclusion
In conclusion, developing a Voice Assistant application in JavaScript offers a robust
framework for efficient web-based communication. Leveraging JavaScript’s versatile
features streamlines development, ensuring scalability and seamless integration with
databases, APIs, and other JavaScript-powered functionalities, enhancing user experience.