Since testing cannot be automated, therefore no need to learn automation.<\/p>\n

While the first half is true, the conclusion is not..<\/p>\n

While collaborating, investigating and reasoning with people cannot be automated,<\/p>\n

The kind of applications we are building now cannot be completely ‘checked’ in person either because of:<\/p>\n

1. Size of the applications
\nLayers of abstraction have made things easier to develop, and add features more quickly,
\nMaking applications exponentially grow in size.<\/p>\n

2. The complexity level
\nDesktop apps, to monolithic web apps to native mobile apps to now miro-service architectures,
\nIt’s quickly becoming impossible to test core features of applications without a LOT of different tools<\/p>\n

3. Required speed to do the job ‘in time’
\nA first mover’s advantage can mean the make or break of the company. This coupled with the drastically evolving technological landscape for software development has spiked the need for rapid deployment.<\/p>\n

These three things are fundamentally shifting how we can adequately test applications.<\/p>\n

We need grunt workers to do the heavy lifting for us,<\/p>\n

‘Probes’ to get into the system which we cannot easily test,<\/p>\n

Which all points to the need of automation and a LOT of testing tools.<\/p>\n

#QsDaily #Automation #WhyAutomate<\/p>\n

 <\/p>\n

 <\/p>\n<\/div>