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

What is TDD?

The shortest possible description of TDD is actually the term itself. It describes that, by using this as your methodology for your application development, this development will be driven by tests. Meaning, tests need to be defined to trigger the writing of your application code, and in this, your tests are directly derived from the requirements. The ultimate consequence of this is:

"No tests, no code."

You will never build code that does not have tests to it, and, as the tests are one-to-one related to the requirements, your application code will not have any undocumented features.

Only two rules to the game

The preceding description is not the basic definition of TDD. TDD is defined by only two rules, and everything else is deduced from that:

  • Rule 1: Never write a single line of code unless you have a failing automated test.
  • Rule 2: Eliminate duplication.

The first rule clearly defines the trigger for writing application code...