| Revision as of 20:07, 6 June 2021 editJede123 (talk | contribs)2 edits →Web application performance toolTag: Reverted← Previous edit | Revision as of 20:34, 6 June 2021 edit undoJede123 (talk | contribs)2 editsNo edit summaryTag: RevertedNext edit → | ||
| Line 5: | Line 5: | ||
| }} | }} | ||
| Web testing is the name given to software testing that focuses on web applications. Complete testing of a web-based system before going live can help address issues before the system is revealed to the public. Issues may include the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, its ability to adapt to the multitude of desktops, devices, and operating systems, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing. | |||
| E-commerce had many expensive failures in the past, some of which could have been avoided by better testing before the site was opened to the general public. Other factors that need to be improved regarding web applications are security, reliability and recoverability. People expect that websites are secure, and available all the time. Designers should be careful about this, as the consequences of badly operating websites are severe, and even affect the brick and mortar stores that the websites are enabling online. Moreover it’s important that the website is working on computers and mobile phones at the same time. | |||
| <ref>Kundu, S. (March, 2012). School of Computer Applications. Web Testing: Tool, Challenges and Methods</ref> | |||
| The applications usually undergo all the typical test: | |||
| * Functional Testing | |||
| * Usability Testing | |||
| * Security Testing | |||
| * Performance Testing | |||
| * Database Testing | |||
| * Mobile Application Testing | |||
| * A/B testing. | |||
| <ref>Software testing help (April 30, 2021) 8 Important Segments Of Testing ECommerce Websites. Retrieved on 5.6.2021 from URL: https://www.softwaretestinghelp.com/ecommerce-testing/ | |||
| </ref> | |||
| == Web application performance tool == | == Web application performance tool == | ||
| Line 59: | Line 73: | ||
| }}</ref> | }}</ref> | ||
| There is a web application security testing plug-in collection for FireFox<ref>{{cite web|title=Web Application Security Penetration Testing :: Collections :: Add-ons for Firefox|url=https://addons.mozilla.org/en-US/firefox/collection/webappsec|website=addons.mozilla.org}}</ref> | There is a web application security testing plug-in collection for FireFox<ref>{{cite web|title=Web Application Security Penetration Testing :: Collections :: Add-ons for Firefox|url=https://addons.mozilla.org/en-US/firefox/collection/webappsec|website=addons.mozilla.org}}</ref> | ||
| Webpages and web applications are becoming more and more versatile and offer plenty of functionalities that were previously only limited to desktop applications. As many users shift their usage to the web, so does the data related to those activities such as private content, shopping, money operations such as banking and transfers pretty much everything has shifted on the web. That brings security concerns because of all the data accumulated on those web pages that might be prone to attacks from cybercriminals. | |||
| Testing for security issues within web applications is a sub-type of software testing and is necessary to pinpoint various weaknesses within the website that cybercriminals could use for cyberattacks. The testers have to test the website or web application on different elements of security such as integrity, confidentiality, vulnerability, continuity, and authenticity. The testing on different layers as infrastructure, access points ( tablet, mobile, computer ), and network identify the potential risks the website faces. When those risks are detected security experts and developers can fix those vulnerabilities to make the website or web application safer for the users. | |||
| <ref>How to Implement Security Testing for Web Applications. (n.d.) Preformance Lab. Retrived from https://performancelabus.com/web-security-testing-implementation/ | |||
| </ref> | |||
| == See also == | == See also == | ||
Revision as of 20:34, 6 June 2021
 | Certain historical revisions of this page may meet criterion RD1 for revision deletion, as they contain significant copyright violations of https://drpete.co/?topic=25-point-website-usability-checklist that have been removed in the meantime.
Note to admins: In case of doubt, remove this template and post a message asking for review at WT:CP. With this script, go to the history with auto-selected revisions. Note to the requestor: Make sure the page has already been reverted to a non-infringing revision or that infringing text has been removed or replaced before submitting this request. This template is reserved for obvious cases only, for other cases refer to Misplaced Pages:Copyright problems. Note to others: Please do not remove this template until an administrator has reviewed it. |
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
Web testing is the name given to software testing that focuses on web applications. Complete testing of a web-based system before going live can help address issues before the system is revealed to the public. Issues may include the security of the web application, the basic functionality of the site, its accessibility to handicapped users and fully able users, its ability to adapt to the multitude of desktops, devices, and operating systems, as well as readiness for expected traffic and number of users and the ability to survive a massive spike in user traffic, both of which are related to load testing.
E-commerce had many expensive failures in the past, some of which could have been avoided by better testing before the site was opened to the general public. Other factors that need to be improved regarding web applications are security, reliability and recoverability. People expect that websites are secure, and available all the time. Designers should be careful about this, as the consequences of badly operating websites are severe, and even affect the brick and mortar stores that the websites are enabling online. Moreover it’s important that the website is working on computers and mobile phones at the same time.
The applications usually undergo all the typical test:
- Functional Testing
- Usability Testing
- Security Testing
- Performance Testing
- Database Testing
- Mobile Application Testing
- A/B testing.
Web application performance tool
A web application performance tool (WAPT) is used to test web applications and web related interfaces. These tools are used for performance, load and stress testing of web applications, web sites, web API, web servers and other web interfaces. WAPT tends to simulate virtual users which will repeat either recorded URLs or specified URL and allows the users to specify number of times or iterations that the virtual users will have to repeat the recorded URLs. By doing so, the tool is useful to check for bottleneck and performance leakage in the website or web application being tested.
A WAPT faces various challenges during testing and should be able to conduct tests for:
- Browser compatibility
- Operating System compatibility
- Windows application compatibility where required
- Insufficient Hardware resources
- Bottlenecking
- Poor Scalability
Web Performance Testing metrics:
- Response time
- Wait time
- Average load time
- Peak response time
- Error Rate
- Concurrent Users
- Requests per second
- Transactions passed/failed
- Throughput
- CPU utilisation
- Memory Utilisation
WAPT allows a user to specify how virtual users are involved in the testing environment.ie either increasing users or constant users or periodic users load. Increasing user load, step by step is called RAMP where virtual users are increased from 0 to hundreds. Constant user load maintains specified user load at all time. Periodic user load tends to increase and decrease the user load from time to time.
Load testing identifies:
1. Maximum operating capacity of an application
2. Whether current infrastructure is sufficient to run the application
3. The sustainability of an application with respect to peak user load
4. Number of concurrent users that an application can support, and scalability to allow more users to access it.
Web security testing
Web security testing tells us whether Web-based applications requirements are met when they are subjected to malicious input data. There is a web application security testing plug-in collection for FireFox
Webpages and web applications are becoming more and more versatile and offer plenty of functionalities that were previously only limited to desktop applications. As many users shift their usage to the web, so does the data related to those activities such as private content, shopping, money operations such as banking and transfers pretty much everything has shifted on the web. That brings security concerns because of all the data accumulated on those web pages that might be prone to attacks from cybercriminals.
Testing for security issues within web applications is a sub-type of software testing and is necessary to pinpoint various weaknesses within the website that cybercriminals could use for cyberattacks. The testers have to test the website or web application on different elements of security such as integrity, confidentiality, vulnerability, continuity, and authenticity. The testing on different layers as infrastructure, access points ( tablet, mobile, computer ), and network identify the potential risks the website faces. When those risks are detected security experts and developers can fix those vulnerabilities to make the website or web application safer for the users.
See also
References
- Kundu, S. (March, 2012). School of Computer Applications. Web Testing: Tool, Challenges and Methods
- Software testing help (April 30, 2021) 8 Important Segments Of Testing ECommerce Websites. Retrieved on 5.6.2021 from URL: https://www.softwaretestinghelp.com/ecommerce-testing/
- https://stackify.com/ultimate-guide-performance-testing-and-software-testing/
- https://stackify.com/ultimate-guide-performance-testing-and-software-testing/
- https://theqalead.com/tools/load-testing-tools/
- Hope, Paco; Walther, Ben (2008), Web Security Testing Cookbook, Sebastopol, CA: O'Reilly Media, Inc., ISBN 978-0-596-51483-9
- "Web Application Security Penetration Testing :: Collections :: Add-ons for Firefox". addons.mozilla.org.
- How to Implement Security Testing for Web Applications. (n.d.) Preformance Lab. Retrived from https://performancelabus.com/web-security-testing-implementation/
Further reading
- Hung Nguyen, Bob Johnson, Michael Hackett: Testing Applications on the Web (2nd Edition): Test Planning for Mobile and Internet-Based Systems ISBN 0-471-20100-6
- James A. Whittaker: How to Break Web Software: Functional and Security Testing of Web Applications and Web Services, Addison-Wesley Professional, February 2, 2006. ISBN 0-321-36944-0
- Lydia Ash: The Web Testing Companion: The Insider's Guide to Efficient and Effective Tests, Wiley, May 2, 2003. ISBN 0-471-43021-8
- S. Sampath, R. Bryce, Gokulanand Viswanath, Vani Kandimalla, A. Gunes Koru. Prioritizing User-Session-Based Test Cases for Web Applications Testing. Proceedings of the International Conference on Software Testing, Verification, and Validation (ICST), Lillehammer, Norway, April 2008.
- "An Empirical Approach to Testing Web Applications Across Diverse Client Platform Configurations" by Cyntrica Eaton and Atif M. Memon. International Journal on Web Engineering and Technology (IJWET), Special Issue on Empirical Studies in Web Engineering, vol. 3, no. 3, 2007, pp. 227–253, Inderscience Publishers.