Author Topic: Preparing for 2.0b2 (Read 337 times)

Simon Stewart · « **on:** April 04, 2012, 07:50:40 PM »

Hi everyone,
With the Bug Bash complete, it's time to prepare for 2.0 beta 2. Other
than reworking the pom.xml files so that that we can release to the
maven repos without muss or fuss, are there any major blockers? I'm
not aware of any, though there are always bugs that are annoying and
really should be fixed (typing "y" using typeKeys being my personal
bugbear)

If there aren't any, I'll do the release of the Java code the minute I
know that we can push successfully to the maven repos. David, I think
it's time we pushed the python bindings live too. What do you think?

Simon

Jeff · « **Reply #1 on:** April 04, 2012, 07:50:57 PM »

A few annoying issues for me (not sure if they are official bugs) :

- *selenium.getAllLinks()* only returns the ID's of the <A>
elements...which for me is *completely useless* since most don't have an
ID attribute and I don't control the content or page structure. *Could
it return a more useful locator string if there is no ID?* (see
http://groups.google.com/group/selenium-users/browse_thread/thread/bd...
)
- *selenium.mouseOver()* doesn't work for me. From a user perspective,
the menu I'm trying to target only expands when the mouse pointer hovers
over it. When I try to use selenium.mouseOver(), nothing happens. The
suggested workarounds from the thread below are currently outside the scope
of my understanding and will part of some needed additional learning in the
near future, but it would be nice if the default selenium.mouseOver() method
worked. (see
http://groups.google.com/group/webdriver/browse_thread/thread/41e1e23...
)
- HTMLUnit and Chrome drivers don't work for me (can't get them
instantiated). I've attached my SeleniumHelper.java class that I use with
TestNG @Factory to instantiate my test classes. I've tried to modularize a
helper method so I can just pass in the type of browser instance I want to
use and it will instantiate the correct driver. I had problems with IE
previously, but since 2.0b1 IE works better (though I still haven't used it
extensively. Some eyes on what I'm doing would be nice in case a fix is
warranted.
- In a related vein:
- Detailed and consolidated *documentation* of all supported
WebDriver profile and/or DesiredCapabilities options when
instantiating/manipulating each driver. I haven't found the
definitive
resource, only sporadic blogs or posts to mailing lists and
any "official"
documentation is not nearly detailed enough.
- Documentation on when to skip the "Selenium" (webdriver backed
selenium) object and go under the covers to the driver or
even lower objects
(WebElements, RenderedWebElements, RenderedRemoteWebElements,
CommandProcessors, etc..)
- I'm finding it difficult to navigate online resources and search
results since they seem to come in a mix of Selenium 1.0,
Selenium 2.0 and
Legacy WebDriver results.

I'm running 2.0b1 on Windows 7 x64. I'm building and testing using TestNG
in NetBeans 6.9.1. Depending on how you'd like to handle these, I'd love to
get some eyes on my code to help me understand if these are issues so they
could get fixed for 2.0b2 as appropriate.

Thanks!!

-Jeff
On Wed, Feb 2, 2011 at 6:15 AM, Simon Stewart <simon.m.stew...@gmail.com>wrote:

- Show quoted text -

--
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

SeleniumHelper.java
7K Download

John · « **Reply #2 on:** April 04, 2012, 07:51:09 PM »

I'm just getting started switching our project from Se 1.0 to Se 2, so I'd
be delighted to get b2. I'd prefer to download the jar that includes all
dependencies (selenium-server-standalone) as we're not currently using
Maven. Please let me know if this is something that's likely to become
available before Monday afternoon.

Thanks!
John

Selenium Webdriver · « **Reply #2 on:** April 04, 2012, 07:51:09 PM »

WebDriver · « **Reply #3 on:** April 04, 2012, 07:51:20 PM »

Simon,
I am also curiously waiting for the fix of issue 1203 in 2.0b2, this
issue has halted our testing as our app is totally xsl rendered.

Can you please us know when you are planning for release of b2

Thanks

On Feb 3, 7:08 pm, John <jwb...@gmail.com> wrote:

- Show quoted text -

Jim Evans · « **Reply #4 on:** April 04, 2012, 07:51:33 PM »

This issue was fixed in r11018[1], so it will be in 2.0b2. The
description of what caused the issue and what was changed tgo fix it
can be found in the issue report[2].
Incidentally, thank you to the submitter for providing sample pages
along with the test code; it made diagnosing and fixing the issue so
much easier. Let me give a quote from the issue resolution to give
credit where it is due:

"...[T]his is an example of an almost perfect issue report. With the
samples provided, I was able to pinpoint the exact problem, and fix it
in short order. Thank you for an excellent submission."

Regards,
--Jim

[1] http://code.google.com/p/selenium/source/detail?r=11018
[2] http://code.google.com/p/selenium/issues/detail?id=1203

On Feb 4, 7:28 am, WebDriver <sridurgad...@gmail.com> wrote:

- Show quoted text -

News:

Preparing for 2.0b2

Welcome to Selenium Webdriver Forum