From a Testers perspective, I have shared about web testing and how could it be tested effectively. We are going to look into the techniques on how to improve the web testing.
What is Web Testing?
Website Testing is nothing but checking and analyzing web application for bugs/errors before it’s made live or before code moves to live environment.
During this process issues such as functioning of the site, UI of the site and web security and User Acceptance testing are done and its ability handle traffic is checked
Testing website points to be considered:
Client/server applications are websites —with web servers and ‘browser; clients
There are a wide variety of browsers and servers with different versions of each, which has significant differences between them, variations in connection speeds, changing technologies. At the end major effort of testing for webAdditionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes unique differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for websites can become a major ongoing effort.
Other considerations might include:
- Expected loads on the server(e.g. number of hits per unit time?), and what kind of performance is required under such loads. and what kind of tools are used for performance testing(Eg. meter etc.)
- Analyzing the target customers? and What kind of browsers thy mostly using? and analyzing their network and connection speed?(intra-organisation with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?
- Analysing client expectation on performance(eg., how fast should pages appear, how should animations, applets, etc. load and run)?
- Analyzing what kind of security will be required and how it can be tested and what are expectations for the clients
- What processes will be required to manage updates to the web site’s content?
- Analyzing the maintaining requirements, controlling page content, graphics, links, etc.?
- Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?
- Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site??
- Analyzing the validations of internal and external links and how to update? and how often?
- Analysing how the testing can be done on the production system or by separate test system can be required? How is the browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet ‘traffic congestion’ problems to be accounted for in testing?
- How extensive or customized are the server logging and reporting requirements; are they considered as an integral part of the system and do they require testing?
- Pages should be 3-5 screens max unless the content is tightly focused on a single topic. If larger, provide internal links within the page.
- The page UI and design elements should be consistent all over the site so that to ensure the user that they’re still within a site
- Pages should be as browser-independent, or pages should be provided or generated based on the browser type.
- Every page should contain links external to the pages, there should be no dead-end pages.
- The page owner, copyright date and person/organization to contact should include on each page
This concludes almost all the major ways to test a website efficiently.
I have shared some of the techniques used to test web application, and it’s not possible to cover each and every point but I have shared major techniques of web testing.