[#WET-197] Elements with unicode characters are captured inaccurately when operated through the WetUI

WET

Elements with unicode characters are captured inaccurately when operated through the WetUI

Created: 27/Aug/06 12:12 AM Updated: 18/Jun/07 10:23 AM

Component/s:

None

Affects Version/s:

1.0.0, 0.9.8_beta1, 0.9.8 Final

Fix Version/s:

1.2

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

Steps:
1) Open a page which has non ascii characters - eg. www.google.com -(observe the 'more »' button).
2) Synchronize the Wet UI's Simulated browser with this google page.
Expect:
View on simulated browser matches the real browser's view.
Actual:
Same.

so far..

3) Click on the 'more »' button in the simulated browser view, choose any function and in the function dialog change the view from object_depot view to 'full definition view' - click on Add

4) Open the tab for script view generated in the transaction page of the test definition.

Expect to see:
Browser("title:=Google").Link("text:=more »").check_exists

Actually see:
Browser("title:=Google").Link("text:=more ").check_exists

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Raghu Venkataramana - 27/Aug/06 12:15 AM

The trouble was with that in the xmlrpc package that we used, I modified the DeserializeResponse such that it uses a LoadXml - without doing this, the xmlrpc response received was always thrown away as the » character isn't allowed in the default Encoding. When I changed the encoding to something which is not 'Utf-8' (in the xmlrpc client), ruby gets confused when a request is made. So the trick was to send the xmlrpc request in the default encoding - but when the response comes back, treat is a unicode encoding.

It appears that when we do a LoadXml() method, the encoding is ignored.

[ Permlink | « Hide ]

Raghu Venkataramana - 02/Oct/06 04:20 AM

Since ruby itself doesn't support unicode very well, it is probably ok to defer to 'after 1.0'

[ Permlink | « Hide ]

Raghu Venkataramana - 18/Jun/07 10:23 AM

This was also duplicated as ~~WET-315~~. David Vijec had reported:

Launch browser and type "http://www.google.se".

Try to add something, like a click event, to the button "Google-sökning".

"Script.assistant.RpcExecutionFailedException..."