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

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

Learning and improving by taking small steps

You get to master test automation one step at a time. Learn and improve by doing the following:

Choose one of the when-to-use-automated-testing options as discussed in Chapter 1, Introduction to Automated Testing, that fits you and your team best, and/or gives the best return on investment, to start mastering test automation.
Start casting the customer wish into the scenarios that come to mind. Try to keep it simple. Preferably, you would like to get full coverage right away, but as it is a team effort, chances are high that holes will be identified before implementation starts. And if they will not be seen, chances are even bigger that you will hit upon these holes when starting to implement the code.
Make use of my 4-steps recipe (create, embed, write, and construct) for the conception of the test code. Let the ATDD.TestScriptor module and/or extension make this work even more efficient.
Get the test(s) run with every...