Have you tried splitting it into 2 parts?
txt = "103481 Company$reg; Some product"
puts "fail" unless (test.match /103481 Company/) && (test.match /Some
Product/)
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
Yes, i see 3 table by that name grid-btable.
irb(main):004:0> browser.tables(:class, "grid-btable").size
=> 3
I tried below with index as 1, 2 and 3, but evertime it failed :
$ie.table(:class => "grid-btable", :index => 1).div(:class,
"comboboxpp").td(:text, 'Summary').click
failed unable to lo
We have functionality that allows the user to search on a description for a
product.
I'm grabbing the product description from a database like so:
Company® Some Product
.
It's searching for the product correctly and returning the expected
results: item id, product description. I want to assert
Works great. Thanks!
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com
The headless (ala xvfb) options are tempting, but you're still process
bound. In my experiments I've managed to get 3 to 5 headless browsers
running before performance suffers on the client side (obviously dependent
on size of desktop/VM you're doing this on)... So you still need alot of
VMs (a
The short answer is that tools like watir are great for UI automation and
validating end user experience under load. I sometimes use watirgrid to help
drive multiple browsers fom different locations.
But to generate significant load in terms of things like concurrency/throughput
it's much more
Just use -d webdriver_performance when starting the providers and it should
load/expose the relevant gem/methods when executed via the controller.
Let me know how u go.
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
watir-general@googlegr
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
Wati
