There are already specs [1] for this and they're passing. I modified tests data to make one of the specs to fail [2] and fixed it in master [3]. The problem was not with SelectList#select_value, but in Element#to_subtype instead.
There is also a comment "deprecate?" for #select_value specs in WatirSpec. I have to agree with that comment - i'd deprecate and remove that method too and use SelectList#select instead, which also selects by value automatically. [1] https://github.com/watir/watirspec/blob/master/select_list_spec.rb#L325-343 [2] https://github.com/watir/watirspec/commit/bc7471cf1f52569def04d07e8d2dab82099bd000 [3] https://github.com/watir/watir/commit/b6a32f4cebc4864550da8a8e272561adac956a1c Jarmo On Jan 19, 1:08 am, Chuck van der Linden <[email protected]> wrote: > I note this change listed which might impact that > > SelectList code rewritten, causing changes in its API > > However I don't see much in the way of details. > > Given that select_value is present in watir-webdriver I'm pretty sure > those changes did not include removing that method (nor did your error > indicate that is the case) > > good to have the report. This is why we have RC releases. > > Seems like we might need some unit tests or rspecs to cover this > particular case. > > On Jan 18, 11:59 am, Michael <[email protected]> wrote: > > > > > > > > > A heads up that I created a bug report about an issue we experienced > > while testing our code with Watir 3.0.rc1. > > >http://jira.openqa.org/browse/WTR-498 -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
