Re: Testing a package
- From: Joseph Pelrine <foo@xxxxxxx>
- Date: Fri, 09 Sep 2005 09:14:58 +0200
Bill Schwab wrote:
Joseph,
Thanks for the offer, Bill. Where do I find it?
It is in my goodies, in AcmeClassBrowser.pac.
And where do I find your goodies?
Aren't you following contrary goals here? On the one side, you say that the framework is too complicated for its' own good. On the other side, you want it to automagically figure out which resources the tests need. Sure, we could implement that, but the amount of meta-level magic necessary for such DWIM functionality would be much greater than what's there right now.> Also, I never heard any
comment from you on the TestResource paper...
DOH!!!! Sorry about that. I started to give it the review it deserves, and then got torn away from it.
You have done a nice job of describing the topic. However, I am stuck that the entire framework is, or at least appears to be, too complicated for its own good. That extends to resources. For example, in an ideal world, I would want the tests to know which resources they need vs. my needing to tell them. Resources could be singletons, and could have some layers of default cleanup: per session, never, other stuff in between that might make sense.
Long ago (in computer years anyway), I read something that suggested that GLORP used test resources to create huge schemas, and that work was done lazily or on demand vs. being done routinely. It sounded great, but I have never grasped how to get that level of service from the framework. In fairness to the framework, I've never much worked at it.The TestResources framework was developed for GLORP! Alan Knight asked me if it was possible to make the miminal change/addition necessary to SUnit to support resources. The implementation was reviewed and approved by him and IIRC 10 other heavy-hitters. We thought that this was enough review and criticism to get the resource support down to the simplest possible level. Maybe we were wrong.
Let me know if this sounds insightful (in which case I am probably done for now) or totally off the wall (in which case I need to re-read your documentation and give it another shot).>
Apologies again for letting it get lost in the stack.No problem. Thanks for your input. I'm constantly trying to improve the quality of the code I write, and constructive criticism is always helpful there. May I suggest, though, that you re-read the document while sitting at the computer and typing the example in? Resources really are much simpler to use than you make them out to be.
If anyone else is interested, the draft TestResource paper, as well as a number of other goodies, are available at http://www.metaprog.com/ESUG/.
Cheers Joseph .
- Follow-Ups:
- Re: Testing a package
- From: Bill Schwab
- Re: Testing a package
- References:
- Testing a package
- From: Fernando Rodriguez
- Re: Testing a package
- From: Joseph Pelrine
- Re: Testing a package
- From: Fernando Rodriguez
- Re: Testing a package
- From: Joseph Pelrine
- Re: Testing a package
- From: Bill Schwab
- Re: Testing a package
- From: Joseph Pelrine
- Re: Testing a package
- From: Bill Schwab
- Testing a package
- Prev by Date: Re: Testing a package
- Next by Date: Progress dialog getting lazy on me
- Previous by thread: Re: Testing a package
- Next by thread: Re: Testing a package
- Index(es):
Relevant Pages
|