similar to: Edge rspec - running Test::Unit tests

With rspec 1.0.8 I have a spec in the directory: spec/units/controllers/application_controller_spec.rb require File.dirname(__FILE__) + ''/../../spec_helper'' class DummyController < ApplicationController def index raise "Prevent index from rendering" end end describe ApplicationController, "Handling errors in production", :behaviour_type =>

I generated a new rails app then installed rspec and rspec_on_rails from trunk. I then created a sample story: require File.dirname(__FILE__) + "/helper" Story "View Home Page", %{ As a user I want to view my home page So that I can get a birds eye view of the system }, :type => RailsStory do Scenario "Publisher with no videos" do When

There is an option "--reverse" to run examples in the reverse order which is good for detecting inter-dependencies between examples. Is it feasible for rspec to automatically switch between "forward" and "reverse" order each time a spec is run? My goal is to detect inter-dependencies sooner than later... Thanks Alvin.

After trying RailsStory for a few days, I have learned: 1. Rails testing support does not serve up static pages 2. RailsStory masks errors generated by the app under test 3. The masked errors are available in log/test 4. I should read log/test more often See http://pastie.caboo.se/107876 for an example for points 2 and 3 The welcome controller fails when the HTTP_USER_AGENT is missing.

Comments and suggestions for improving the specifications are welcome. Thanks, Alvin One example comparing context/specify (CS) with given/when/then (GWT) with a strategy pattern follows: Consider a pipeline transporting oil supplied by multiple partners. The amounts transported on behalf of each partner are recorded as transactions in a general ledger. There are multiple approaches to

Back in August David Chelimsky wrote: "FYI - I tried using the unit_record gem and there are some changes required in rspec to make it work, but they are trivial and it works great. The only trick is that the prevention of DB access is global per process, so you''d have to separate examples that hit the DB from those that don''t into two separate suites. I''ll explore

Hi, We just spent half an afternoon figuring out why "jruby -S rake spec" didn''t generate any output at all (no warnings) on an edge rails app. We were seeing different behaviour on different boxes, and after a while figured out that it was related to a missing diff-lcs gem on one box. HTH, Stefan -- Bekk Open Source http://boss.bekk.no -------------- next part

The RSpec Development Team is pleased to announce the release of RSpec-1.0.8. RSpec 1.0.6 is the "holy cow, batman, it''s been a long time since we released and there are a ton of bug fixes, patches and even new features" release. RSpec 1.0.7 and 1.0.8 deal with a regression introduced in 1.0.6 and a hiccup in releasing 1.0.7, respectively. == RSpec RSpec is a Behaviour Driven

That makes for an interesting problem. I cannot open port 24007 to allow RPC access. On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is > of glusterd. > glusterd will be listening in this port and all volume management > communication > happens via RPC. > > Thanks, >

Hi there, I installed the rspec on rails plugin for a new project today and guess what -- it blows up! All by other rspec on rails projects are working fine. I updated all gems & still no joy. Any ideas how I can troubleshoot this one ? Here''s my setup: - ruby 1.8.4 (2005-12-24) [powerpc-darwin8.7.0] - Rails 1.2.5 Installed with svn: ruby script/plugin install

Ccing glusterd team for information On Thu, Feb 8, 2018 at 10:02 AM, Alvin Starr <alvin at netvel.net> wrote: > That makes for an interesting problem. > > I cannot open port 24007 to allow RPC access. > > On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is of >

Hi Alvin, Yes, geo-replication sync happens via SSH. Ther server port 24007 is of glusterd. glusterd will be listening in this port and all volume management communication happens via RPC. Thanks, Kotresh HR On Wed, Feb 7, 2018 at 8:29 PM, Alvin Starr <alvin at netvel.net> wrote: > I am running gluster 3.8.9 and trying to setup a geo-replicated volume > over ssh, > > It looks

Hi all, For those of you checking out the Rails 2.0 preview release: RSpec-1.0.8 does not support Rails 2.0. Unfortunately, we''re in the middle of some big changes to the internals in trunk and won''t be in a position to do a release for another week or so. Therefore, if you are using the Rails 2.0 preview, you''ll need to use the RSpec trunk. Additionally, right now

Is it OK to go ahead and generate a Rails 2.0 project with RSpec 1.0.8? Am I likely to run into problems? Would it be best advised to wait or can I go ahead now? Thanks, Yitzhak -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071212/c6fcea0f/attachment.html

> If you run top what are you seeing on the %Cpu(s) line? %20 On Mon, Feb 8, 2016 at 9:30 PM, Alvin Starr <alvin at netvel.net> wrote: > Slow disks will show up as higher I/Owait times. > If your seeing 99% cpu usage then your likely looking at some other problem. > > If you run top what are you seeing on the %Cpu(s) line? > > > On 02/08/2016 02:20 PM, Gokan Atmaca

I am running gluster 3.8.9 and trying to setup a geo-replicated volume over ssh, It looks like the volume create command is trying to directly access the server over port 24007. The docs imply that all communications are over ssh. What am I missing? -- Alvin Starr || land: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin at netvel.net

This is interesting. The default rspec rake tasks generated by Hoe give you an rspec.rake file that looks like: > begin > require ''spec'' > rescue LoadError > require ''rubygems'' > require ''spec'' > end > So far so good. When you invoke rake to do something, say check_manifest > rake check_manifest > You

Before I chalk this up as a bug and report it, I just want to make sure I''m not doing something silly. Running ZenTest''s autotest on OS 10.4.10 with RSpec 1.0.8, drb, produces the following failed test: ActiveRecord::AssociationTypeMismatch in ''User should create an avatar with uploaded_data'' Avatar expected, got Avatar This only happens with that exact

I was sort of hoping that is was something simple like setting the "do_the_right_thing" flag. The libvirtd kicks out 2014-10-31 11:58:57.111+0000: 8741: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31 11:59:29.379+0000: 8840: error : virRegisterNetworkDriver:549 : driver in virRegisterNetworkDriver must not be NULL 2014-10-31

Hi all, We''ve moved the rspec website to http://rspec.info. We want http://rspec.org, of course, but someone is squatting on and has yet to respond to my email :( The 1.1.0 docs are there. The 1.0.8 docs are still at http://rspec.rubyforge.org for the time being. We''ll be archiving them at the new site soon. This new site is hosted on our shiny new sponsored slice at Engine