Deciding what to automate – part 2<\/p>\n

\n

Once you what to test, find the subset of what to automate<\/p>\n

\n

Again everything you want to ‘test’ cannot be ‘checked’<\/p>\n

\n

It’s best to be smart about what should be automated<\/p>\n

\n

While the most common answer to this question is ‘automate what we can’<\/p>\n

\n

There’s a fundamental flaw in that, not necessarily all we CAN automate is WORTH automating<\/p>\n

\n

If a feature is hardly changed and used, automation efforts are best spent elsewhere<\/p>\n

\n

Conversely, if a certain feature is time consuming to test and has to be done every time, I’d rather automate that feature.<\/p>\n

\n

More factors IMHO to help deciding what to automate here:<\/p>\n

\n<\/div>