On Thu, Feb 4, 2010 at 11:39 AM, doug livesey <[email protected]> wrote:
> Hi -- I have this expectation in a cucumber steps file (using capybara and > the selenium webdriver driver) that should be changing a value (from > "010210" to "020210", fwiw): http://pastie.org/809167 > Even though I explicitly set the value of the input element in the first > line of the expectation, the second line that tests that it has indeed been > set fails, and it's been driving me crazy for half a day! > Does anything spring to mind in any of the gurus on the list that might > help? > Am I doing it wrong? > Cheers, > Doug. > > -- > You received this message because you are subscribed to the Google Groups > "NWRUG" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nwrug-members%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nwrug-members?hl=en. > Top of me head no idea, personally I would do something like: x = find( "//*...@class = 'current']//input" ) and then print x out. It looks like you're searching for the same thing x.set(value) puts x.inspect y = find ... puts y.inspect I think maybe you're getting a new object the second time that doesn't have the value set, do you have to do a save or something after the set? Thanks and regards, Francis Follow me on twitter https://twitter.com/fjfish Blog at http://www.francisfish.com (you can also buy my books from there!) Skype: fjfish My other sig is much funnier and world changing but I can't find it anywhere -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en.
