Blue Prism Intelligent RPA is well suited for the processes which are rules-based in nature. This software works well with web based application integrations. It's very easy to capture the object details and code the workflow with ease. The record functionally will do the trick most of the time and will save a lot of effort in coding the workflow. Work needs to continue in the surface automation part. It works with surface automation but there are chances of failure sometimes and we feel like the control of automation is very fragile.
When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.
Object handling can be improved more and instead of going through each and every object to find its functionality it is hard and only the experienced BP tool user can understand.
The identification of the elements can be improved much more with having useful details in place instead of only using the Indexes for the elements.
In the environment variables pane, they can add some grouping facility to divide the variables in the environment variables section.
Can improve the calculation stage for doing string operations using the VB commands instead of using code and inbuilt native functions to save time.
Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.
We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.
It's easy to handle and automate. Saves time and money in significant manner. Once a process is implemented, it performs the tasks with more than 95% accuracy so that's a big help. Costing is a bit high and object recognition work may need time to be hands on that's [the reason] this rating.
As I mentioned earlier, the reason I use Selenium is because there is a fairly widespread community of users, and user support services are at a good level. because the application is open source, it works on many platforms (Windows, Linux, IOS) without any problems. In addition, it gives us a lot of options for writing functional tests. For errors that we receive through the application, we can easily find the reasons for errors in the forums.
Support is good and now with time online support in other forums is becoming available as well. Blue Prism support in itself is also good. Documents and blogs can help to find the solution. Since it's relatively new, sometimes if I'm stuck it can take time to find the solution or connect to their team.
Selenium does not have technical support available easily. You have to go through forums to get the information you need. However, there are excellent forums out there that make it easy to troubleshoot. The open-source flexibility makes it difficult to have dedicated support.
We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.
Better User Interface.Better customer service.Easier to learn and use. But has greater risk compliances. Less preloaded automation. Less editing features and a big no while working on big projects. Fluidmesh is better in pricing and better management of multiple projects but I believe Blue Prism is perfect for beginners and small-scale companies.
At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.
For a level of medium projects, Blue Prism performs well, and the speed of execution is good. In our organization, we are applying for medium projects, where we can increase the workforce of our employees.
Blue Prism's Client Server Architecture is good, because we need such a feature to implement automation.
When it comes to pricing, I personally feel that it is costlier.
