Success Story: Passenger, Inc

Company Profile

Passenger is an interactive online application that enables brands to connect with customers in an engaging, personalized environment to build knowledge and advocacy.

Passenger communities deliver

  • Real-time insights on how the customer’s brand is perceived
  • Customer-driven innovation to inform marketing, product and operations
  • A personal connection with customers that builds scalable brand advocacy.

Challenges

As we are preparing to launch the next generation of software, we want to test the load handling abilities of our software and see where the bottlenecks are.

Testing the upload/download capacity of files, posts in complex web forms and monitoring the database, servers and getting reliable response time were not quite possible with the other tool we were using.

We were using jmeter for back end testing and for the previous version of the software we were using the open source version of webload.

The application is a web based client with flex UI, which provides interactive features such as live chat, discussion forums, ability to upload and view pictures, audio ,video, documents etc.

In a typical community, many users are logged into the application and doing one or many of these actions.

Protocols tested:

  • http
  • Flex

Solution

The ease with which the flex UI could be automated for performance testing, the good monitoring tools provided and the cost were the important factors playing in favour of NeoLoad.

The other tools that were considered are:

  • webload
  • jmeter
  • loadrunner
  • silk performance

By constantly tuning our application based on the response time numbers provided by NeoLoad, we were able to improve the performance of the modules. We were also able to add more monitoring tools, once we identified hardware resources became the bottleneck.

Test Results and Added Value

By using NeoLoad, we have been able to significantly improve the software quality and reduce the risk of introducing any major changes to the API’s.

Currently we have been using NeoLoad to primarily test the behaviour of a certain module for a certain amount of time. While we will continue to use this type of testing, we’ll also be using NeoLoad for running some longevity tests.