[meego-packaging] [meego-commits] 9592 declined: home:talahtel/qttas-server to Trunk:Testing/qttas-server

[Tatu Lahtela]

On 11/23/2010 01:54 AM, ext Selbak, Rolla N wrote:
> On 11/19/10 12:00 PM, "Tatu Lahtela"<lahtela at iki.fi>  wrote:
>
>> On Fri, Nov 19, 2010 at 3:43 PM, Peter Zhu<no_reply at build.meego.com>  wrote:
>>> Hi -,
>>> The following change has been rejected.
>>>
>>> Reason:  Didn't talk about FEA#8504 in changelog; we are meego, don't need to
>>> consider fedora; use %make_instal; you might also condider using %qmake4 and
>>> %qmake4_install
>>>   
>>> Please fix the issues above and resubmit.
>>>
>> Hi, 
>>
>> Is it really necessary to remove the Fedora specifics? I was hoping to use the
>> same spec to create the package for Tools:Testing repo, which in turn is used
>> in Fedora among others [0].
> Do you need this pkg in MeeGo core itself?  Why do you need it in both MeeGo
> and Tools:Testing?
>
The package is mandatory on the target that is being tested, in this 
case a MeeGo device that has core as its repository. Having the package 
also in Tools:Testing is more a matter of convenience - you can also 
test your Qt applications running your host machine. The tools:testing 
repo doesn't offer anything else to the target device (at least right 
now), so I'd rather have this mandatory package on the target.

A simplified cut-through overview of the components involved in the 
testability driver for anyone interested:
- The Testability Driver is a driver for running automated tests. Ruby 
is used for test description.

Example:
myapplication.SomeButton(:name =>'MyButton').tap

- This translates to: TDriver (ruby library) finds SomeButton object 
with property "name" with value "MyButton" in myapplication, and tries 
to tap (click) it.
- If the object target was found, TDriver core sends the operation to 
the target via TCP/IP.
- qttas-server (on our MeeGo device) receives the command and relays it 
to myapplication.
- myapplication, via a plugin it automatically loads from qttas-server 
package, finds SomeObject Qt object and sends the QEvents for the tap 
operation. SomeButton is tapped.

The Testability Driver core is two  rubygem packages 
(testability-driver, testability-driver-qt-sut-plugin) and the entire 
test could be executed on the target. But for now we want to enable host 
based testing, and for this we need qttas-server in trunk.

Cheers,
Tatu Lahtela