Agile development has been around for nearly a decade. However, its popularity as the methodology of choice to develop software has only been embraced in the last couple of years. A revolutionary way of deploying software projects, Agile methodology supports rapid delivery of solutions, responds to changes at any point in the development cycle, and encourages a self-governing and motivated team of developers.
Way back late summer 2009. Almost a year ago NAV 2009 was out of our hands, NAV 2009 SP1 was at the verge of being pushed into the world and I … just one month ago the MS doors were closed behind me and I made my steps into the partner world picking up my new job at Imtech ICT Dynamics Solutions as Technical Consultant, which became more and more Product Manager.
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.
Getting our first two tests, test #1 and test #2, working (GREEN! … GREEN! … GREEN!), we successfully implemented the first part of our feature, i.e. the function CalcDocAmount, leaving us now with it’s counterpart: the verification of the manually entered total amount of the document (invoice).
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).
There we go. Let’s turn to our companion on this journey, our Test List, pick out our first test:
NAV TechDays 2011,day 2 had just started and Jan and I had run into each other again, joining on our way up to the presentation rooms, executing the time map each of us had probably setup way before we came to Antwerp.
Vertalen
