3 ms·
Automated testing of UIs will only ever cover a relatively limited range of observable behaviour we might care about. Like a lot of unit testing, it's one of th
by Silhouette 16y ago
Automated testing of UIs will only ever cover a relatively limited range of observable behaviour we might care about. Like a lot of unit testing, it's one of those ideas that works really neatly if you're writing a simple database front-end or calculator that deals only with easily parsed/rendered data that is input and output via well-defined, programmable interfaces.
Unfortunately, most UIs aren't built with that kind of code. Tools like Selenium aren't going to help you spot that the browser is rendering your page elements with a z-order bug, the canvas/SVG output has an aliasing problem, and your entire page design is getting a flickering scrollbar effect because of a change in the font rendering when the underline for a link appears. (And those are just examples of possible browser bugs, not even counting testing your own code to make sure the UI is rendering properly to a human looking at a screen.)