No Automated Testing

Don't be taken aback if you see following changes in software testing (read people perception) in 2012 - Management's Disillusionments Tester != Bots Testing != Monkeying around Tester != Project delivery blockers More tester != More defect discoveries Testing != Just keep testing More tester != Less time needed for testing Automation tool != Less manual testing needed != Less testers needed Tester salary = Dev salary (sigh) Testing certificate != Expertise Automated tester !> Manual tester (though vice versa may be true)

You might find umpteen resources on learning to write UI automation. But rarely you find any guide on writing bad automation code. Bad automation code is not actually "bad" especially when you consider following - Bad automation code keeps you job safe. Well who can understand the code other than you. Gives you an opportunity to ask for more raise as you are the only one who can maintain the code you write Lets you keep your head up as you the geek of your company who knows that abstruse code  Now coming to writing bad automation code, here are some silver bullets - Record and Replay is the core or writing good (read bad) automation code. It has so many advantages which just out do many others. Biggest being you don't have to write any good code (read bad), tool does it for you. The way to convince decision owners in to enlightening is to let them know that record and replay does not require any special skills. Even your HR can do this.