Home > Subjects > IT/Technology > Step by Step Testing of Web Applications

Step by Step Testing of Web Applications



This paper talks about the testing of web applications on large or small scales. In contrast, different methods & techniques for an application’s testing purpose are discussed along with the previous work in this domain.

Index Terms – Web, Application, Testing, Techniques.


I. ​​ Introduction

Websites are ending up progressively perplexing as an ever-increasing number of information & services are made accessible over the Internet &​​ intranets. In the meantime, the right conduct of websites has turned out to be essential to accomplishing organizations & associations & hence ought to be tested altogether & as often as possible. Albeit software testing is as of now a famously difficult,​​ tedious & costly process, testing applications like Web displays significantly more prominently dynamic: Web interfaces are compelling; the necessary environment of Web applications is involved than that of common monolithic or applications like client-server; Web applications, most strikingly online business sites, have a vast number of clients who have no preparation on the most proficient method to utilize the application & consequently will probably practice it in strange ways [1].

Moreover, existing tools for testing in an automated way toward testing dynamic Web applications require test scenarios, which brings about a restricted test scope. In the present regularly changing & focused web-based business situation, associations dependably need to test their web-based applications right before launching their website. By web application testing, any association can make sure that the web application will work consummately & will be effortlessly acknowledged by the end-clients. The web application testing​​ procedures likewise check the web application's similarity with browsers, load, scalability, resolution & stress testing.

Web Testing checks your web application for bugs & defects previously making it live or before the code is moved into a production environment. During this stage, like the security of the web applications, webpage working & the access of it to each type of user (age, gender, etc.) & the capability of the platform how well it handles the traffic is checked thoroughly. More web applications are being produced nowadays. What's more, with each line of code being composed, the potential for bugs emerges. As a rule, the expenses of settling bugs or defects increment exponentially the later you find.

At IBM, the Institute of system science, it has been found that "the cost to settle a mistake found after item discharge was 4 to 5 times the amount of as one revealed while planning, & up to 100 times over one recognized in the phase of maintenance" [3].

Here, the web application testing comes in; it's not necessary by any means that the web application testing guarantees that an application under test is wholly bug-free & runs safely & efficiently, although there will be loopholes in the system always. At the same time, it's the essential piece of development for the web & ensures that the application is in the completely running phase before its proper launch.

II. ​​ Web Applications Testing a Costly Procedure

The more composite a situation is, the more prominent the exertion required to exhibit the unwavering quality working in that condition. Also, in the days of old mainframe environments, testing was reliably troublesome & time consuming. Considering that the working system was unsurprising, the teleprocessing monitors & database systems were similarly reliable & that security was not the main problem. Despite everything, it required up to 30% of the project's effort to test new applications. The community for the testing research has continuously demanded that testing is disparaged & that it requires similarly the same effort to try a particular program needed to develop it. This applies to the project where the working condition is thought to be right & not part of the testing issue. It ends up being a fair representation of the truth when just like the case with the web when the testing problem is basically because of the environment [2].

III. ​​ Web Architecture Testing:

The project's design is under test can be referred to as DotNet, Php with a framework or whatever testing may be the same for​​ each of them. At the same time, XSL templates are utilized to portray the web pages to test a web application architecture. These are then changed over using XSLT to XML reports, sent to the application server for preparing the SQL Server database. One could state that this framework holds a complex structure with numerous components & much more interrelationships between them, so very obviously, their testing is also challenging work to do. Moreover, if we look through their architecture in a web application, there are client, server & database access components to test [2].

IV. Web XML Outputs Validations

This exhibited an issue to the testers of the website. Since new versions of the product were being discharged each month, there must be an approach to rehash past tests with at least exertion. The arrangement picked was to record the discourse tests with a tool capture replay that is named as Empirix & to play them back. Notwithstanding that, another technique was used to verify the data. The XML records​​ delivered by the server to be changed over to XSL-Stylesheets & afterward shown to the client were blocked after clearing out the server & put away in a consecutive record. After that, the XML document produced by the current versions' test is contrasted with that created by the last versions, as shown in figure 1.

Figure 1: XML output file comparison [2].

V. Web Database (SQL) Validation:

A similar device used to approve the output of XML is likewise used to support the SQL databases' status after the​​ testing. There are typical SQL collection reasons for this case, which distinguish identical viewpoints from both the past and the current database tables. These such views are then put away as by comma isolated value records. Note that this preselection is done to not think about the entire content of the database tables; however, those characteristics are considered pivotal [2]. The old CSV document is contrasted & the new CSV record is utilizing the statements. Tuples of the database can be absent in the​​ old database, missing in the original database or not coordinating that can be fixed after the testing.

VI. Step by Step Testing of Web Application:

In this paper, I propose a step by step procedure to let the testers get an overview to test a web application what type of tests are to be run [3].

Step 1: Functional Testing

The initial phase in web testing guarantees that the elements of a system are tested. Functional testing occurs in the source code, where the system is tested against useful prerequisites & details.​​ 

Ordinarily, Functional testing incorporates:​​ 

  • The distinguishing proof of capacities that product should do​​ 

  • Input Data.​​ 

  • The execution of the test case​​ 

  • An investigation of the real outcomes​​ 

Amid useful testing, the actual​​ utilization of the system is recreated. The idea is to move as near as possible to the actual method use & make test conditions identified with client necessities [3].

Step 2: Usability Testing

Usability goes past functionality testing & joins testing for​​ usefulness &, besides, generally speaking for client encounter. Of Consumer Acceptance Research[3], usability testing should not be heated up.

Usability testing includes the accompanying advances:​​ 

  • A testing technique is developed that guarantees each element of the application that will be analyzed. This also incorporates content.

  • Recruit individuals for testing, either inside or remotely.​​ 

  • Tests should be run under experienced professionals​​ 

  • Analyze outcomes & enhance application under​​ test appropriately.

web app testing

Figure 2: Usability testing procedure [3].

Step 3: Interface Testing

Interface testing guarantees that all communications between the web server & application server interfaces are running efficiently. This incorporates checking the correspondence versions & also ensuring that any message about errors is shown effectively. Promote things to test are that the client's interferences & even by the server are taken care of accurately [3].

Step 4: Performance Testing

In the wake of guaranteeing that your application's functionality is working legitimately & responsively on all programs & devices, the time has come to investigate how it performs under substantial load. This incorporates testing the application under various internet speeds &​​ how it carries on under typical & pinnacle loads (This is known as load-testing). To decide the limit of your application, it is put under expanding stress-testing measures until the point that it stops to work (This is known as stress-testing) [3].

Step​​ 5: Security Testing

The last step for web application testing guidance ensures that your application is secured against unapproved & unsafe activities through infections or different vindictive software [3].

Security testing for web applications includes​​ the accompanying exercises:​​ 

  • Test whether secure pages can be access to without approval​​ 

  • Check that open session is close down in the wake of continuous client idleness​​ 

  • Verify application's SSL​​ 

  • Make beyond any doubt that restricted documents can't be downloaded without legitimate approval.

VII. Related Work:

From the literature, though considerable effort was made to analyse models of testing in web applications, formalisms went to help the plan of web applications, only a few works thought about the​​ issues identified with web website development, testing & maintenance. The paper's commitment by Ricca & Tonella [2] to the available research on the Web is based on the UML model that can be utilized in the investigation & testing of the system under examination & testing systems, which is viably connected to Web applications.

Whereas the model suggested by Ricca & Tonella[2] is somewhat close to that suggested by Conallen[4], the same model was offerd and later updated by Conallen[4] Ricca & Tonella [2] with the innovation of technology.

VIII. Conclusion:

Some of the testing methods proposed here were effectively connected with Web applications running around the world because whether the site in developing is on a large scale or small, these basic techniques are always used,​​ 

The presented testing methods & techniques were incredibly valuable in the appraisal of the quality of the website. They permitted a profound understanding of the inner working of Web applications, featuring qualities & shortcomings.​​ Moreover, future work will be given to decrease the manual exercises required (e.g., for state unrolling & merging).

IX. References
  • [1] Sneed, H. (n.d.). Testing a Web application. Web Site Evolution, Sixth IEEE International Workshop on (WSE04). DOI:10.1109/wse.2004.10011

  • [2] Ricca, F., & Tonella, P. (n.d.). Analysis & testing of Web applications. Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001. doi:10.1109/icse.2001.919078

  • [3] Vogels, R. (2018, May 07). A 6-Step​​ Guide to Web Application Testing - Usersnap. Retrieved August 3, 2018, from https://usersnap.com/blog/web-application-testing/

  • [4] J. Conallen. Building Web Applications with UML.Addison-Wesley Publishing Company, Reading, MA, 2000.


Related Posts

Leave a Comment