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

Testing outgoing calls

In everyday practice, both incoming and outgoing calls happen between two separate, independent systems. This makes testing of incoming and outgoing calls a challenge with respect to controlling the flow of the tests. As shown in the previous section, Testing incoming calls, with incoming calls we can quasi switch between client-side and server-side while actually running our tests on one system. With outgoing calls, however, this is not possible as our application code – the client – is most likely calling upon an external system – the server – that we do not and cannot control and/or we do not want to interact with for whatever reason in our test context. In Chapter 12, Writing Testable Code, handling the interaction with an external system was mentioned as an example of why we should be writing testable code. Testable code should allow us to mimic the interaction and test the behavior of our application code given a controllable...