In our company, we use the REFramework for all the projects that we are building as a standard and a best practice…
However, POC’s have short time period to complete, and introducing REFramework for a POC might make things little complicated because of the time frame we have. Hence, for a POC, we might choose not to use REFramework and stick with the basics.
Basics means, we still use multiple workflows, but combine them in a separate sequence or a flowchart depending on the requirement. However, if there is time, we could introduce REFramework as well. This depends on the requirement and the complexity of the task. I did one POC, few months back, it was not that difficult, so I used the REFramework. But for complex POC’s, we didn’t use it.
However, considering a project or a full scale solution, we always go for the REFramewok as it has lot of benefits and added reliability. As you may be aware by now, REFramework provides a good level of error handling, retrying ability in cases of failures, business rule and application exception handling any many more. These are very important to have in a full scale production solution to make the solution stable, reliable and friendly. It also helps us to breakdown the entire automation solution into separate segments, and sometimes as separate individual solutions which can be independent from one another. This also helps to maintain the code, and also for parallel and separate executions without depending on other solutions.
Hence, I would recommend to always use the REFramework for all the solutions irrespective of the automation project or the frequency it is being executed.