[Ogden] Ogden specs
Mark Van De Vyver
Is there any reason/benefit for Ogden to buck the rspec naming
conventions ./spec/*_spec.rb?
On the topic of specs:
What a spec file actually describes gets opaque when multiple classes
are in a single file.
Is it classed as minor (i.e. branching not required) to reorganize
when writing a spec? Renaming classes?
Cheers
_______________________________________________
Ogden-developers mailing list
Ogden-de...@rubyforge.org
http://rubyforge.org/mailman/listinfo/ogden-developers
Judson Lester
I've actually been focusing on cleaning up specs in my branch. I'd agree with you: there's a value to following convention wrt /spec/*.rb - but *_spec.rb isn't completely universal, and I for one find it redundant.
Your other points are subject to larger discussion, I think. I'd tend to think that a group of examples often describes a class, but Ogden is a very different project in a lot of ways, and it makes sense to describe "validation" in one place as opposed to Og::Model.
Judson
--
Your subnet is currently 169.254.0.0/16. You are likely to be eaten by a grue.
Mark Van De Vyver
On Dec 21, 2007 8:55 AM, Mark Van De Vyver <mvy...@gmail.com> wrote:
> On Dec 21, 2007 6:12 AM, Judson Lester <nya...@gmail.com> wrote:
> > Mark,
> >
> > I've actually been focusing on cleaning up specs in my branch. I'd agree
> > with you: there's a value to following convention wrt /spec/*.rb - but
> > *_spec.rb isn't completely universal, and I for one find it redundant.
This probably depends on how specs are run and how files are
organized: Not every file under ./spec will be a spec file.
Probably not serious.
> > Your other points are subject to larger discussion, I think. I'd tend to
> > think that a group of examples often describes a class, but Ogden is a very
> > different project in a lot of ways, and it makes sense to describe
> > "validation" in one place as opposed to Og::Model.
>
Perhaps we should put something in the wiki with suggestions about how
specs are organized and tips/hints for writing them?
Cheers
> I was thinking more of the case where you have several classes in one file.
> and classes and modules in a file.
> Yep, spec's become tricky since it can be difficult to separate
> adapter behavior.
> We may have to live with some level of duplication?
>
> Cheers
>
>
> > Judson
> > --
> > Your subnet is currently 169.254.0.0/16. You are likely to be eaten by a
> > grue.
>