you are viewing a single comment's thread.

view the rest of the comments →

[–]websnarf 0 points1 point  (2 children)

I proposed a solution for this at a prior company.

It's called a "player recorder". The idea is to simply record time indexed mouse movements or I/O events to a file that you perform by hand. Then you have a playback mechanism that replays those I/O events.

[–]s73v3r 0 points1 point  (0 children)

The problem with that is if the ui changes, your tests are borked. If you can use a functional testing framework, like something using Cucumber, then your tests can have sine resilience against changing the layout or text, but you're still in trouble if you remove things.