similar to: Ugly, garbled output from autotest

Hey Guys, I''ve got a test class that loads a bunch of fixtures. My understanding is that fixtures are reloaded between each test... and I even have the following two method calls at the top of my test class to make doubly sure... class TaskTest < Test::Unit::TestCase self.use_transactional_fixtures = true self.use_instantiated_fixtures = false When I run my tests

Hi, I have a table which has a column called due_date. Datatype of this column in mySQL is "Date". Here is what I extracted from schema.rb > t.column "due_date", :date My fixture tasks.yml file has the following line > due_date: 07/17/2006 My test_task.rb has the following line > assert_equal "07/17/2006", @task.due_date When I run

I''ve been using polymorphic joins from edge rails based on about 5 lines of advice Rick Olson gave me over IRC. There''s some sparse documentation popping up but it seems to cover a somewhat different case. Anyway - I pretty much got it to work - save for one detail. Here''s what I have: class Event < ActiveRecord::Base belongs_to :attachable, :polymorphic =>

Hi, Im running windows xp and configured autotest with: http://railsforum.com/viewtopic.php?pid=4796 when i do autotest --rails i get following error: D:/servers/InstantRails/ruby/lib/ruby/gems/1.8/gems/ZenTest-3.6.1/lib/unit_diff. rb:187:in ``'': No such file or directory - diff.exe -u C:/DOCUME~1/Piotrek/USTAW I~1/Temp/expect.5412.0 C:/DOCUME~1/Piotrek/USTAWI~1/Temp/butwas.5412.0

Hi, First, thanks for the plugin. Sorry if this is not strictly a backgroundrb issue but I thought others on this list might have come across this problem. I''m trying to run the test that comes via the worker generator. The test works fine when running ''rake test_functional'', but when the tests are run by autotest I get "uninitialized constant BackgrounDRb"

When I try to run autotest (zenspider) (which looks VERY cool), I get this error: (run from within a Rails app directory) C:\ruby_home\analysis>autotest -rails # Testing updated files + c:/ruby/bin/ruby -Ilib:test -e ''["test/unit/user_test.rb", "test/unit/role_test.rb"].each { |f| load f }'' | unit_diff -u ''c:'' is not recognized

Hello all, I''m new to rSpec but after reading a couple of tutorials I''ve become enamored. Anyway, I am at minute 42 of the rSpec basics screencast ( peepcode.com) and I''m having the following error running autotest w/rSpec: D:\ruby\projects\forecaster>autotest loading autotest/rails_rspec c:\ruby\bin\ruby -rrubygems -e "require ''redgreen''"

Railsters: Despite Rails being the only Web platform designed for TDD, a lot of its test infrastructure is still "cargo cult" - imitating other test rigs instead of understanding their principles. Most importantly, tests should run instantly. There''s no excuse for breaking this rule, and if you invent a platform that can''t obey it then you are doing something

Hi all, Running on OSX 10.5.3, Latest Rspec trunk, Rspec rails trunk, latest autotest gem and rails 2.1 I''ve lost my colour output in autotest. rake spec gives colour output, but autotest gives me black and white. It was working a little bit before, I think I upgraded to the latest versions of everything to get all the textmate snippets talking and being friendly to one another again

I am having this crazy problem where it ONLY shows up in testing. This is my test code <code> def test_should_destroy task1 = Task.new(:description => "tmp", :done => false, :user => User.find_by_login(''admin'')) assert task1.save assert task1.destroy end </code> This is my task model

Hi Are there any tools around that make rspec''s failure messages easier to read? unit_diff from ZenTest doesn''t seem to work - unless I missed something. A simple but very helpful improvement would be to use more line- breaks, e.g. Current output: expected "this is a very long string blah blah", got "this is a very very long string blah blah" (using

I''m trying to spec my views with 0.7.1 on edge rails per the instructions on the rspec site [1] and David''s blog [2], but I''m not having much luck. Here''s my spec in specs/views/accounts/ new_view_spec.rb: require File.dirname(__FILE__) + ''/../../spec_helper'' context "The new account form" do specify "should have an

Hi, I''m using Test::Unit::TastCase and am having some problems getting expected database state before the test methods. My Ruby on rails book quite clearly says that the following things happen before every test method is run: - all records in the database are deleted - all the data in the fixtures are loaded into the database - the setup method is run. In the following

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)

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

When an autotest finishes running, then the output for the qemu logfile in /var/log/libvirt/qemu/ is added to the output. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- autotest.sh | 14 +++++++++++++- 1 files changed, 13 insertions(+), 1 deletions(-) diff --git a/autotest.sh b/autotest.sh index 7503be0..5ccdbbb 100755 --- a/autotest.sh +++ b/autotest.sh @@ -41,8 +41,9 @@

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

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:

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__) +

Hey all, Does anyone know how to disable the cucumber autotest support on a project? With this commit: http://github.com/aslakhellesoy/cucumber/commit/93470e2580b5e3cfe0c8eb3fce86e21bf8afa219 The cucumber features are worked into the autotest cycle automatically. This is cool, but on some projects I don''t think it fits well with my red->green->refactor cycle. Any ideas on