[TIP] PythonTestingToolsTaxonomy: link to Selenium bindings for Python
geoff.bache at gmail.com
Sat Aug 27 02:52:38 PDT 2011
On Sat, Aug 27, 2011 at 7:15 AM, Mark Mc Mahon <mtnbikingmark at gmail.com> wrote:
> On Wed, Aug 24, 2011 at 3:19 PM, Geoff Bache <geoff.bache at gmail.com> wrote:
>> On Wed, Aug 24, 2011 at 6:32 AM, Robert Collins
>> <robertc at robertcollins.net> wrote:
>>> On Wed, Aug 24, 2011 at 1:24 PM, Laura Creighton <lac at openend.se> wrote:
>>>> I don't want things that appear to be unmaintained to be deleted.
>>>> I'm pretty hostile to the notion that somehting needs to have
>>>> active development in order to be useful, and I think that is
>>>> what you would be detecting. Some things may not have changed
>>>> since 2004 because nothing needed changing since 2004 -- plugins
>>>> in particular.
>>> +1 : I was about to say, the benefit of writing small focused things
>>> is that they rarely have to change.
>> Well OK, that can of course be true. But it can also be the case that
>> someone started a project and then got bored before it was finished,
>> which may be more common...
>> I think you can get an insight into this by the nature of the tool.
>> Plugins can be "small and focussed". GUI test tools tend not to be,
>> especially as the libraries they support themselves change over time.
>> I'd suggest we can do this on a case by case basis. Create a separate
>> reference page for stuff that appears unmaintained but still may have
>> some value. I (and others) can then post edit suggestions here along
>> the lines of :
>> Kiwi - delete
> " pyWinAuto - unmaintained"
> I guess I shouldn't be surprised - I have done so little with the
> module in such a long time. If there is anybody out there that would
> like to help - I would be glad to let them.
> Or maybe it would be better to fork it - or rip it apart for code?
> I still think it is by far the complete of any of the Open Source
> Python Windows GUI automation solutions out there.
>  There are lots more complete Closed Source apps, and things like
> .NET provide a lot of functionality out of the Box.
> My excuses for pywinauto - are that I never actually ended up using it
> myself :( (so a big motivation to improve it vanished right there).
> And I was too ambitious with my original code - it is doing too much
> to be easy to maintain.
> Anyway - I still think it works, has basic (ref) documentation - and
> if anybody would like to help - that would be great :)
>> and wait a few days for anyone to object.
> I don't think I can object (though Watsup and WinGUIAuto are even more
> unmaintained in my opinion)
Oops - I actually meant WinGUIAuto in the first place... All these
wins and autos got me confused :) Sorry.
But having the author describe the state of something is even better, thanks.
More information about the testing-in-python