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

Casting the customer wish into ATDD scenarios

Crucial to getting test automation into your daily development practices is the adoption of it by the team. Like requirements and application code, tests and test code should be owned by the development team; not just formally, but also actively. Good application code does not emerge from a single-lined customer wish; it derives from an eventually well-detailed and formalized customer wish, aka requirements. And the same applies to tests and test code.

As discussed in Chapter 5, Test Plan and Test Design, formalize your requirements by using the ATDD design pattern. Cast your customer wish in ATDD scenarios. Break down each wish into a list of tests and make this your primary vehicle of communication for (1) detailing of your customer wish, (2) implementation of your application code, (3) structured execution of your manual tests, (4) coding of your test automation, and (5) up-to-date documentation of your solution. Your test automation...