pyqt partially wraps QTest with QTest you can activate buttons, fill in text fields etc. see an example here: http://www.voom.net/pyqt-qtest-example
it might also be a simple, although fragile way for users to instrument Leo dialogs and menus. a scripted way to get to a specific Leo setup, to replicate a bug or start work on a new project. On Oct 20, 1:32 pm, "Edward K. Ream" <[email protected]> wrote: > 2. Many (most?) bugs nowadays depend on a specific set of plugins > being enabled, or a specific set of options being in effect. But I > run unit tests from a *particular* script, that runs unitTest.leo with > a *particular* set of options. Furthermore, running tests externally > is *more* restrictive, not less, because at present running tests > externally uses the leoBridge module, which in turn uses the nullGui. > > 3. Gui-related bugs cause particular problems for unitTest.leo, > because I don't like to pollute the output with the output from > various work-arounds to code that would otherwise put up dialogs and > thus pause the unit tests. > > In other words, gui-related unit tests often result in added code (in > the code being tested) that a) are almost pure cruft and b) typically > actively subvert the intention of the actual test! This does not seem > like progress: I would (usually) prefer to endure repeated (failed) > attempts to fix the bug rather than pollute the code. > > In short, a more general testing framework is needed. Until that > happens, we will have to muddle through with untested, and thus very- > likely buggy code. > > Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
