Business Value – Purpose

Posted by Albert Gareev on Jun 27, 2014
By industry standard definitions, test automation is created with the purpose of extending coverage, saving in test execution time, allowing for increase of test iterations, earlier detection of defects, and everything altogether. Therefore, only created and successfully used on a regular basis test automation should be considered as adding value. Coverage assessment must be done […] ...

Automation Requirements, Revisited – 2014

Posted by Albert Gareev on Jun 24, 2014
As I’m finding myself, I’ve been writing about QA Test Automation quite extensively in the years around 2010. No surprise – it was my main specialty. Then I was extending and sharpening my skillset in the field of QA Testing, and writing more and more about my new interests. Yet it wasn’t a transition – […] ...

Beware of Rapid Software Testing

Posted by Albert Gareev on Jun 10, 2014
Let my story be a warning. About 4 years ago, being a successful test automation engineer, I felt strong enough to challenge James Bach and Michael Bolton, who were loudly advocating for exploratory testing approach and, specifically, a methodology for a structured exploratory testing – Rapid Software Testing. So I challenged them… Oh, It didn’t […] ...
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.