[Rspec-devel] Nested contexts

[itsme213]

From: "David Chelimsky" <dchelimsky at gmail.com>

> Structures like nested contexts are going to
> lead to degredation in clarity

I am curious what this is based on.

If it is based on the experience with the x-Unit family then is that really 
the right comparison? The best written and most readable specs I have seen 
(not in the context of TDD) have very clear nested tables of contents. Not 
everything fits this structure, but it helps more than enough that I would 
hate to read or maintain those specs as a 2-level flat list.

Some uses of that nesting are for things that may not correspond to (say) 
chains of initializers (r-spec setups). I think that is a separate matter. 
If the structure is useful enough, why rule it out? Why not figure out the 
variations in its use?

> I do think that we'll have to address the duplication issue at one
> point,

What kind of ratio do you expect (in the very near term) for:
    Lines-of-Spec / Lines-of-Code

Isn't there evidence that the ratio is close to 1, or even > 1?