similar to: [PATCH] Adds the qemu log to the autotest output.

Autobuild has to be updated to call make in the recipe directory and move the resulting iso to the main build directory. Importing the existing autotest.sh script from ovirt-node-image Signed-off-by: Mike Burns <mburns at redhat.com> --- autobuild.sh | 7 + autotest.sh | 764 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 771 insertions(+), 0 deletions(-)

If the -p option is provided, then no VMs are destroyed. Instead they, and their related networks, are left intact. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 11 ++++++++++- 1 files changed, 10 insertions(+), 1 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..b72ec98 100755 --- a/autotest.sh +++ b/autotest.sh @@ -219,6 +219,9 @@

The test_stateless_pxe_nohd test was broken. Fixed. Result code was not matching the success/failure state for the tests. Fixed. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 115 +++++++++++++++++++++++++++++++++------------------------- 1 files changed, 65 insertions(+), 50 deletions(-) diff --git a/autotest.sh b/autotest.sh index 12d3e30..e5e23a8 100755

All temporary files are kept in a single directory. At the end of the autotests that one directory is deleted. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 20 +++++++++++--------- 1 files changed, 11 insertions(+), 9 deletions(-) diff --git a/autotest.sh b/autotest.sh index c9f8a2d..d658cf3 100755 --- a/autotest.sh +++ b/autotest.sh @@ -40,6 +40,7 @@ # an

By default it's 120 ms, but can be changed through command line arguments. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 16 ++++++++++------ 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/autotest.sh b/autotest.sh index c67931a..bcd9bd5 100755 --- a/autotest.sh +++ b/autotest.sh @@ -62,6 +62,7 @@ Usage: $ME [-n test_name] [LOGFILE] -i:

I have been using autotest/zentest 3.5.0 with my rails 2.0.2 and rspec. I upgraded my gems and got 3.9.3 and had a problem. I went back to 3.5.0 and it worked. I stayed there until moving to rails 2.1. I again updated my gems and got 3.10. This one had the same problem. This time I need to figure out what is wrong. Here is what I get:

Hi folks, I''m going through railstutorial.org and so I apologize if I''m hitting the wrong group here and would appreciate any appropriate redirection if necessary. I''ve set up Spork + Autotest as per Michael''s instructions in http://ruby.railstutorial.org/chapters/static-pages#sec:testing_tools Essentially by doing the following (using rvm & I''m

Not sure if anyone needs this, but I have successfully been running rspec/trunk with autotest for a few days now on a non-rails project. The process is pretty simple: 1. Put rspec into vendor/plugins/rspec (on externals, or simply frozen) 2. Add autotest/discover.rb: Autotest.add_discovery do "myproj" end 3. Add autotest/myproj.rb: require File.dirname(__FILE__) +

People, I''m trying to run autotest on rails 2.3 I get a NoMethodError. Here is what I see: Sat Mar 21 20:47 /b/tmp/myfc23 maco$ Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest loading autotest/rails_rspec ./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize'': undefined method `failed_results_re='' for #<Autotest::RailsRspec:0x1205b88> (NoMethodError)

Running: Rails 3.0.5 ZenTest 4.5.0 autotest (4.4.6, 4.3.2) autotest-fsevent (0.2.5, 0.2.2) autotest-growl (0.2.9, 0.2.4) autotest-rails (4.1.0) autotest-rails-pure (4.1.2, 4.1.0) cucumber (0.10.2) cucumber-rails (0.4.0) spork (0.9.0.rc4) Gives me a truly bizarre situation. When I touch my features file, autotest runs a single, unrelated rspec test. Cucumber alone or with spork gives me the

I am using latest version for rspec-rails, ZenTest. I am getting following error, when ever I try to run autotest. Please help -head at mhart6/gems/ZenTest-4.6.2/lib/autotest.rb:315:in `load'': /Users/ jayparteek/.autotest:7: invalid multibyte char (US-ASCII) (SyntaxError)

I have had this problem for a while. autotest has never worked properly for me. I have tried different versions of rspec with different versions of ZenTest. I have tried it with .autotest files and without. When I run autotest from my rails app root, it says: loading autotest/rails_rspec and then it just sits there. If I look at the output from autotest -v, it is traversing the tree and it

Hi all, I tried testing with Rspec for first time, following a tutorial. "rspec spec/" works fine but when I try ''autotest'' it gives me the error message below. I also made a gist about it: https://gist.github.com/779265 It seems like a redgreen or ZenTest error. I''m using Ubuntu10, Rails3, Ruby 1.9 and RVM. Any help is appriciated, thanks in advance, gezope

Hello, I''ve been trying to google the definitive way to combine autotest, rspec, and spec-server, but to no avail. It seems like there are lots of suggestions from old versions. Furthermore, some commands such as rake:autotest don''t seem to be around anymore. So, is it required to install ZenTest as a gem? I have version 3.9.1. I believe this gets me the autotest

I''m having trouble getting autotest to run "out of the box" with rspec. I''ve got a Leopard setup with Zentest 3.5.0, rspec on trunk, and rails 2.0PR. No ".autotest" file. There are a couple of issues: 1. Running ''autotest'' inititally yields a command not found for "spec --diff unified etc etc". This seems to be an old issue but

Hi, When I start the "autotest" it gives me the following error...not sure what HOME path I have to set...all Ruby/Rails related components are in path! --- C:\>autotest -rails C:/Tools/InstantRails/ruby/lib/ruby/gems/1.8/gems/ZenTest-3.3.0/lib/autotest.rb:285:in `expand_path'': couldn''t find HOME environment -- expanding `~/.autotest'' (ArgumentError) ---

I''ve read about integrating Growl with Autotest/RSpec to display test results. For cygwin users - here is a snippet that will play a sound after autotest runs. Add the code below to your ~/.autotest file. Modify the path of the .wav file to the sounds you want to play on your system. Cheers, Andy vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv Module

Hi guys, I''m trying to find some information on how to get autotest to run the rspec2 tests. I have my project setup so "rake spec" runs the specs properly, but autotest seems to ignore/don''t know that there are specs to test. I read on the rspec2 wiki that autotest integration is o be added eventually. Any ideas on how to achieve this? Thanks, Jeroen

Hi! I''m rather new to Merb, but I thought I''d give it a shot. I found that autotest wasn''t running my specs when my models were changing. Maybe this is because of how I have set up Merb, but in the even that it''s not just me, I''ve adapted Autotest''s mappings for Rails and have attached my efforts to this email. Unfortunately, you need to

Autotest is running continuously - even when the files mtimes aren''t changing. I believe this only happens if using a failures file. autotest -v gives me: euclid% autotest -v loading autotest/rails_rspec /opt/local/bin/ruby -S script/spec -O spec/spec.opts spec/ controllers/log_entries_controller_spec.rb spec/views/login/ new_spec.rb spec/controllers/login_controller_spec.rb