[Sloth-devs] [ sloth-Stories-1750648 ] Plugin Support

[SourceForge.net <no...@so...>]

Stories item #1750648, was opened at 2007-07-09 15:40
Message generated for change (Comment added) made by grahambrooks
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=973428&aid=1750648&group_id=200319

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Graham Brooks (grahambrooks)
Assigned to: Nobody/Anonymous (nobody)
Summary: Plugin Support

Initial Comment:
As a developer I would like to extend Sloth (perhaps with a plugin architecture) so I can add concepts and capabilities that are not currently available.

----------------------------------------------------------------------

>Comment By: Graham Brooks (grahambrooks)
Date: 2007-07-09 16:12

Message:
Logged In: YES 
user_id=635168
Originator: YES

Some implementation thoughts

If the page/suite implemented an operational context interface that
allowed 'fixture' resolutions to be defined by an appropriate plug-in then
things like do fixtures could add their own custom resolvers within the
page context. The resolvers would act like a stack with each deferring to
its parent if it cannot resolve a name.

Type adapters could be implemented in a similar way. A type adapter would
be constrained by scope (field type, field type & fixture type etc). These
could be declared in the page in properties or dynamically by the loaded
fixture adapters.

This would make the page a declarative framework that can be extended and
more importantly provides a useful construct for maintaining state during
test execution

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=973428&aid=1750648&group_id=200319