Testing at Digg
The Quality Assurance team at Digg is always looking for new ways to break things. We use a combination of unit and automated functional tests to make sure our code is working properly. As code is being developed, so are the unit tests which have 100% coverage. Of course, having machines do work for you is always better than doing it yourself, so we have a heavy focus on functional test automation. We use Selenium because it's open source and has support for lots of different browsers, Operating Systems, and programming languages.
We are an agile environment and practice test-driven development, continuous integration and deployment, and parallel development and testing. This means we are constantly interacting with development, design, and product to understand how features should behave and identify the best ways to test them.
We use really cool tools like Twist from Thoughtworks (to manage our automated suite), Sauce Labs (to run all of our tests on all of our supported browsers in parallel) and Hudson (to manage our continuous integration environment). We've hooked these all together so that when automated tests fail, an embedded video of the failure is already waiting for us in our reports. Look for more QA posts in the future about the specifics of our process.
If any of this sounds interesting to you, we are looking for amazing test engineers. To find out more about joining Digg's rock star QA team, go to digg.com/jobs; we're all business.
