Tsung is an robust load-testing tool that makes it easy to record sessions and then play them back, with dynamic data and a massively scalable client base. The goal of tsung-rails is to provide some automation for common tasks, especially related to rails testing.
This is an experimental library, meant for testing. It should never be added as a production dependency (you can still test production servers from a development environment if you really want to do that).
This was developed on OSX Lion, using homebrew 0.8.1, erlang R14B04, tsung 1.4.1, rails 3, and ruby 1.9.2. Since it hasn't been ported to other environments yet, it will likely fail in these. Please consider contributing and then removing this message.
- Add
gem 'tsung-rails'to yourGemfile - Run
rails g tsung:install[TODO: not implemented yet!] - Run
rake tsung:checkto ensure tsung is installed and the gem can see it
By default, tsung creates an http proxy on localhost:8090. I like to have a firefox profile specifically for recording via this proxy that I leave with these default settings.
- Start recording (and give the recording a useful name)
% rake tsung:record RECORDING=login- Play back the last recording
% rake tsung:play- List recordings
% rake tsung:recordings:list- Play back a specific recording
% rake tsung:play RECORDING=loginYou know the game: fork, hack, pull request.
- tsung-rails's understanding of object creation is currently very basic, and does not support nested resources, PUTs, or subsequent GETs to the same resource.
- when POST data is sent as form/multipart, tsung records the data into a separate file, which currently isn't being picked up by tsung-rails
- refactor to leverage rails configuration params (but also work standalone)
- refactor to move all platform-specific logic to platform.rb
- use knowledge of config/routes.rb in rails to allow for better dynamic handling of object (and nested-object) creation / redirects / links / etc.
- automate both recording and playback via rspec and/or cucumber tests
Released under the MIT License. See the LICENSE file for further details.