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

Test example 7 – how to refactor your code

From a TDD perspective, the previous six test examples fully neglected a very essential part: the refactoring of the code, or more accurately, one of the two rules that make TDD: Rule 2 Eliminate duplication.

As I hope you will experience here, refactoring is not rocket science but a discipline, as I tend to call it. Refactoring is not a goal on its own, but a means to exercise this second rule of TDD, with the valuable resulting effects of getting reusable, readable, and minimalistic code.

Contrary to what many of us have been taught when becoming a developer, though, with TDD we do not design reusable, readable, and minimalistic code upfront. No, when performed with common coding sense, rule 2 leads you there. As you might recall from Chapter 2, Test Automation and Test-Driven Development, with TDD your first gear is taking small steps to be effective and efficient. Meaning that you don't do more than required for that...