[rspec-devel] [Proposed Refactoring] - Example -> ExampleDefinition && ExampleSpace -> Example

David Chelimsky dchelimsky at gmail.com
Thu Aug 23 07:55:08 EDT 2007


On 8/23/07, Jay Levitt <lists-rspec at shopwatch.org> wrote:
> On 8/23/2007 5:59 AM, David Chelimsky wrote:
> > On 8/23/07, Brian Takita <brian.takita at gmail.com> wrote:
> >> This object is currently responsible for:
> >> * Running the Example (this includes all lifecycle management)
> >> * Storing the Example description
> >> * Determining if the Example description matches another Example description
> >>
> >> I think these names encompass the all of the behaviour:
> >> * ExampleWrapper
> >> * ExampleDriver
> >> * ExampleContainer
> >> * ExampleLifeCycle (possibly)
> >
> > ExampleWrapper and ExampleLifeCycle both express (to me) the
> > one-to-one mapping to Example that exists. Runner, Driver, and
> > Container all suggest collections to me, so I'd avoid these.
> >
> > Of these, I think ExampleLifeCycle is the most interesting, but I'm
> > not convinced that the best name has appeared yet.
>
> Is ExampleOverseer too much like ExampleManager?
> ExampleChaperone?   ExamplePilot?  ExampleBrain?
>
> It's hard to think of things that control/manage a single other thing
> without controlling/managing a collection.

ExampleFrame
ExampleBox
ExampleHolder
ExampleHolster
ExampleSheath
ExampleScabbard
ExampleOwner
ExampleHousing
ExampleIntegument (look THAT one up)
ExampleEnvelope
ExampleSleeve
ExampleJacket
ExampleAgent
ExampleProxy
ExampleLaminate
ExampleVeneer

I'm beginning to think Brian's earlier idea ExampleDefinition might make sense.

>
> Jay
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>


More information about the rspec-devel mailing list