Work or School Accounts Now Enabled in Community!
On May 12 Work or School Accounts were enabled in Community, along with Microsoft accounts (MSA). This allows seamless navigation between Community, Dynamics 365 applications, and Azure Active Directory enabled sites while logged into your Work or School account.
Read more | Managing Accounts
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
In a previous post I have shown how to use Azure DevOps (was Visual Studio Team Services) builds with Dynamics 365 Build Tools to export an unmanaged solution as a managed solution and then install into into a different instance.
I have also then provided some guidance on how to use FakeXrmEasy to create unit tests for plugins & coded activities in another post.
The next step is to prevent solutions being installed if the unit tests fail. This a simple but powerful addition to the build profile as it helps to further reduce the amount of bugs deployed to production. It can also be used to identify issues before development code is moved to test instances.
I will assume that the previous post about using Azure DevOps has been read and understood.
The first step is to ensure that the unit test assembly (.dll) files are in the source control. Without these, the test runner will be unable to run the tests.
Adding the unit test step is as easy as editing the build & adding the ‘Visual Studio Test‘ step at the beginning of the agent and then configuring the Test files field to include the search pattern that would find the test assembly.
After the step has been added, any future runs of the build will first check to make sure the unit tests pass. If they do not, then the build fails and subsequently the release is not triggered, so the solutions are not installed on the target instance.
I hope you will agree that this is a quick & easy addition to the build profile which will allow even more confidence that plugins & coded activities inside solutions are bug free.
The post Dynamics 365 & Azure DevOps – Unit Testing appeared first on Jason Clair.
Business Applications communities