Re: [rspec-users] Preconditions

2007-09-09 Thread David Chelimsky
On 9/8/07, Ben Mabey [EMAIL PROTECTED] wrote:
 What was the motivation behind taking that tutorial down, BTW?  I really
 like and benefited from it when I was starting to learn rspec.  Was it
 just a  maintenance issue as far as updating the tutorial to the current
 API (DSL)?

That was part of the deal. The other part was that I thought it would
be more demonstrative to have something w/ two or more classes dealing
w/ interactions. Just never got around to it. We should probably
resurrect the Stack tutorial in the mean time.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users


[rspec-users] Going beyond the default html formatter/report?

2007-09-09 Thread Priit Tamboom
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 place.

Integrate to trac or very lightweight standalone stuff. However it
should not be trac reinventing effort.

I haven't use rspec with customer yet but planning to do so with next
project, so I might overreact about this matter right now.

Priit
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users


Re: [rspec-users] Failure Messages in RSpec + inline debugging of a spec

2007-09-09 Thread Luis Lavena
On 9/8/07, Jay Levitt [EMAIL PROTECTED] wrote:
 On 9/8/2007 4:19 PM, Scott Taylor wrote:
  So far it has been
  a mixed experience - I have found that it doesn't work very well with
  rails as you end up debugging more of rails then of your own code.

 Finally, a debugging environment that matches the production environment!


I agree.

When debug is required, I switch to script/spec and specify the exact
file and specification to run, in that way, reduce the problems
loading ruby-debug and getting my feet wet with Rails code :)

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users


Re: [rspec-users] Going beyond the default html formatter/report?

2007-09-09 Thread aslak hellesoy
On 9/9/07, Priit Tamboom [EMAIL PROTECTED] wrote:
 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 place.

 Integrate to trac or very lightweight standalone stuff. However it
 should not be trac reinventing effort.

 I haven't use rspec with customer yet but planning to do so with next
 project, so I might overreact about this matter right now.


This sounds like a fantastic idea. Why don't you give it a shot?

Aslak


 Priit
 ___
 rspec-users mailing list
 rspec-users@rubyforge.org
 http://rubyforge.org/mailman/listinfo/rspec-users

___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users