RSpactor

Comments and changes to this ticket

• 

  Andreas Wolff May 3rd, 2008 @ 08:50 PM

  • → State changed from “new” to “invalid”

  Hm.. Could you explain it a litte more? The ticket description seems to have an error :)

• 

  steve May 4th, 2008 @ 04:59 AM

  A set of specs that pass with rspactor and pass with rspec (rake spec) fail when a new example is introduced that is pending. For example:

  it "should do something but I'm not sure what yet"

  -or-

  it "should do something but I'm not sure what yet" od

  pending "I get motivated"

  end

• 

  Andreas Wolff May 4th, 2008 @ 03:55 PM

  • → State changed from “invalid” to “hold”

  Ok.. I think we come a little closer.. You have passing specs, which start to fail as soon as a new pending spec is introduced?

• 

  steve May 4th, 2008 @ 07:18 PM

  The specs pass from rake at the command line after the pending spec is introduced. My apologies on the first bug report. Seems like a bad example of copy/paste. Here is what happens:

  $ rake spec

  Pending:

  Client should do something else (Not Yet Implemented)

  Finished in 0.281817 seconds

  rspactor:

  reporter.rb:110:in `example pending': wrong number of arguments (2 for 3)

  Note: copy in the details box does not work. I'll file it separately.

• 

  Andreas Wolff May 5th, 2008 @ 08:50 PM

  • → State changed from “hold” to “open”
• 

  Jeff June 1st, 2008 @ 09:18 PM

  confirmed in the plugin. (can't get the gui to run - a readme would be nice)

  This is only present in newer versions of rspec (git versions, 2.1 compatible, etc.)

  for the plugin, the fix is as simple as editing lib/resulting.rb line 28 to remove a parameter.

• 

  Andreas Wolff August 4th, 2008 @ 12:20 AM

  • → State changed from “open” to “resolved”
  • → Tag changed from “” to “bug core”