[Nitro] Isolated specs bundle

Judson Lester nyarly at gmail.com
Fri Mar 9 13:17:51 EST 2007


Is there a point to that other than the output?  Because you can just
as easily do

context "Og PostgreSQL Model" do
end

It does bring up the question that lingers with me: is there a more
flexible way to test different stores?  I suppose creating a bunch of
files with "config=:storename" and then requiring them, a la -rdebug
or whatnot.  I just think it'd be extra cool to be able to run the
specs against all the DB types that you have ready for it.

Judson

On 3/9/07, Michael Fellinger <manveru at weez-int.com> wrote:
> On Tue, 06 Mar 2007 16:32:56 +0900, George Moschovitis
> <george.moschovitis at gmail.com> wrote:
>
> > Judson,
> >
> > if possible please break your specs in more specify blogs  so that we
> > get a better (more descriptive) implementation. For example:
> >
> > specify "should provide standard og features" do
> >
> > is too general and could possibly be splite in more blocks.
> >
>
> Please note that you can nest the contexts...
> which gives you something like "Og PostgreSQL Model should create_with"
> for:
>
>    context "Og" do
>      context "PostgreSQL" do
>        context "Model" do
>          specify "should create_with" do
>            user = User.create_with :age => 42
>            user.age.should == 42
>          end
>        end
>      end
>    end
>
> nothing big, just wanted to point it out (one can generate nicer docs from
> the specs afterwards and they just look better on errors)
>
> ^ manveru
>
> > thanks for your work,
> > George.
> >
> >
> > PS: btw, please use attr_accessor instead of property!
> >
> >
> >
> >
>
>
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>


More information about the Nitro-general mailing list