You're reading from Automated Testing in Microsoft Dynamics 365 Business Central Efficiently automate test cases for faster development cycles with less time needed for manual testing

Product type Paperback

Published in Dec 2021

Publisher Packt

ISBN-13 9781801816427

Length 406 pages

Edition 2nd Edition

Tools

Dynamics 365

Concepts

Enterprise Resource Planning

Author (1):

Luc van Vugt

View More author details

Table of Contents (22) Chapters

Preface

1. Section 1: Automated Testing – A General Overview

2. Chapter 1: Introduction to Automated Testing FREE CHAPTER

3. Chapter 2: Test Automation and Test-Driven Development

4. Section 2:Automated Testing in Microsoft Dynamics 365 Business Central

5. Chapter 3: The Testability Framework

6. Chapter 4: The Test Tools, Standard Tests, and Standard Test Libraries

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

8. Chapter 5: Test Plan and Test Design

9. Chapter 6: From Customer Wish to Test Automation – the Basics

10. Chapter 7: From Customer Wish to Test Automation – Next Level

11. Chapter 8: From Customer Wish to Test Automation – the TDD way

12. Section 4:Integrating Automated Tests in Your Daily Development Practice

13. Chapter 9: How to Integrate Test Automation in Daily Development Practice

14. Chapter 10: Getting Business Central Standard Tests Working on Your Code

15. Section 5:Advanced Topics

16. Chapter 11: How to Construct Complex Scenarios

17. Chapter 12: Writing Testable Code

18. Chapter 13: Testing Incoming and Outgoing Calls

19. Section 6:Appendix

20. Other Books You May Enjoy

Appendix: Getting Up and Running with Business Central, VS Code, and the GitHub Project

And what about unit and functional tests?

Except for a short note in Chapter 1, Introduction to Automated Testing, and mentioning a couple of MS test codeunits that apparently hold unit tests, we haven't paid any attention to the concept of unit tests so far. In this chapter, however, discussing the need for a test plan entailing all tests verifying the behavior of the feature, it makes a lot of sense to pick up that gauntlet laying in sight: what about unit tests?

My short answer to this question is: please, go ahead and implement them.

But quite obviously that might not be the answer you're looking for. So, let me work this out a little bit more in a number of bullet points:

In my humble opinion, unit tests are the sole responsibility of developers. They build them to check the validity of the atomic units that altogether make up a feature. These atomic units are the procedures and methods they have created to implement a feature. As such, unit tests are not...