Inflectra Rapise vs Visual Studio Test Professional comparison

"It's pretty straightforward to set up."

"The most valuable feature of the solution is its versatility."

"We always use the product for end-to-end automation test cases."

"Searching is extensive and helpful."

"Code testing is the most valuable feature of this solution for developing software."

"User-friendly ID and direct integration with GitHub are the most valuable."

"What I like most about Visual Studio Test Professional is the way people publish templates and publish integration."

"It's great for the development of .NET."

"The user interface is very friendly."

"The most valuable features are tools like IntelliSense and ReSharper."

"The integrated unit testing and extensive search features have made things easier."

"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."

"Inflectra Rapise needs to expand its ability."

"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."

"I would like to see more integration in the solution."

"It could be available for multiple platforms and other operating systems like Mac with a native port."

"It is not good in terms of performance. When you open Visual Studio, you have to wait for a while to process your code. It uses a lot of resources and has a lot of features. If we could disable some of the features, it would be lighter and faster to use. Nowadays, for some of the projects, we use VS Code for JavaScript or Python. VS Code is very light and easy to use, whereas, in Visual Studio, we have to wait because it takes time to compile or run a project. It has a lot of competitors in terms of performance, such as Intelligent ID. Intelligent ID is very easy to use. It has many features, and it is lighter to use than Visual Studio. In terms of error handling, sometimes, it shows an error before you finish your code, which can be improved. It would be good if it has a version for Linux. I use VS Code on Linux, but I am not sure if Visual Studio has a version for Linux."

"In Visual Studio we still don't have anything which can pinpoint memory leaks on a certain code line."

"The vendor must release a lightweight version of the solution."

"There are too many features with the product and I would like there to be less."

"The solution is quite expensive."

"It needs more integration with other tools for monitoring. Microsoft also needs to make it more modern to make it work with microservices and the cloud. It is a bit outdated currently."

"We pay no more than $50 annually for support of each one of the licenses."

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

"We have licensing for Visual Studio Community edition."

"Our company pays a yearly licensing fee for Visual Studio Test Professional."

"I positioned it at a mid-range level. It isn't an inexpensive solution, but considering its capabilities, it represents excellent value for the functionalities it offers."

"The product is very expensive."

"The tool is affordable."

"I think that the pricing is quite good."

"We use the solution’s community version, and the solution’s pricing could be cheaper."

"We pay for the solution annually and the price could be reduced."