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

Composing complex scenarios

Now that we have outlined what can make a scenario complex, it will be very practical to describe how we could compose complex scenarios enabling us to handle them efficiently and effectively. One after the other, the following are the hurdles to take to help you to get there:

  1. Before a feature is being implemented, a test plan should be in place, detailed out in a test design, and reviewed by the team, as was discussed in Chapter 5, Test Plan and Test Design. Well-thought-out ATDD definitions will save a lot of work downstream.
  2. Describe the data setup – the ATDD GIVEN parts – for your complex scenario, efficiently and effectively making use of a common language (see Chapter 5).

    Remove unneeded details and unveil missed details by team review.

    In this, make a clear split between this part – data setup – and the next – exercise. Determine what are the preparatory, data setup, steps needed to get the code under test...