Robotic Process Automation (RPA) can be regarded as a special kind of Business Process Management (BPM) that relies on GUI automation adaptors instead of regular interfaces for intersystem communication. Another difference between RPA and standard BPM is that RPA processes do not need to be defined from scratch as RPA is basically transforming an operator’s implicit process knowledge into a workflow definition to be executed by the robot’s workflow engine. In this context, the basic idea of Test Driven Development (TDD) can be used to jump start requirements engineering and process definition by leveraging the operator’s interaction with the workflow targeted for automation. This paper presents a conceptual approach for integrating TDD with RPA development: In a first step, the manual process is enriched with probes that record input and output values for each execution of the workflow. Users then manually perform the process using screen recording and the probes to define annotated test cases stored in a backlog. TDD works by selecting an arbitrary recording from the backlog and using it for automating the equivalence class of test cases to which it belongs. All test cases from this equivalence class are then removed from the backlog. These two steps are iteratively repeated until all test cases are covered by the robot process definition.
Minimal Effort Requirements Engineering for Robotic Process Automation with Test Driven Development and Screen Recording
—