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

TDD and our test examples

After I introduced the concept of Test-Driven Development in Chapter 2, Test Automation and Test-Driven Development, I did not pay any attention to the topic until now. In fact, I deliberately evaded to use TDD as our way of working for mainly one reason:

To write automated tests for application code that already exists.

This is most probably the context in which most of you will start applying test automation.

Now, what if you had applied TDD to our test examples?

To be honest, it wouldn't have looked much different, as a lot of the TDD principles were implicitly exercised by:

  • Defining your customer wishes by means of the ATDD scenarios, you created yourselves a sufficient set of tests, that is, a test list.
  • Implementing your tests with the 4-steps recipe.

With the latter, we:

  • Took small steps.
  • Created a structure for each test based on the GIVEN-WHEN-THEN tags.
  • Constructed the real code to get it to work...