3 key arguments supporting / debunking test automation technique and process automation requirements collision?

Synopsis : This post will cover my personal opinions about PROS AND CONS supporting / disagreeing to arguments driving this collision of simlar-on-the-outside areas of RPA and Test Automation.

Following are formulated based on limited sources of information from the world wide noodle stack. I will selfishly claim that there is room for extensive research on this, and invite your comments and thoughts, to plug this gap.

#1 : Both areas have similar "Critical Success Factors" deep down.

PRO : A good software test automation resource and RPA expert will exhibit the skill of "understanding the business processes".

ANTI : Some specific requirements in each areas stand equally important, such as "Systems development thinking" for Test automaiton and "Business process exceptions handling and impact" on the RPA side.

Consolidation : On the prevalent similarity level of Critical Success Factors of the two roles, one cannot guarantee the successful consolidation of workforces. In my opinion, it may be easier for a Test Automator to be a RPA Automator than vice-versa.

Gelato for thought : Seek.com.au returns 88 counts on RPA and 902 counts on Test Automation keywords. 

#2 : Both areas have common stakeholder personas

PRO : While there are examples of RPA being handled by dedicated Intelligent automation directors, most organizations benefit from existing Directors and CXOs picking up RPA.

ANTI : In most cases, even where QA organizations are given RPA responsibility, separate teams are being formed for RPA specialists.

Consolidation : In almost all places the Lines of Business and thier operational demand is driving the RPA need. In organizations where trusted advisor bridges exist between Business and IT, existing IT units have a higher success at securing RPA. In top down strategic focus on RPA, depending on the extend of focus, higher possibility of a new division / director of innovation through Intelligent Automation. An exception that threatens to be the norm is if the LOB setup "Shadow ITs" for setting RPA up.

Gelato for thought : Linkedin search returns 8,226 Australian CXOs with about 807 of these with Automation keyword included.

#3 : Tools supporting automation both areas are similar

PRO : In many cases where existing QA units have been called in to deliver RPA, there is a higher tendency to use Test Automation tools for RPA.

ANTI : Test automation solutions cater to a broader set of use cases including negative and edge cases, not just straight throughs. Test management capability, requirements coverage, all are additional features that add value to test automation solutions. For more mature test automation practices, the features that aid virtualization, maintenance friendliness all add further complexity in the face of RPA solutions. RPA solutions will further face security, orchestration and ease of use requirements.

Consolidation : Despite the gap between the practices, there is a case to consolidate. Both by way of tools and skillsets, as well as acceleration through re-use. Enterprise Automation will help IT - Business relationships further.

Gelato for thought : Linkedin search returns 25,288 hits for Australian IT Business Partners. That gives every CXO 3 IT Business partners, on average.