On Thursday 06 June 2002 06:10 pm, A. Keyton Weissinger wrote: > In the mean time, let me ask you (all) to consider this question: > Would you still want a script-based version as much if a GUI > prevented your exposure to the XML nastiness? In your experience with > QA professionals, do you think it would be useful to QA folks?
I can't answer the last question. Yes, I'd still want the Pythonic version over the GUI because of the power that I get by having access to libraries. I mean, how else do I iterate over the test users in the test database? And even providing that, I will eventually come up with something. In any case, I don't see the conflict. Wouldn't this approach work?: - Make testing framework oriented towards Python, like I described. - Make DeclarativePlan(Plan) class that can handle the XML declarative format (and perhaps a Python dictionary declarative format) like what you have now. - Make a GUI for the convenience of declaring DeclarativePlan instances. Now everyone can have cake and frosting! Also, consider using Purcell's framework (unless you have some beef with it) as the bottom layer in this rich testing framework. Food for thought. I could be missing some issues. -Chuck -- http://webware.sf.net/ _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
