Testing can be a real pain! Isn't it good enough that it looks fine in Chrome? Should I really have to test the login page for a change to the contact form?
As a front-end dev, I've lazily assumed that testing is the realm of QA. Sure, I'll begrudgingly check my site in IE to see how much repair it needs, but I confess to cutting corners when testing and saying "That shouldn't break anything..."
This worked okay while I was building small sites, but now that I'm working with multiple teams on large projects, cutting corners doesn't work. The edge case always comes in to play and things that probably won't break do.
Instead of getting bogged down manually testing my site in browser after browser for every change, I decided to get smart (i.e. lazy). Using a combination of Visual Regression Testing and Functional Testing, I've automated my UI testing using simple NodeJS scripts.
This talk will cover a real-world implementation of browser testing using WebdriverIO and WebdriverCSS. We'll cover all the steps to get started writing automated browser tests, so that you can make changes with confidence.