After identifying a bug, the tester should submit it to the developer report with options for fixing the bug with QA testing games. Almost all modern programs are network-oriented. Data storage of web applications is carried out mainly on the server. The exchange of information occurs over the network. When we see an error in a network environment, it is often difficult to pinpoint exactly where it happened. And therefore the mode of operation, or the error message we receive. It may be the result of errors that happened in different parts of the network system.
Having much in common with testing classic applications, testing web-oriented applications has its own characteristics. It’s primarily related to the operating environment. Having component, structural and technological features, web applications are characterized by the features of operation modes, installation, start, stop and delete. As well as the formation of interfaces. Working always with a network and with a large number of users, web applications mean different access rights for different users.
The logic of the web application is distributed between the server and the client. Data is stored on the server. And information is exchanged over the network. The clients do not depend on the specific operating system. And, this aspect should be at the center of attention. So web applications are cross-platform services.
Features of testing web applications:
Classic application work on related technologies.
The web application works using fundamentally different technologies.
The classic application is “monolithic”. Consists of one or a small number of modules. Doesn’t use database servers, web servers, etc. The web application is “multicomponent”. Consists of a large number of modules. Be sure to use database servers, web servers, application servers. The classic application works in real-time. I.e. is aware of the user’s actions as soon as they are completed. The web application operates in a request-response Mode. It is known about a certain set of actions only after a request to the server.
Features of testing web applications, operating mode
Differences in the formation of the interface.
The classic application uses relatively well-established and standardized technologies to form the user interface. The web application uses rapidly evolving technologies to form the user interface. Many of them are in competition with each other.
Differences in working with the network:
The classic application practically does not use network data transmission channels.
The web application actively uses network data transmission channels.
Differences between start and stop.
The classic application rarely starts and stops.
The web application starts and stops as soon as each request arrives, i.e. Often.
The difference is in the number of users.
Classic Application: The number of concurrent users of the application is controllable, limited, and easily predictable.
Web application: The number of concurrent users of the application is difficult to predict and can jump across wide ranges.
A minor bug that does not break the logic of the tested part of the game by 3d environment artists, an obvious problem with the user interface.
Features of crashes and failures
A classic application: the failure of certain components becomes immediately obvious.
Web application: the failure of some components has an unpredictable effect on the performance of the application as a whole.
Classic application. The installation process is standard and maximally focused on a wide audience of users. Does not require specific knowledge.
Web Application. The installation process is often not available to the end-user. Installation requires specific knowledge. The process of changing application components is not provided or requires user qualifications. no installer.
Classic application. The uninstallation process is standard and, is performed automatically or semi-automatically.
Web application. The uninstallation process requires specific knowledge for administrator intervention. And, it is often associated with changing the code of the application operating environment, database. And system there are OS settings.
The main goal of any testing, including testing web applications, is to detect all errors in the software. And, develop recommendations for their prevention in the future.