Ouch, keep on singing the RED/GREEN/REFACTOR mantra wasn’t that easy the last couple of weeks preparing myself on my NAV Development with Team Foundation Server presentation. But that’s past now and I can look forward again. I can go ahead again.
And even though I want to push forward to get on with the next test (make it turn GREEN, son), I owe myself, and OK you too, a little bit more explanation to the second part of my previous post. Well, uhhh, actually, I have to confess, Bas, my TDD guru, gave me some small hint on this.
We already have our first test function PIwithOneLine in codeunit 60000 (Test Doc. Amount) and our second test function will have a lot in common and thus we will create a PIwithTwoLines test function as a copy of PIwithOneLine (you might recall one of my first blog entries on how to copy functions in NAV).
With the delivery of the 3-tier architecture in Microsoft Dynamics NAV then it has opened up the possibility of developing applications utilising the NAV 2009 middle tier web services.
Microsoft Dynamics NAV 2009 SP1 includes the following features to help you test your application:
- Test codeunits
- Test runner codeunits
- UI handlers
- ASSERTERROR statement
Before you release a customized Microsoft Dynamics NAV 2009 application to a production environment, you must test the application.
Vertalen
