The rapid development of Internet technology, commerce, and the whole network dictates its market professionals who are able to provide the process with all necessary for the proper level. These also include the so-called web designers and web masters, in whose hands – the card in Intrenet any self-respecting company – Web (page, site, server). And if the first (web designer) is developing the site, the second – his support. There is one possible and discreet, but is gaining his strength specialty – web tester. As a kind of beta tester, this specialist is designed to ensure the highest quality of web pages, and therefore the maximum number of visitors on them.
The purpose of this article – to answer questions that concern anyone who found it necessary to test the Web. Similarly, we can conduct testing of applications developed HTML HELP.
Web tester tester we call not only Web-pages, websites, servers, and who by virtue of their profession faces a test-intensive applications Web-based interface. Due to various circumstances in the role of Web-tester can be not only taken separately specialist, and anyone else who creates and maintains resources and / or applications that are somehow “tied” to the Web.
We will not dwell on what is necessary for successful testing. Web tester can (and should) use all the software that is used by any tester. This bug collectors and managers of TestCase, and tools for automated testing. An important feature of Web testing is its timing. If you test software tester for a few months (sometimes years), then the web tester is only days or weeks (at best) on the proposed testing site. Therefore, if the testing program can and should be detailed test plans, describe the Test Cases based on information received from the developer documentation, testing Web-pages that can significantly move the date of publication on the Internet.
It is important that anyone who decided to test the Web had before the Internet connection (ideally – a variety of its forms: from dial-up to ISDN), various operating systems and different versions of the most popular browsers.
So in order to conduct testing web to pay attention to the following general points:
The following are only general provisions:
Let us examine each of the points of detail.
Under the unity of design, we understand not only, or rather not so much the color compatibility of the elements (as is the destiny of the designer), but compliance with the selected color, which imparts to all pages in the site “unity.” This includes the background color (or picture), references (including attendance and active), and any other items located on the page. In addition, at this stage we propose to evaluate the size and type of font used for different levels of attachment of the text (titles of various levels, the actual text, links, notes, etc.) It also makes sense to assess the compatibility with the design of sound, graphics and animation and check whether there is a unity mapping when using other display enhancements and color depths.
Navigation involves testing site navigation, which gives an idea of ??the possibility of any user can easily find the desired section, regardless of the ways to implement the menu (text links, images, single image with a map link, etc.). At the same stage the logical move between forms, buttons and other page elements using the TAB, arrow keys, etc.
Common approaches to testing the functionality of Web pages are similar to those for testing applications. Below is a sample list of the basic functionality of Web pages:
It is well known that due to competition or that the browser is often even significant differences in displaying the same page. In order to make sure that any user can obtain all the necessary information required for the testing of Web-pages in different browsers. In addition there are differences between different versions of the same browser. It must also be considered for testing.
Different operating systems can also affect the display of certain pages. This dictates the need to conduct testing on different operating systems, as well as in their various versions and upgrades.
Under the “friendly” we mean, how simple, easy to use and intuitive interface of the site: Is it easy to navigate, the menu is available, not whether to use annoying tricks, not how many pop-ups, if all links are “working”, all whether the necessary data available to the user, etc. For example, if the site has a file for download, it is desirable that the user can know in advance of its size, could appreciate the download time.
Check the “efficiency” implies the assessment of download speeds as pages in the whole and each element separately. This includes the estimate of the size used in drawings, html-files, audio and video files, adapting them to different types of connections (from conventional modem dial-up connections, ranging from 14400, to high-speed technology).
This article is a review and reflects only the most general terms and approaches to Web-based testing. No doubt, depending on the goals, objectives and directions of the site to test it may depart from the standards and regulations. One thing is certain – Web-site testing is very important, regardless of whether the site is commercial or is it just your own personal Web page.