Bug 641131
| Summary: | Selenium throws a "_102 is undefined" exception | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | dgao | ||||||||||
| Component: | Tests | Assignee: | Jay Shaughnessy <jshaughn> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 4.0.0 | ||||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | All | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-02-14 14:27:45 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 585306 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
dgao
2010-10-07 19:46:42 UTC
Created attachment 452187 [details]
Client log for failed run
Created attachment 452188 [details]
Selenium log for failed run
Created attachment 452189 [details]
Client log for successful run
Created attachment 452190 [details]
Selenium log for successful run
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. (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 This bug was not encountered w/ the 9/15 build. But upon examining build #352 on 9/28, this popped up. This was reported to Smartgwt and is fixed in the 2.4 release. |