SmartBear Software, the leader in software quality tools for the connected world, is bringing the power of its Ready! API testing framework to API developers using the most popular coding languages in the world. Now developers using Visual Studio to build software leveraging the open source .NET Framework can ensure API quality directly from within their primary workspace.
Launched in March 2016 with similar support for Java developers using tools like Eclipse, IntelliJ and others, the latest TestServer .NET capabilities are introduced as part of the broader update to the Ready! API testing framework. By delivering these open source TestServer SDKs for Java and .NET framework languages, SmartBear ensures that developers can express their API functional tests in their preferred coding language.
“As testing obligations continue to spread throughout API development and test organizations, a phenomenon many refer to as ‘Shifting Left,’ application providers must become smarter about their user expectations,” said John Purcell, Vice President of Products, API Readiness at SmartBear. “It is simply not reasonable to assume development and test professionals will automatically adjust their workflows to adopt a tool. In fact, the opposite must happen.”
With this Ready! API 1.8 release, SmartBear is delivering key improvements to both desktop and server components of the framework. Organizations seriously committed to API quality can:
• Enable users to move to more comprehensive, multi-component, real-world API testing by importing simple tests built using Postman into SoapUI NG Pro
• Eliminate inter-organizational dependencies by putting API virtualization in the hands of every developer and intuitively manage more granular routing rules across ever-larger numbers of Virts in ServiceV Pro
• Acknowledge that everyone is accountable for API security and make it easy for them to quickly find and diagnose security vulnerabilities at a deeper level using Secure Pro
The 2016 survey conducted by SmartBear on API usage and development revealed that almost 40 percent of all respondents wanted to see easier integration between tools in the near future. As testing obligations continue to shift left in software organizations, this integration challenge grows in importance.
