search for: spec_serv

I have looked through the docs, looked at the code, even gave a cursory (2 page) glance at google, and it is not clear to me what SpecServer is or what it is for. Is it meant to speed up the execution of specs in a rails environment by doing some magic on the database? Or I am thinking it keeps a copy of Rails running to avoid the rails reload delay... Is there any documentation on this so I

I have some specs that ''require'' other files. When running spec_server, if these required files are changed, it''s not picked up when the specs are run. I have to restart spec_server to get the changes recognized. Is there an option or some such to have spec_server reload required files as well when a spec is run? Thanks, Steve

hi all I''m seeing strange behaviour when running specs using spec_server. They take longer to execute, and it looks like none of examples are being run. here''s the output for a simple spec file using just the spec command: ---------- foo at holly:~/rails/allison$ time ruby/script spec spec/models/listing_spec.rb ...... Finished in 0.060469 seconds 6 exampl...

Hi everyone. I can''t get the above(subject line) combination to work. If I use a standard sqlite3 file db for the test db, and spec_server all the specs on my models pass. If I use an in-memory db for the test db, script/spec w/o spec_server, they all pass. But if I use in-memory and spec_server I get the following error: 1) ActiveRecord::StatementInvalid in ''User should be valid'' ActiveRecord::StatementInvalid ./s...

Hey guys, I''m running spec_server and using --drb with my specs in Rails, and I''m seeing virtually no speed up. I''m using rspec/rspec_on_rails trunk. Is there something I''m doing wrong? TIA, Jeremy -- Jeremy Stephens Computer Systems Analyst I School of Medicine Department o...

Hello, Running RSpec without DRB works fine. However, "spec -X" runs without error but provides no output at all, even though the DRB spec_server seems to be fine. Has anyone got some suggestions as to why and how to fix? RSpec: 1-1-0RC1 build time 20071212145122 RSpec on Rails: Build time 20071212145122 Ruby: 1.8.6 Rails: 2-0-1 Win XP SP 2 Thanks very much, Dave -------------- next part -------------- An HTML attachment was scrubbed......

hi all a few days ago i reported spec_server didn''t appear to be running specs and the command itself was running slowly. I''ve since tried it on a new system with a clean install of ubuntu 7.04, rails 1.2.3 and rspec 1.0.2 and I''m seeing the same behavior. *** without spec_server *** x at holly:~/rails/test$ time...

hi all I''m trying to use spec_server to run my specs in rails, but the specs don''t seem to be running any faster, and it looks like they''re being run twice when I use the --drb option ..? The app I''m testing is just a basic rails app with 2 empty models and a hello world controller. The specs are just the...

...k::Utils.parse_query to convert query strings to hashes. Closes #872. * errors correctly bubble up when a controller spec in isolation mode requests a non-existent action/template * no error if either action or template exist * error if neither exist * Closes #888. * removals * spec_server has been removed in favor of spork. * You can still use the --drb flag, but you''ve got to install the spork gem. * Windows users who cannot use the spork gem can install the spec_server from http://github.com/dchelimsky/spec_server

...as a gem, there is no spec command for the command line. That might make it easier to run my specs with options. So, I installed rspec 1.1.3 as a gem. That provided me with the spec command that I can issue on the command line. What is the recommended way to start the spec-server? ./script/ spec_server or rake:spec:server:start? I''ve tried both and cannot discern the differences. Finally, what is the recommended way to run my specs? spec -O spec/ spec.opts spec/XXX or rake spec:XXX ? I''ve edited spec.opts to include --drb on the first line. The rake method didn''...

Windows XP SP 2 ruby 1.8.5 gems: rails 1.2.3 rake 0.7.3 win32console 1.0.8 plugins: rspec 1.0.8 rspec_rails 1.0.8 spec.opts: --colour --format progress --loadby mtime --reverse --drb When I run "rake spec" or "ruby script/spec spec --color" this is the output: D:\dev\project>rake spec (in D:/dev/project)

Is the rspec_autotest plugin mentioned here, http://blog.nicksieger.com/articles/2006/11/15/rspec-autotest-now-a-rails-plugin the accepted method of auto testing specs? It''s an old article, and after grabbing the plugin, and giving it a run, it fails with: $ rake spec:autotest:rails trunk/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/rails_example.rb:31: undefined method

When do these files, along with lib/spec and lib/spec_server get created? I tried to create a quick test project and can''t remember how they were created in a previous project. Thanks -- Posted via http://www.ruby-forum.com/.

...om the first arg passed to describe in view specs * separate routing specs (in spec/routing) * bug fixes * you no longer *have* to load ActionMailer to get specs to run. Closes #650. * query_params are now parsed by Rack::Utils.parse_query in redirect_to matcher. Closes #684. * cleaned up spec_server (there was a bunch of pre-rails 2.0 material). Closes #685. * rspec''s rake tasks are not loaded when running "rake gems" or any of its subtasks * only warn when rspec is not installed when trying to invoke an rspec rake task * support 2 arg version of ActionController::Ba...

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

Is there something currently going on on the rspec trunk that causes a massive slowdown when running rake spec and autotest (without spec_server)? I updated to the latest trunk yesterday and the time needed to run the specs of my app jumped from ~20 seconds to more than a minute. The weird thing is that if I run the rake spec tasks separately (controllers, models, views, helpers), they still take about 20 seconds in total: http://...

Just ran svn up this morning, and got this (after running ./script/ generate rspec) escher: ./script/spec spec/models/item_spec.rb Finished in 8.0e-06 seconds 0 examples, 0 failures ./script/spec:4:in `run'': wrong number of arguments (3 for 1) (ArgumentError) from ./script/spec:4 Using rails 1.2.3, rspec trunk, on Mac OS X.4.9. Any ideas, or is this a bug in

...or all plugin specs rake spec:plugins # Run the specs under vendor/plugins (... rake spec:plugins:rspec_on_rails # Runs the examples for rspec_on_rails rake spec:rcov # Run all specs in spec directory with... rake spec:server:restart # reload spec_server. rake spec:server:start # start spec_server. rake spec:server:stop # stop spec_server. rake spec:translate # Translate/upgrade specs using the bu... rake spec:views # Run the specs under spec/views Macintosh-2:myequity greg$ =====...

...c -X spec'' to execute my specs. Now that I added ZenTest on it, found that the test takes longer to run due the complete load of test environment. Since autotest uses ''script/spec -O spec/spec.opts'' as the command, I decided to add --drb to spec.opts Using --drb or -X, spec_server is just ignored and environment get loaded locally. Trying to pinpoint the problem, it seems that using -O don''t handle/load set --drb, but when you put all the options in the command line, works as expected. Couldn''t find anything besides this (rspec/lib/spec/runner/option_pa...

...find a solution. So if anyone has any suggestions, I''m all ears. Does script/server need to be running in conjunction with the spec server? I have "--drb" specified in spec/spec.opts . I start the spec server with either of these commands: $ rake spec:server:start $ script/spec_server and confirm that it''s running and listening: $ lsof -nPi | grep ruby ruby 20809 nick 4u IPv6 0x3c2e4bc 0t0 TCP [::1]:8989 (LISTEN) However, when I run any of these commands: $ rake spec:models $ spec -X spec/models/property_spec.rb $ script/spec -X spec/models/property_spec.rb This...