For some reason I heard that reply in Eric Cartman's voice.
"beh... you guys"
fwiw I prefer separate directories - stories and specs - because they are
targeted (intentionally) at different audiences.
I started off trying behaviour/specs and behaviour/stories but then I
thought about who would a
On Oct 23, 2007, at 6:32 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)
>>
>> /b
On the note of suffixes, I've been using _story over _spec for story files.
I have also add two top level directories in my project:
project/
specs/
stories/
Zach
On 10/23/07, Ashley Moran <[EMAIL PROTECTED]> wrote:
>
> Bleeding-edge story-writers,
>
> How are you structuring your s
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 :)
__
"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, 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, somet
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 fe
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 ob
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 p
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 thing we've toyed with is:
PROJECT_ROOT/behaviour/specs
PROJ
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 "
11 matches
Mail list logo
