Re: [Development] Testability Driver

2015-05-28 Thread Turunen Tuukka 


 Harri Porten por...@froglogic.com 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 use TDriver for release test automation of Qt 
4.8. In Qt 5 it is replaced by Squish. 

Yours,

Tuukka

 For our own tool Squish we are also kept busy constantly with advances not 
 only in QML but especially hybrid solutions that mix in HTML content or 
 QWidgets (or vice versa)... :}
 
 For anyone wishing to express their UI tests in an easily readable and 
 non-tool-specific way I suggest to take a look at the Gherkin syntax btw. 
 We just added support this kind of behavior-driven testing:
 
  http://doc.froglogic.com/squish/6.0.0/bdd-tutorial-implementation.html
 
 Harri.
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Testability Driver

2015-05-28 Thread Gerry Boland 
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.gitorious.org/tdriver

 But that won't be for long since Gitorious has this big fat warning:
 „*System notice*: Gitorious is being acquired by GitLab and
 gitorious.org http://gitorious.org will shut down end of May.”

 Cheers,
 Cristian.

Hey,
sadly 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.
-Gerry


[1] http://unity.ubuntu.com/autopilot/index.html
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Testability Driver

2015-05-28 Thread Friedemann Kleint 
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 the code introduced by 
https://codereview.qt-project.org/#/c/66513/ can be removed ? - No need 
to keep dead code?

Thanks,
Friedemann

-- 
Friedemann Kleint | The Qt Company

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Testability Driver

2015-05-28 Thread Michael Zanetti 
-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 python, so  we ended
 up building our own: AutoPilot [1]. IMO TDriver is more powerful
 though.
 
 Does this mean the code introduced by 
 https://codereview.qt-project.org/#/c/66513/ can be removed ? - No
 need to keep dead code?

No, we'd still need that. The autopilot driver uses the same
mechanism to be loaded.

Br,
Michael
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlVnLYAACgkQXJwWsxE5x7hyUACdF5mRG/PgPA7p9j1RJzDy+O7m
7MEAoIsW/ow10TKwdu9/tqKr1EqnIfHC
=wOf8
-END PGP SIGNATURE-
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Testability Driver

2015-05-28 Thread Harri Porten 
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 hybrid solutions that mix in HTML content or 
QWidgets (or vice versa)... :}

For anyone wishing to express their UI tests in an easily readable and 
non-tool-specific way I suggest to take a look at the Gherkin syntax btw. 
We just added support this kind of behavior-driven testing:

  http://doc.froglogic.com/squish/6.0.0/bdd-tutorial-implementation.html

Harri.

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development