IBM Robotic Process Automation with Automation Anywhere is a robotic process automation solution combining business process management tools from IBM with Automation Anywhere's bots and automation capabilities.
$840
per month
SpecFlow
Score 10.0 out of 10
N/A
SpecFlow is an open source BDD for .NET. that aims to bridge the communication gap between domain experts and developers by binding readable behavior specifications to the underlying implementation.
N/A
Pricing
IBM Robotic Process Automation
SpecFlow
Editions & Modules
IBM RPA On premises
Platform starter pack, starting at USD 840.00 per month
per month
IBM RPA Software as a service (SaaS)
Platform starter pack, starting at USD 840.00 per month
While it can be applied to various scenarios, its suitability can depend on the specific requirements of a given task or process. Here are some scenarios where IBM RPA is well-suited and scenarios where it may be less appropriate: Well suited: 1.Data Entry and Data Migration: RPA can efficiently automate data entry tasks, such as copying information from one system to another or migrating data between databases, reducing the risk of human error 2. Report Generation: RPA can generate routine reports by extracting data from various sources, formatting it, and delivering the reports to the relevant stakeholders, saving time and effort. 3. Email and Message Handling: RPA can help manage and categorize emails and messages, such as routing customer inquiries to the right department or processing routine email requests.Less suited for: 1. Cases where there is High Variability: RPA may struggle with tasks that have a high degree of variability, where each case is unique and difficult to standardize. 2. For Complex Decision-Making: RPA is rule-based and not designed for complex decision-making processes. It cannot replace the judgment and decision-making capabilities of humans. 3.Tasks Requiring Creativity: RPA is not suitable for tasks that require creativity, innovation, or problem-solving skills, as it operates based on predefined rules and logic.
It is best suited for implementing the automated test cases in a human readable form so it's easy for non-technical members of the team and stakeholders to understand the test cases, features and the functionalities of the application. Automation of Integration tests and End to End tests are good use case. It is less appropriate or situations where the focus is only on the writing and maintenance of unit tests.
It was programmed to navigate to the web page requiring reCAPTCHA verification, locate the reCAPTCHA challenge, and generate a screenshot or other data to present to a user for manual input.
It was programmed to extract employee data from emails or forms, update the employee record in Workday, and send automated notifications.
Versatility to be used in combination with different kinds of automated testing like automated performance testing, API testing, UI testing etc. I use JavaScript, Selenium, C#, email testing libraries, database testing libraries in combination with BDD with SpecFlow. I am able to use all these with SpecFlow to make my automation framework to be able to automate any kind of automated testing.
It provides different widely used runner options like NUnit, XUnit etc. Before I started to work on establishing proper test automation in my workplace, the previous automation framework (non-BDD based) as well as unit tests used NUnit runner. The transition to using BDD was smooth because we could use the same runner and there were no compatibility issues.
The auto-complete feature is good. I use it with Visual Studio as well as Rider and I don't have to recall the entire Gherkin statements. I just type a few words and the entire Gherkin statement implemented in framework is auto-suggested by SpecFlow. It saves time and context switching.
Security and data privacy: IBM RPA may not have the strongest security features, which can leave sensitive data vulnerable to breaches or hacking.
Scalability: IBM RPA may not scale well to accommodate larger businesses and more complex processes, which can lead to performance issues and increased costs.
Customization: IBM RPA may not provide as much customization options as some users would like, making it difficult to tailor the software to specific business needs.
SpecFlow does not accepts optional input variables in the methods defined during Gherkin statement implementation. Cucumber supports optional input variables in the methods defined during Gherkin statement implementation.
The tests identified while using SpecFlow with NUnit removes all white spaces in the scenario names. It makes the tests less readable. If the white spaces are not auto-removed, it would be much better for readability as well as their actual identification in the repository.
By implementing IBM Robotic Process Automation, we realized that they are digital robots with a great impact on our manual tasks, generating good automation capabilities that are beneficial to the entire company.
IBM RPA is a very powerful tool, it has almost all the features that are necessary to build, implement and manage highly functional robots. The learning curve is very fast, so excellent skills are acquired. It is not necessary to have strong programming knowledge because its use is very easy. It is just drag and drop commands. By adding rules and logic, wonderful robots can be achieved.
IBM has done a great job with enablement for the product. There is documentation for use-cases, development videos for beginners, and a community forum that has proven useful for getting started with the application. Although the resources cannot solve every problem a developer comes across, they have been very beneficial to our technical team.
I am main developer of the this implementation. I have faced many chanllenges in implementation as IBM RPA not provided direct commands to automate Excel. I enjoyed in finding solution and best approach for the implementation
I've always had excellent service and had no trouble communicating. It has aided in my understanding of how I can continue to use the bots. Reading peer assessments reveals that while IBM RPA demands a substantial initial financial commitment, it justifies its cost, unlike Blue Prism RPA, which does not.
SpecFlow is .Net based which supports C#. Behave is Python based. Cucumber is Java based. Ghost Inspector is no-code based but provides very limited testing features. We wanted to implement BDD so we rued out using Ghost Inspector. Most of the developers in my team are C# experts so it was decided for everyone's comfort to go for SpecFlow rather than Behave or Cucumber. It's import to have technical experts in the language of the automation framework because there are many situations where the solutions to the test automation needs are not straightforward and implementing those requires expertise in the related programming language.
IBM Robotic Process Automation has helped save on cost and time as it is able to automate tasks that are repetitive and routine tasks.
IBM Robotic Process Automation has helped us increase productivity. This is because it is able to perform tasks with a high degree of accuracy and speed.
It has enhanced compliance as it is able to automate compliance-related tasks. This has helped us improve our reputation.
Everyone stays on the same page regarding the behavior of existing functionalities whether it be technical or non-technical individuals. So there is less need for multiple people to get involved which saves time and thus money.
Reusing the same code through the implemented Gherkin statement saves test automation time and thus reduces cost.
We combine SpecFlow with other opensource testing technologies to make our automation framework more versatile which further saves costs for us.
