> Harri Porten kirjoitti 28.5.2015 kello 18.28:
>
>> On Thu, 28 May 2015, Cristian Adam wrote:
>>
>> Does anyone know what happened with the Testablity Driver?
>
> I can only confirm what Gerry said: it couldn't keep up with the speed of
> Qt development.
>
Exactly. The Qt QA systems still
On Thu, 28 May 2015, Cristian Adam wrote:
> Does anyone know what happened with the Testablity Driver?
I can only confirm what Gerry said: it couldn't keep up with the speed of
Qt development.
For our own tool Squish we are also kept busy constantly with advances not
only in QML but especially
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 28.05.2015 16:36, Friedemann Kleint wrote:
> Hi,
>
>> adly we're not using it in Canonical any more. TDriver did a good
>> job
> with Qt4 apps. But it was desired to have a single tool to test
> multiple toolkits (Qt & GTK & Html5) using pytho
Hi,
>adly we're not using it in Canonical any more. TDriver did a good job
with Qt4 apps. But it was desired to have a single tool to test multiple
toolkits (Qt & GTK & Html5) using python, so > >we ended up building our
own: AutoPilot [1]. IMO TDriver is more powerful though.
Does this mean
On 28/05/15 13:03, Cristian Adam wrote:
> Hi,
>
> Does anyone know what happened with the Testablity Driver?
>
> One can read about TDriver here:
> http://voices.canonical.com/tag/testability%20driver/
>
> It was released by Nokia as LGPL, source code is still available on
> Gitorious: https://www.
Hi,
Does anyone know what happened with the Testablity Driver?
One can read about TDriver here:
http://voices.canonical.com/tag/testability%20driver/
It was released by Nokia as LGPL, source code is still available on
Gitorious: https://www.gitorious.org/tdriver
But that won't be for long since
