On 23.2.2008, at 4.00, Joe Van Dyk wrote:
How are you using both autotest and the stories?
I use Geoffrey's rstakeout (http://nubyonrails.com/articles/automation-with-rstakeout
) to watch a single story (running all stories a la autotest is too
slow) and /app, and autotest in a different ter
Andreas Axelsson-2 wrote:
>
>> > Does the plain text story framework support teardowns? There doesn't
>> seem to
>> > be anywhere to put an "after" method.
>
>>For now I'd stick this in a Given that
>> you use at the beginning of each scenario, for example:
>>
>> Given "the stash is in a clean
Sometimes I need a spec that tests something which can't work inside a
transaction. Is it possible to disable transactional fixtures for one
spec?
I tried:
describe "MyClass without transactional fixtures" do
before(:all) do
Spec::Runner.configure { |config|
config.use_transactional_fixture
Hi, I'm mostly quite happy using autotest with rspec, but there's one
thing that's been bothering me, and as my test suite grows larger it'd
becoming more painful.
Autotest re-runs the entire suite whenever a spec that had previously
failed passes for the first time. I find that incompatible with
On Fri, Feb 22, 2008 at 11:18 AM, Paul Dowman <[EMAIL PROTECTED]> wrote:
> Hi, I'm mostly quite happy using autotest with rspec, but there's one
> thing that's been bothering me, and as my test suite grows larger it'd
> becoming more painful.
>
> Autotest re-runs the entire suite whenever a spe
On Fri, Feb 22, 2008 at 11:21 AM, Paul Dowman <[EMAIL PROTECTED]> wrote:
> Sometimes I need a spec that tests something which can't work inside a
> transaction. Is it possible to disable transactional fixtures for one
> spec?
>
> I tried:
>
> describe "MyClass without transactional fixtures" do
Any reason why there isn't a rake task for stories yet? (I'm looking in trunk)
Someone want to share theirs?
Joe
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Feb 23, 2008, at 12:16 PM, "Joe Van Dyk" <[EMAIL PROTECTED]> wrote:
> Any reason why there isn't a rake task for stories yet? (I'm
> looking in trunk)
There is one for rspec_on_rails but it is nothing special. It just
calls stories/ all.rb which is up to you to maintain.
I know of at lea
On Feb 22, 2008, at 12:18 PM, Paul Dowman wrote:
> Hi, I'm mostly quite happy using autotest with rspec, but there's one
> thing that's been bothering me, and as my test suite grows larger it'd
> becoming more painful.
>
> Autotest re-runs the entire suite whenever a spec that had previously
> f
Brian Takita wrote:
There are automated & manual tests.
Automated customer facing & Automated developer tests.
Both customer facing and developer tests can have a unit, functional,
and integration scope.
That being said, you can have effective high level developer Specs.
They certainly can, but
On Sat, Feb 23, 2008 at 10:41 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Feb 23, 2008, at 12:16 PM, "Joe Van Dyk" <[EMAIL PROTECTED]> wrote:
>
> > Any reason why there isn't a rake task for stories yet? (I'm
> > looking in trunk)
>
> There is one for rspec_on_rails but it is nothing sp
On Sat, Feb 23, 2008 at 6:10 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 22, 2008 at 11:18 AM, Paul Dowman <[EMAIL PROTECTED]> wrote:
> > Hi, I'm mostly quite happy using autotest with rspec, but there's one
> > thing that's been bothering me, and as my test suite grows larger
On Sat, Feb 23, 2008 at 2:35 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> On Sat, Feb 23, 2008 at 10:41 AM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> > On Feb 23, 2008, at 12:16 PM, "Joe Van Dyk" <[EMAIL PROTECTED]> wrote:
> >
> > > Any reason why there isn't a rake task for stories yet? (I
On Thu, Feb 21, 2008 at 8:09 AM, Chuck Remes <[EMAIL PROTECTED]> wrote:
> While practicing BDD on my first-ever BDD project, I have come to a
> point where it makes sense to change my original class to an abstract
> class and create one (or more) concrete subclasses that implement a
> specific m
14 matches
Mail list logo
