At the end of the second post of this series I left you hanging just when I was ready to really start refactoring. Sorry for that and shouldn’t let you wait no longer. So, here we go. Refactoring can start But where to start? Well, let’s list the things that…
In the first post of this series I started with stating the intention that … I would like to display a very simple, though instructive, example of how easy refactoring works when you have both app and test code at your disposal. And that’s what I am going to do…
In this series of posts I would like to display a very simple, though instructive, example of how easy refactoring works when you have both app and test code at your disposal. And at the same time I will show you the power of starting coding from specific and gradually…
Various times I have been asked what the differences are between the 1st and 2nd edition of my book Automated Testing in Microsoft Dynamics 365 Business Central. Or in other words: Luc, tell me, why should I buy the 2nd edition of your book? So, I made a quick overview…
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. Nothing to stop me from getting to GREEN … Nothing? Really…
All our tests successfully passed and now only one test remaining on our test list (test #4): # Description Status 1a Create PI (purchase invoice) with 1 line and check that total line amount is calculated right Complete 1b Create PI with 1 line, populate line amount with random value…
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). # Description Status 1a Create…
Well, don't let us be distracted anymore. Our next test is awaiting us: Test #2. # Description Status 1a Create PI (purchase invoice) with 1 line and check that total line amount is calculated right Complete 1b Create PI with 1 line, populate line amount with random value and check…
Test #1 has passed and we can cross it off on our test list: # Description Status 1 Create PI (purchase invoice) with 1 line and check that total line amount is calculated right Complete 2 Create PI with multiple (2) lines and check that total line amount is calculated…
There we go. Let’s turn to our companion on this journey, our Test List, pick out our first test: # Description Status 1 Create PI (purchase invoice) with 1 line and check that total line amount is calculated right In Progress 2 Create PI with multiple (2) lines and check…