TestToTester

Me: Why did you add the new page element “For those who think Test Automation is easy, saves time, converts manual tests, etc,”? in your blog? Me: I have been asked questions like # I am planning to change my job, which tool shall I learn? # Will only manual testing experience fetch me a job? # Shall I learn some scripting language? Will it improve my chances of getting a job? # What will I say if the interviewer asks “Haven’t you done any automation”? # Why don’t you automate the program? I have previously seen a test group do that, they run the tests and next day morning they have the results? # How hard is it to automate? All you have to record it right? # Let’s build a test framework; it will surely reduce testing time? # You should not be stuck with manual testing, you should start automating? And many more, so I felt the papers by legendary test gurus could help us understand “Test Automation” better. Second reason why I added the new page element would be When I was an

“Dealing with yesterday’s bugs keeps part of our attention away from today’s bugs” – This statement from http://blogs.msdn.com/james_whittaker/archive/2008/08/11/if-microsoft-is-so-good-at-testing-why-does-your-software-suck.aspx by james whittaker grabbed my attention since I previously remember similar words from one of my manger before. In today’s software projects I feel bugs are treated humanlike. Last week my colleague asked me “What is the life of a bug?” To which my answer was - the bug is born when you find one in the program under test, the bug is issued a birth-certificate when it’s logged in the bug tracker. A developer who listened to our conversation expressed to torture it (bug). To which my reply was – the bug might die of a heart attack, or might have a slow death or might live in the dark stomaching your torture, until a day when he breaks loose, forms an army of his own or even better becomes a gladiator and takes down your empire. My previous manager used to addre