Automate what users do first (Getting Started Manual?)
I like to try to automate important, useful things first. When customers first use the System-Under-Test, I want them to have a good experience. If we have a Getting Started Manual or equivalent Help page, that’s often a good place to start. • Isolate the maintenance effort Test Suites are constantly evolving – due to added tests, changing requirements, and changes in the System-Under-Test. I want to be able to maintain these tests without having to constantly throw large chunks away and rewrite them. • Produce “readable” scripts I want lots of people on my QA Team to be able to go in and at least understand what the Test Suite is doing. That’s often made simpler by having a scripting language that is readable. It’s often aided by having well-commented scripts, too. • Ability to reset the environment as needed I like to have a Test Suite that’s able to reboot a machine and continue. I find that’s often needed for a really full-featured Suite. I also like to be able to re-initialize a d
