-
Notifications
You must be signed in to change notification settings - Fork 19
Rake Tasks
Based on Taza 0.8.2
The artifacts produced by running a Rake task are stored in the artifacts/
directory by default. In earlier versions of Taza the structure in artifacts/
reflected the spec/
folder. The decision was made to put the artifacts into a folder with the name coming from Time.now.to_i
since we wanted an easier way for Continuous Integration systems to get the latest results. We understand this may not be ideal and we would love a way that could fulfill the criteria of readability and CI support.
In 0.8.2 you can customize your the rake tasks options more easily. The code below is what gets generated in the default Rakefile for a Taza project.
require 'rubygems'
require 'taza/tasks'
Taza::Rake::Tasks.new do |t|
file_hole = “artifacts/#{Time.now.to_i}”
t.spec_opts = [“—format html:#{file_hole}/index.html”,
“—format p”,
“—format failing_examples:#{file_hole}/failing_examples.txt”]
end
Using Taglob style tags in your tests can let you run your tests by an arbitrary tag grouping. To do this just run something like $ rake spec:isolation:google TAGS=foo,bar
. This will run only the functional / isolation tests for the Google Site that are tagged with foo AND bar. For OR style filtering use the following $ rake spec:isolation:google TAGS="foo|bar"
and note the quotes around foo|bar. Obviously unix systems would treat the |
as a pipe and make everything all weird.