http://gist.github.com/452385
(It's the default generated from rails g rspec:install).
I'm not sure what else it could be. I literally change my Gemfile
from beta.12 (where specs work) to beta.13 run 'bundle install/update'
and it then fails.
On Jun 24, 8:49 pm, David Chelimsky wrote:
> On Jun
On Jun 24, 2010, at 10:36 PM, geetarista wrote:
> On Jun 24, 8:21 pm, David Chelimsky wrote:
>> On Thu, Jun 24, 2010 at 10:12 PM, geetarista wrote:
>>
>>> On Jun 24, 7:10 pm, David Chelimsky wrote:
On Jun 24, 2010, at 2:24 PM, geetarista wrote:
>>
> On Jun 24, 12:03 pm, David Chelims
Here's the backtrace and the spec file: http://gist.github.com/452355
Also, if I delete that spec file, it just goes to the next
alphabetical file and gives the same error for that model name.
On Jun 24, 8:21 pm, David Chelimsky wrote:
> On Thu, Jun 24, 2010 at 10:12 PM, geetarista wrote:
>
> >
On Thu, Jun 24, 2010 at 10:12 PM, geetarista wrote:
>
> On Jun 24, 7:10 pm, David Chelimsky wrote:
>> On Jun 24, 2010, at 2:24 PM, geetarista wrote:
>>
>> > On Jun 24, 12:03 pm, David Chelimsky wrote:
>> >> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>>
>> >>> I just upgraded to beta.13 and I
I'm using Rails master.
On Jun 24, 7:10 pm, David Chelimsky wrote:
> On Jun 24, 2010, at 2:24 PM, geetarista wrote:
>
> > On Jun 24, 12:03 pm, David Chelimsky wrote:
> >> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>
> >>> I just upgraded to beta.13 and I'm running into an issue where when I
On Jun 24, 2010, at 2:24 PM, geetarista wrote:
> On Jun 24, 12:03 pm, David Chelimsky wrote:
>> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>>
>>> I just upgraded to beta.13 and I'm running into an issue where when I
>>> run 'rake spec', I get an 'uninitialized constant Comment' error.
>>> Co
PLEASE NOTE: rspec-rails-2.0.0.beta.13 requires rails-3.0.0.beta4.
If you are upgrading to rspec-rails-2.0.0.beta.13, you must also upgrade to
rails-3.0.0.beta4.
Apologies for any confusion caused by my not making an announcement about it
earlier.
Cheers,
David
On Jun 20, 2010, at 1:37 AM, Narayanan wrote:
> Hi,
>
> I have a library of RSpec Test examples. Now, from an upper ruby
> layer, I need to run only individual separate test example from the
> library that matches a particular string in the upper layer.
>
> For Example:
>
> My RSpec library fil
On Jun 22, 2010, at 11:10 AM, Miriam wrote:
> I'm having the same problem the OP mentions -- undefined method
> "visit"
>
> Trying to upgrade from Rails 2.3 to Rails 3.0.beta4
>
> My test stack:
> webrat (0.7.1)
> cucumber (0.8.3)
> pickle (0.2.1)
> factory_girl (1.3.0)
> factory_girl_rails (1.0
On Jun 22, 2010, at 3:29 AM, Timo Rößner wrote:
> Hey guys,
>
> i have a problem with latest rails 3 and rspec2.0.0.12beta.
> When running most of my (with rails 2 and rspec 1 working) controller
> specs i get:
>
>route set not finalized
>
> I reduced the problem to the max:
>
> $ cat con
I'm having the same problem the OP mentions -- undefined method
"visit"
Trying to upgrade from Rails 2.3 to Rails 3.0.beta4
My test stack:
webrat (0.7.1)
cucumber (0.8.3)
pickle (0.2.1)
factory_girl (1.3.0)
factory_girl_rails (1.0)
I changed config.mode = :rack, as suggested, but I"m still getti
On Jun 24, 2010, at 1:37 AM, anywho wrote:
> Running into issues with latest rspec beta.
>
> Beta.12 works flawlessly. Any insights are appriciated.
>
> /mnt/bob/bob.building.app/vendor/bundle/gems/activesupport-3.0.0.beta3/
rspec-rails-2.0.0.beta.13 only works with rails-3.0.0.beta4.
HTH,
Da
On Jun 22, 2010, at 8:10 PM, antonyw wrote:
> Hello,
>
> I have some code that is going to be used in other applications, so I
> decided to bundle the code (mostly controllers and views) into a plugin to
> make sharing easier. I copied the RSpec tests for the controllers into the
> plugin as well
Hey guys,
i have a problem with latest rails 3 and rspec2.0.0.12beta.
When running most of my (with rails 2 and rspec 1 working) controller
specs i get:
route set not finalized
I reduced the problem to the max:
$ cat config/routes.rb
Foo::Application.routes.draw do |map|
resources :profil
To get this working, I had to comment out line 21:
SPEC_PROGRAM = File.expand_path(File.join(File.dirname(__FILE__),
'..', '..', 'bin', 'spec'))
My output said that I already had SPEC_PROGRAM initialized and also
this line made it point to ../../bin/spec where I do not have spec
installed (correc
Running into issues with latest rspec beta.
Beta.12 works flawlessly. Any insights are appriciated.
/mnt/bob/bob.building.app/vendor/bundle/gems/activesupport-3.0.0.beta3/
lib/active_support/dependencies.rb:209:in `require': no such file to
load -- action_view/testing/resolvers (LoadError)
Hi,
I have a library of RSpec Test examples. Now, from an upper ruby
layer, I need to run only individual separate test example from the
library that matches a particular string in the upper layer.
For Example:
My RSpec library file contains many test examples like:
describe arithmetic do
it
Hello,
I have some code that is going to be used in other applications, so I
decided to bundle the code (mostly controllers and views) into a plugin to
make sharing easier. I copied the RSpec tests for the controllers into the
plugin as well.
The plugin RSpec tests run, however when it gets to s
I did both 'bundle install' and 'bundle update'.
On Jun 24, 12:03 pm, David Chelimsky wrote:
> On Jun 24, 2010, at 1:23 PM, geetarista wrote:
>
> > I just upgraded to beta.13 and I'm running into an issue where when I
> > run 'rake spec', I get an 'uninitialized constant Comment' error.
> > Comme
On Jun 24, 2010, at 1:23 PM, geetarista wrote:
> I just upgraded to beta.13 and I'm running into an issue where when I
> run 'rake spec', I get an 'uninitialized constant Comment' error.
> Comment is the first model (alphabetically) in my project. If I
> switch back to beta.12, it works. If I us
I just upgraded to beta.13 and I'm running into an issue where when I
run 'rake spec', I get an 'uninitialized constant Comment' error.
Comment is the first model (alphabetically) in my project. If I
switch back to beta.12, it works. If I use 'spec .' and not 'rake
spec', it also works.
Environm
Fixed, the problem was the path of my textmate. The solution is open
preferences, go to advanced/shell variables and make sure that your
PATH entry includes the path of your imagemagick (in my casa, with
homebrew is /usr/local/bin).
On Jun 22, 2:05 am, Daniel Lopes wrote:
> Hello, I'm experiencin
On Jun 24, 2010, at 9:30 AM, Valentino Lun wrote:
> Dear all
>
> For the scenario outline example:
>
> Example:
>| start | eat | left |
>| 12 | 5 | 7 |
>| 20 | 5 | 15 |
>
> If my examples got 30 columns and 1000 rows. It would be difficult to
> organize in the .featur
Dear all
For the scenario outline example:
Example:
| start | eat | left |
| 12 | 5 | 7 |
| 20 | 5 | 15 |
If my examples got 30 columns and 1000 rows. It would be difficult to
organize in the .feature file. Can the example store in a csv file or an
active record model?
On Jun 24, 2010, at 8:12 AM, Ivo Wever wrote:
> Hey,
>
> Thanks, that works fine and makes sense. Now there are also a few specs
> that assert the inverse direction:
>
> describe SessionsController do
> describe "route generation" do
>it "should route the destroy sessions action correctly"
Hey,
Thanks, that works fine and makes sense. Now there are also a few specs
that assert the inverse direction:
describe SessionsController do
describe "route generation" do
it "should route the destroy sessions action correctly" do
route_for(:controller => 'sessions', :action => 'de
On Jun 24, 2010, at 3:05 AM, Ivo Wever wrote:
> Hey,
>
> I'm migrating an app to Rails 3 + RSpec 2 and, as expected, a number of
> specs broke. Unfortunately, I can't really find how to fix them. For
> instance, there is a spec:
>
> describe SessionsController do
> describe "route recognition"
Some additional info:
* I'm on Rails 3 beta4 and RSpec 2 beta 13.
* It doesn't matter whether I invoke the spec as
bundle exec spec spec/controllers/sessions_controller_spec.rb
or
bundle exec rake spec
--
Posted via http://www.ruby-forum.com/.
__
Hey,
I'm migrating an app to Rails 3 + RSpec 2 and, as expected, a number of
specs broke. Unfortunately, I can't really find how to fix them. For
instance, there is a spec:
describe SessionsController do
describe "route recognition" do
it "should generate params from GET /login correctly" d
29 matches
Mail list logo
