Analysis of web application testing methods

Abstract

An important practical task for developers is the rapid creation and maintenance of high-quality multi-level software. It is assumed that the developed product will meet the qual-ity characteristics. And, if we talk about testing applications of different types, then you should pay attention to their features. For example, web applications have critical areas that must be checked. Thus, the purpose of this article is to analyse various methods and technics for testing web applications. The article provides a detailed analysis of the latest publications related to testing web applications. It turned out that most of the articles are aimed at describing terms or general information about testing. Several articles describe automated testing with Selenium, IBM Rational, SilkPerformer, TestComplete, HP QuickTest Professional, JUnit and compare them in terms of efficiency in various applications. However, most of the articles are devoted to various aspects of manual testing. In order to identify the factors that distinguish web application testing from desktop ap-plication testing, a table has been compiled comparing them according to the following crite-ria: environment, platform, deployment and updating, architecture, connectivity, availability. This comparison shows that web applications have several features that need to be consid-ered when testing them. In our opinion, the main critical areas of web applications that require additional de-scription and instructions are unity of design, navigation and "friendliness" to the user, func-tionality, security, compatibility with browsers and operating systems, and productivity. The article describes the specifics of testing critical zones and gives an estimate of the resource consumption of their testing. Tests are also recommended, which are useful for testing web and desktop applications.