Re: [Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-28 Thread Dieter Maurer
Stephan Richter wrote at 2005-11-28 08:02 -0500: > ... >If people would use the mechanize objects, >their test code could not be converted to tutorials. Then some test could not be converted to tutorials... Is that really worse than being unable to test quite interesting use cases (such as file u

Re: [Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-28 Thread Chris Withers
sureshvv wrote: I am +1 on the substance of the text and -0 on the style ;) Yes, I do want to change it when I get a chance so that it's clearer that these docs are _only_ there because testbrowser doesn't currently support the required functionality... Chris -- Simplistix - Content Manag

Re: [Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-28 Thread Chris Withers
Stephan Richter wrote: I'll just note that I am +1 on all of Benji's comments. And I will remove the offending checkins before I cut the branch, if noone else does. Given that there are currently more people in favour of having useful docs than a pedantic exclusion policy, please _don't_ remov

Re: [Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-28 Thread Stephan Richter
I'll just note that I am +1 on all of Benji's comments. And I will remove the offending checkins before I cut the branch, if noone else does. Here my reasoning. I am currently writing a tool that allows you to convert testbrowser tests into tutorials. That means that I am providing an alternati

[Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-28 Thread sureshvv
Benji York wrote: Chris Withers wrote: """ testbrowser currently doesn't help much unless you already know the controls you will be looking for, however, you can do some introspection by utilizing the underlying mechanize functionality. """ """ Unfortunately, testbrowser doesn't really supp

Re: [Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-25 Thread Dieter Maurer
Benji York wrote at 2005-11-25 11:17 -0500: > ... >They are clear in what they say, but they do not say that a user of >zope.testbrowser shouldn't depend on them and that they may go away at >any time. Even if it did I don't think that would be sufficient, I >don't think the docs should mention

[Zope3-dev] Re: zope.testbrowser and mechanize

2005-11-25 Thread Benji York
Chris Withers wrote: Benji York wrote: I actually don't want to support any exposure of mechanize functionality in zope.testbrowser. Mechanize is an implementation detail (although a very important one) and may change in the future. I think the documentation I added makes this clear. It do