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.

Related Content you might be interested in

Current Title:

Small book image
Automated Testing in Microsoft Dynamics 365 Business Central - Second Edition
Dec, 2021 | 406 pages
Small book image
Mastering Microsoft Dynamics 365 Business Central
Stefano Demiliani | Duilio Tacconi
Dec, 2019 | 770 pages
Small book image
Dynamics 365 Business Central Development Quick Start Guide
Stefano Demiliani | Duilio Tacconi
Aug, 2018 | 224 pages
Small book image
Microsoft Dynamics 365 Business Central Cookbook
Michael Glue
Aug, 2019 | 380 pages
Table of Contents (22 chapters)
Preface
Preface
Who this book is for
What this book covers
To get the most out of this book
Download the example code files
Get the color images
Conventions used
Get in touch
Share Your Thoughts
1
Section 1: Automated Testing – A General Overview
Section 1: Automated Testing – A General Overview
Free Chapter
2
Chapter 1: Introduction to Automated Testing
Chapter 1: Introduction to Automated Testing
Why automated testing?
When to use automated testing?
What is automated testing?
Summary
3
Chapter 2: Test Automation and Test-Driven Development
Chapter 2: Test Automation and Test-Driven Development
TA versus TDD
What is TDD?
TDD and Microsoft Dynamics 365 Business Central
TDD – inside-out or outside-in
Summary
Further reading
4
Section 2:Automated Testing in Microsoft Dynamics 365 Business Central
Section 2:Automated Testing in Microsoft Dynamics 365 Business Central
5
Chapter 3: The Testability Framework
Chapter 3: The Testability Framework
Technical requirements
The five pillars of the testability framework
Summary
6
Chapter 4: The Test Tools, Standard Tests, and Standard Test Libraries
Chapter 4: The Test Tools, Standard Tests, and Standard Test Libraries
Technical requirements
Test Tools
Standard tests
Standard libraries
Summary
7
Section 3:Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
Section 3:Designing and Building Automated Tests for Microsoft Dynamics 365 Business Central
8
Chapter 5: Test Plan and Test Design
Chapter 5: Test Plan and Test Design
No plan, no test
Setting up a test plan
Test case design patterns
Test data setup design patterns
Using customer wish as test plan
And what about unit and functional tests?
Summary
Further reading
9
Chapter 6: From Customer Wish to Test Automation – the Basics
Chapter 6: From Customer Wish to Test Automation – the Basics
Technical requirements
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
10
Chapter 7: From Customer Wish to Test Automation – Next Level
Chapter 7: From Customer Wish to Test Automation – Next Level
Technical requirements
Sales documents, customer template, and warehouse shipment
Test example 4 – how to set up a shared fixture
Test example 5 – how to parameterize tests
Test example 6 – how to hand over data to UI handlers
Summary
11
Chapter 8: From Customer Wish to Test Automation – the TDD way
Chapter 8: From Customer Wish to Test Automation – the TDD way
Technical requirements
TDD and our test examples
Test example 7 – how to refactor your code
Test example 8 – how to test a report
Test example 9 – how to test with permissions
Summary
12
Section 4:Integrating Automated Tests in Your Daily Development Practice
Section 4:Integrating Automated Tests in Your Daily Development Practice
13
Chapter 9: How to Integrate Test Automation in Daily Development Practice
Chapter 9: How to Integrate Test Automation in Daily Development Practice
Technical requirements
Casting the customer wish into ATDD scenarios
Learning and improving by taking small steps
Making the test tool, and some more, your friend
Maintaining your test code
Organizing your extensions
Integrating with the daily build system
Summary
14
Chapter 10: Getting Business Central Standard Tests Working on Your Code
Chapter 10: Getting Business Central Standard Tests Working on Your Code
Technical requirements
Why use the standard tests?
Executing standard tests against your code
Fixing failing standard tests
Disabling failing tests
It's all about data
Is it all really about data?
Summary
15
Section 5:Advanced Topics
Section 5:Advanced Topics
16
Chapter 11: How to Construct Complex Scenarios
Chapter 11: How to Construct Complex Scenarios
Technical requirements
What makes a scenario complex?
Composing complex scenarios
Creating reusable parts
Test example 10 – how to construct an extensive scenario
Summary
17
Chapter 12: Writing Testable Code
Chapter 12: Writing Testable Code
Technical requirements
What is testable code?
How to make your code testable?
Test example 11 – how to unit test event subscribers' logic
Summary
Further reading
18
Chapter 13: Testing Incoming and Outgoing Calls
Chapter 13: Testing Incoming and Outgoing Calls
Technical requirements
Testing incoming calls
Testing outgoing calls
Test example 12 – testing incoming calls: Lookup Value API
Test example 13 – VAT Registration No. validation
Summary
19
Section 6:Appendix
Section 6:Appendix
20
Other Books You May Enjoy
Other Books You May Enjoy
Packt is searching for authors like you
Share Your Thoughts
Appendix: Getting Up and Running with Business Central, VS Code, and the GitHub Project
Appendix: Getting Up and Running with Business Central, VS Code, and the GitHub Project
Setting up your Business Central environment
The GitHub repository
Setting up VS Code
Notes on the AL code
Why subscribe?

Organizing your extensions

Starting with a new project, like we did with the LookupValue extension, I tend to have both the application and the test code in one VS Code folder just for one reason: practicality. This way, I only have to deploy one extension when verifying my work after an addition or change in either application or test code – or both, although TDD teaches us to do one or the other. This helps me to get my work done more efficiently.

Once the code is ready, however, we need to make sure that the application and test code end up in separate extensions – but still in the same repo – with the logical consequence that the test app will have a dependency on the application app. This way, we prevent tests from ending up, and possibly getting run, in a production environment. For this very reason, standard CRONUS does not contain the standard test codeunits – and test helper libraries.

Sure, if test codeunits are run within the test isolation...

Previous Section
End of Section 7
Next Section