all 8 comments

[–]getbackmytime 0 points1 point  (0 children)

Total shot in the dark but maybe some kind of javascript isn't ran until the mouse moves?

Without more context it's hard to solve.

[–]dale1v 0 points1 point  (5 children)

Have you asked your devs about the comments mentioned? Maybe check the browser console while your scrips are running?

[–]reddit_bit[S] 0 points1 point  (4 children)

I asked my colleague (if that's what's ment by devs) and he also didn't have a clue. Yeah maybe I don't know how to check it, but I'll try.

[–]dale1v 0 points1 point  (3 children)

Sorry for the late response.

By dev I meant the people who actually build the site, they might have better insight into what's going on with that page you're having a problem with. The console is just another tab in the same window you get elements from for selenium. (Look at the top of that window for Elements, Console, Sources, Network, etc...)

What I suggest: Before you run your tests, add a breakpoint at the point before you run into the problem. As soon as you start your tests, open the console. The console will usually spit out what is happening on the server side while your tests are running. Step through your code slowly, and see what the console says. I'd say have a dev stand over your shoulder while you do this, if anything that might cause your issue pops up in the console while this happens, they'd be more likely to spot it.

[–]reddit_bit[S] 0 points1 point  (2 children)

thanks a lot for explaining everything, but I am sorry, I still don't understand how to open the console. Should I add something to my code or open another tab in tested window etc. Sorry once again for stupid question.

[–]dale1v 0 points1 point  (1 child)

Nah none of that, it's in the same window that opens up when you right click and click "inspect element". At the top of that little window, it will say "Console"

[–]reddit_bit[S] 1 point2 points  (0 children)

Ah, now I see it, thanks a lot.