62: Gojko Adzic: Fifty Quick Ideas to Improve your Tests

Fifty Quick Ideas to Improve your Tests

In this episode you’re going to find out how to test your software better, easier and faster with Gojko Adzic, author of  Fifty Quick Ideas to Improve your Test. 

Gojko reveals some of his favorite ideas from his book, all of which can be applied to many different contexts — from small web start-ups to the world’s largest companies.

This episode will improve your team members’ collaboration on defining, creating and executing your tests.

Bonus: Listen all the way to the end to learn how to get 50% off a copy of Fifty Quick Ideas to Improve your Tests!

–> GET FULL TRANSCRIPT <–

About Gojko

Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. He specializes in agile and lean quality improvement, in particular agile testing, specification by example and behavior driven development. 

Gojko’s book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010. 

Gojko is the author of Fifty Quick Ideas to Improve your Tests, Fifty Quick Ideas to Improve your User Stories, Impact Mapping, Specification by Example, Bridging the Communication Gap, and Test Driven .NET Development with FitNesse.

Quotes & Insights from this Test Talk

• Try and list things that should always happen and that should never happen. It's a particularly good heuristic because those kind of absolute statements are relatively easy to shoot down and often we'd start with something where people would say a transaction should always be logged
• What kind of model do we need so we can describe the thing with relatively few examples and we feel it's complete. At that point, you know that you're ready to move on. If you don't do modeling first, pretty much everything else is paint in the curves. 
• One of the big problems with fast paced, iterative delivery is that, it's difficult to keep sight of the big picture. 
• It's very easy for something that is a mathematical formula to seem concrete and precise whilst still hiding the details and not having good discussion.
• I'm primarily writing code these days and one of the things I really, really hate is context switching. A lot of developers I know hate context switching as well and delayed feedback that comes from somebody else testing the code or checking the code is often causing a lot of context switching where by the time a developer is deep into some other problem, the report of the previous test comes back and then they have to stop what they're doing.
• On a holistic level, I think, getting people to collaborate is pretty much the most important thing that is missing from most of teams.

Resources

• For limited time get 50% off Fifty Quick Ideas To Improve Your Tests by using this link:—>http://leanpub.com/50quickideas-tests/c/testtalks<-

Connect with Gojko

• Twitter:@gojkoadzic
• Blog: http://gojko.net/

May I Ask You For a Favor?

Thanks again for listening to the show. If it has helped you in any way, shape or form, please share it using the social media buttons you see on the page.

Additionally, reviews for the podcast on iTunes are extremely helpful and greatly appreciated! They do matter in the rankings of the show and I read each and every one of them.

Special offer for TestTalks listeners, get 20 hours of automated testing for free when you sign-up with promo code testtalks14 (more info).