After several months of sprinting along with Microsoft's agile cadence for Visual Studio 2015, today DevPartner offers to the market DevPartner Studio 11.3. Devpartner Studio packs a set of tools together for code troubleshooting for the professional developer. The 11.3 release tackles the latest Microsoft development platform Visual Studio 2015 and Operating System Windows 10, while keeping true to its BoundsChecker roots set in native development.
Now why is this important for the developers out there? After a long week in the office we are all starting to feel sluggish right? But how do you feel if your apps are sluggish in responding? Do you know where exactly in the code the performance hits are happening? DevPartner Performance Analysis (TrueTime) can pinpoint the exact lines of code that are causing the sluggish responses from your application.
Does your application suffer from Memory Leaks or worse potential buffer overruns? DevPartner Error Detection (BoundsChecker) can detect these errors as they occur and show you in the source code where the memory was allocated and leaked. Boundschecker can show you a multitude of errors and stop the execution, show the source code and help explain the errors.
Are your apps moving to the mobile platform while maintaining a traditional PC / tablet platform as well? Test your applications common logic (Universal app) under DevPartner to ensure the mobile application is performant and memory efficient.
How much of your application is actually being tested by your automated test suite? Or by your QA teams testing? Has the developer tested all of the code changes being submitted? Important questions that should be answered to know the risks associated with this code change or release. Luckily DevPartner Code Coverage (True Coverage) can answer these questions for you. Code Coverage can also be run in combination with Boundscheker.
There are many other benefits to be had by testing your code with DevPartner. There are also plenty of command line options that would allow using DevPartner in a Continuous Integration testing (CIT) scenario that would alert a dev team to a regression with a new build. This can save a team plenty of time determining when a change in application stability or performance occurred. This is one of the things we do with changes to the instrumentation layer or subsystems in BoundsChecker. We have a suite of unit tests that we run compiling small tests with each version of Visual Studio from VS6 through 2015. Run BoundsChecker against the application and extract the session file output and compare against a benchmark. This is not limited to Boundschecker but it is a way to know if any errors have been introduced to a new build of your application.
Want to know more? Mosey on over to the DevPartner web site. http://www.borland.com/Products/Software-Testing/Automated-Testing/Devpartner-Studio
Heard enough? Want to download a trial? http://www.borland.com/Products/Software-Testing/Automated-Testing/Devpartner-Studio/Product-Trial