Qooxdoo 1.4 and FF4 issue

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Hi,

I just migrated my application to qx 1.4.
I was using 1.3.0.
It was working fine with both FF4 and Safari.
I'm on Mac OS 10.6.7.

After the migration it's working fine with Safari but it fail to show anything in FF4.
No error message, not even a warning, just nothing on screen.

Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?

Thanks !
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Solved : it was a FF plugin : ghostery that was blocking qooxdoo 1.4 but not qooxdoo 1.3.

On 8 avr. 2011, at 22:30, Jean-Baptiste BRIAUD -- Novlog wrote:

> Hi,
>
> I just migrated my application to qx 1.4.
> I was using 1.3.0.
> It was working fine with both FF4 and Safari.
> I'm on Mac OS 10.6.7.
>
> After the migration it's working fine with Safari but it fail to show anything in FF4.
> No error message, not even a warning, just nothing on screen.
>
> Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?
>
> Thanks !
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

MartinWittemann
Administrator
Hello JBB,
Thanks for the hint with the plugin. Do you have any idea why this thing is blocking 1.4 and not 1.3?
How did the rest of the migration work for you?
Regards,
Martin

Am 09.04.2011 um 15:09 schrieb Jean-Baptiste BRIAUD -- Novlog:

> Solved : it was a FF plugin : ghostery that was blocking qooxdoo 1.4 but not qooxdoo 1.3.
>
> On 8 avr. 2011, at 22:30, Jean-Baptiste BRIAUD -- Novlog wrote:
>
>> Hi,
>>
>> I just migrated my application to qx 1.4.
>> I was using 1.3.0.
>> It was working fine with both FF4 and Safari.
>> I'm on Mac OS 10.6.7.
>>
>> After the migration it's working fine with Safari but it fail to show anything in FF4.
>> No error message, not even a warning, just nothing on screen.
>>
>> Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?
>>
>> Thanks !
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Hi Martin,

Thanks for caring.
3 points :

1. The plugin
Unfortunately, that FF plugin isn't very configurable (ghostery), so I have no idea ... I had to whitelist localhost domain.
I'm afraid I'll have the issue on our production servers which are not localhost ...

2. The toolchain
The migration goes well, like a breeze for the code base but I haven't tested everything.
Amazingly, I had to amend all the python scripts to replace all the CMD_PYTHON=sys.executable that pypy guys advice to add (I replaced by CMD_PYTHON = python).
In fact, due to the fact we are launching that python toolchain automatically, I mean by a Java program as we're generarting qooxdoo apps, that sys.executable was not referencing python for obscure reason.
Anyway, it was easy and quick to do.
Could I set some env value so I can use the toolchain without changing anything, for example, could I set sys.executable = python from Java prior to launch generate.py ?

3. Selenium tests
I currently fight with our Selenium test that are failing with only a timeout as a hint ...
We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...



Thanks,
JBB.


On 11 avr. 2011, at 09:15, Martin Wittemann wrote:

> Hello JBB,
> Thanks for the hint with the plugin. Do you have any idea why this thing is blocking 1.4 and not 1.3?
> How did the rest of the migration work for you?
> Regards,
> Martin
>
> Am 09.04.2011 um 15:09 schrieb Jean-Baptiste BRIAUD -- Novlog:
>
>> Solved : it was a FF plugin : ghostery that was blocking qooxdoo 1.4 but not qooxdoo 1.3.
>>
>> On 8 avr. 2011, at 22:30, Jean-Baptiste BRIAUD -- Novlog wrote:
>>
>>> Hi,
>>>
>>> I just migrated my application to qx 1.4.
>>> I was using 1.3.0.
>>> It was working fine with both FF4 and Safari.
>>> I'm on Mac OS 10.6.7.
>>>
>>> After the migration it's working fine with Safari but it fail to show anything in FF4.
>>> No error message, not even a warning, just nothing on screen.
>>>
>>> Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?
>>>
>>> Thanks !
>>> ------------------------------------------------------------------------------
>>> Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic gaming
>>> smartphone on the nation's most reliable network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

MartinWittemann
Administrator
Hey,
Thanks for the feedback. I'll point Thomas and Daniel to your mail to check your questions as they are the experts in the toolchain and selenium.
Regards,
Martin

Am 11.04.2011 um 10:27 schrieb Jean-Baptiste BRIAUD -- Novlog:

> Hi Martin,
>
> Thanks for caring.
> 3 points :
>
> 1. The plugin
> Unfortunately, that FF plugin isn't very configurable (ghostery), so I have no idea ... I had to whitelist localhost domain.
> I'm afraid I'll have the issue on our production servers which are not localhost ...
>
> 2. The toolchain
> The migration goes well, like a breeze for the code base but I haven't tested everything.
> Amazingly, I had to amend all the python scripts to replace all the CMD_PYTHON=sys.executable that pypy guys advice to add (I replaced by CMD_PYTHON = python).
> In fact, due to the fact we are launching that python toolchain automatically, I mean by a Java program as we're generarting qooxdoo apps, that sys.executable was not referencing python for obscure reason.
> Anyway, it was easy and quick to do.
> Could I set some env value so I can use the toolchain without changing anything, for example, could I set sys.executable = python from Java prior to launch generate.py ?
>
> 3. Selenium tests
> I currently fight with our Selenium test that are failing with only a timeout as a hint ...
> We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...
>
>
>
> Thanks,
> JBB.
>
>
> On 11 avr. 2011, at 09:15, Martin Wittemann wrote:
>
>> Hello JBB,
>> Thanks for the hint with the plugin. Do you have any idea why this thing is blocking 1.4 and not 1.3?
>> How did the rest of the migration work for you?
>> Regards,
>> Martin
>>
>> Am 09.04.2011 um 15:09 schrieb Jean-Baptiste BRIAUD -- Novlog:
>>
>>> Solved : it was a FF plugin : ghostery that was blocking qooxdoo 1.4 but not qooxdoo 1.3.
>>>
>>> On 8 avr. 2011, at 22:30, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>
>>>> Hi,
>>>>
>>>> I just migrated my application to qx 1.4.
>>>> I was using 1.3.0.
>>>> It was working fine with both FF4 and Safari.
>>>> I'm on Mac OS 10.6.7.
>>>>
>>>> After the migration it's working fine with Safari but it fail to show anything in FF4.
>>>> No error message, not even a warning, just nothing on screen.
>>>>
>>>> Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?
>>>>
>>>> Thanks !
>>>> ------------------------------------------------------------------------------
>>>> Xperia(TM) PLAY
>>>> It's a major breakthrough. An authentic gaming
>>>> smartphone on the nation's most reliable network.
>>>> And it wants your games.
>>>> http://p.sf.net/sfu/verizon-sfdev
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic gaming
>>> smartphone on the nation's most reliable network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
OK, thanks.

For the Selenium tests, that dialog happen during a table cell edition.
Still investigating ...


On 11 avr. 2011, at 11:10, Martin Wittemann wrote:

> Hey,
> Thanks for the feedback. I'll point Thomas and Daniel to your mail to check your questions as they are the experts in the toolchain and selenium.
> Regards,
> Martin
>
> Am 11.04.2011 um 10:27 schrieb Jean-Baptiste BRIAUD -- Novlog:
>
>> Hi Martin,
>>
>> Thanks for caring.
>> 3 points :
>>
>> 1. The plugin
>> Unfortunately, that FF plugin isn't very configurable (ghostery), so I have no idea ... I had to whitelist localhost domain.
>> I'm afraid I'll have the issue on our production servers which are not localhost ...
>>
>> 2. The toolchain
>> The migration goes well, like a breeze for the code base but I haven't tested everything.
>> Amazingly, I had to amend all the python scripts to replace all the CMD_PYTHON=sys.executable that pypy guys advice to add (I replaced by CMD_PYTHON = python).
>> In fact, due to the fact we are launching that python toolchain automatically, I mean by a Java program as we're generarting qooxdoo apps, that sys.executable was not referencing python for obscure reason.
>> Anyway, it was easy and quick to do.
>> Could I set some env value so I can use the toolchain without changing anything, for example, could I set sys.executable = python from Java prior to launch generate.py ?
>>
>> 3. Selenium tests
>> I currently fight with our Selenium test that are failing with only a timeout as a hint ...
>> We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
>> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
>> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...
>>
>>
>>
>> Thanks,
>> JBB.
>>
>>
>> On 11 avr. 2011, at 09:15, Martin Wittemann wrote:
>>
>>> Hello JBB,
>>> Thanks for the hint with the plugin. Do you have any idea why this thing is blocking 1.4 and not 1.3?
>>> How did the rest of the migration work for you?
>>> Regards,
>>> Martin
>>>
>>> Am 09.04.2011 um 15:09 schrieb Jean-Baptiste BRIAUD -- Novlog:
>>>
>>>> Solved : it was a FF plugin : ghostery that was blocking qooxdoo 1.4 but not qooxdoo 1.3.
>>>>
>>>> On 8 avr. 2011, at 22:30, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I just migrated my application to qx 1.4.
>>>>> I was using 1.3.0.
>>>>> It was working fine with both FF4 and Safari.
>>>>> I'm on Mac OS 10.6.7.
>>>>>
>>>>> After the migration it's working fine with Safari but it fail to show anything in FF4.
>>>>> No error message, not even a warning, just nothing on screen.
>>>>>
>>>>> Any idea ? Any known issue or something that would have change since 1.3.0 in FF4 that I would have to amend in my code ?
>>>>>
>>>>> Thanks !
>>>>> ------------------------------------------------------------------------------
>>>>> Xperia(TM) PLAY
>>>>> It's a major breakthrough. An authentic gaming
>>>>> smartphone on the nation's most reliable network.
>>>>> And it wants your games.
>>>>> http://p.sf.net/sfu/verizon-sfdev
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Xperia(TM) PLAY
>>>> It's a major breakthrough. An authentic gaming
>>>> smartphone on the nation's most reliable network.
>>>> And it wants your games.
>>>> http://p.sf.net/sfu/verizon-sfdev
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic gaming
>>> smartphone on the nation's most reliable network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Thomas Herchenroeder
In reply to this post by Jean-Baptiste BRIAUD -- Novlog


On 04/11/2011 10:27 AM, Jean-Baptiste BRIAUD -- Novlog wrote:
> Hi Martin,
>
> Thanks for caring. 3 points :
>
> 1. The plugin Unfortunately, that FF plugin isn't very configurable
> (ghostery), so I have no idea ... I had to whitelist localhost
> domain. I'm afraid I'll have the issue on our production servers
> which are not localhost ...

If I get it right, Ghostery offers you a FF status bar entry (a la
Firebug), maybe this is something you have to enable. But with this in
place you should be able to get a menu which shows you what has been
blocked on any particular page, so you could see what of you app has
been blocked, and maybe why. They offer a comprehensive set of
"drill-in" features.

>
> 2. The toolchain The migration goes well, like a breeze for the code
> base but I haven't tested everything. Amazingly, I had to amend all
> the python scripts to replace all the CMD_PYTHON=sys.executable that
> pypy guys advice to add (I replaced by CMD_PYTHON = python). In fact,
> due to the fact we are launching that python toolchain automatically,
> I mean by a Java program as we're generarting qooxdoo apps, that
> sys.executable was not referencing python for obscure reason. Anyway,
> it was easy and quick to do. Could I set some env value so I can use
> the toolchain without changing anything, for example, could I set
> sys.executable = python from Java prior to launch generate.py ?

No, you can't change an internal Python value like sys.executable
through simple environment variables (thankfully).

As you might gathered from the release notes, we are now using
sys.executable throughout the tool chain, also in the form of a
PYTHON_CMD macro. But as your problem is not config files but patched
.py files, I'm afraid you have to look through the places you used it.
For the places it is used in the vanilla qooxdoo SDK (basically the
generate.py script), there is no reason why this should not work.

Except, of course, as you are launching the generator though a Java
program, it all depends through which Java API you are launching it (I
presume as a separate process), and which settings the API passes to the
launched program. Write a Shell script to just dump the passed argv, to
see if the executable is passed as well. Maybe you have to tweak the
launch call.

T.


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Daniel Wagner
Administrator
In reply to this post by Jean-Baptiste BRIAUD -- Novlog
Hi JBB,

On 04/11/2011 10:27 AM, Jean-Baptiste BRIAUD -- Novlog wrote:
> 3. Selenium tests
> I currently fight with our Selenium test that are failing with only a timeout as a hint ...
> We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...

1.0.3 is the Selenium version I've had the most success with in terms of
browser compatibility.

This is how I got FF4 to run with our tests:
1) Create a new Firefox profile (by starting Firefox with the -P
option), naming it e.g. "FF4-Selenium".
2) In that profile, disable popup blocking and add a manual proxy
configuration, using your Selenium server's host name and port number.
3) Configure your test to use the custom launcher and the new profile:
*custom /path/to/firefox/firefox -P FF4-Selenium

As for the long running script warning, I'd suggest taking a close look
at Selenium's log window while the test is running. That should give you
a better idea if what's going wrong.


Regards,
Daniel

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog

On 11 avr. 2011, at 14:30, Daniel Wagner wrote:

> Hi JBB,
>
> On 04/11/2011 10:27 AM, Jean-Baptiste BRIAUD -- Novlog wrote:
>> 3. Selenium tests
>> I currently fight with our Selenium test that are failing with only a timeout as a hint ...
>> We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
>> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
>> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...
>
> 1.0.3 is the Selenium version I've had the most success with in terms of
> browser compatibility.
>
I think that's the one we're using.

> This is how I got FF4 to run with our tests:
> 1) Create a new Firefox profile (by starting Firefox with the -P
> option), naming it e.g. "FF4-Selenium".
> 2) In that profile, disable popup blocking and add a manual proxy
> configuration, using your Selenium server's host name and port number.
> 3) Configure your test to use the custom launcher and the new profile:
> *custom /path/to/firefox/firefox -P FF4-Selenium
>

Well, I'm not sure ...
I'm using Selenium for testing as much as possible in real situation.
So, if the "slow script" dialog appears in real situation, I'm OK to fail my tests.
So basically, I'm not sure it is a good idea to disable that dialog on test server.
What do you think ?

also, I didn't use that Firefox profile mainly because it works without and I launching the test on a test server that is not use for browsing.
Would you advise us to use such profile ? if yes why ?
Is it for FF4 ? Currently, we're still using 3.1.16 for our tests.

> As for the long running script warning, I'd suggest taking a close look
> at Selenium's log window while the test is running. That should give you
> a better idea if what's going wrong.
>
This happen during a table cell edition but I really don't understand why, obviously link with something new in qooxdoo 1.4 ...
Unfortunately, I have nothing more to give here that could help you helping me :-)

>
> Regards,
> Daniel
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Daniel Wagner
Administrator


On 04/11/2011 03:21 PM, Jean-Baptiste BRIAUD -- Novlog wrote:

>
> On 11 avr. 2011, at 14:30, Daniel Wagner wrote:
>
>> Hi JBB,
>>
>> On 04/11/2011 10:27 AM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>> 3. Selenium tests
>>> I currently fight with our Selenium test that are failing with only a timeout as a hint ...
>>> We are still using an old Selenium version, what is the recommended Selenium version for qooxdoo 1.4 ?
>>> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium (including with the hack I've found to replace some 3.6.* by 4.* in some Selenium file).
>>> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box during our tests, so the time out ... still under investigation ...
>>
>> 1.0.3 is the Selenium version I've had the most success with in terms of
>> browser compatibility.
>>
> I think that's the one we're using.
>
>> This is how I got FF4 to run with our tests:
>> 1) Create a new Firefox profile (by starting Firefox with the -P
>> option), naming it e.g. "FF4-Selenium".
>> 2) In that profile, disable popup blocking and add a manual proxy
>> configuration, using your Selenium server's host name and port number.
>> 3) Configure your test to use the custom launcher and the new profile:
>> *custom /path/to/firefox/firefox -P FF4-Selenium
>>
>
> Well, I'm not sure ...
> I'm using Selenium for testing as much as possible in real situation.
> So, if the "slow script" dialog appears in real situation, I'm OK to fail my tests.
> So basically, I'm not sure it is a good idea to disable that dialog on test server.
> What do you think ?
>
> also, I didn't use that Firefox profile mainly because it works without and I launching the test on a test server that is not use for browsing.
> Would you advise us to use such profile ? if yes why ?
> Is it for FF4 ? Currently, we're still using 3.1.16 for our tests.

Yes, the profile workaround is just to get FF4 to launch at all. Without
that, I just get a 404 error since Selenium can't configure the browser
to use the server as a proxy. This won't fix any long running script
warnings.
>
>> As for the long running script warning, I'd suggest taking a close look
>> at Selenium's log window while the test is running. That should give you
>> a better idea if what's going wrong.
>>
> This happen during a table cell edition but I really don't understand why, obviously link with something new in qooxdoo 1.4 ...
> Unfortunately, I have nothing more to give here that could help you helping me :-)

There's a known bug where a resize event will cause the table to enter
an infinite loop, ultimately triggering the long running script dialog:

http://bugzilla.qooxdoo.org/show_bug.cgi?id=4934
(Description says TreeVirtual but the table uses the same code)

Could this be the issue you're seeing?


Regards,
Daniel

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
In reply to this post by Daniel Wagner
Is there a new version of Selenium user extension for qooxdoo that come with qooxdoo 1.4 ?

http://qooxdoo.org/contrib/project/simulator#selenium_user_extension_for_qooxdoo

Test is failing taking 100% CPU on a table cell edition.
No resize as far as I can see.
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Daniel Wagner
Administrator
On 04/11/2011 04:51 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
> Is there a new version of Selenium user extension for qooxdoo that come with qooxdoo 1.4 ?
Yes, it was moved to the framework for 1.4:
/component/simulator/tool/user-extensions/user-extensions.js

The Simulator contrib (trunk) has an SVN external pointing to the
framework file.
>
> http://qooxdoo.org/contrib/project/simulator#selenium_user_extension_for_qooxdoo
>
> Test is failing taking 100% CPU on a table cell edition.
> No resize as far as I can see.

So you can't reproduce this behavior by going through the test steps
manually?


Regards,
Daniel

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
OK, I updated both java client driver and server with the new 1.4 material.

Tests are still failing at the same place with the following error, no more blocking, so it is getting better :

19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session

Few lines later in the log :
com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
[CUT]


What is an hybrid locator ? What Hybrid mean ?
Also, the locator look like "reworked" from
qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
to
qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]

and I don't think this rework is done in our code.
Any idea ?

Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
[DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)

It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
What do you think about that idea ?


About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?


Thanks for the help !

On 11 avr. 2011, at 18:00, Daniel Wagner wrote:

> On 04/11/2011 04:51 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>> Is there a new version of Selenium user extension for qooxdoo that come with qooxdoo 1.4 ?
> Yes, it was moved to the framework for 1.4:
> /component/simulator/tool/user-extensions/user-extensions.js
>
> The Simulator contrib (trunk) has an SVN external pointing to the
> framework file.
>>
>> http://qooxdoo.org/contrib/project/simulator#selenium_user_extension_for_qooxdoo
>>
>> Test is failing taking 100% CPU on a table cell edition.
>> No resize as far as I can see.
>
> So you can't reproduce this behavior by going through the test steps
> manually?
>
>
> Regards,
> Daniel
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Too much for the time I have : I give up after a fight of 2.5 days.
I'm going for 1.3.1 step and I'll see later for 1.4.

-----
Lao Tzeu said to work only on customer's added value.

On 11 avr. 2011, at 19:53, Jean-Baptiste BRIAUD -- Novlog wrote:

> OK, I updated both java client driver and server with the new 1.4 material.
>
> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>
> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>
> Few lines later in the log :
> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
> [CUT]
>
>
> What is an hybrid locator ? What Hybrid mean ?
> Also, the locator look like "reworked" from
> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
> to
> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>
> and I don't think this rework is done in our code.
> Any idea ?
>
> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>
> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
> What do you think about that idea ?
>
>
> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>
>
> Thanks for the help !
>
> On 11 avr. 2011, at 18:00, Daniel Wagner wrote:
>
>> On 04/11/2011 04:51 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>> Is there a new version of Selenium user extension for qooxdoo that come with qooxdoo 1.4 ?
>> Yes, it was moved to the framework for 1.4:
>> /component/simulator/tool/user-extensions/user-extensions.js
>>
>> The Simulator contrib (trunk) has an SVN external pointing to the
>> framework file.
>>>
>>> http://qooxdoo.org/contrib/project/simulator#selenium_user_extension_for_qooxdoo
>>>
>>> Test is failing taking 100% CPU on a table cell edition.
>>> No resize as far as I can see.
>>
>> So you can't reproduce this behavior by going through the test steps
>> manually?
>>
>>
>> Regards,
>> Daniel
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Daniel Wagner
Administrator
In reply to this post by Jean-Baptiste BRIAUD -- Novlog
Hi again,

I read your mail about giving up but I'm still going to answer this one
on the off chance you're willing to invest more time in this.

On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:

> OK, I updated both java client driver and server with the new 1.4 material.
>
> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>
> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>
> Few lines later in the log :
> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
> [CUT]
>
>
> What is an hybrid locator ? What Hybrid mean ?

http://bit.ly/ik1Vfv

In short, a special type of locator. The qxTable* commands use it to
access the internal widget structure of the table.

> Also, the locator look like "reworked" from
> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
> to
> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>
> and I don't think this rework is done in our code.
> Any idea ?

See above. The hybrid locator uses the one you supplied to find the
table, then adds the "reworked" one to find the FocusIndicator child widget.

>
> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>
> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
> What do you think about that idea ?

Doesn't look that way. I would've noticed that in the test suite I use
to check the user extensions.

Still, from the error message you're getting, it's obvious the locator
can't find the FocusIndicator's DOM element. This can easily happen if
nothing is selected in the table. As you're aware, the table needs to be
put into editing mode (by double clicking a cell) before using
qxEditTableCell. This makes the FocusIndicator appear if nothing was
selected in the table before.
So you need to make sure that the double click executed before
qxEditTableCell had the intended effect. Maybe try waiting for a second
between the two commands so the browser has time to update the DOM.

It's also often helpful to watch the browser as the test suite is
executed, keeping an eye on Selenium's debug log (the one accessed via
the button in the Selenium browser window). This is were debug output
from the qooxdoo user extensions ends up.

>
>
> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?

Yes, since TreeVirtual shares much of the table's code. But judging from
the error message you posted it doesn't seem likely that this causes
your problem.


Regards,
Daniel

------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Hi Daniel,

Thanks again for all your help.
I may try again soon but now I really need to stabilize our product and add some features.
I upgraded to 1.3.1 and all our tests are passing.

I'll let you know what's happening for our tests in 1.4.
In fact, we are double clicking before the editTableCell and it works in 1.3.1.
So, why are the same tests passing in 1.3.1 and not in 1.4 with only that difference ?
Mystery until further investigation :-)


On 12 avr. 2011, at 09:27, Daniel Wagner wrote:

> Hi again,
>
> I read your mail about giving up but I'm still going to answer this one
> on the off chance you're willing to invest more time in this.
>
> On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>> OK, I updated both java client driver and server with the new 1.4 material.
>>
>> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>>
>> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
>> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>>
>> Few lines later in the log :
>> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
>> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
>> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
>> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
>> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
>> [CUT]
>>
>>
>> What is an hybrid locator ? What Hybrid mean ?
>
> http://bit.ly/ik1Vfv
>
> In short, a special type of locator. The qxTable* commands use it to
> access the internal widget structure of the table.
>
>> Also, the locator look like "reworked" from
>> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
>> to
>> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>>
>> and I don't think this rework is done in our code.
>> Any idea ?
>
> See above. The hybrid locator uses the one you supplied to find the
> table, then adds the "reworked" one to find the FocusIndicator child widget.
>
>>
>> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
>> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>>
>> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
>> What do you think about that idea ?
>
> Doesn't look that way. I would've noticed that in the test suite I use
> to check the user extensions.
>
> Still, from the error message you're getting, it's obvious the locator
> can't find the FocusIndicator's DOM element. This can easily happen if
> nothing is selected in the table. As you're aware, the table needs to be
> put into editing mode (by double clicking a cell) before using
> qxEditTableCell. This makes the FocusIndicator appear if nothing was
> selected in the table before.
> So you need to make sure that the double click executed before
> qxEditTableCell had the intended effect. Maybe try waiting for a second
> between the two commands so the browser has time to update the DOM.
>
> It's also often helpful to watch the browser as the test suite is
> executed, keeping an eye on Selenium's debug log (the one accessed via
> the button in the Selenium browser window). This is were debug output
> from the qooxdoo user extensions ends up.
>
>>
>>
>> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>
> Yes, since TreeVirtual shares much of the table's code. But judging from
> the error message you posted it doesn't seem likely that this causes
> your problem.
>
>
> Regards,
> Daniel
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Daniel Wagner
Administrator
Hi JBB,

if you do try again, please use the latest version of the user
extensions. I just fixed a bug that affected qxTableClick and
qxEditTableCell:

http://bugzilla.qooxdoo.org/show_bug.cgi?id=5005

Although I'm not 100% sure this is related to your problem since I don't
see why it should have worked differently in 1.3.


Regards,
Daniel

On 04/12/2011 02:47 PM, Jean-Baptiste BRIAUD -- Novlog wrote:

> Hi Daniel,
>
> Thanks again for all your help.
> I may try again soon but now I really need to stabilize our product and add some features.
> I upgraded to 1.3.1 and all our tests are passing.
>
> I'll let you know what's happening for our tests in 1.4.
> In fact, we are double clicking before the editTableCell and it works in 1.3.1.
> So, why are the same tests passing in 1.3.1 and not in 1.4 with only that difference ?
> Mystery until further investigation :-)
>
>
> On 12 avr. 2011, at 09:27, Daniel Wagner wrote:
>
>> Hi again,
>>
>> I read your mail about giving up but I'm still going to answer this one
>> on the off chance you're willing to invest more time in this.
>>
>> On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>> OK, I updated both java client driver and server with the new 1.4 material.
>>>
>>> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>>>
>>> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
>>> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>>>
>>> Few lines later in the log :
>>> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
>>> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
>>> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
>>> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
>>> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
>>> [CUT]
>>>
>>>
>>> What is an hybrid locator ? What Hybrid mean ?
>>
>> http://bit.ly/ik1Vfv
>>
>> In short, a special type of locator. The qxTable* commands use it to
>> access the internal widget structure of the table.
>>
>>> Also, the locator look like "reworked" from
>>> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
>>> to
>>> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>>>
>>> and I don't think this rework is done in our code.
>>> Any idea ?
>>
>> See above. The hybrid locator uses the one you supplied to find the
>> table, then adds the "reworked" one to find the FocusIndicator child widget.
>>
>>>
>>> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
>>> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>>>
>>> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
>>> What do you think about that idea ?
>>
>> Doesn't look that way. I would've noticed that in the test suite I use
>> to check the user extensions.
>>
>> Still, from the error message you're getting, it's obvious the locator
>> can't find the FocusIndicator's DOM element. This can easily happen if
>> nothing is selected in the table. As you're aware, the table needs to be
>> put into editing mode (by double clicking a cell) before using
>> qxEditTableCell. This makes the FocusIndicator appear if nothing was
>> selected in the table before.
>> So you need to make sure that the double click executed before
>> qxEditTableCell had the intended effect. Maybe try waiting for a second
>> between the two commands so the browser has time to update the DOM.
>>
>> It's also often helpful to watch the browser as the test suite is
>> executed, keeping an eye on Selenium's debug log (the one accessed via
>> the button in the Selenium browser window). This is were debug output
>> from the qooxdoo user extensions ends up.
>>
>>>
>>>
>>> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>>
>> Yes, since TreeVirtual shares much of the table's code. But judging from
>> the error message you posted it doesn't seem likely that this causes
>> your problem.
>>
>>
>> Regards,
>> Daniel
>>
>> ------------------------------------------------------------------------------
>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>> part of an in-depth evaluation of disaster recovery service providers.
>> Forrester found the best-in-class provider in terms of services and vision.
>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
Hi Daniel,

I try with the latest user extension and QxSelenium.class from the trunk and qooxdoo 1.4.
Tests are failing, always at the same place :
There is a sequence of 1 click, 1 double click, 1 cell edition in a loop.
It then freeze on the click of the second loop.
The table has only one row and no scroll bar.

It finally raise the FF "unresponsive script" dialog box and Selenium time out.

All that is 100% OK with qooxdoo 1.3.1.
The only differences is qooxdoo SDK and both user-extension + QxSelenium.class.


On 13 avr. 2011, at 14:02, Daniel Wagner wrote:

> Hi JBB,
>
> if you do try again, please use the latest version of the user
> extensions. I just fixed a bug that affected qxTableClick and
> qxEditTableCell:
>
> http://bugzilla.qooxdoo.org/show_bug.cgi?id=5005
>
> Although I'm not 100% sure this is related to your problem since I don't
> see why it should have worked differently in 1.3.
>
>
> Regards,
> Daniel
>
> On 04/12/2011 02:47 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>> Hi Daniel,
>>
>> Thanks again for all your help.
>> I may try again soon but now I really need to stabilize our product and add some features.
>> I upgraded to 1.3.1 and all our tests are passing.
>>
>> I'll let you know what's happening for our tests in 1.4.
>> In fact, we are double clicking before the editTableCell and it works in 1.3.1.
>> So, why are the same tests passing in 1.3.1 and not in 1.4 with only that difference ?
>> Mystery until further investigation :-)
>>
>>
>> On 12 avr. 2011, at 09:27, Daniel Wagner wrote:
>>
>>> Hi again,
>>>
>>> I read your mail about giving up but I'm still going to answer this one
>>> on the off chance you're willing to invest more time in this.
>>>
>>> On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>> OK, I updated both java client driver and server with the new 1.4 material.
>>>>
>>>> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>>>>
>>>> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
>>>> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>>>>
>>>> Few lines later in the log :
>>>> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
>>>> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
>>>> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
>>>> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
>>>> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
>>>> [CUT]
>>>>
>>>>
>>>> What is an hybrid locator ? What Hybrid mean ?
>>>
>>> http://bit.ly/ik1Vfv
>>>
>>> In short, a special type of locator. The qxTable* commands use it to
>>> access the internal widget structure of the table.
>>>
>>>> Also, the locator look like "reworked" from
>>>> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
>>>> to
>>>> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>>>>
>>>> and I don't think this rework is done in our code.
>>>> Any idea ?
>>>
>>> See above. The hybrid locator uses the one you supplied to find the
>>> table, then adds the "reworked" one to find the FocusIndicator child widget.
>>>
>>>>
>>>> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
>>>> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>>>>
>>>> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
>>>> What do you think about that idea ?
>>>
>>> Doesn't look that way. I would've noticed that in the test suite I use
>>> to check the user extensions.
>>>
>>> Still, from the error message you're getting, it's obvious the locator
>>> can't find the FocusIndicator's DOM element. This can easily happen if
>>> nothing is selected in the table. As you're aware, the table needs to be
>>> put into editing mode (by double clicking a cell) before using
>>> qxEditTableCell. This makes the FocusIndicator appear if nothing was
>>> selected in the table before.
>>> So you need to make sure that the double click executed before
>>> qxEditTableCell had the intended effect. Maybe try waiting for a second
>>> between the two commands so the browser has time to update the DOM.
>>>
>>> It's also often helpful to watch the browser as the test suite is
>>> executed, keeping an eye on Selenium's debug log (the one accessed via
>>> the button in the Selenium browser window). This is were debug output
>>> from the qooxdoo user extensions ends up.
>>>
>>>>
>>>>
>>>> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>>>
>>> Yes, since TreeVirtual shares much of the table's code. But judging from
>>> the error message you posted it doesn't seem likely that this causes
>>> your problem.
>>>
>>>
>>> Regards,
>>> Daniel
>>>
>>> ------------------------------------------------------------------------------
>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>> part of an in-depth evaluation of disaster recovery service providers.
>>> Forrester found the best-in-class provider in terms of services and vision.
>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>> part of an in-depth evaluation of disaster recovery service providers.
>> Forrester found the best-in-class provider in terms of services and vision.
>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
One more thing : on a visual point of view, the edition look like frozen *after* the cell edition.
I can see the added value in the cell.
I can see the cell, apparently frozen, with a not blinking cursor after the value added.

It may not be the click action that froze the test but the cell edition.


On 13 avr. 2011, at 19:29, Jean-Baptiste BRIAUD -- Novlog wrote:

> Hi Daniel,
>
> I try with the latest user extension and QxSelenium.class from the trunk and qooxdoo 1.4.
> Tests are failing, always at the same place :
> There is a sequence of 1 click, 1 double click, 1 cell edition in a loop.
> It then freeze on the click of the second loop.
> The table has only one row and no scroll bar.
>
> It finally raise the FF "unresponsive script" dialog box and Selenium time out.
>
> All that is 100% OK with qooxdoo 1.3.1.
> The only differences is qooxdoo SDK and both user-extension + QxSelenium.class.
>
>
> On 13 avr. 2011, at 14:02, Daniel Wagner wrote:
>
>> Hi JBB,
>>
>> if you do try again, please use the latest version of the user
>> extensions. I just fixed a bug that affected qxTableClick and
>> qxEditTableCell:
>>
>> http://bugzilla.qooxdoo.org/show_bug.cgi?id=5005
>>
>> Although I'm not 100% sure this is related to your problem since I don't
>> see why it should have worked differently in 1.3.
>>
>>
>> Regards,
>> Daniel
>>
>> On 04/12/2011 02:47 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>> Hi Daniel,
>>>
>>> Thanks again for all your help.
>>> I may try again soon but now I really need to stabilize our product and add some features.
>>> I upgraded to 1.3.1 and all our tests are passing.
>>>
>>> I'll let you know what's happening for our tests in 1.4.
>>> In fact, we are double clicking before the editTableCell and it works in 1.3.1.
>>> So, why are the same tests passing in 1.3.1 and not in 1.4 with only that difference ?
>>> Mystery until further investigation :-)
>>>
>>>
>>> On 12 avr. 2011, at 09:27, Daniel Wagner wrote:
>>>
>>>> Hi again,
>>>>
>>>> I read your mail about giving up but I'm still going to answer this one
>>>> on the off chance you're willing to invest more time in this.
>>>>
>>>> On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>>> OK, I updated both java client driver and server with the new 1.4 material.
>>>>>
>>>>> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>>>>>
>>>>> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
>>>>> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>>>>>
>>>>> Few lines later in the log :
>>>>> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
>>>>> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
>>>>> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
>>>>> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
>>>>> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
>>>>> [CUT]
>>>>>
>>>>>
>>>>> What is an hybrid locator ? What Hybrid mean ?
>>>>
>>>> http://bit.ly/ik1Vfv
>>>>
>>>> In short, a special type of locator. The qxTable* commands use it to
>>>> access the internal widget structure of the table.
>>>>
>>>>> Also, the locator look like "reworked" from
>>>>> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
>>>>> to
>>>>> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>>>>>
>>>>> and I don't think this rework is done in our code.
>>>>> Any idea ?
>>>>
>>>> See above. The hybrid locator uses the one you supplied to find the
>>>> table, then adds the "reworked" one to find the FocusIndicator child widget.
>>>>
>>>>>
>>>>> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
>>>>> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>>>>>
>>>>> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
>>>>> What do you think about that idea ?
>>>>
>>>> Doesn't look that way. I would've noticed that in the test suite I use
>>>> to check the user extensions.
>>>>
>>>> Still, from the error message you're getting, it's obvious the locator
>>>> can't find the FocusIndicator's DOM element. This can easily happen if
>>>> nothing is selected in the table. As you're aware, the table needs to be
>>>> put into editing mode (by double clicking a cell) before using
>>>> qxEditTableCell. This makes the FocusIndicator appear if nothing was
>>>> selected in the table before.
>>>> So you need to make sure that the double click executed before
>>>> qxEditTableCell had the intended effect. Maybe try waiting for a second
>>>> between the two commands so the browser has time to update the DOM.
>>>>
>>>> It's also often helpful to watch the browser as the test suite is
>>>> executed, keeping an eye on Selenium's debug log (the one accessed via
>>>> the button in the Selenium browser window). This is were debug output
>>>> from the qooxdoo user extensions ends up.
>>>>
>>>>>
>>>>>
>>>>> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>>>>
>>>> Yes, since TreeVirtual shares much of the table's code. But judging from
>>>> the error message you posted it doesn't seem likely that this causes
>>>> your problem.
>>>>
>>>>
>>>> Regards,
>>>> Daniel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>>> part of an in-depth evaluation of disaster recovery service providers.
>>>> Forrester found the best-in-class provider in terms of services and vision.
>>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>> part of an in-depth evaluation of disaster recovery service providers.
>>> Forrester found the best-in-class provider in terms of services and vision.
>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>> part of an in-depth evaluation of disaster recovery service providers.
>> Forrester found the best-in-class provider in terms of services and vision.
>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Forrester Wave Report - Recovery time is now measured in hours and minutes
> not days. Key insights are discussed in the 2010 Forrester Wave Report as
> part of an in-depth evaluation of disaster recovery service providers.
> Forrester found the best-in-class provider in terms of services and vision.
> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Reply | Threaded
Open this post in threaded view
|

Re: Qooxdoo 1.4 and FF4 issue

Jean-Baptiste BRIAUD -- Novlog
I just realize the title could lead to misunderstanding : tests are using FF 3.6.16.
This question start with FF 4 that I have locally but ends now with a selenium test question that run on FF 3.6.16 and fails with qooxdoo 1.4.

On 14 avr. 2011, at 11:50, Jean-Baptiste BRIAUD -- Novlog wrote:

> One more thing : on a visual point of view, the edition look like frozen *after* the cell edition.
> I can see the added value in the cell.
> I can see the cell, apparently frozen, with a not blinking cursor after the value added.
>
> It may not be the click action that froze the test but the cell edition.
>
>
> On 13 avr. 2011, at 19:29, Jean-Baptiste BRIAUD -- Novlog wrote:
>
>> Hi Daniel,
>>
>> I try with the latest user extension and QxSelenium.class from the trunk and qooxdoo 1.4.
>> Tests are failing, always at the same place :
>> There is a sequence of 1 click, 1 double click, 1 cell edition in a loop.
>> It then freeze on the click of the second loop.
>> The table has only one row and no scroll bar.
>>
>> It finally raise the FF "unresponsive script" dialog box and Selenium time out.
>>
>> All that is 100% OK with qooxdoo 1.3.1.
>> The only differences is qooxdoo SDK and both user-extension + QxSelenium.class.
>>
>>
>> On 13 avr. 2011, at 14:02, Daniel Wagner wrote:
>>
>>> Hi JBB,
>>>
>>> if you do try again, please use the latest version of the user
>>> extensions. I just fixed a bug that affected qxTableClick and
>>> qxEditTableCell:
>>>
>>> http://bugzilla.qooxdoo.org/show_bug.cgi?id=5005
>>>
>>> Although I'm not 100% sure this is related to your problem since I don't
>>> see why it should have worked differently in 1.3.
>>>
>>>
>>> Regards,
>>> Daniel
>>>
>>> On 04/12/2011 02:47 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>> Hi Daniel,
>>>>
>>>> Thanks again for all your help.
>>>> I may try again soon but now I really need to stabilize our product and add some features.
>>>> I upgraded to 1.3.1 and all our tests are passing.
>>>>
>>>> I'll let you know what's happening for our tests in 1.4.
>>>> In fact, we are double clicking before the editTableCell and it works in 1.3.1.
>>>> So, why are the same tests passing in 1.3.1 and not in 1.4 with only that difference ?
>>>> Mystery until further investigation :-)
>>>>
>>>>
>>>> On 12 avr. 2011, at 09:27, Daniel Wagner wrote:
>>>>
>>>>> Hi again,
>>>>>
>>>>> I read your mail about giving up but I'm still going to answer this one
>>>>> on the off chance you're willing to invest more time in this.
>>>>>
>>>>> On 04/11/2011 07:53 PM, Jean-Baptiste BRIAUD -- Novlog wrote:
>>>>>> OK, I updated both java client driver and server with the new 1.4 material.
>>>>>>
>>>>>> Tests are still failing at the same place with the following error, no more blocking, so it is getting better :
>>>>>>
>>>>>> 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session
>>>>>> 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session
>>>>>>
>>>>>> Few lines later in the log :
>>>>>> com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at
>>>>>> com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at
>>>>>> com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at
>>>>>> com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at
>>>>>> novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at
>>>>>> [CUT]
>>>>>>
>>>>>>
>>>>>> What is an hybrid locator ? What Hybrid mean ?
>>>>>
>>>>> http://bit.ly/ik1Vfv
>>>>>
>>>>> In short, a special type of locator. The qxTable* commands use it to
>>>>> access the internal widget structure of the table.
>>>>>
>>>>>> Also, the locator look like "reworked" from
>>>>>> qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"]
>>>>>> to
>>>>>> qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0]
>>>>>>
>>>>>> and I don't think this rework is done in our code.
>>>>>> Any idea ?
>>>>>
>>>>> See above. The hybrid locator uses the one you supplied to find the
>>>>> table, then adds the "reworked" one to find the FocusIndicator child widget.
>>>>>
>>>>>>
>>>>>> Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method:
>>>>>> [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge)
>>>>>>
>>>>>> It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong.
>>>>>> What do you think about that idea ?
>>>>>
>>>>> Doesn't look that way. I would've noticed that in the test suite I use
>>>>> to check the user extensions.
>>>>>
>>>>> Still, from the error message you're getting, it's obvious the locator
>>>>> can't find the FocusIndicator's DOM element. This can easily happen if
>>>>> nothing is selected in the table. As you're aware, the table needs to be
>>>>> put into editing mode (by double clicking a cell) before using
>>>>> qxEditTableCell. This makes the FocusIndicator appear if nothing was
>>>>> selected in the table before.
>>>>> So you need to make sure that the double click executed before
>>>>> qxEditTableCell had the intended effect. Maybe try waiting for a second
>>>>> between the two commands so the browser has time to update the DOM.
>>>>>
>>>>> It's also often helpful to watch the browser as the test suite is
>>>>> executed, keeping an eye on Selenium's debug log (the one accessed via
>>>>> the button in the Selenium browser window). This is were debug output
>>>>> from the qooxdoo user extensions ends up.
>>>>>
>>>>>>
>>>>>>
>>>>>> About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ?
>>>>>
>>>>> Yes, since TreeVirtual shares much of the table's code. But judging from
>>>>> the error message you posted it doesn't seem likely that this causes
>>>>> your problem.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Daniel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>>>> part of an in-depth evaluation of disaster recovery service providers.
>>>>> Forrester found the best-in-class provider in terms of services and vision.
>>>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>>> part of an in-depth evaluation of disaster recovery service providers.
>>>> Forrester found the best-in-class provider in terms of services and vision.
>>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>>> part of an in-depth evaluation of disaster recovery service providers.
>>> Forrester found the best-in-class provider in terms of services and vision.
>>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Forrester Wave Report - Recovery time is now measured in hours and minutes
>> not days. Key insights are discussed in the 2010 Forrester Wave Report as
>> part of an in-depth evaluation of disaster recovery service providers.
>> Forrester found the best-in-class provider in terms of services and vision.
>> Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Benefiting from Server Virtualization: Beyond Initial Workload
> Consolidation -- Increasing the use of server virtualization is a top
> priority.Virtualization can reduce costs, simplify management, and improve
> application availability and disaster protection. Learn more about boosting
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel