tests failing periodically
Opened this issue · 4 comments
Hello!
I've started to look into your project, it seems very promising. Was quite easy to setup and start using in our project.
Stumbled onto a problem when running locally, the tests are passing roughly 1 out of 3 times, with timeout errors
Error: wait(".some-class") timed out after 500ms
I am running local server, so there is no connection issues I would think.
Could that be related to async nature of our app? we use angularjs
Or could it mean that the page doesn't have time to load and this particular element is not available yet? I played around with timeouts as well to no effect, while this helped when using protractor (waiting for the page to load).
Any advice will be appreciated.
after 500ms, it cannot find .some-class so it returns error. You should expand the waiting time
@dunecatnat which version of Chrome are you using?
@adieuadieu I use chrome v63.0.3239.84
as well what I realised is when I run the tests one by one, that is one at a time, they pass, but not when run sequentially. I tried starting and ending browser session after each test to see what can it do, to no luck either.
@sonnguyen1989 the first thing I did was to expand the waiting time, as I had similar problems with Protractor at some point, and expanding waiting time helped.
@adieuadieu I managed to make my tests work, by configuring creation of a new chromeless session differently.
Although now I have a problem that tests crash on await chromeless.end()
A bit of background that I had to mention earlier, I am trying to adapt chormeless to be used within cucumber step definitions. So I am thinking some issues I might face are the result of cucumber way of dealing with promises.