Calabash Android random failures because of elements not found -
we use calabash-android our functional tests here , experiencing strange behaviors. have simple scenario like:
when skip tutorial must land on 'fancy' screen
this scenario succeed of time, (about 10-15% of time) 2 failures possible. first 1 because element looked when skip tutorial
not found calabash-android (it button id button_ok
). when inspecting screenshot taken see element, quite weird. suspecting animation of element, i've had post_timeout
, this:
tap_when_element_exists("* id:'button_ok'", :post_timeout => 2)
but nothing changed.
the second possible failure when step when skip tutorial
passed next step check on correct page fails, because page has not changed... on screenshot taken calabash indeed on page of tutorial, not on next 1 expected. how possible since step change page successful?
does faced kind of random failures?
(sorry bad english, not mother tongue :( )
i have faced similar random failure on devices. problem element trying touch rendered later timeout of previous step. in case, keyboard taking long disappear blocking calabash see elements behind that. right approach avoid such mistake wait element appear.
wait_for_element_exists(uiquery)
use above before every such touch event , might work.
Comments
Post a Comment