.Automated Testing in Microsoft Dynamics 365 Business Central

By : Luc van Vugt

5 (2)

Buy this Book

.Automated Testing in Microsoft Dynamics 365 Business Central

5 (2)

By: Luc van Vugt

Buy this Book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Section 1: Automated Testing - A General Overview

Introduction to Automated Testing

Why automated testing?

When to use automated testing

What is automated testing?

Summary

Section 2: Automated Testing in Microsoft Dynamics 365 Business Central

The Testability Framework

The five pillars of the testability framework

Summary

The Test Tool and Standard Tests

Test Tool

Standard tests

Standard libraries

Summary

Section 3: Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central

Test Design

No design, no test

Understanding test case design patterns

Understanding test data setup design patterns

Using customer wish as test design

Summary

From Customer Wish to Test Automation - The Basics

From customer wish to test automation

Test example 1 – a first headless test

Test example 2 – a first positive-negative test

Test example 3 – a first UI test

Headless versus UI

Summary

From Customer Wish to Test Automation - Next Level

Sales documents, customer template, and warehouse shipment

Test example 4 – how to set up a shared fixture

Test example 5 – how to parametrize tests

Test example 6 – how to hand over data to UI handlers

Summary

From Customer Wish to Test Automation - And Some More

Test example 7 – how to test a report

Test example 8 – how to construct an extensive scenario

Refactoring

Summary

Section 4: Integrating Automated Tests in Your Daily Development Practice

How to Integrate Test Automation in Daily Development Practice

Casting the customer wish into ATDD scenarios

Taking small steps

Making the test tool your friend

Integrating with daily build

Maintaining your test code

Summary

Getting Business Central Standard Tests Working on Your Code

Why use the standard tests?

Executing standard test

Fixing failing standard tests

It's all about data

Making your code testable

Is it all really about data?

Summary

Test-Driven Development

TDD, a short description

TDD, red-green-refactor

TDD and our test examples

Summary

Setting Up VS Code and Using the GitHub Project

VS Code and AL development

The GitHub repository

Notes on the AL code

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

5 (2)

5 star

100%

4 star

3 star

2 star

1 star

Sales documents, customer template, and warehouse shipment

With the three examples of Chapter 5, From Customer Wish to Test Automation - The Basics, we added the Lookup Value Code field to the Customer table. However, that's just a part of the customer wish as it describes clearly that…

"… this field has to be carried over to the whole bunch of sales documents and, at the same time, it needs to be included in the warehouse shipping."

So, before we dive into the following test examples, a note needs to be made that, parallel to the implementation of the Lookup Value Code field on the Customer table, the same field has to be implemented on the Sales Header table, the Customer Template table, the Warehouse Shipment Line table, and all related pages. The ATDD test case descriptions are very much alike, and this will be the same case for the application...