search for: specdoc

Greetings, In the thread on another user''s first context, David offered his advice based on how the output read in specdoc format. My thinking to- date about the specdoc format is that it was this great thing to have when I was done with my software. I now realize that it can be so much more than that if read after each run of the specs! I foresee that reading it after each run may allow me to notice things abou...

I''m doing some housekeeping and just realised that the rdoc formatter produces gibberish: http://rspec.rubyforge.org/rdoc/files/EXAMPLES_rd.html Will anyone protest if I just go ahead and remove it? (I can''t imagine anyone using it, especially with the much better HTML formatter) Aslak

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.

...iff Show unified diff of Strings that are expected to be equal when they are not -c, --colour, --color Show coloured (red/green) output -s, --spec SPECIFICATION_NAME Execute a single specification -f, --format FORMAT Builtin formats: specdoc|s|rdoc| r|html|h You can also specify a custom formatter class (in which case you should also specify --require) -r, --require FILE Require FILE before running specs...

Hey all, I have a spec that is hanging when it is running. How do I get the rspec runner to show what specs it''s running so I can which one is hanging? I am calling the runner from my rails project. Thanks, Ben

...#39;t jive well with rspec''s ability to write docs for you. For example, I use the rspec_expectation_matchers plugin from spicycode.com (scanned for a name, didn''t find one =), and end up writing specs like: it { @ticket.should validate_presence_of(:name) } Which results in specdocs such as: Ticket - NO NAME (Because of --dry-run) - NO NAME (Because of --dry-run) - NO NAME (Because of --dry-run) The examples_specdoc task for rspec itself, however, doesn''t use --dry-run. Using dry runs presumably speeds things up significantly, but results in "broken&q...

Thanks for posting your specdoc, Brandon -- they''re a great example. On 11/21/06, Brandon Keepers <bkeepers at gmail.com> wrote: > > A user purchasing items > - should create an order > - should add to the user''s orders > - should create line items > - should set line item amount to the...

hi I''m using restful_authentication and have controller specs working using users fixtures (and login_as) however i''ve been trying for hours without success to do it without fixtures, using mocks and stubs instead. anyone here done this? got code? :) thanks

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

hi, When running rails spec tests is there a log file generated? i''m looking for generated sql to help me debug like in development.log or is there a way to run the test against a webrick server so i can see logs? (i''m not running with spec_server at the moment, it doesnt seem to work well with autotest) thanks linoj

....png'') end end # controller.rb require ''sinatra'' require ''fileutils'' post ''/'' do tempfile = params[''file''][:tempfile] FileUtils.copy_file(tempfile.path, ''files'') end But when I ran... $ spec -f specdoc controller.rb ...I get the following output. Application - should accept uploaded files and save them into the `files` directory (FAILED - 1) 1) ''Application should accept uploaded files and save them into the `files` directory'' FAILED expected [] to include "files/test_fi...

...-- ActionController::UnknownAction in ''MembershipsController handling PUT /project/ID/membership/N/accept should flash message'' No action responded to accept --- but if I run the spec file individually, all the examples pass with no failures $ script/spec --color --format specdoc spec/controllers/ memberships_controller_spec.rb My routes.rb contains map.resources :projects do |project| project.resources :memberships, :member => { :accept => :get } ... end but I have other resources with :member actions defined and they spec ok This is completely repeat...

...pecs in spec directory (exc... rake spec:clobber_rcov # Remove rcov products for rcov rake spec:controllers # Run the specs under spec/controllers rake spec:db:fixtures:load # Load fixtures (from spec/fixtures) i... rake spec:doc # Print Specdoc for all specs (excludi... rake spec:helpers # Run the specs under spec/helpers rake spec:lib # Run the specs under spec/lib rake spec:models # Run the specs under spec/models rake spec:plugin_doc # Print Specdoc for all p...

Hi! I was just wondering how you typically generate a spec HTML report in a Rails app. Currently I''m doing something like this: spec spec -f h:spec/spec_report.html But that seems sort of clumsy and I would have thought that there was a rake task for it. Have I overlooked something? Thanks! Peter ---------------------------- Peter Marklund Garvar Lundins Gr?nd 7 11220 Stockholm

...oller some other facet'' end And corresponding ApplicationController subclass specs: describe OtherController do it_should_behave_like ''ApplicationController'' end Both of the shared behaviour blocks get executed twice when running the subclass specs; the specdoc output looks like: OtherController - foo - bar - abc - xyz - abc - xyz - foo - bar And note that it''s running the shared behaviours in this order: - ''one facet'' - ''some other facet'' - ''some other facet'...

...* progress, but thought I''d throw it to the list * I run ruby, including rb-rubygems using the MacPorts install (per JDD''s Sandboxing Rails) * installed rspec 0.9.4 (also rcov 0.8.0.2 and ZenTest 3.5.2) * tried the game.rb /game_spec.rb demo * running $ spec game_spec.rb --format=specdoc works great * installed the RSpec 0.9.4 tmbundle by downloading it and clicking -- nothing fancy #game.rb class Game def hit(pins) end def score 0 end end # game_spec.rb require ''game'' describe Game do before(:each) do @game = Game.new end it "shoul...

This is pretty much the same as last time around, if you recall. Thanks to Wilson for converting to the new form. I''ve added a few lines. Basically, it iterates over your model associations and does two things. - First, just try to call the association. Usually fixes speeling erors or other such silliness. - Second, try to find a record with an :include on the association. This

...'s subversion under trunk/vendor/watir http://rubyforge.org/scm/?group_id=797 http://rubyforge.org/plugins/scmsvn/viewcvs.php/trunk/vendor/watir/?root=rspec There is a README where I try explain some of the benefits of the RSpec/Watir combo - from a user/qa/tester perspective. RSpec''s specdoc feature, documentation and communication is key here. Please take a look and give some feedback. I''d like to put this up on RSpec''s web page soon. Aslak

...e lib\/spec,bin \/spec,config\/boot.rb -o "coverage" "/usr/local/lib/ruby/gems/1.8/gems/rspec-1.1.1/bin/spec" -- "spec/controllers/goodbye_merb_spec.rb" "spec/helpers/goodbye_merb_helper_spec.rb" "spec/views/goodbye_merb/index_html_spec.rb" --format specdoc --colour failed (See full trace by running task with --trace) rake aborted! Command failed with status (1): [rake rcov...] /project/merb/test_app/rakefile:100 (See full trace by running task with --trace) eoghan-js-Computer:test_app eoghanj$ Thanks Eoghan

Hi! I wonder does anybody planning to go beyond the default html formatter/report? The current html report is nice and green but what about to go a little silly and enable also user input. For example to let customer to add a new pending spec, comments etc. I feel it might be mentally easier for some customers to jump into spec world when it is possible to give input at "the same