Non Functional Testing of Web Applications
Non Functional or White Box Testing of Web Applications invove either or all of the following seven types of testing
1) Configuration Testing: This type of test includes
2) Usability Testing
3) Performance Testing
4) Scalability Testing
6) Recoverability Testing
7) Reliability Testing
Let us discuss each types of these testings in detail
1) Configuration Testing: This type of test includes
a) The operating system platforms used.
b) The type of network connection.
c) Internet service provider type.
d) Browser used (including version).
The real work for this type of test is ensuring that the requirements and assumptions are understood by the development team, and that test environments with those choices are put in place to properly test it.
2) Usability Testing:
For usability testing, there are standards and guidelines that have been established throughout the industry. The end-users can blindly accept these sites since the standards are being followed. But the designer shouldn’t completely rely on these standards.
While following these standards and guidelines during the making of the website, he should also consider the learnability, understandability, and operability features so that the user can easily use the website.
3) Performance Testing: Performance testing involves testing a program for timely responses.
The time needed to complete an action is usually benchmarked, or compared, against either the time to perform a similar action in a previous version of the same program or against the time to perform the identical action in a similar program. The time to open a new file in one application would be compared against the time to open a new file in previous versions of that same application, as well as the time to open a new file in the competing application. When conducting performance testing, also consider the file size.
In this testing the designer should also consider the loading time of the web page during more transactions. For example: a web page loads in less than eight seconds, or can be as complex as requiring the system to handle 10,000 transactions per minute, while still being able to load a web page within eight seconds.
Another variant of performance testing is load testing. Load testing for a web application can be thought of as multi-user performance testing, where you want to test for performance slow-downs that occur as additional users use the application. The key difference in conducting performance testing of a web application versus a desktop application is that the web application has many physical points where slow-downs can occur. The bottlenecks may be at the web server, the application server, or at the database server, and pinpointing their root causes can be extremely difficult.
We can create performance test cases by following steps:
a) Identify the software processes that directly influence the overall performance of the system.
b) For each of the identified processes, identify only the essential input parameters that influence system performance.
c) Create usage scenarios by determining realistic values for the parameters based on past use. Include both average and heavy workload scenarios. Determine the window of observation at this time.
d) If there is no historical data to base the parameter values on, use estimates based on requirements, an earlier version, or similar systems.
e) If there is a parameter where the estimated values form a range, select values that are likely to reveal useful information about the performance of the system. Each value should be made into a separate test case.
Performance testing can be done through the “window” of the browser, or directly on the server. If done on the server, some of the performance time that the browser takes is not accounted for.
4) Scalability Testing:
The term “scalability” can be defined as a web application’s ability to sustain its required number of simultaneous users and/or transactions, while maintaining adequate response times to its end users.
When testing scalability, configuration of the server under test is critical. All logging levels, server timeouts, etc. need to be configured. In an ideal situation, all of the configuration files should be simply copied from test environment to the production environment, with only minor changes to the global variables.
In order to test scalability, the web traffic loads must be determined to know what the threshold requirement for scalability should be. To do this, use existing traffic levels if there is an existing website, or choose a representative algorithm (exponential, constant, Poisson) to simulate how the user “load” enters the system.
5) Security Testing:
Probably the most critical criterion for a web application is that of security. The need to regulate access to information, to verify user identities, and to encrypt confidential information is of paramount importance. Credit card information, medical information, financial information, and corporate information must all be protected from persons ranging from the casual visitor to the determined cracker. There are many layers of security, from password-based security to digital certificates, each of which has its pros and cons.
We can create security test cases by following steps:
a) The web server should be setup so that unauthorized users cannot browse directories and the log files in which all data from the website stores.
b) Early in the project, encourage developers to use the POST command wherever possible because the POST command is used for large data.
c) When testing, check URLs to ensure that there are no “information leaks” due to sensitive information being placed in the URL while using a GET command.
d) A cookie is a text file that is placed on a website visitor’s system that identifies the user’s “identity.” The cookie is retrieved when the user revisits the site at a later time. Cookies can be controlled by the user, regarding whether they want to allow them or not. If the user does not accept cookies, will the site still work?
e) Is sensitive information stored in the cookie? If multiple people use a workstation, the second person may be able to read the sensitive information saved from the first person’s visit. Information in a cookie should be encoded or encrypted.
6) Recoverability Testing:
Website should have backup or redundant server to which the traffic is rerouted when the primary server fails. And the rerouting mechanism for the data must be tested. If a user finds your service unavailable for an excessive period of time, the userwill switch over or browse the competitor’s website. If the site can’t recover quickly then inform the user when the site will be available and functional.
7) Reliability Testing:
Reliability testing is done to evaluate the product’s ability to perform its required functions and give response under stated conditions for a specified period of time.
For example: A web application is trusted by users who use an online banking web application (service) to complete all of their banking transactions. One would hope that the results are consistent and up to date and according to the user’s requirements.
Many More Articles & Tutorials on Website Testing
Hey thanks a lot for sharing this. I must say it is quite useful. I came across non-functional testing by Maveric Systems and it has some really very interesting stuff. It’s worth having a look.