testability-driver-runner 0.9.2

data/rakefile

@@ -0,0 +1,135 @@
+#
+# rakefile for building and releasing tdrunner
+
+@__release_mode = ENV['rel_mode']
+@__release_mode = 'minor' if @__release_mode == nil
+GEM_NAME='testability-driver-runner'
+
+require 'rubygems'
+require 'rake'
+require 'rake/clean'
+require 'rake/gempackagetask'
+require 'rake/rdoctask'
+require 'rake/testtask'
+require 'spec/rake/spectask'
+
+# version information
+def read_version
+	version = "0"
+	File.open(Dir.getwd << '/debian/changelog') do |file|
+
+		line = file.gets
+		arr = line.split(')')
+		arr = arr[0].split('(')
+		arr = arr[1].split('-')
+		version = arr[0]
+	end
+
+	if(@__release_mode == 'release')
+		return version
+        elsif( @__release_mode == 'cruise' )
+                return version + "." + Time.now.strftime("pre%Y%m%d")
+	else
+		return version + "." + Time.now.strftime("%Y%m%d%H%M%S")
+	end
+end
+
+@__revision = read_version
+puts "version " << @__revision
+
+
+@__gem_version = @__revision
+def make_spec
+  gem_version = @__gem_version
+  return Gem::Specification.new do |s|
+    s.name = GEM_NAME
+    s.version = "#{gem_version}"
+    s.has_rdoc = true
+    s.extra_rdoc_files = ['readme']
+    s.summary = 'Testability Driver test runner'
+    s.description = s.summary
+    s.author = "Testability Driver team"
+    s.email = "no@mail.com"
+    s.executables = ["tdrunner","sierra"]
+    s.files = %w(readme rakefile) + Dir.glob("{bin,lib,spec,websi}/**/*")
+    s.require_path = "lib"
+    s.bindir = "bin"
+    s.add_dependency("testability-driver")
+    s.add_dependency("rails", "=2.3.5")
+    s.add_dependency("zippy")
+    s.add_dependency("sqlite3-ruby", "1.2.5")
+    
+  end
+end
+
+Rake::GemPackageTask.new(make_spec) do |p|
+  p.gem_spec = make_spec
+  p.need_tar = true
+  p.need_zip = true
+end
+
+Rake::RDocTask.new do |rdoc|
+  files =['readme', 'lib/**/*.rb']
+  rdoc.rdoc_files.add(files)
+  rdoc.main = "README" # page to start on
+  rdoc.title = "tdrunner Docs"
+  rdoc.rdoc_dir = 'doc/rdoc' # rdoc output folder
+  rdoc.options << '--line-numbers'
+end
+
+Rake::TestTask.new do |t|
+  t.test_files = FileList['test/**/*.rb']
+end
+
+Spec::Rake::SpecTask.new do |t|
+  t.spec_files = FileList['spec/**/*.rb']
+end
+
+
+desc "Task for installing the generated gem"
+task :gem_install do
+  
+  puts "#########################################################"
+  puts "### Installing GEM  #{GEM_NAME}       ###"
+  puts "#########################################################"
+  tdrunner_gem = "tdrunner-#{@__gem_version}.gem"
+  if /win/ =~ RUBY_PLATFORM
+    cmd = "gem install pkg\\*.gem --LOCAL"
+  else
+    cmd = "gem install pkg/*.gem --LOCAL"
+  end
+  failure = system(cmd)
+  raise "installing  #{GEM_NAME} failed" if (failure != true) or ($? != 0)
+  
+end
+
+
+desc "Task for uninstalling the generated gem"
+task :gem_uninstall do
+  
+  puts "#########################################################"
+  puts "### Uninstalling GEM #{GEM_NAME}     ###"
+  puts "#########################################################"
+  tdrunner_gem = "tdrunner-#{@__gem_version}.gem"
+  if /win/ =~ RUBY_PLATFORM    
+    cmd = "del /F /Q pkg\\"
+    failure = system(cmd)
+    #raise "deleting #{GEM_NAME} in pkg folder failed" if (failure != true) or ($? != 0)
+
+    cmd = "gem uninstall --executables #{GEM_NAME}"
+    failure = system(cmd)
+    #raise "uninstalling  #{GEM_NAME} failed" if (failure != true) or ($? != 0)
+  else
+    `gem uninstall pkg/#{tdrunner_gem}`
+  end
+  
+end
+
+
+
+desc "Task for cruise control on Windows"
+#task :cruise => ['unit_test', 'build_help', 'gem', 'gem_install', 'gem_copy_to_share'] do
+task :cruise => ['gem_uninstall', 'gem', 'gem_install'] do
+	
+end
+

data/readme

@@ -0,0 +1,186 @@
+== tdrunner
+
+TDRunner
+
+Table of contents:
+
+    * Introduction
+    * Supported frameworks
+    * Installation
+    * TDRunner long period testing modes
+    * TDRunner parameters
+    * TDRunner Profiles
+          o Preprocessing with ERb
+          o Execution profiles
+    * Howto use TDRunner with Cucumber
+    * Howto use TDRunner with Test::Unit
+
+Introduction
+
+TDRunner is a tool for runnig long period testing for different opensource test frameworks. With TDRunner you can execute long period testing using different parameters and execution profiles.
+Supported frameworks
+
+    * Cucumber
+    * Test::Unit
+
+Installation
+
+TDRunner is distributed in a regular rubygems application and you can install it using command.
+
+    gem install tdrunner
+
+TDRunner long period testing modes
+
+TDRunner supports the following LPT execution modes:
+
+    * LPT duration in hours
+    * LPT duration in iterations
+    * LPT duration in end date and time stamp
+    * LPT with execution profiles
+
+TDRunner parameters
+
+TDRunner command has two sections:
+
+    tdrunner [options] [framework command]
+
+    * [options]
+          o This is the section where TDRunner parameters are defined
+    * [framework command]
+          o This is the section where the test framework specific command is defined
+          o For cucumber the framework command shoud start with cucumber
+          o For Test::Unit the framework command shoud start with test_suite
+
+    * [options]
+          o -H i Defines how many hours tdrunner will run i as number of hours.
+                + Executes tests for 1.5 hours:
+
+                                        tdrunner -H 1.5 cucumber features
+
+          o -i i Defines how many iterations tdrunner will run the tests i as number of iterations.
+                + Repeats tests for ten iterations:
+
+                                          tdrunner -i 10 test_suite ts_my_test_unit_suite.rb
+
+          o -d "date time" Defines end date and time when tdrunner will stop testing.
+                + Runs tests until defined date and time is reached:
+
+                                        tdrunner -d "12.12.2100 12:00" cucumber features
+
+          o -e execution_profile Defines tdrunner to use execution profile for running tests.
+                + Runs tests using execution profile:
+
+                                        tdrunner -e my_execution_profile -d "12.12.2100 12:00" test_suite ts_my_test_unit_suite.rb
+
+          o --teardown Defines test unit teardown only when the testcase is failed.
+                + Run test unit teardown only when the testcase is failed:
+
+                                        tdrunner --teardown -i 10 test_suite ts_my_test_unit_suite.rb
+
+          o -p profile_name Pull commandline arguments from tdrunner.yml which can be defined as strings or arrays.
+                + Run tests using a tdrunner profile:
+
+                                        tdrunner -p my_profile_name
+
+
+TDRunner Profiles
+
+TDRunner lets you store and reuse commonly used tdrunner command line arguments for a project in a tdrunner.yml or tdrunner.yaml file.
+
+NOTE: This file must be in your project�s root directory, config or .config.
+
+For example, by having this in your config/tdrunner.yml:
+
+    default: -i 100 cucumber features
+    html_report: -H 1 cucumber features -f TDriverReport::CucumberListener
+
+You can reuse the arguments listed above:
+
+    tdrunner -p html_report
+
+Preprocessing with ERb
+
+The tdrunner.yml file is preprocessed by ERb; this allows you to use ruby code to generate values in the tdrunner.yml file. So if you have several profiles with similar values you could do something like:
+
+    <% common = "-i 100" %>
+    default: <%= common %> cucumber features
+    html_report: <%= common %> cucumber features -f TDriverReport::CucumberListener
+
+Execution profiles
+
+You can define execution profiles with emphasis for test cases using parameter -e profile_file_name. When profile file is defined and it does not exist tdrunner will create the sip file for you and add the tests in to the file with default emphasis value 1.
+
+NOTE: This file must be in your project�s root directory, config or .config.
+
+For example, by having this in your config/calculator.sip for Test::Unit tests:
+
+    test_simple_addition(TC_Calculator)=3
+    test_memory_recall(TC_Calculator)=1
+    test_memory_store(TC_Calculator)=1
+    test_simple_addition(TC_Calculator)=1
+
+Will execute test_simple_addition test three times more than the other tests. The default emphasis for tests is 1.
+
+For example, by having this in your config/calculator.sip for cucumber tests:
+
+    features/move.feature=1
+    features/move_mouse.feature=3
+    features/press_key.feature=1
+
+Will execute move_mouse.feature test three times more than the other tests. The default emphasis for tests is 1.
+
+NOTE: The tests which do not have a emphasis value are added automatically in to the execution profile with default value 1.
+
+To run tdrunner with execution profile use -e rofile_file_name parameter in your tdrunner command:
+
+    tdrunner -H 2 -e calculator test_suite my_test_unit_suite.rb
+
+
+Howto use TDRunner with Cucumber
+
+TDRunner command has two sections:
+
+    tdrunner [options] [framework command]
+
+    * [options]
+          o This is the section where TDRunner parameters are defined
+    * [framework command]
+          o This is the section where the test framework specific command is defined
+          o For cucumber the framework command shoud start with cucumber
+
+   1. Install tdrunner
+   2. Go to your test folder where cucumber features folder is located
+   3. Run command:
+
+            tdrunner -h
+
+      this displays the tdrunner help.
+   4. Test tdrunner by running a command:
+
+            tdrunner -i 2 cucumber your_feature_folder_name
+
+Howto use TDRunner with Test::Unit
+
+TDRunner command has two sections:
+
+    tdrunner [options] [framework command]
+
+    * [options]
+          o This is the section where TDRunner parameters are defined
+    * [framework command]
+          o This is the section where the test framework specific command is defined
+          o For Test::Unit the framework command shoud start with test_suite
+
+   1. Install TDriver
+   2. Install tdrunner
+   3. Go to your test folder where cucumber features folder is located
+   4. Run command:
+
+            tdrunner -h
+
+      this displays the tdrunner help.
+   5. Test tdrunner by running a command:
+
+            tdrunner -i 2 test_suite your_test_suite_file_name
+
+

data/websi/README

@@ -0,0 +1,243 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create 
+database-backed web applications according to the Model-View-Control pattern. 
+
+This pattern splits the view (also called the presentation) into "dumb" templates
+that are primarily responsible for inserting pre-built data in between HTML tags.
+The model contains the "smart" domain objects (such as Account, Product, Person,
+Post) that holds all the business logic and knows how to persist themselves to
+a database. The controller handles the incoming requests (such as Save New Account,
+Update Product, Show Post) by manipulating the model and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails.  You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, start a new Rails application using the <tt>rails</tt> command
+   and your application name. Ex: rails myapp
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
+4. Follow the guidelines to start developing your application
+
+
+== Web Servers
+
+By default, Rails will try to use Mongrel if it's are installed when started with script/server, otherwise Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails
+with a variety of other web servers.
+
+Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+
+Say other Ruby web servers like Thin and Ebb or regular web servers like Apache or LiteSpeed or
+Lighttpd or IIS. The Ruby web servers are run through Rack and the latter can either be setup to use
+FCGI or proxy to a pack of Mongrels/Thin/Ebb servers.
+
+== Apache .htaccess example for FCGI/CGI
+
+# General Apache options
+AddHandler fastcgi-script .fcgi
+AddHandler cgi-script .cgi
+Options +FollowSymLinks +ExecCGI
+
+# If you don't want Rails to look in certain directories,
+# use the following rewrite rules so that Apache won't rewrite certain requests
+# 
+# Example:
+#   RewriteCond %{REQUEST_URI} ^/notrails.*
+#   RewriteRule .* - [L]
+
+# Redirect all requests not available on the filesystem to Rails
+# By default the cgi dispatcher is used which is very slow
+# 
+# For better performance replace the dispatcher with the fastcgi one
+#
+# Example:
+#   RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
+RewriteEngine On
+
+# If your Rails application is accessed via an Alias directive,
+# then you MUST also set the RewriteBase in this htaccess file.
+#
+# Example:
+#   Alias /myrailsapp /path/to/myrailsapp/public
+#   RewriteBase /myrailsapp
+
+RewriteRule ^$ index.html [QSA]
+RewriteRule ^([^.]+)$ $1.html [QSA]
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
+
+# In case Rails experiences terminal errors
+# Instead of displaying this message you can supply a file here which will be rendered instead
+# 
+# Example:
+#   ErrorDocument 500 /500.html
+
+ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong.  Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files.  Have "tail -f" commands running
+on the server.log and development.log. Rails will automatically display debugging
+and runtime information to these files. Debugging info will also be shown in the
+browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code using
+the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/ including:
+
+* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
+* Learn to Program: http://pine.fm/LearnToProgram/  (a beginners guide)
+
+These two online (and free) books will bring you up to speed on the Ruby language
+and also on programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your Mongrel or
+Webrick server with --debugger. This means that you can break out of execution at any point
+in the code, investigate and change the model, AND then resume execution! 
+You need to install ruby-debug to run the server in debugging mode. With gems, use 'gem install ruby-debug'
+Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8 @attributes={\"title\"=>nil, \"body\"=>nil, \"id\"=>\"1\"}>,
+       #<Post:0x14a6620 @attributes={\"title\"=>\"Rails you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better is that you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you enter "cont"
+
+
+== Console
+
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+Here you'll have all parts of the application configured, just like it is when the
+application is running. You can inspect domain models, change values, and save to the
+database. Starting the script without arguments will launch it in the development environment.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>script/dbconsole</tt>.
+You would be connected to the database with the credentials defined in database.yml.
+Starting the script without arguments will connect you to the development database. Passing an
+argument will connect you to a different database, like <tt>script/dbconsole production</tt>.
+Currently works for mysql, postgresql and sqlite.
+
+== Description of Contents
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from ApplicationController
+  which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb.
+  Most models will descend from ActiveRecord::Base.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use eRuby
+  syntax.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the common
+  header/footer method of wrapping views. In your views, define a layout using the
+  <tt>layout :default</tt> and create a file named default.html.erb. Inside default.html.erb,
+  call <% yield %> to render the view using this layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are generated
+  for you automatically when using script/generate for controllers. Helpers can be used to
+  wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database, and other dependencies.
+
+db
+  Contains the database schema in schema.rb.  db/migrate contains all
+  the sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when generated
+  using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that doesn't
+  belong under controllers, models, or helpers. This directory is in the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for images, stylesheets,
+  and javascripts. Also contains the dispatchers and the default HTML files. This should be
+  set as the DOCUMENT_ROOT of your web server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the script/generate scripts, template
+  test files will be generated for you and placed in this directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins subdirectory.
+  If the app has frozen rails, those gems also go here, under vendor/rails/.
+  This directory is in the load path.