The thing about success is, it’s easy to attribute to our own efforts and abilities while disregarding circumstantial elements, timing, and quite honestly, pure luck. Failure gives concrete feedback on our lack of perfection and should trigger self-reflection on some level. Not to say we can not fail out of “bad luck”, but at least it unveils the inherent uncertainty which lurks in the world we live. Success is a false sense of security that can impede us from asking the tough questions. Is this good enough? Would I have made it otherwise?
Read More2009 was a very important year for test automation. It signalled the dawn of a new era of seriousness on the subject. Eight years after Cem Kaner and James Bach published Lessons Learned in Software Testing, a landmark piece which helped defined the QA role as we know it, QA experts turned to automation and its proper integration into test strategy. Along with this awakening came several key publications that till today, are seen as major contributions to the test automation and QA world.
Read MoreAs testers, we didn't use to give much thought to our machines. Especially when we did only manual testing. The QA function wasn't any different from that of the business analyst in terms of computational needs. We got the standard company machine, which was most likely a PC. Even more so if the company was not particularly in the tech industry. All we needed was a machine that could run the software which we were testing.
Read MoreI think it's fair to say that in the QA world today, if you know nothing about test automation, you should be worried. QA isn’t what it used to be 15, 20, years ago. Testing is getting more technical, and the very trade now demands a completely different set of skills.
Read MoreMuch has been said about which programming language should be used for building your test automation scripts. This is easily one of the most contentious issues at the beginning of any test automation effort.
Read More