Automated Web Testing Is Hard

There are so many tools to choose from that you don’t know where to start. You’re worried you’ll pick one and find yourself down a rabbit hole with little to show for it.

Maybe you go open source and build out a quick test suite. You might even roll your own framework. Things seem good at first, but then your tests start breaking. You fix a couple and order is restored. You add more tests. But then more breakage occurs. The maintenance burden starts to keep you from doing real work. And your tests are starting to get ignored, considered noise.

This is a common occurrence I’ve seen time and again while working with various software development shops over the last few years.

Most experts will tell you this is avoidable. Some may say to read a scattershot of books and blog posts, or to subscribe to a couple of mailing lists. That’s great, but it’s a serious investment of your time with nothing to show for it today.

What if there was a tool to help shape the path for you? One built from experience that said “Hey, do it this way”? And perhaps even open source?

Well, there is, and we didn’t build it. But we did just make it available in Ruby.

Introducing ChemistryKit – a simple and opinionated web testing framework for Selenium WebDriver that follows convention over configuration, wired ready for your Continuous Integration server, and integrates with SauceLabs for cross-browser execution in the cloud.

You can download the gem here. And see our getting started guide and source code here.

Check it out!

And if you’d like to hear the latest news about ChemistryKit, or would like general tips on QA Strategy and Automated Web Testing, then complete the e-mail form below.

Comments