search for: rspec_model

rspec_resource_generator ======================== By Pat Maddox Use this generator to generate RESTful scaffolding with RSpec specifications. Syntax is exactly the same as the scaffold_resource generator: ./script/generate rspec_resource ModelName [field:type field:type] When you run this generator, it will create a migration, model, and model spec file. In addition, it gives you a RESTful

...ls plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails --version Rails 1.1.6 However, when I try to run the specs ... $ rake spec:models /usr/local/bin/ruby -I"/usr/local/lib/ruby/gems/1.8/gems/rspec-0.7.2/lib" "/usr/local/lib/ruby/gems/1.8/gems/rspec-0.7.2/bin/spec" "spec/models/da...

I''m just getting started with rspec, I''m running on edge for both. In a fresh project, I freeze edge, install the edge rspec plugin. I generate a simple rspec_model and run the spec. It passes. When I run rake spec:doc, I get the following output: - NO NAME (Because of --dry-run) where the specification should be. In fact if I just make a pending spec, it does the same. I''ve tracked it down to something in ''spec/rails'' because if...

...port" commands using the "current release install instructions" here [1]. However, there doesn''t seem to be any mention of the rspec_resource generator?. When I run script/generate I get the following: Installed Generators Plugins: authenticated, rspec, rspec_controller, rspec_model, rspec_scaffold Builtin: controller, integration_test, mailer, migration, model, observer, plugin, resource, scaffold, scaffold_resource, session_migration, web_service Could anyone spread any light as to why rspec_resource isn''t being installed? Sorry for the simple question but I ca...

...ails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails --version Rails 1.1.6 However, when I try to run the specs ... $ rake spec:models /usr/local/bin/ruby -I"/usr/local/lib/ruby/gems/1.8/gems/rspec-0.7.2/lib" "/usr/local/lib/ruby/gems/1.8/gems/rspec-0.7.2/bin/spec" "spec/models/da...

I have the latest version of rspec and rails-rspec installed. I''m using the debian versions of ruby and rails. On a new project after a generate an "rspec_model" and then try to run "rake spec", I get the following error: dan at dan-server:~/projects/cw/registration$ rake spec (in /home/dan/projects/cw/registration) /home/dan/projects/cw/registration/vendor/plugins/rspec_on_rails/lib/spec/rails/extensions/action_controller/rescue.rb:19:...

....5 Ruby 1.8.6 Rake 0.7.3 RSpec 1.0.8 PostgreSQL 8.2.5 I am experiencing a problem with the "rake spec spec" task on an initial trial of rspec. After creating the rails app I installed rspec and rspec_on_rails in the vendor\plugins subdirectory from svn. I then used ruby script\generate rspec_model product. I next manually created the database instances depot_development and depot_test via pgAdmin III. I then confirmed rails configuration connectivity by running rake db:migrate from the app root. When I run rake spec spec\models for the first time, without modifying the product_rspec.rb fi...

Hi all, I had some specs that were using fixture_file_upload that were passing just fine. Then I froze edge rails to get some 2.0 functionality, then a I upgraded to trunk rspec to deal with uninitialized constant ActionView::Helpers::JavaScriptMacrosHelper After a couple other of tribulations, I have now gotten down to just a couple of not passing specs, all using the fixture_file_upload.

...app/ $ jedit config/database.yml $ createdb test_app_test $ createdb test_app_development $ ./script/plugin install http://rspec.rubyforge.org/svn/tags/CURRENT/rspec_on_rails $ ./script/plugin install http://rspec.rubyforge.org/svn/tags/CURRENT/rspec $ ./script/generate rspec $ ./script/generate rspec_model Account $ jedit db/migrate/001_create_accounts.rb app/models/account.rb spec/models/account_spec.rb $ rake spec:models (in /Users/kmcd/tmp/test_app) /Users/kmcd/tmp/test_app/vendor/plugins/rspec/lib/spec/version.rb:10: undefined method `[]'' for nil:NilClass (NoMethodError) from...

I''m trying to wrap my head around the new describe/it syntax. First, a few of observations: - the "describe" word itself encourages you to think about contexts as things/nouns; this is reinforced by the way "script/generate rspec_model" and friends by default generate a template spec of the form "describe ClassName do ... end", because classes so often represent "things" (even if they are abstract things like relationships) - the ability to follow a bare class name with a qualifying string -- examp...

Hello All, I am hoping someone can help me. I am having a nightmare of a time trying to get rSpec to work. It was working at one time, but I tried installing Zentest to get autotest to work with rSpec and it''s been downhill ever since. Here are the gems I have installed in my rails app: ZenTest 3.6.1 if it matters (technically this is in my Ruby gems list and not in my vendor

Hi, Hi I am trying to use RSPEC on windows and i keep getting the following error "You must gem install win32console to use colour on Windows" I have installed this Gem but i am still getting the same error. The file that error is coming from is: C:\ruby\lib\ruby\gems\1.8\gems\rspec-0.8.2\lib\spec\runner\formatter\base_text_formatter.rb Do i need to put this line of code in? Where

I''ve been working through the book ''Beginning Ruby on Rails E-Commerce'' which is very heavy on Test Driven Development. As in, you have to write tests for scaffolding methods and validations and crap like that. And then they fail. And you KNOW its the test not the method. So you spend 2x the time writing a test that has to be adapted when requirements change. You