similar to: Autotest doesn''t work on WinXP?

Ok, David says on page 241 that sometimes a many-to-many relation with attributes are better implemented as an actual model instead of using HABTM. Well, I''ve got that situation and I can''t figure it out. All of the examples in the book have HABTM examples between 2 different tables, but I want to have a HABTM relation on 1 table with itself. (e.g., if I have a table Things,

I''d like to use Mongrel_cluster with SSL on a green-field application (it can be configured however is best - initially, "ease of setup" is important, but then soon after will be scaling and response time). I''ve read a lot of emails on this topic, and checked out the Mongrel pages, etc, but I''m left with this question of what is recommended: For a

I''d like to always add a condition to any version of "find" (e.g. Thing.find(), Thing.find_by_name(), Thing.find_by_whatever) so that in addition to whatever conditions are set, an additional condition is set :conditions=>"user_id=#{current_user.id}" I''d like to make sure that a user only sees/edits/creates entries in the database that have the user_id

I am getting this horribly ugly output from autotest when a test fails. Normal output from ''rake test'': -- 1) Failure: test_export_format(TaskTest) [./test/unit/task_test.rb:61]: <"Michael Alvarez"> expected but was <nil>. -- Same failure, as seen via autotest: -- 1) Failure: test_export_format(TaskTest) [./test/unit/task_test.rb:61]: ---

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''"

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"

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

Josh Knowles http://joshknowles.com/ just let me know that ZenTest Autotest 3.50 now handles your RSpec specs. http://blog.zenspider.com/archives/2007/04/zentest_version_350_has_been_released.html That''s a great news. Josh also shared with me a quick hack to make autotest work with only the RSpec plugin installed. Add the following into your ~/.autotest file

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

My autotest runs but when I make changes to a spec it doesn''t reload. I checked another application I was building that had 1.0.9 but it was reloading fine. How would I debug a problem such as autotest not reloading? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070930/6be7160d/attachment.html

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

I need to extract the main body from an HTML email - or - strip all of the email related stuff out of an email leaving just the HTML code that is in the body (ideally, so that it could be saved as an HTML page that is ready to show in a browser). Has anyone had success doing something like this? I''ve found RubyMail and TMail that purport to help with this, but was wondering if anyone had

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

Just upgraded to latest rails and rspec builds and my autotest doesnt work undefined method `before'' for Spec::Rails::DSL::RailsExample:Class (NoMethodError) Here''s the full trace: http://pastie.caboo.se/112754 Any ideas? -- Posted via http://www.ruby-forum.com/.

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

Hello, I''m running AutoTest with Rspec on a Rails application. Every 20 or so runs I get "stack level too deep" on one particular controller stub. Ex. controller.stub!(:login).and_return(true) This particular line is in a before block of a certain describe block. The strange thing is, every single spec in this file fails on that one line, even the specs in other describe

False Positives I just discovered how easy it was to create a false positive when I, trying my first RSpec test, did this: ob.should eql?(''foo'') instead of: ob.should eql(''foo'') or: ob.should == ''foo'' As far as I can see, this is roughly equivalent to: ob.should false Neither eql?(''foo'') nor false causes the spec

Just a positive experience I would like to share with you : testing is great on paper but very tedious to apply because nobody wants to run manually the tests by hand. Last week I have discovered zentest, an automated test process command line utility. That was at the beginning (hopefully) of a new project. Believe it or not, I have started to code most parts of the application without using

I believe for rails projects you can put rspec''s code repos into vendor/plugins, and autotest will automatically use the rspec binary in that directory, and not the gem installed. Is there an easy way to do this for non-rails projects? There are a few advancements on trunk which I would like to take advantage of. Tips welcome ; ). Scott Taylor