Hi, I'm also having this concern while executing UI test cases in WSO2 ES.
In my case ES Publisher App take ablout 15sec in order to populate properly after completing indexing and all. Hence, I have to thread sleep all the test classes. I would also like to know whether this is the recommended way to slow down the web driver, or can we implicitly wait to start the test execution by the framework. Thanks! - Ayesha On Fri, Oct 17, 2014 at 10:10 AM, Sohani Weerasinghe <soh...@wso2.com> wrote: > Hi, > > When using selenium web driver to write test cases, currently I am using > Thread sleeps in order to control the speed of the browser. Is this the > recommended way to slow down the execution speed? > > Please note that I am also using explicit waits to wait for certain > conditions to occur before proceeding further and implicit waits to poll > the DOM for a certain amount of time to find an element. > > Thanks, > Sohani > Sohani Weerasinghe > Software Engineer > WSO2, Inc: http://wso2.com > > Mobile : +94 716439774 > Blog :http://christinetechtips.blogspot.com/ > Twitter : https://twitter.com/sohanichristine > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Ayesha Dissanayaka* Software Engineer, WSO2, Inc : http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> 20, Palmgrove Avenue, Colombo 3 E-Mail: aye...@wso2.com <ayshsa...@gmail.com>
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
