On Mon, Jun 14, 2004 at 03:38:23PM +0200, Antoon Pardon wrote: > Can anyone give a reference on how to combine unittests > and pygtk? Or if that is not possible maybe a reference > on combining unittests and GUI in general?
This is the kind of question that makes us software engineers get under our beds, turn off the lights and pretend we're on vacation. Seriously, Brad Meyers says it best in his (somewhat disenheartiningly-titled) "Why are User Interfaces Difficult to Design and Implement" when he points out the title for problem 4.6: "Low Testability". There are some ways PyGTK helps when unit testing the UI. You can, for instance, drive the application almost entirely via the widget and signal API, using mainiteration()s whenever necessary. You'll find basic testing is possible in this manner, though more complex testing is hideously difficult particularly in complex applications. The other way to go around this is to use a screen capture/replay tool. I won't advocate these because I hate the fact that they are too closely tied to implementation to be a sustainable software construction tool for software whose UI is constantly evolving. If that's not the case with yours, however, you might differ. There are good references on the net; googling should turn up more than a good night's read. While I'm hidden under my bed. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
