Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
Let´s make a reminder about TDD (Test Driven Development). The TDD principles tell that you must design based in test, and this means:
The TDD principles are resumed in acronym F.I.R.S.T.:
Well we are talking too much about TDD in a non TDD post. Please, if you aren´t familiar with TDD, you can follow this user https://dynamicsuser.net/nav/b/vanvugt.
Before explain TDD and unit test, could be good to take a short look at what must do the test code:
And very important, all these steps must be automated, even the assert. So, we can define:
For the same reason that we make production code: save time. Test code could be a product itself instead of being part of a methodology.
TDD is the better way to do quality software. But not all the people use TDD. And not all the software we do is quality software. But even if you don´t do TDD you could propose use test code.
Let´s see tree real cases using unit test without TDD.
We bought a specific Navision software from other vendor.
This module is a legal modification that gets sales invoice headers, and create an XML file for a tax office declaration.
Test other vendor isn´t our responsibility. But we did a very simple test code to do:
Assert.AreEqual(SalesInvoiceHeader."VAT Registration No.",LibraryXMLRead.GetNodeValueInSubtree('VatRegNode','VatRegNo'),ErrFieldXML);
Assert.AreEqual(SalesInvoiceHeader.Amount, AmountInFile, ErrFieldXML);
We used two existing test Codeunits in NAV test toolkit:
LibraryXMLRead Codeunit Library - XML Read
Assert Codeunit Assert
We said test other vendor code not our responsibility, but we did a little test. Why? Two good reasons:
Business Applications communities