Book Image

.Automated Testing in Microsoft Dynamics 365 Business Central

By : Luc van Vugt
Book Image

.Automated Testing in Microsoft Dynamics 365 Business Central

By: Luc van Vugt

Overview of this book

Dynamics 365 Business Central is the new cloud-based SaaS ERP proposition from Microsoft. It’s not as simple as it used to be way back when it was called Navigator, Navision Financials, or Microsoft Business Solutions-Navision. Our development practices are becoming more formal, and with this, the call for test automation is pressing on us. This book will teach you to leverage testing tools available with Dynamics 365 Business Central to perform automated testing. We’ll begin with a quick introduction to automated testing, followed by an overview of test automation in Dynamics 365 Business Central. Then you’ll learn to design and build automated tests and we’ll go through some efficient methods to get from requirements to application and testing code. Lastly, you’ll learn to incorporate your own and Microsoft tests into your daily development practice. By the end of the book, you’ll be able to write your own automated tests for Dynamics 365 Business Central.
Table of Contents (17 chapters)
Free Chapter
1
Section 1: Automated Testing - A General Overview
3
Section 2: Automated Testing in Microsoft Dynamics 365 Business Central
6
Section 3: Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
11
Section 4: Integrating Automated Tests in Your Daily Development Practice

TDD, red-green-refactor

Given a test list, the actionable steps are described by what has become the red-green-refactor mantra. Where red and green respectively refer to a failing (red) and succeeding (green) test, this mantra tells you to take the following steps:

  1. Take a test from the list and write the test code
  2. Compile the test code yielding red as the application code that is not yet there
  3. Implement just enough application code to make the test code compile
  4. Run the test seeing it probably fail, still red
  5. Adjust the application code just enough to make it pass, that is, green
  1. Refactor your code, either test or application code or both, one after the other, and rerun the test after each change to prove all code is still well (green)
  2. Move to the next test on the list and repeat from Step 1

The red-green-refactor mantra urges you to get things done step by step and as efficiently...