Sorry. This is running from cruisecontrol rb:
---
Cucumber::Rake::Task.new(:cruise) do |t|
t.cucumber_opts = "-r features/cucumber_env --format pretty
--out=#{ENV['CC_BUILD_ARTIFACTS']}/features.txt --format html
--out=#{ENV['CC_BUILD_ARTIFACTS']}/features.html"
t.rcov = true
t.rcov_opts = ["#{RCOV_COMMON_OPTS} -o
#{ENV['CC_BUILD_ARTIFACTS']}/features_rcov"]
t.feature_pattern = ["features/control*/*.feature"]
end
---
Thanks,
Tim
On Tue, Apr 14, 2009 at 12:26 PM, aslak hellesoy
<aslak.helle...@gmail.com> wrote:
>
>
> On Tue, Apr 14, 2009 at 7:19 PM, Tim Walker <walke...@gmail.com> wrote:
>>
>> Hi Guys,
>>
>> My nightly tests stopped working suddenly over the weekend. Not sure
>> why yet. It's wierd because they just look like the exited without a
>> clue mid-test. Nothing in the logs is a smoking gun.
>>
>> Here's my question: It seems like the contents of features.txt do not
>
> What's features.txt?
>
>>
>> get written until the tests are done. In my current case this file is
>> 0 length at the end of the run. Any way to affect this behavior and
>> force the output to be written as the tests run.
>>
>> Many thanks guys.
>>
>> Sincerely,
>>
>> Tim
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
