similar to: rspec_autotest testing with the use of the controller Namespaces

In case anyone else is trying to make this work, here is what I did (Before 0.7.4 I had patched the regex in zentest redgreen, but that is not used any more) To use directly, it is very simple. In rspec_autotest/lib/ rspec_autotest.rb, add a -c to the spec_command in the initializer function: @spec_command = "spec -c --diff unified" This won''t help however if you want

Hi, Is it possible to run both autotest and rspec_autotest at the same time while I convert my tests over to specs? autotest seems to either want to run one or the other. Also, rspec_autotest doesn''t seem to red/green the error/successes. It should, right? Thanks, Joe

Ok, this is INCREDIBLY finicky of me, and I''m a really finicky person at the best of times, but I noticed that when you use the TM Alternate File command to create specs, it does it with a header line like this: File.dirname(__FILE__) + ''/../../../spec_helper'' I use a header line like this require File.expand_path(File.join(File.dirname(__FILE__), *%w [..

Hi, there, I have some methods which I have written as helpers. They are in spec/support/controller_macros.rb (yes, I will change the name soon). The 2 methods, login_user and login_admin_user works in the controller specs BUT fail to work in the view specs when I call them in the view specs. ---------- spec/spec_helper.rb start -------------------------- # This file is copied to spec/

My app is builded with rails 2.3.12, rspec-rails 1.3.2, webrat 0.7.3. My spec_helper.rb ENV["RAILS_ENV"] ||= ''test'' require File.expand_path(File.join(File.dirname(__FILE__),''..'',''config'',''environment'')) require ''spec/autorun'' require ''spec/rails'' require

Is the rspec_autotest plugin mentioned here, http://blog.nicksieger.com/articles/2006/11/15/rspec-autotest-now-a-rails-plugin the accepted method of auto testing specs? It''s an old article, and after grabbing the plugin, and giving it a run, it fails with: $ rake spec:autotest:rails trunk/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/rails_example.rb:31: undefined method

If I got this to work, do you think we could/should check in rspec_autotest into rspec? I''ve updated rspec_autotest abit, so let me know if you''d like the modified code. Scott

I''m trying to test registration emails (sent with devise), and I keep getting the error: Net::SMTPServerBusy: 454 4.7.1 <model_spec-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org>: Relay access denied I''m running Rails 3.2.11 with Capybara, and I have (temporarily) chopped my spec_helper.rb and test.rb files down to the bare minimum, still getting the error above.

Has anyone else encountered this problem? What I mean is, rspec_autotest runs all specs, then waits. When you change a spec, it reruns that spec. However, if that spec now passes, it should run the whole suite again, so you can see the next one to work on. It no longer does this. This renders it somewhat useless. Does anyone have autotest working with rspec 0.7.5, or does anyone have any

I am taking over a code base and am trying to run the tests. I am somewhat new to RSpec so this might be a trivial problem. Basically I can tell that the fixtures are not getting loaded. All 100 tests fail with a similar error. But I don''t know why. Below is the code, with my narrative with *** before it... Can you see anything or give me a clue where to look. So far I am coming up

Hi, I am confused (a normal state for me) about the State-Of-The-Art Story API to use. examples/calculator.rb has one syntax, the Blogs have another Syntax, so do the various tutorials. I realize that Stories are ongoing work, but it would be nice if there were something I could refer to to make sure that I am not using a syntax that will soon be deprecated, and that I am doing "what is

this my first rspec test, it is very simple ----------------------------------------------------------------------------------------------------------------------------------------- > require File.expand_path(File.dirname(__FILE__) + ''/../spec_helper'') describe Doc do fixtures :docs before(:each) do @doc=docs(:yjn_bjy) end it "should create a new instance

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''m trying to spec a subclass of ActionController::Base using an anonymous subclass but I am running into errors but I am receiving a uninitialized constant StubResource Here is my base class class Admin::BaseController < ApplicationController before_filter :etherweb_site load_and_authorize_resource layout "admin/admin" protected def etherweb_site end end

hi list - should it be possible to use autotest to continuously run specs for a non-rails project? when i execute autotest in the base directory of my project, it complains that it cannot load rspec_autotest, however looking at rspec_autotest[1] and rspec_rails_autotest.rb, it appears as though both are geared towards rails (perhaps even rspec on rails). cheers, jean-pierre [1]

Here is a very simple spec: -- require File.expand_path(File.dirname(__FILE__) + ''/../spec_helper'') describe Product, "The Product model" do describe "When a new blank product object gets created" do before(:each) do @product = Product.new end it "should not be valid" do @product.should_not be_valid

We recently upgraded to rspec2 / rails 3 and our specs are taking a very long time to run. It takes nearly 12 minutes before the first dot comes out. Before the upgrade, our entire suite of 6000+ specs would run in about 6 minutes. The majority of the delay seems to be during the loading of the spec files. Adding instrumentation to the rspec-core lib/rspec/core/ command_line.rb, you can see

Hello, everyone. I''ve been lurking here for a while, but this is my first post. I think I''ve run into a RSpec bug in a Rails project I''m working on. I was working on a few REST controllers, and started getting failures on a specific spec that verified whether a certain action returned XML output. I spent quite a lot of time checking my code to see if it was something I

I haven''t been spec''ing lately, but been hopping back on and adding autotest. However I get an error: http://pastie.caboo.se/177538/wrap I also noticed a post by Scott and there was mention of rspec_autotest. Is this is what everyone is using? http://svn.caldersphere.net/svn/main/plugins/rspec_autotest/

I am writing a gem and using RSpec to drive my development. However, whenever I describe a class within the gems lib I get an uninitialized constant error. I am placing my folder structure, spec.rake and first spec below. I feel I must be missing something obvious. Additionally, I did output the value of f in lib inclusion code and it is traversing the lib folder correctly and I can