Currently, if a user interaction has been selected the user can choose:
Transition reloads page:
-> No
-> Seconds to wait for result: ...
--> It would be useful to be able to define an element which need to be present before proceeding
Description
Currently, if a user interaction has been selected the user can choose:
Transition reloads page:
-> No
-> Seconds to wait for result: ...
--> It would be useful to be able to define an element which need to be present before proceeding
The wait for page to load feature has been rewritten in CubicTest 1.8.11. Now there is a timeout for asserting each element instead, and not a "global" wait for page to load. Better for Ajax and JavaScript issues. The timeout can be set on the user interaction transition. Default is 20 sec. Can also be changed globally in test-project.properties.
I think this remedies the need for wait for a custom element present feature.
Christian Schwarz added a comment - 03/Dec/08 02:17 AM The wait for page to load feature has been rewritten in CubicTest 1.8.11. Now there is a timeout for asserting each element instead, and not a "global" wait for page to load. Better for Ajax and JavaScript issues. The timeout can be set on the user interaction transition. Default is 20 sec. Can also be changed globally in test-project.properties.
I think this remedies the need for wait for a custom element present feature.
New Feature
Resolved
Major
WaitForElementPresent feature similar to Selenium IDEs waitForElementPresent command
The wait for page to load feature has been rewritten in CubicTest 1.8.11. Now there is a timeout for asserting each element instead, and not a "global" wait for page to load. Better for Ajax and JavaScript issues. The timeout can be set on the user interaction transition. Default is 20 sec. Can also be changed globally in test-project.properties.
I think this remedies the need for wait for a custom element present feature.