similar to: rake spec does not run specs -- just writes to spec.opts directory

Hi I ran across the following when running spec on an old merb app. $ cat spec/spec.opts $ spec spec/models/topic_spec.rb Options written to spec/spec.opts. You can now use these options with: spec --options spec/spec.opts $ cat spec/spec.opts spec/models/topic_spec.rb $ spec spec/models/topic_spec.rb Options written to spec/spec.opts. You can now use these options with: spec --options

Hi guys. I''m unable to run my specs through a spec server. I''ve spent several hours searching and playing around with this problem, and I simply can''t find a solution. So if anyone has any suggestions, I''m all ears. Does script/server need to be running in conjunction with the spec server? I have "--drb" specified in spec/spec.opts . I start

Questions concerning spec.opts: 1. Am I correct in believing that each option should go on a separate line of spec.opts in the rails spec directory? If this is so, why is it so? 2. Using a formatter in spec.opts doesn''t seem to work. Here is my spec.opts file: --colour -f s and this is what happens when I run the rake task: Couldn''t find formatter class s Make

Windows XP SP 2 ruby 1.8.5 gems: rails 1.2.3 rake 0.7.3 win32console 1.0.8 plugins: rspec 1.0.8 rspec_rails 1.0.8 spec.opts: --colour --format progress --loadby mtime --reverse --drb When I run "rake spec" or "ruby script/spec spec --color" this is the output: D:\dev\project>rake spec (in D:/dev/project)

Hi, I have been trying to run unit tests through rake and getting closed stream error. The trace output is mentioned below: http://pastie.org/828398 I am on a Mac OSX 10.5.6 (leopard). And having the following setting % Ruby - ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0] % Rails - 2.3.5 % mysql gem - (2.8.1, 2.7) % MySql Server - 5.1.44 (installed from binary) I have followed

Hi, Just built the gem from trunk for the first time and ran into an issue with the generated spec.opts file (rev. 1493). Moving the file out of the way fixed the problem. I''m not on windows, so this is not a win32console gem issue as per the README. /usr/lib/ruby/gems/1.8/gems/rspec-0.8.0/lib/spec/expectations/sugar.rb:13:in `call'': undefined local variable or method

Hello Guys. I''m upgrading a project from 0.9.8 to 1.0.8, following this procedure: * Removed vendor/plugins/rspec* completely. * installed rspec and rspec_on_rails from svn://rubyforge.org/var/svn/rspec/tags/REL_1_0_8 * Run script/generate rspec to update spec_helper and spec.opts Now, when running rake, get the following error: superclass mismatch for class Annotation The following

Hi All, I submitted a patch last week to fix a bug with --drb not working if it''s specified in spec.opts, this causes autotest to run obscenely slowly out of the box on my machine. Please let me know if you need anything else from me on this. Cheers! Patrick

At work we''ve got a rather complex app with both specs and tests. Our default rake task runs all our our tests and specs. We''ve also got separate rake tasks to run groups of tests and specs in the various subdirectories. The default task simply lists all the individual tasks as pre-reqs. We do a lot of branching and merging, so we really want to run all of the tests and specs

Hello all, I''ve been trying to get ruby on rails to work with my local install of mysql(its with wamp). Windows XP, Ruby 1.8.6, rails 2.3.5, rubygems 1.3.5, mysql 5.2 something I believe. I have ruby installed in: C:\Ruby and my mysql is installed in: C:\wamp\bin\mysql\mysql5.1.30\bin I''ve attempted to change my database.yml file to include the port 80, and port 3036, the

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 am having inconsistent output with multiple options in the spec.opts file. I can, for instance, pass --color or --colour, or, separately, use --drb. But when combining them I get: /opt/local/lib/ruby/1.8/optparse.rb:1381:in `complete'': invalid option: --options --color --drb (OptionParser::InvalidOption) from /opt/local/lib/ruby/1.8/optparse.rb:1379:in `catch''

When specing observers I usually put them into models directory under / spec. Then, when specs are run observer class can''t be found unless I remove --load-by mtime from spec.opts. My question is what''s the Big Idea behind loading specs in that order by default? Shouldn''t default spec.opts contain just formatting options? Because as you see it DOES cause problems

i have a rails app that tests fine with "rake spec" but gets a segmentation fault when "rake spec:rcov" is run. i am on windows xp, ruby 1.8.6, rails 2.1.1, mysql 5 my app is at http://github.com/scottnj/test_blog/tree/master so maybe someone can try to replicate my error so i know if the problem is with my code or something installed on my pc. here is a copy of my shell

I updated to ruby 1.8.6p111 last night and updated some gems and now mongrel doesn''t work: MacOS 10.4.10 $ ruby --version ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-darwin8.10.1] $ gem list rails *** LOCAL GEMS *** rails (1.2.5, 1.2.4, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.6) Here''s a simple test: $ rails test5 create ... $ cd test5 $ script/server => Booting

I went ahead and moved to the trunk versions of RSpec and Spec:Rails because I wanted to try out the new Story Runner feature. However, when I tried to do "rake spec:doc", I got the following: AccountController - NO NAME (Because of --dry-run) AccountHelper - NO NAME (Because of --dry-run) User (in general) - NO NAME (Because of --dry-run) - NO NAME (Because of --dry-run) - NO NAME

In my spec folder, I have a "remote" directory, which contains my specs for live data transferring with an outside api. When I run rake spec, it runs the remote specs and I don''t want it to. Keep in mind there is NO lib/tasks/remote.task file. I ONLY want these remote specs to run when I execute rake spec:remote How can I achieve this?

The title says it all - please bear with me. To let you know where I stand, I have been working for up to 12 hours a day for 2 months and 2 weeks trying to get my site ready for release. In development (on windows) it works perfectly. In production (on linux ubuntu) it does not. I stopped using capistrano because there are problems with the repo on github and things aren''t working

Hello, I have noticed that, since version 1.1.4, autotest/autospec does not run any of my specs. After getting a hint from http://b.logi.cx/2008/10/9/non-auto-spec, I dove a bit deeper into the code and found that spec is no longer being run by ruby. I monkey-patched Autotest::Rspec in my .autotest file so that spec is again executed (using code taken from version 1.1.4). autospec is now

I''m still trying to work into Ruby 1.9.2 and am now experiencing something that makes no sense to me. Using rspec 1.3.2 and rspec-rails 1.3.4 with rails 2.3.11 on ruby 1.9.2-p180, when I $ rake spec:models they all pass. When I $ rake spec:controllers they all pass. When I $ rake spec:views they all pass. But when I $ rake spec I get <path to