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

Test case design patterns

Goal: Learn the basic patterns for designing tests.

Once a test plan is in place, it is time to detail the various tests it defines. In this section, we move from a test plan into a test design.

If you have been testing software, you might know that each test has a similar overall structure. Before you can perform the action under test, for example, the posting of a document, the data needs to be set up. Then, the action will be exercised. And finally, the result of the action has to be verified. In some cases, a fourth phase applies, a so-called teardown. This is used to revert the system under test to its previous state before a next test can take off, making each test repeatable.

Four-phase testing

The four phases of a test case design pattern are listed as follows:

  1. Setup
  2. Exercise
  3. Verify
  4. Teardown

This four-phase test design pattern was used by Microsoft in the early years of C/SIDE test coding. Like the following test...