[wxPython-users] Automated testing of wxPython

[Desilets, Alain]

I and some collegues at NRC (Mark Vidger, ) are working on a autoamted testing framework for wxPython applications. The framework is called wxManipulators. It allows you to programmatically manipulate wxWindows widgets "from the inside". 

For example, if you want to write a Python script that clicks on a button which is instantiated as a variable called someButton, you would write something that looks like this:

  wxManipulators.ButtonManipulator(someButton).click()

When this statement is executed, it's EXACTLY as if the end user had clicked on the graphical button.

We are starting to use the framework for our own projects and it's a bit early to tell how useful it is. But if others on this list are interested, we could maybe release it already (I'd have to discuss this with my collegues). For sure, you could use the framework to test wxWindows itself. You would basically write some dummy wxWindows app, manipulate its widgets using wxManipulators, and then make sure that the dummy app behaved as expected.


----
Alain Désilets, MASc 
Agent de recherches/Research Officer 
Institut de technologie de l'information du CNRC / 
NRC Institute for Information Technology 

alain.desilets at nrc-cnrc.gc.ca 
Tél/Tel (613) 990-2813 
Facsimile/télécopieur: (613) 952-7151 

Conseil national de recherches Canada, M50, 1200 chemin Montréal, 
Ottawa (Ontario) K1A 0R6 
National Research Council Canada, M50, 1200 Montreal Rd., Ottawa, ON 
K1A 0R6 

Gouvernement du Canada | Government of Canada 
 

> -----Original Message-----
> From: news [mailto:news at sea.gmane.org] On Behalf Of Don Dwiggins
> Sent: May 23, 2007 12:08 PM
> To: wxpython-users at lists.wxwidgets.org
> Subject: [wxPython-users] Automated testing of wxPython
> 
> Kevin Ollivier wrote:
> > We currently don't have automated testing in place, and so 
> > unfortunately it's not uncommon to get regressions in the codebase, 
> > but until we have an automated solution in place we are very, very 
> > dependent on users reporting bugs that they found to 
> improve wxPython. 
> > Robin, myself, and a few other people really can't test 
> hard enough to 
> > find all the problems in wxPython ourselves.
> 
> This seems to suggest that you're working on an automated way 
> to test wxPython components; is this right?  If so, could it 
> also be used for automated testing of wxPython applications?  
> I generally write my apps in a semi-MVC style that allows 
> automated unit testing of the model, but it'd be neat to be 
> able to do the same for the GUI component.
> 
> -- 
> Don Dwiggins
> Advanced Publishing Technology
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: 
> wxPython-users-help at lists.wxwidgets.org
> 
>