Mercury Interactive Testing Tools

16.11.2018by admin
Interactive

Testing Tools Institute In Hyderabad

The end of the line for the original Test Automation vendors? Including the Mercury-Interactive tools. While some of the fragments of the tools that we had started with way back in 1994 will. Mercury Interactive has released an updated version of its application quality assurance tool, adding user-acceptance features to the software and expanding its integration with other Mercury. My company has licenses for these Mercury Interactive products: WinRunner LoadRunner My team has built web applications using J2EE, JSP,.

Mercury Interactive Llc

Software testing tools

Chris Benedetto, VP Marketing, Solstice Software, provided some thoughtful insights in response to my recent on the SOA implications of HP's pending $4.5-billion acquisition of Mercury Interactive. While 60 percent of Mercury's revenues come from testing tools, this was only briefly mentioned by HP. Benedetto observes that the HP-Mercury acquisition story 'has mostly spun around SOA management, registries, and governance, tied, of course, to HP’s core competencies in centralized IT operations and service management.' However, he continues, 'testing was only briefly mentioned in the publicly released information by HP, although more than 60 percent of Mercury’s revenue comes from application testing tools.

Moreover, this acquisition doesn’t truly provide end-to-end testing of SOAs.' While traditional testing looks at application performance, SOA testing needs to look at the whole business process, and if pieces of that process interact properly. End-to-end SOA testing, Benedetto says, involves 'testing an entire business process path to assure that the integration has resulted in the intended execution of transactions, interactions, and data transformations,' as well as 'testing across multiple platforms, transport protocols, ESBs, language interfaces, and messages,' and 'Validating the linkages and integrations between business services and operational systems to meet target defect rates and SLAs.' There’s more to testing than reviewing and debugging code and interfaces for particular applications. Web services are not designed as islands; they exist to interact and eventually form the fine-grained building blocks of larger service-oriented architectures. The interaction and process flow needs to be tested. A while back, I spoke to Optimyz's Narendra Patil about this issue, who observed that.