Randomised Testing - How we find the needles in the haystack

In my last post I endeavoured to explain the what, when and why of randomised testing. In this post I will detail how we have implemented randomised testing for our Java codebases. At Brandwatch we use a few tools to assist us with unit testing. We hang our unit tests off of the JUnit4 testing framework so it made sense to continue to use this for our randomised test cases. Maven has done a great job of building and running our tests so there was no reason to replace it, while Jenkins quite happily handles scheduling and running tests as »

Randomised Testing: Finding the needles in the haystack

You have some haystacks; you're fairly sure you've found most of the needles inside of them. You've checked the areas you usually find needles using tried and tested techniques. But you can't be sure - you can never be sure. Some haystacks are smaller or sparser than the others and they're not being used for anything too important. The checks you've made on these haystacks are probably enough to ascertain that the really dangerous needles have been removed, and if there are any remaining needles they should be easy enough to take care of. But what about that veritable mountain »