Bug 641131 - Selenium throws a "_102 is undefined" exception
Summary: Selenium throws a "_102 is undefined" exception
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Tests
Version: 4.0.0
Hardware: All
OS: Linux
high
high vote
Target Milestone: ---
: ---
Assignee: Jay Shaughnessy
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4
TreeView+ depends on / blocked
 
Reported: 2010-10-07 19:46 UTC by dgao
Modified: 2011-02-14 14:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-14 14:27:45 UTC


Attachments (Terms of Use)
Client log for failed run (77.74 KB, text/x-log)
2010-10-07 19:48 UTC, dgao
no flags Details
Selenium log for failed run (347.04 KB, text/x-log)
2010-10-07 19:48 UTC, dgao
no flags Details
Client log for successful run (78.47 KB, text/x-log)
2010-10-07 19:48 UTC, dgao
no flags Details
Selenium log for successful run (430.24 KB, text/x-log)
2010-10-07 19:49 UTC, dgao
no flags Details

Description dgao 2010-10-07 19:46:42 UTC
Description of problem:

When executing selenium RC test, selenium server returns a "_102 is undefined" exception, which halts the test. 

Setup:

selenium-rc 2.0a5
smartgwt-2.2 selenium extension
firefox 3.6.7
Fedora 13 - Linux 2.6.34.6-47.fc13.x86_64

How To Reproduce:

1) git clone git://git.engineering.redhat.com/srv/git/users/jweiss/automatjon.git
2) git clone http://github.com/weissjeffm/webui-framework
3) Start selenium-rc via: java -jar selenium-server-standalone-2.0a5.jar -userExtensions /opt/smartgwt-2.2/selenium/user-extensions.js
4) cd automatjon/jon
5) Copy jonSuite-template.properties to $HOME
6) Rename $HOME/jonSuite-template.properties $HOME/automation.properties
7) Modify jon.server.url to point to RHQ server in $HOME/automation.properties
8) ant jon30functional-testng

Expected result:

[testng] com.thoughtworks.selenium.SeleniumException: _102 is undefined

Comment 1 dgao 2010-10-07 19:48:08 UTC
Created attachment 452187 [details]
Client log for failed run

Comment 2 dgao 2010-10-07 19:48:30 UTC
Created attachment 452188 [details]
Selenium log for failed run

Comment 3 dgao 2010-10-07 19:48:57 UTC
Created attachment 452189 [details]
Client log for successful run

Comment 4 dgao 2010-10-07 19:49:36 UTC
Created attachment 452190 [details]
Selenium log for successful run

Comment 5 dgao 2010-10-07 19:52:33 UTC
Refer to this https://wiki.idm.lab.bos.redhat.com/export/idmwiki/Setting_up_JON_Automation if you have any problems setting up jon automation.

Comment 6 dgao 2010-10-07 19:55:34 UTC
(In reply to comment #5)
> Refer to this
> https://wiki.idm.lab.bos.redhat.com/export/idmwiki/Setting_up_JON_Automation if
> you have any problems setting up jon automation.

Oops, posted incorrect link in my previous comment:

https://engineering.redhat.com/trac/IntegratedMgmtQE/wiki/Automation_Setup

Comment 7 dgao 2010-10-07 22:34:29 UTC
This bug was not encountered w/ the 9/15 build. But upon examining build #352 on 9/28, this popped up.

Comment 8 Jay Shaughnessy 2011-02-14 14:27:45 UTC
This was reported to Smartgwt and is fixed in the 2.4 release.


Note You need to log in before you can comment on or make changes to this bug.