New Team Foundation Server Connector : Looking for Beta Testers

I am working with Team Foundation Server for our NAV team since 2010. As you can read on this blog we are using version control, agile planning and collaboration, build automation and test management. The first version of our source control plugin was based on visual studio 2010. Now we have visual studio / team foundation server (online) 2013. Time to migrate to the latest and greatest version of both products.

Our source control plugin for vs2010 was a plugin inside visual studio. That was certainly a nice solution but not perfect: one had to switch to visual studio to check-out objects and the plugin was dependent on the vs version. In order to improve the user experience we have shifted to a new architecture: we now have a Dynamics Nav connector for Team Foundation Server which runs silently in the background and does all the heavy lifting for you. You can now use the standard Microsoft Dynamics NAV development experience to develop your NAV solution and you can use the full power of TFS. This makes it possible to use the advanced features like shelving, developer isolation, build automation, unit testing and many other great features.

The new Team Foundation Server Connector for Microsoft Dynamics NAV

The new Team Foundation Server Connector for Microsoft Dynamics NAV

The connector has an easy to use cloud deployment which ensures you are always on the latest version. In the past months I have been working together with a number of alpha testers which gave great feedback. The connector is now stable and I am looking for beta testers.

Please let me know if you are interested.

NAV Test Automation and Build Automation

Last week we did some improvements in our Build Automation for Dynamics NAV. One of the most important changes was on the area of Test Automation. We have integrated Test Automation with our NAV Build Automation since a year. Our initial setup was using a Microsoft Dynamics NAV Soap web service to run the unit tests. Soap web services have some limitations which makes them less suitable for unit testing. One of the disadvantages of using the soap web services is that UI elements are not allowed.

The Microsoft Dynamics NAV 2013 Role Tailored Client has been provided with command line parameters which makes it possible to run the client in console mode without a user interface. We decided to change the Dynamics NAV Build template and use the command line option rather than the soap web service. This gives us the possibility to run all our unit tests automated for each build.

2013-04-04_09h37_58

Imagine the quality improvement this brought to our team. It gives insight in the tests applied on a particular build. Unit test failures are captured in the build result. As a result you have real evidence of the quality of your product in an early stage of the development cycle.

I would like to write a number of posts about this great feature and show you how you can really improve the quality of your development team.

Applying Scrum to build Connectivity Studio for NAV 2013

In the Business Integration Solutions team we are applying Scrum and TFS to develop our next generation of Business Integration Solutions on Microsoft Dynamics NAV 2013. Check out http://blog.to-increase.com for an overview of the architectural changes. In subsequent posts we will present details on the product and scenarios for integration. Scrum and the tight integration between Team Foundation Server and Dynamics NAV allow us to achieve impressive results with a small team.