This is awesome!
Many thanks
- Andy
David Chelimsky-2 wrote:
Thanks to discussions on this list, suggestions from many of you and a
patch from Pat Maddox, we now have Plain Text User Stories in Story
Runner.
Read more:
Of course when I said Pat, I in fact meant David and his monkey :)
On 10/22/07, Pat Maddox [EMAIL PROTECTED] wrote:
On 10/22/07, Dan North [EMAIL PROTECTED] wrote:
Haha - brilliant! I was just putting something together myself based on
the
original thread but it looks like Pat has a)
On 10/23/07, Matt Lins [EMAIL PROTECTED] wrote:
Hey Guys,
I'm getting the following error:
1)
NameError in 'ProductsController with a GET to /products NO NAME (Because
of Error raised in matcher)'
uninitialized constant
Spec::Mocks::BaseExpectation::AnyArgsConstraint
I want to create a spec/regressions directory with various
regressions (for my rails project). I tried the following:
describe LoginController, regression for user creation when
steves_sister does not exist, :behavior_type = :controller do
controller_name :login
before :each do
http://www.georgeglazer.com/prints/illus/wein-monkeydress.JPG
On Oct 23, 2007, at 11:11 AM, Dan North wrote:
Of course when I said Pat, I in fact meant David and his monkey :)
On 10/22/07, Pat Maddox [EMAIL PROTECTED] wrote:
On 10/22/07, Dan North [EMAIL PROTECTED] wrote:
Haha -
On 10/23/07, David Chelimsky [EMAIL PROTECTED] wrote:
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
I want to create a spec/regressions directory with various
regressions (for my rails project). I tried the following:
describe LoginController, regression for user creation when
Hi,
Updated from the trunk/edge again today however all the specs still fail as
before.
I uninstalled and moved back to the 1.0.8 release and all specs are
successful again.
Unfortunately, no Story Runner.
Cheers!
sinclair
On 10/22/07, sinclair bain [EMAIL PROTECTED] wrote:
Morning,
Having
Sorry about that.
This spec was never tried on 1.0.5. I upgraded to 1.0.8 and immediately
wrote the spec following the documentation on the Rspec site.
I assumed it may have had something to do with the upgrade, since the
controller spec was so simple.
Just to clarify:
I upgraded the
On 10/23/07, sinclair bain [EMAIL PROTECTED] wrote:
Hi,Updated from the trunk/edge again today however all the specs still fail
as before.
I uninstalled and moved back to the 1.0.8 release and all specs are
successful again.
Unfortunately, no Story Runner.
Sorry Sinclair, but I have no
Have you also piston'd:
svn://rubyforge.org/var/svn/rspec/tags/CURRENT/rspec_on_rails?
On 10/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On 10/23/07, Matt Lins [EMAIL PROTECTED] wrote:
I upgraded the Rspec gem to the latest.
I upgraded the rspec rails plugin to the latest.
I
On Oct 23, 2007, at 12:10 PM, David Chelimsky wrote:
On 10/23/07, David Chelimsky [EMAIL PROTECTED] wrote:
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
I want to create a spec/regressions directory with various
regressions (for my rails project). I tried the following:
describe
LOLOLOLOL.
You forgot the u:
behaviour_type
:)
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
On Oct 23, 2007, at 12:10 PM, David Chelimsky wrote:
On 10/23/07, David Chelimsky [EMAIL PROTECTED] wrote:
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
I want to create a
On Oct 23, 2007, at 1:15 PM, David Chelimsky wrote:
LOLOLOLOL.
You forgot the u:
behaviour_type
:)
Ouch. Wish I was British.
Ha. Thanks, David.
Scott
___
rspec-users mailing list
rspec-users@rubyforge.org
On Oct 23, 2007, at 1:15 PM, David Chelimsky wrote:
LOLOLOLOL.
You forgot the u:
behaviour_type
:)
Looks like I need to submit a patch! Haven't done that in a while.
Scott
___
rspec-users mailing list
rspec-users@rubyforge.org
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
On Oct 23, 2007, at 1:15 PM, David Chelimsky wrote:
LOLOLOLOL.
You forgot the u:
behaviour_type
:)
Looks like I need to submit a patch! Haven't done that in a while.
On Oct 23, 2007, at 1:32 PM, David Chelimsky wrote:
On 10/23/07, Scott Taylor [EMAIL PROTECTED] wrote:
On Oct 23, 2007, at 1:15 PM, David Chelimsky wrote:
LOLOLOLOL.
You forgot the u:
behaviour_type
:)
Looks like I need to submit a patch! Haven't done that in a while.
Ok
Using rails 1.2.3
rails trunk-error -d sqlite3
cd trunk-error
ruby script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/rspec
ruby script/plugin install
svn://rubyforge.org/var/svn/rspec/trunk/rspec_on_rails
ruby script/generate rspec
In an editor create the following model spec
Oops,
A bit over-zealous on the send.
As I meant to add
This was not the case last week. This did not occur until yesterday when I
svn upped the project (I had installed the rspec trunk as an svn:external).
This all occurs on WindowsXP
___
rspec-users
On 10/23/07, sinclair bain [EMAIL PROTECTED] wrote:
Oops,
A bit over-zealous on the send.
As I meant to add
This was not the case last week. This did not occur until yesterday when I
svn upped the project (I had installed the rspec trunk as an svn:external).
This all occurs on WindowsXP
On 10/23/07, David Chelimsky [EMAIL PROTECTED] wrote:
On 10/23/07, sinclair bain [EMAIL PROTECTED] wrote:
This all occurs on WindowsXP
Ah - I am therefore not able to help debug this precisely
In case this wasn't clear - because I don't have that OS available :)
On 10/23/07, sinclair bain [EMAIL PROTECTED] wrote:
David,
This does the trick.
However this is the same in the REL_1_0_8 tag yet that works as before. The
only thing which changed being the rspec plugin versions.
So it looks like something else may have changed, I am wondering if this was
OK.
Looks like this whole area has been worked upon.
In the trunk the
rspec_on_rails/lib/spec/rails/dsl/behaviour/
directory has been reworked.
The rails_example.rb file contains the class method #before_eval where the
error is sourced.
In REL_1_0_8 this functionality was in the base.rb
On 10/23/07, sinclair bain [EMAIL PROTECTED] wrote:
So ... somewhere in there lies the cause.; )
Anyway I get the Story Runner back with the manual config modification so
that's where we want to be.
Just to be clear - that's where you *should* have been all along. It
looks
Bleeding-edge story-writers,
How are you structuring your specs?
I am working on a new project and tried this:
./lib
./blah
./spec
./blah
./stories
But it breaks autotest, so I moved stories parallel to lib and spec.
Also what about suffixes?
I have adopted xyz_story_spec.rb, and
On Oct 23, 2007, at 9:55 pm, David Chelimsky wrote:
PROJECT_ROOT/behaviour/specs
PROJECT_ROOT/behaviour/stories
I like this
but then a rails view spec ends up being:
PROJECT_ROOT/behaviour/specs/views/controllername/
index.html.erb_spec.rb
pretty long, ay?
I don't mind long paths, I
On 10/23/07, David Chelimsky [EMAIL PROTECTED] wrote:
On 10/23/07, Ashley Moran [EMAIL PROTECTED] wrote:
Bleeding-edge story-writers,
How are you structuring your specs?
PROJECT_ROOT/spec
PROJECT_ROOT/stories
They are intended to be separate beasts. This makes it more obvious.
One
On Oct 23, 2007, at 11:02 pm, Ashley Moran wrote:
Is there an easy way to get autotest support for behaviour/spec? I
just got it working but had to copy:
svn://rubyforge.org/var/svn/rspec/trunk/rspec/lib/autotest/
to ./autotest
Never mind... I found out it broke the new twin-file
On 10/23/07, Ashley Moran [EMAIL PROTECTED] wrote:
PS I did all this messing around in darcs - working with a patch
based SCM makes life much easier. I worked in a test branch, then
applied the patches from the test repo to the main one, but I was
still able to unrecord them there, something
app is short for application,
lib is short for library
so why not shorten behavior to something like beh or behav
(also avoids the 2 english spellings)
/beh/specs
/beh/stories
On Oct 23, 2007, at 6:02 PM, Ashley Moran wrote:
On Oct 23, 2007, at 9:55 pm, David Chelimsky wrote:
On 10/23/07, Jonathan Linowes [EMAIL PROTECTED] wrote:
app is short for application,
lib is short for library
so why not shorten behavior to something like beh or behav
(also avoids the 2 english spellings)
/beh/specs
/beh/stories
beh
that's why :)
Nice work David! This is a wonderful step in the right direction!
Zach Dennis
http://www.continuousthinking.com
On 10/21/07, David Chelimsky [EMAIL PROTECTED] wrote:
Thanks to discussions on this list, suggestions from many of you and a
patch from Pat Maddox, we now have Plain Text User
On Tue, 23 Oct 2007 17:58:45 -0500, David Chelimsky wrote:
I don't know if there are any repercussions, but just adding :text to the
array in
rspec_on_rails/lib/spec/rails/dsl/behaviour/view_example.rb:subject_of_render
was enough to make it work.
That's cool, but that's not how we do
Hi,
Anyone know a way to traverse/query the DOM in a response?
I'm trying to write reusable story step implementations and as much as
possible want to work with the actual response from a previous GET.
As an example, I often have buttons that POST/PUT a hidden value.
My goal is a reusable step
I completely forgot about Hpricot
http://code.whytheluckystiff.net/hpricot/
Looks perfect for this.
- Andy
Andy Watts wrote:
Hi,
Anyone know a way to traverse/query the DOM in a response?
I'm trying to write reusable story step implementations and as much as
possible want to work
Hi all,
The following only affects people who have bravely begun to experiment
with the 2 day-old plain text story runner and definable groups of
steps.
For those who fit that bill, I just committed a few changes that will
require you to make changes to your code.
The StepMatchers class is now
35 matches
Mail list logo
