The future of automation and startups
The IT organizations of any type of company or startups or individual software developers are currently grappling with a multiplication of application development projects with, at the same time, a contraction of release times, which is not always matched by an increase in the budget or resources. An even more challenging scenario if we think that companies rely on very complex processing infrastructures. A normal organization can depend on a series of applications developed to work on different operating systems, which use different front-end clients, involve numerous business processes and interact with many separate data sets. Testing all possible permutations of these components creates a highly complex situation, with hundreds or thousands of test scenarios.
Any software errors can cost a lot, in terms of lost sales, unproductiveness of employees, customer dissatisfaction, but also demoralization of development teams and Qa. Moreover, the more advanced the development phase in which the defects are identified, the more expensive these are to be corrected (“Correcting a detected fault in the production environment can cost more than 100 times more than solving it immediately in the planning phase” reports Hp in the white paper ‘Best practices to implement solutions for automated functional tests’ ).
The automation road, usually, reduces the risk of inefficiency and ineffectiveness of the solutions; ensuring a broader coverage, automated functional tests reduce the risk of production errors and improve Roi.
And the decision to automate the test process or not should be based on Roi’s criteria. In general, the return is positive when the application requires regression testing, involves multiple creation / patching / correction tasks, must be tested on numerous hardware or software configurations and supports a large number of users. However, automation is economically convenient even when repetitive tasks such as data loading or system configuration are involved or if the application must meet a specific SLA. On the other hand, it is not recommended when testing the usability of a user interface (Ui), conducting exploratory tests or when applications are not yet mature.
However, when assessing the potential benefits of automation, it is important to also consider intangible benefits, such as higher morale and greater tester satisfaction, greater customer satisfaction and loyalty, the better reputation in terms of software reliability between end users.