On Sunday 24 September 2006 1:44 am, Giovanni Bajo wrote:
Phil Thompson wrote:
Anything else, like the QTEST/QVERIFY family of macros, are part of
the framework, which I personally don't plan to ever use in a PyQt
application anyway.
Thanks - it's so much easier when somebody provides a
On Friday 22 September 2006 1:37 pm, Giovanni Bajo wrote:
Phil Thompson wrote:
Is there planned any support for the Qt Uni Testing Framework?
No plans. It seems to use templates for some things (addColumn())
which makes it a real pain. Is there a useful subset you can identify?
In my
HiIs there planned any support for the Qt Uni Testing Framework?regardsMarco
___
PyKDE mailing listPyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Hi
Is there planned any support for the Qt Uni Testing Framework?
No plans. It seems to use templates for some things (addColumn()) which
makes it a real pain. Is there a useful subset you can identify?
Phil
___
PyKDE mailing list
On 22.09.06 12:45:02, Phil Thompson wrote:
Is there planned any support for the Qt Uni Testing Framework?
No plans. It seems to use templates for some things (addColumn()) which
makes it a real pain. Is there a useful subset you can identify?
Well, the gui-stuff would be nice I think,
Phil Thompson wrote:
Is there planned any support for the Qt Uni Testing Framework?
No plans. It seems to use templates for some things (addColumn())
which makes it a real pain. Is there a useful subset you can identify?
In my opinion, the testing *framework* itself is not very useful: we
