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)
1
Section 1: Automated Testing – A General Overview
4
Section 2:Automated Testing in Microsoft Dynamics 365 Business Central
7
Section 3:Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
12
Section 4:Integrating Automated Tests in Your Daily Development Practice
15
Section 5:Advanced Topics
19
Section 6:Appendix

And what about unit and functional tests?

Except for a short note in Chapter 1, Introduction to Automated Testing, and mentioning a couple of MS test codeunits that apparently hold unit tests, we haven't paid any attention to the concept of unit tests so far. In this chapter, however, discussing the need for a test plan entailing all tests verifying the behavior of the feature, it makes a lot of sense to pick up that gauntlet laying in sight: what about unit tests?

My short answer to this question is: please, go ahead and implement them.

But quite obviously that might not be the answer you're looking for. So, let me work this out a little bit more in a number of bullet points:

  • In my humble opinion, unit tests are the sole responsibility of developers. They build them to check the validity of the atomic units that altogether make up a feature. These atomic units are the procedures and methods they have created to implement a feature. As such, unit tests are not...