Inflectra Rapise Reviews

I use Inflectra Rapise in my company since we have contracts with a lot of government entities. Our company could not get the tool to work in a government network because government networks typically have a more secure setup than commercial entities. The tool could never get past the setup of government entities, and they are not going to rewrite their tool for specific companies or organizations. Either Trellix or the government settings within the networks would kill the product and not allow Inflectra Rapise to be utilized.

Inflectra Rapise didn't help our organization, especially since most of the organizations use SAP GUI and haven't switched to SAP S4HANA or SAP Fiori because of the initial cost of doing the changeover.

The most valuable feature of the solution is its versatility. Any automation tool needs to be more than just something meant to be your enterprise solution. It needs to work across different technologies, whether it revolves around .NET, Visual Basic, Oracle, or any tool in today's market, so it has to be versatile because otherwise, it's a very narrow tool with scope for just certain software products.

Inflectra Rapise needs to expand its ability. I spoke with Inflectra's executive account rep on the need to expand the tool's ability. The problem with Inflectra Rapise is that a lot of companies are still using SAP GUI. Inflectra has no intention of building Rapise in a way that allows it to interact with SAP GUI. Inflectra Rapise has very limited value for the companies I work with because they they still use SAP GUI since their top priority is SAP testing, and they want to get into automation, for which they need a tool that cannot only used to automate processes, but can also do end-to-end testing where you are not only using SAP GUI, but you are using the interface with old legacy systems that are still in use or with today's more modern technologies.

In the future, the tool needs to increase its versatility. If I am at a company that uses 23 different technologies, like .NET Visual Basic, Oracle, SQL, or whatever, Inflectra Rapise needs to be made as a product that is an out-of-the-box usable tool for any technology.

I have been using Inflectra Rapise for six months. I don't remember the version of the solution, but it was one from the previous year.

Stability-wise, I rate the solution a four out of ten.

The product's stability just wasn't there since, in a very tightly secured environment, it just doesn't work.

Scalability-wise, I rate the solution a five out of ten.

Inflectra's support was fine. I noticed that with Inflectra's support team, the problem was when you found an issue that is not a part of their roadmap for improvements over time or in their future versions, then it just wasn't addressed at all.

Previously, I used Micro Focus UFT One, which used to be HP UFT, and before that, it was Mercury Interactive. I also used QuickTest Professional extensively, but the tool couldn't outlive its lifespan.

The tool's installation wasn't an issue. It was the execution part of the tool that was an issue since it cannot be executed in the environment of a government entity because of all the extra layers of security that are laid out.

The solution is deployed on an on-premises model. I represent a lot of government entities, and unless they already have approved cloud usage, most of their organizations operate on an on-premises model because of security concerns.

I rate the product's price an eight on a scale of one to ten, where ten means very good pricing.

During the evaluation phase, I have used Tricentis Tosca. Tricentis was a solution that my company was able to install without any issues in a tightly secured environment, and we were able to use it in a tightly secured environment during its evaluation phase with no issues. Tricentis could be used to automate any existing technology out there that is used today by large market corporations or government entities.

I did a deep dive with a couple of Inflectra's tools, which consisted of not only automation tools but also a test management tool called Rapise, which was a decent tool that was lacking in a few features since some requirements that companies have couldn't be met with it.

During the evaluation phase of Inflectra Rapise, I realized that it doesn't work well if your business deals with government entities. Inflectra Rapise does not work with government security setup. Government IT systems continuously crashed Inflectra Rapise, and it wasn't allowed to be fully launched or utilized. Inflectra Rapise doesn't work with SAP GUI at all. The tool works with SAP S/4HANA or SAP Fiori, meaning you would have to have the aforementioned SAP products installed if you want to work with Inflectra Rapise and the original SAP GUI version, which a lot of clients use. The tool is ineffective as it doesn't work with SAP GUI, and Inflectra doesn't even address the issue.

Inflectra Rapise needs to make sure it works in today's environment because of all the cyber concerns, which are the top concerns in almost all of the large companies, where tools for help are put in place, and unfortunately, such tools most of the time cause the automation tools to not work. Inflectra Rapise needs to put up with the security settings of the current time and basically expand the tool to utilize more technologies.

I rate the overall tool a four out of ten.

We primarily use this solution for end-to-end automation with Salesforce. We automate all the authorization of Salesforce Lightning and Classic versions. We use it for SAP S/4, which is the latest version of SAP. We basically use it on HANA and in the Cloud of SAP and even for other ERPs.

We always use the product for end-to-end automation test cases, never for unit automation tests. We use it to automate functional testing of end-to-end test cases for evaluating the impact on the databases and to override the time that we need to use the front end. That is all. 

Moreover, I have found the correlation of the values for Object ID to be valuable. These are two of the most important features that are very well managed.

The solution is integrated well with the Spira Team. Even so, it would be good if there could be more integration of Inflectra Rapise, since not all customers use the same tool for test management and automation integration. We would have better results were we offered a wider range of options for integration. Even though the product has good integration, a little more would be better, such as with, for example, Rational and Solman solutions in SAP. While we managed to fix the problem, a native solution would be preferred.

We have been using the solution for nearly eight years.

We had some issues with the initial version of the product, but it has demonstrated itself to be very stable over the last three years.

Our maintenance of the scripts has decreased by 75% or 80%.

It's incredible but the support and and maintenance of Inflectra Rapise's scripts is less than 30% of the effort that was involved in maintaining Selenium. It's very easy and this is the reason that we are switching everything that needs handling from Selenium to Inflectra Rapise. It is easy to maintain and provides a benefit in cost and efforts a 90% reduction factor in the maintenance of the scripts.

As Inflectra Rapise is on-premises and not cloud-based, it lacks a server license that can be shared with the users of the license. So too, there is no server for validating the number of users that are active, meaning each one is on-premise. This does not pose any problems due to it's one-to-one nature. It's open, without affording the option, for example, of a licensed server that would mandate validation with the server. If one has the the number of users available, the product can be directly installed in his own computer, meaning there would be no issues with its performance.

Inflectra Rapise's technical support is one of its best features. We have been utilizing the product from the get go and have benefited from complete support straight off the bat.We have all the documentation and tutorials. Response time is less than 24 hours. We work in several South American countries and are the beneficiaries of support and results. It's incredible, really. 

We could be at the end of the world and still receive the tech support we need. Response time can be under two hours. This is something that isn't common in South America. Even if they can't provide the solution, they will call you to collaborate and point you in the right direction. The tech support is incredible. I believe that their support team is from the development part of the company since it's superior to the competition.

We previously used EHP and I took the decision to switch the company to Inflectra Rapise for several reasons. One reason involves licensing costs. Another one is that Inflectra Rapise offers better support, which is direct and not across a dealer. The growth of the solution is a further consideration. In comparison with the competition, the solution has offered many enhancements from one year to the next. 

The initial setup of Rapise was incredibly simple because one can start to use it as soon as it's been installed. The company responsible for the product provides good tutorials and manuals for getting started. No special knowledge is required for installation, deployment or  configuration.

We have been utilizing Inflectra Rapise from the beginning, starting from around five years ago with the release of its second version. Installation and deployment took no more than 15 minutes. 

There is no need for us to make use of an integrator, a reseller or a consultant for the installation and deployment. It's so simple that we were able to do it directly, on our own, without the need for any support.

There are 12 people in charge of deployment and maintenance of the product. It is in their discretion when to switch versions. Broadly speaking, we coordinate this with the support staff of the Inflectra Rapise company. By and large, if they tell us that there are no problems with the continuous running of the scripts or with bugs and compatibility, we would make the switch for the entire team. Usually there are no problems. Occasionally, we encounter a special script needing adjustment but this happens in less than five percent of cases. 

We pay for the licensing of the product. For Inflectra Rapise this is on-premises. The Spira Team is Cloud-based. While the subscription cost is monthly, we pay in advance for the entire year. The Inflectra Rapise licensing fee covers support for the entire year because it's on-premise and we pay different sites for the license. Consequently, we don't have to pay too much. We pay no more than $50 annually for support of each one of the licenses.

Prior to choosing Inflectra Rapise, we evaluated Kafka, Selenium, Selenium for Jira and Zephyr. 

We obtain the results of the automation plan that is directly impacted by the Spira Team. Then, we take the results of the entire device without the involvement of any manual staff. We, subsequently, receive an automatic simultaneous report from both the manual and automation features that are in place.

Previously, I made use of the ALM, or HP Quality Center, and I switched to the Spira Team. With the robot, we changed EHP to Inflectra Rapise. We changed the setup, the suite of solutions, from HP to Micro Focus, and then to the Inflectra Rapise solution. We are very happy with that.

We generally have 100 users of Inflectra Rapise. While I don't recall exactly which version we use, I know it to be the latest one, both as concerns Inflectra Rapise and the Spira team.

We have a contract which Inflectra Rapise support and it is excellent. That is the driving force for continuing to use Spira and Inflectra Rapise and we are really provided with the guidelines and the support for operations.

When it comes to the support contract, we have it in production and, no more than two months after announcing it's availability, new functionalities beyond the last version are made available, even though we do not consider this period to be short. 

The Spira team is cloud-based and Inflectra Rapise is on-premises.

While my work history primarily focuses on IT in a variety of positions, I have also worked in development, as an IT manager, and I am currently in charge of PI. However, I have an economic background from my studies at university. I have always kept an eye on the cost-benefit balance. Overall, I feel Inflectra Rapise to be a good business tool, as it provides a good balance between the costs and the benefits.

We don't even feel the need for retaining an expert since, if someone leaves the company, we can utilize Inflectra training, documentation and support by way of a replacement. This is relevant and covers most values in Latin America, as a person may work for the company in one month and be gone by the next. 

From talks I have had with people who have left the company about other tools they have utilized, even for open source software or small licensing costs such as those of Kafka or EHP, they contemplate the benefits of Inflectra Rapise's features when making an evaluation. 

I would rate it a nine out of ten. 

We primarily use the solution for managing the database for our organization.

The platform overall is good.

It's pretty straightforward to set up.

The solution offers good availability.

So far, technical support has been helpful.

The maintenance is very difficult. We've only been using the platform for three months, so I'm not sure if that will continue, but right now it's an observation I've had.

The solution needs to improve its compatibility with other solutions.

The solution is quite new for us. I've been working with the solution for three months. We're still testing it out.

I can't really comment on the stability just yet, as we're still struggling with maintenance issues, and the stability plays into that.

The scalability of the solution is low. You can't scale it too much. It's also very complex. It takes a long time to go through the documentation.

We've had a chance to contact technical support and so far they've been good. We've been satisfied with the level of support they've provided us so far over the past three months of use.

The initial setup was straightforward. It wasn't complex at all. In fact, we found it nice and easy.

I don't have any idea about the pricing on the solution right now. We're still evaluating the product.

We're partners with Inflectra.

I'd rate the solution seven out of ten. The compatibility needs to be improved. If it was, I'd rate it a bit higher.

I'd recommend the solution. Writing the scripts etc. is very difficult, but we can increase the availability quite well. There is definitely a minimum skill set required in order to use the solution. It's good to hire someone that knows a bit about the solution to make it easier to implement it. Even so, for us at least, the maintenance has been challenging.

It has great record and playback functionality and excellent cross browser testing functionality. Automated Manual test recording feature and executing hybrid (manual & automated test) functionality is very nice.

• Web Application Testing is very strong
• Custom user functions can be created and easily dragged and dropped into the test project
• Cross-browser testing is excellent
• Report Export to Excel and Export to PDF functionality
• Webservices test and Manual test Functionality is very good
• Test Xpath and Test CSS tool is unique in Rapise
• DoQueryXPath and DoQueryCss functions are unique

We moved to agile recently and in order to support agile delivery of our product we needed to release a new version of our software every month and Rapise helped us a lot doing so. Tests are automated in no time and now they run every day. Earlier where we used to get only 3 or 4 manual test rounds every iteration, we are now getting almost 1 a day. Rapise helped us identifying regression issues on the same day decreasing the overall cost of defect fixing

• Only support Java Script – Should have at least an option to use two languages (TestComplete gives 5 and Ranorex gives two)
• Mobile testing is still basic and requires Appium installed
• Built in compare files functionality
• Keyword test approach is preferable to their script approach
• Soap Testing Support

I've used it for two years. It has great record and playback functionality and excellent cross browser testing functionality. Automated Manual test recording feature and executing hybrid (manual & automated test) functionality is very nice.

No problem during deployment.

It has some stability issues where the tool crashes sometimes on Windows 10.

There is one small issue where the older licenses need to be uninstalled first. It would be very good if the installation process also allows seamless upgrade.

I've never used it but we do get notifications from Inflectra about product updates.

We used to use Rational Robot which is very old technology and doesn’t support all the latest platforms. We moved on to rapise because

• It supports almost all the latest technologies
• Licenses are cheaper than other tools such as HP UFT or Tosca Testsuite
• Installation is relatively simpler and no hassle in using the tool right from scratch

The initial set-up was straightforward. Just double clicking the exe/msi file will install the tool. I would suggest trailing on test system first. Although Rapise installation is straightforward, Spira Team configuration can be a little tricky sometimes.

The implementation was straightforward. We did not use vendor support.

We saved thousands of dollars because the Rapise implementation gave us 30 or more executions for every release compared to three or four. So huge savings on manual testing effort plus easy detection of defects is very cost effective.

I would suggest going with a single license first and then upgrading it to 5/10/20 licenses.

Ideally, you should use Rapise with Spira Team which can be used as a version control system and also repository for automated tests. Keep Mobile/Web/Desktop Tests separate Also, make sure all the common functions are managed separately in User functions and call them in your tests using parameters. Make sure that the manual test functionality in Rapise so that all non-automated tests can also be executed as part of the suite.

Record Playback is good but can make things complex when there are dynamic object, so I would suggest learning the objects manually and creating your tests using drag and drop approach. Make use of command line execution so that it can be integrated using any continuous integration tool. Make use of JIRA integration tool – Though the integration is kind of duplication and sync but it works ifthe JIRA is your main defect tracking system

The scripting of this tool is easy and user friendly.

I chose it because it's based on Java script to open source.

I faced one problem where it can't validate the colour of images and text. Also, it could not automate the mobile app, and this needs to be included.

I've used it for one year.

There were no issues with the deployment.

There were no issues encountered with the stability.

We had no issues with scaling it.

8.5/10

8.5/10

It was straightforward for me.

We used a vendor team.

You should use it for automating because it is user-friendly.

The most valuable features are that you can automate many applications and that it's not only a web-based application. You can also share scripts with team members.

The product has made things easy for me as a software tester because I can use the same script to test a lot of things. I've ben able to save a lot of time by doing this.

What I have noticed about Rapise is that sometimes when you keep on using the same script, it fails many times. The other thing that can be improved is being able to play the script by setting the start point from anywhere in the script. When recording date-of-birth in the following format, 12/06/2015, and use tab to go to another text box, this messes up the script because of the way it records dates. I think that could be improved.

We just started using it and are still working it out.

We haven't had issues with deployment so far.

It's been stable for us.

We're able to scale as needed.

Rapise is a good automation tool that's easy to use and learn, and you can share scripts as a team, which is very helpful.

The ease of recording automation scrips blew me away the first time I used the product. I have been doing automation for over 10 years and I am used to a project taking a week with 100% time allocation to it and that assumes no surprises. The first time I used Rapise I completed the automation scripts for a full application in a day. I was shocked how easy it was.

Prior to using Rapise it would take us weeks to automate an application. It would be layers of process to record, then edit JAVA to accept UNIDs that would change on each submission, finally the run/fail/edit cycle till we could get it to function. When the application was updated it would end up being faster to just rewrite the script from scratch.

When we moved to Rapise all this seems to be the seamless process that we have all been promised for years, but have not seen. Recording was quick and easy, defining verification points did not require a JAVA developer knowledge level, and editing the script to accommodate new application features was a simple process.

When there are failures in a nightly run of batches of scripts, it can create a blocking situation where all the following scripts will fail due to unexpected results. This can take a little time refine your test cases to ensure all application pages get closed out before starting the next set of test scripts.

4 years

There have been issues when upgrading if the license is not disabled before beginning the upgrade install. It would be nice if that was integrated in the install process.

We have a configuration that integrates Rapise with SpiraTeam. (I highly suggest this configuration). As the product as matured the process for creating the automation files in the SpiraTeam repository has changed, but the backward compatibility of the product had issues. This only happened with one major upgrade and now that the change has been completed I don't expect to see that problem again.

None in 4 years.

Outstanding customer service. This is the same team that I have worked with on SpiraTeam/SpiraTest. They are all very knowledgeable with their applications. When we call in for support we do not get the normal unskilled person reading from a script and directing us to a web site or another team.

The customer service team is the technical support team. It is so refreshing to have your initial call answered by a person that can resolve the issue and not pass you off to another person. They take ownership of the call and provide you a solution.

We used IBM Rational Functional Tester before Rapise. The Rational solution was painful to modify, the process of automating an application would take weeks, the cost was outrageous, and support was less than helpful. One of the best decisions we have made to move from Rational to Rapise.

Initial setup for Rapise was very simple and straightforward. So much easier that setting up Rational, not sure I can even quantify it. Difference in installing Windows from scratch as compared to installing FireFox.

I did the implementation myself.

Price is very reasonable, much better that many other products of similar functionality.

Yes we did, we had been using Rational and we looked into a few others.