Squish Eval: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
| Line 4: | Line 4: | ||
* No worry of platform native dialogs. Qt provies a switch to turn of native dialogs which is used when recording and playing back tests. | * No worry of platform native dialogs. Qt provies a switch to turn of native dialogs which is used when recording and playing back tests. | ||
* Can test client/server applications. It can start up multiple applications and interact with all of them. I haven't tested this, and I don't know what it does with a non-Qt server application. | * Can test client/server applications. It can start up multiple applications and interact with all of them. I haven't tested this, and I don't know what it does with a non-Qt server application. | ||
* Squish works with the QVTKWidget without having to tell Squish anything special about the widget. Basic mouse clicks/keyboard events are recorded. | * Squish works with the QVTKWidget without having to tell Squish anything special about the widget. Basic mouse clicks/keyboard events are recorded. A few selected widgets have a higher level of abstraction than recording mouse/keyboard events. | ||
* Squish works with unnamed widgets. Names are made up for the recording/playback, which compose of the class name and some index. I assume the index is the index of that type of widget in the layout or something like that. | * Squish works with unnamed widgets. Names are made up for the recording/playback, which compose of the class name and some index. I assume the index is the index of that type of widget in the layout or something like that. | ||
Latest revision as of 13:38, 18 May 2006
Evaluating Squish
Notable features:
- No worry of platform native dialogs. Qt provies a switch to turn of native dialogs which is used when recording and playing back tests.
- Can test client/server applications. It can start up multiple applications and interact with all of them. I haven't tested this, and I don't know what it does with a non-Qt server application.
- Squish works with the QVTKWidget without having to tell Squish anything special about the widget. Basic mouse clicks/keyboard events are recorded. A few selected widgets have a higher level of abstraction than recording mouse/keyboard events.
- Squish works with unnamed widgets. Names are made up for the recording/playback, which compose of the class name and some index. I assume the index is the index of that type of widget in the layout or something like that.
Licensing:
- Requires a per-user license. "Developer" or "runner" licenses are offered. Runner license is limited to only running tests. A user may set up multiple dashboards with the one license he/she has.
Downside:
- We would lose testing coverage contributed by the community.
Issues:
- I tried their latest release with Qt 4.1.2, but couldn't get it built. So I tried their beta and it built fine. But it is "beta" so there were a few bugs.
Costs:
- Developer license is about $2000 per user.
- Runner license is about $400 per user.
Questions ??:
