Software test automation tools have been available for decades, but they have generally only been only been leveraged by most technically advanced organizations. With constant increases in application complexity coupled with budgetary demands for improved efficiency, implementing an effective test automation solution has become a priority for mainstream organizations in both the public and private sector.
Test engineering today is changing rapidly to provide whole new levels of efficiency and accuracy. One area that has garnered a great deal of focus recently is Task Automation.
According to Wiki, Task Automation is “Coding conventions that allow having simple scripts or programs whose job is to process source code for some purpose other than compiling it into an executable.” In less technical terms, any approach (piece of code, scripts, test automation frameworks, etc.) that reduces redundant effort is Task Automation. Then how does Task Automation relate to Test Automation? Conventional test automation involves applying software test automation frameworks to develop reusable assets (Generic functions, Business functions, Test Scripts, etc). In this traditional approach, a team of automation engineers would develop scripts one at a time on top of an established QA Automation Framework. These automated scripts (or automate scenarios) are developed according to the standards imposed by the framework (key word driven testing, data driven testing, etc).