Micro Focus Service Test [EOL] vs Visual Studio Test Professional comparison

"Service Test provides different opportunities in SOA testing, which helps us to provide better SOA solutions to clients."

"The data validation used to take a lot of time, and now through Service Test it is done within minutes."

"It has helped a lot in reducing the time that would be put in for a particular module."

"My team integrated test scripts from HP Service Test into HP QC ALM test management tool, which made it easy for the test team to monitor and measure test execution."

"The most valuable feature is the graphical workflow."

"Service Test is user friendly and requires QTP developers a relatively minimal learning curve to catch up with any changes in features that may get introduced by newer versions."

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

"It is a good and user-friendly tool."

"The most valuable feature has been to store all our packages in one place including SSIS packages, SQL tables, TFS and SSR."

"The solution is easy to use and they have also integrated with Microsoft."

"At the start, many years ago, it was not the best solution, but now it is the best in a technical development environment."

"Visual Studio is the easiest to use."

"The tool is free, resulting in no costs associated with its use. The absence of price makes it cost-effective."

"It is very easy to use, and you can handle a lot of things together at once in one package, which is a good point for us."

"They should come up with something like Fiddler to see the service status."

"Service Test technology is primarily meant to test applications without user interface therefore falling short of helping in the test of UI applications unlike QTP."

"Its pricing is a bit high when compared to other SOA testing tools."

"If the license server went down, all the HPST nodes would fail their automation tests, which would bring down the entire automated test infrastructure and people would think the current build was bad."

"When an entire script is ready in the tool and there is a modification of WSDL at the final point, you need to form the code from scratch and there will be a lot of objects in the tool that wouldn't work after the inclusion of the new WSDL, which requires significant manual effort to fix."

"It's an expensive solution which is an issue for us."

"The price could be improved."

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

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

"Sometimes Visual Studio is slow. It uses a lot of resources like memory and processing power. You should optimize the performance by only installing what you need on your machine. Don't install unnecessary things that will slow your machine."

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

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

"Visual Studio Test Professional should include more automation."

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

"Visual Studio Test Professional is a very expensive solution."

"Visual Studio Test Professional is not an expensive solution."

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

"We pay a yearly licensing fee for Visual Studio Test Professional, which is expensive."

"Users have to pay a licensing fee for Visual Studio Test Professional."

"The product is very expensive."

"The pricing is expensive."