Book Image

Automated Testing in Microsoft Dynamics 365 Business Central - Second Edition

Book Image

Automated Testing in Microsoft Dynamics 365 Business Central - Second Edition

Overview of this book

Dynamics 365 Business Central is a cloud-based SaaS ERP proposition from Microsoft. With development practices becoming more formal, implementing changes or new features is not as simple as it used to be back when Dynamics 365 Business Central was called Navigator, Navision Financials, or Microsoft Business Solutions-Navision, and the call for test automation is increasing. This book will show you how to leverage the testing tools available in Dynamics 365 Business Central to perform automated testing. Starting with a quick introduction to automated testing and test-driven development (TDD), you'll get an overview of test automation in Dynamics 365 Business Central. You'll then learn how to design and build automated tests and explore methods to progress from requirements to application and testing code. Next, you'll find out how you can incorporate your own as well as Microsoft tests into your development practice. With the addition of three new chapters, this second edition covers in detail how to construct complex scenarios, write testable code, and test processes with incoming and outgoing calls. By the end of this book, you'll be able to write your own automated tests for Microsoft Business Central.
Table of Contents (22 chapters)
Section 1: Automated Testing – A General Overview
Section 2:Automated Testing in Microsoft Dynamics 365 Business Central
Section 3:Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
Section 4:Integrating Automated Tests in Your Daily Development Practice
Section 5:Advanced Topics
Section 6:Appendix

Test example 1 – a first headless test

Now, with our backpack full of tools handed over in the previous chapters, the customer wish defined, and the test plan, we're set to start creating our first automated test. Yep, it's true that the test design is also available, and that's how it should be before you start coding, but as mentioned, we will use each test example to do the test design detailing specifically.

Customer wish

Let's pick up the fundamental part of our complete customer wish: the extension of the Customer table with a Lookup Value Code field.


The feature we are building with our extension is called LookupValue UT and the specific part we are now working on is the Customer table. This leads to the following FEATURE tag:

[FEATURE] LookupValue UT Customer


The specific scenario to be implemented and tested is the assignment of a lookup value to a customer, so the SCENARIO tag would be as follows: