Author: Ivan Lisitsyn

Stress testing a web site with 100,000+ virtual users
Testing practice WAPT usage

Stress testing a web site with 100,000+ virtual users

It is not a typical load testing project when you need to create 100 thousand virtual users. More than half of all web load tests are conducted with just a thousand virtual users or less, because higher load is not actually anticipated on the target web site in production.

Note that we are not talking about the number of users per day or hour. Those are concurrent users working with the web site simultaneously, in parallel.

At the same time a huge load mentioned in the title of this article is not a fantasy.

Such tests are really required for web sites with growing audience and advanced client functionality. Imagine any web site that delivers customizable user-dependent content updating dynamically: stock quotes, online meetings and chats, monitoring tools, etc. […]

WAPT Pro 2.5 is finally released!
WAPT usage

WAPT Pro 2.5 is finally released!

We have been working on this release for quite a while and now I am happy to announce the release of WAPT Pro 2.5. The product is available for download here. As usual, all registered users of WAPT Pro can upgrade free of charge.

We will also update the regular version of WAPT soon. It will include same features except the last two in the list below: we provide them only for the experts who use the Pro version. So, here is the list of new features.

Recording tests with Firefox, Chrome, or any other external browser

WAPT is now integrated with the most popular browsers: Internet Explorer, Firefox and Chrome. You can use any of them to record user sessions for your test. You can also use any other external browser running on the same or different system as well as on a mobile device. […]

Creating a load test report
Testing practice

Creating a load test report

One of the most common questions in load testing is how to create a good test report that you would be able to present to your manager or customer. This big question actually consists of many smaller ones. What to start with? How to create the right test? What load parameters should be applied? How to interpret the results? Which numbers to look at when you browse through a long report generated by a load testing tool?

I will hardly answer all these questions and present the complete methodology in one article. This would be a long story and… it would be too boring. I know that there is a 90% chance that you really need something more simple and ready to use right away. I will simply present an example of the load testing report. A typical one, if you want.

Ten names for load testing
General

Ten names for load testing

Load testing is a wide and established area of IT knowledge and software development practices. There are many professionals who specialize here and testing gurus ready to provide useful advices and even teach you a theory on the subject. Surprisingly, the mentioned gurus often do not agree with each other on the very basic terms used in this field.

If you search for information on load testing, most probably you will also find articles mentioning such terms as “performance testing” and “stress testing”.

Are they all just synonyms? Everybody agrees that they are not, but still different sources provide different definitions for these terms.

The most confusing point is the difference between performance and load testing. Some people reasonably say that […]

HTTP Redirects
Testing practice

HTTP Redirects

Each HTTP response produced by a web site contains status code. Browser uses that code to interpret the meaning of the response. Basically there can be three different cases:

The request has been processed successfully by the server and the response body contains the requested resource (web page, image, etc.).

An error has occurred.

Server redirects the request to a new URL.

In the latter case the response contains a special “Location” header in which the new URL is provided. When browser receives such response, it automatically issues a new request using the specified URL. This way it can be redirected even to a different web site. The whole thing is done automatically, so the user does not see the process in the browser window. […]