Typemock, a leading provider of unit testing solutions, announced that it now supports Visual Studio 2017, Microsoft’s newest IDE, as well as testing code written in Visual Basic.NET.
Visual Studio 2017 is the newest version of Microsoft’s popular development environment. Typemock’s latest release showcases its continuous product innovation and fast response to changes in the development environment. Typemock has long supported Visual Studio, and the latest release continues this tradition and allows developers to use multiple versions together to test new or legacy code and not be restricted within their team.
Prior to this release, a third-party tool was required to run a test in Visual Basic or to see the coverage; now you can write the test in Visual Basic, run it on Visual Studio, and see the results.
Visual Basic.NET developers often create critical business applications. However, they lacked the ability to properly unit test their existing legacy code, leading to more bugs and other defects. Typemock now offers Visual Basic.NET developers its SmartRunner, Coverage, and Suggest features, that were previously available only to C# developers. Visual Basic.NET is commonly used to develop Windows Forms and other business applications, it is also the sixth most popular programming language, according to the June 2017 TIOBE Programming Community Index.
An additional new feature is the integration with the Visual Studio Team Services extension now available in the Visual Studio marketplace. Instead of installing Typemock and creating settings on each machine, developers can download it onto their server, saving significant time.
Another new and clean setup has become available with the Typemock Nuget package. The Nuget package is already a widely used tool (Visual Studio Extension) and is a repository for distributing libraries across the developers/projects.
“Businesses rely on unit testing to ensure that their code is good, does what it is supposed to do, and has fewer defects,” noted Eli Lopian, CEO of Typemock. “It is an essential part of agile and DevOps processes, and ensures that quality code can get released to production. Relying on outdated software and not testing existing legacy code is a recipe for disaster. Therefore we are proud to constantly offer the ability to test more code on the latest environments, supporting whatever tool your team is using.”