testing

Testing framework in ruby

I would like to present another case study of the work that I've done for testing on ruby for an MNC client of mine. I won't be disclosing the project details, you all can understand why, but I'll try to explain the different challenges that i along with the team working on the project faced & how we overcome it. So lets start.

One of my client (security product based company) has their product on linux platform. The frontend is web app & can be accessed by using browser & entire system can be configured, monitored & managed using it. Now this was a very big task to automate the testing of the product, as they have 3 product lines & every product has their own settings etc.

Testing AJAX web applications is very difficult. Ajax relies mainly on requests to the server ( and responses received from them). We can't test what is sent and received from the server. The way to solve these problems is to use HTTP Proxy.

A HTTP proxy is a small program which intercepts between the client requests and responses to and from the server. The browser sends a request and the HTTP proxy receives the request. It then sends the request to the server and when it is processed, the response is sent back to the HTTP proxy. It is then sent to the browser. In addition to the interception job, it also records the information transfer. Fiddler is one such HTTP proxy tool which is used for testing and debugging Ajax applications.

WBox is a simple HTTP Testing Tool written in ANSI C which works on a POSIX system like Linux. Windows systems are not supported and compiles on a MacOS X system. It is a 20 Kb zip file which has code written in ANSI C. We can use it to perform many different tasks which include

Benchmarking how much time it takes to generate content for your web application.
Web server and web application stressing.