I have utilized Microsoft's development environments extensively since their early inception, having been actively involved with Microsoft in the nascent stages, particularly during the development of Windows. I also collaborated with IBM on the original version of the IBM PC. The development environments at that time were vastly distinct from contemporary tools. I worked with assemblers and, in one instance, directly wrote in machine code, marking a significant contrast to the present landscape.

We had previously used other solutions such as UI pod, Blue Prism and Bucket Bot. Visual Studio proved to be the most cost-effective for our needs. 

We used the community version before. We decided to use Visual Studio Test Professional because we were scaling our business, and it has more features. It also provides more support compared to the community version. While using the community version, we had to raise a request to the support team and wait for a response. However, now we can contact the team and get support immediately.

We use different solutions for other development environments. We use what’s best for each language we support or use. We use Visual Studio Test Professional because it supports .NET the best.

Many years back not now, very early 2006 or 2007 or around there, we were using a product called BoundsChecker and that time we were using it very extensively and it was a very, very useful tool. We had it integrated with Visual Studio 6.0. Now, we are using Visual Studio 2017 and 2019. However, unfortunately, we haven't found any tool that gives us the same kind of output as BoundsChecker used to. When I searched its history I found that it has been bought by Micro Focus and it has changed names a lot of times. I've been looking for a product giving the same output as BoundsChecker.

I have used previous versions of Microsoft Visual Test Studio including the 2010 and 2008 editions. I switched to the 2015 version because of the new features.

In addition to Visual Studio Test Processional, I used Selenium Java and Selenium C#. I also use products by SmartBear.

Prior to this solution, we used third-party tools. Once we used this solution it was much better because of the higher level of integration with the main product, as well as the overall code management.

We have experience with other testing tools but the choice of product is dependant on the project and the requirements given by the customer.

Just for some analysis.