TeamCity Rake runner supports Test::Unit, Test-Spec, Shoulda, RSpec, Cucumber test frameworks. It is compatible with Ruby interpreters installed using Ruby Version Manager (MRI Ruby, JRuby, IronRuby, REE, MacRuby, etc.) with rake 0.7.3 gem or higher.
In this section:
|Table of Contents|
Make sure to have Ruby interpreter (MRI Ruby, JRuby, IronRuby, REE, MacRuby, or etc) with rake 0.7.3 gem or higher (mandatory) and all necessary gems for your Ruby (or ROR) projects and testing frameworks installed on at least one build agent.
You can install several Ruby interpreters in different folders. On Linux/MacOS it is easier to configure using RVM. It is possible to install Ruby interpreter and necessary Ruby gems using Command Line build runner step. If you want to automatically configure agent requirements for this interpreters you need to register its paths in build agent configuration properties and then refer to such property name in Rake build runner configuration.
To install a gem execute:
Path to a Rakefile file
Enter Rakefile path if you don't want to use a default one. Specified path should be relative to the build checkout directory.
Type in the Rakefile content instead of using existing Rakefile. The new Rakefile will created dynamically from the specified content before running Rake.
Optional. Specify if differs from the build checkout directory.
Enter tasks names separated by space character if you don't want to use '
Additional Rake command line parameters
Specified parameters will be added to '
Use default Ruby
Use Ruby interpreter settings defined in Ruby environment configurator build feature settings or interpreter will be searched in the
Ruby interpreter path
Path to Ruby interpreter. Path cannot be empty. In this field you can use values of environment and system variables. For example:
Specify here the RVM interpreter name and optionally a gemset configured on a build agent.
If you want TeamCity to display test results on the dedicated Tests tab of the Build Results page, select here the testing framework you use: Test::Unit, Test-Spec, Shoulda, RSpec or Cucumber.
XML Report Processing
Select a report type to import. You only need to import tests reports, if the automatic tests reporting fails to detect your tests.
Select report format from a drop-down list. The following report formats are supported: PMD, Surefire, Ant JUnit, NUnit, Checkstyle and FindBugs.
These options can be configured using system properties in Properties and Environment Variables Build Parameters section.
Allows to specify which rake gem to use for launching rake build.
If your application doesn't use latest installed (in Ruby sdk) test-unit gem version please specify it here. Otherwise Test::Unit test reporter may try to load incorrect gem version and affect runtime behavior. If test-unit gem is installed but you application uses Test::Unit bundled in Ruby 1.8.x SDK please set version value to 'built-in'.
Launches bundler emulation for specified bundler gem version (the gem should be already installed on an agent.
Customizes Gemfile if it isn't located in checkout directory root.
Sets BUNDLE_PATH if TeamCity doesn't fetch it correctly from Gemfile <Gemfile containing directorydirectory>/.bundle/config.