I\'ve upgraded my app from using config.gem to a Gemfile with bundler and have noticed that my unit tests have now stopped running.It\'s a bit strange and I\'m not entirely sure where to start looking
I have this kind of relation: class Article < ActiveRecord::Base has_many :comments end class Comment < ActiveRecord::Base
I am new to the unit testing scene; I have only been using unit tests for about 2 months now. When I unit test in Ruby I currently follow the TDD style and use Test::Unit::TestCase. I have also read a
I\'m migrating over to shoulda from rspec and I can\'t seem to get access to the http response. Can someone point out what I may be doing wrong?
edit: this problem only happens sometimes This only appears to happen when I run the test from within TextMate (even when I specify the ruby to run it from by hand w开发者_如何学Pythonith a shebang).
I have a number of ruby files (a.rb, b.rb, c.rb) which define very similar classes. (They should test the same)
Using shoulda with unit/test I have a context which requires one test to pass before the others are even tried.
I\'ve been writing RSpec tests for some Rails controllers and I\'ve discovered a strong impulse to ensure that the Authlogic authentication is working properly. I also feel like I should be verifying
The code below: context \"should destroy participation\" do setup do @p = Factory.create :participation delete :destroy, :id => @p.id.to_param
I have a pre-written Rails app for handling subscription based payments that is currently covered with an Rspec test suite. I\'m trying to merge it into a Rails app that is covered using the Shoulda t