3 ms·
This is really cool! How do you plan to handle the selenium replaying? Does it currently just record the x/y position of the cursor events, because if so I gue
by bizzleDawg 10y ago
This is really cool!
How do you plan to handle the selenium replaying? Does it currently just record the x/y position of the cursor events, because if so I guess it needs playback on a browser window of the same dimensions.
I guess it may be possible to have some adaptors for cursor events which can process the clicked element for a framework, i.e. for reactJS it could pick out the classname and use that as the click target for playback in a screen size independent way.
My gut instinct was that this would mean lots of re-recording tests every time you make a change - but really that's much the case with screenshot testing or any e2e testing already! Great work!
- nenadg 10y agoThanks :-) you can check out https://github.com/nenadg/traquer/tree/master/runner https://github.com/nenadg/traquer/tree/master/runner which is test runner that extrapolates from saved events. Mouse position is irrelevant in selenium cases right now. Right now I'm trying to create basic case in which recorded events would be reproduced in correct sequence, reproducing what we've done on page. The down side is - what is collected is xpath (just because it is shorter than dom selector), xpath is absolutely vulnerable to changes so your tests will fail after F5 (in case of generated ID's whatsoever). I need to work on this, any help is welcome :-).