After working on different testing tools from various vendors, I feel really bad that often I can not reuse assets I have created over the course of time. There is no inter-operability between tool vendors and most of the time we are locked with the tools that we have used initially for the project. This vendor locking is imposed on us from tool vendors and management both.

Most of the time management invests money in getting tools from only one vendor and no matter how hard you try, you will have to live with the tool set they have provided. Management will always have following arguments to stop you from switching tools

Web Services are everywhere. If you want to build your web service, there are chances that you will be developing it on top of/or using some existing web services. Also, output of your web service might be consumed by some other web services. During my involvement in testing web services one thing that I found very challenging is the scope of Web Services testing.

You start doing security testing and will come to know that you do not have to cover security testing because our web services are using some back end web services and hopefully they must have done job properly. Similarly there are other aspects of functionality, which you will not be testing and will be relying on other web services for your task. Well, I am not opposing the concept here all I am saying is that it makes it difficult to figure out what to test and what to leave for other people/teams.