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 12 – testing incoming calls: Lookup Value API

With this example, you learn how to test getting (using GET), deleting (using DELETE), modifying (using PATCH), and creating (using POST) data through an API.


In this example, we focus on the structure and code of the automated tests that test an API, not on the flow of getting from a customer wish into test and application coding and also not on doing it the TDD way.

Application code

The object for our tests is a new page called Lookup Values APIV1 (50090) with PageType set to API and SourceTable pointing to our Lookup Value table. This API contains three columns:

  • id based on SystemId field
  • number based on the Code field
  • displayName based on the Description field

The full object can be seen in the GitHub repo: 13 (LookupValue Extension)/src/page/LookupValuesAPIV1...