Everyone can cook(automate)! [2]

...continued
   

• You need to investigate and find some tool appropriate for your application under test(on this topic I can write more in future)
• Set a realistic goal for the start (forget about 100% automation). You need 2-3 tests that run every day and sends you systematically a test report. The tests should be really simple: validLogin, do something, logout. Here you have 3 tests
• You need to get some /virtual/ environment to run your tests without breaking the tests run accidentally.
• Your developers need to have CI(continuous integration) builds. You should be able to get new build of AUT each day

Now you are having something working on regular basis and you are able to add mores tests, BUT ...

• Your AUT changes UI and functionality too often
• You need to spend time for adding new tests and supporting old ones
• Management get excited and rise expectation - you have so much free time now when automation is doing your work :-)
• You start to notice that "testability" of AUT is preventing you to advance in automation
• It seems like time spend for automation is too much and it is better to do those 3-5 test manually...

To be continued...