Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing Microsoft Dynamics 365 for Finance and Operations Apps

You're reading from   Implementing Microsoft Dynamics 365 for Finance and Operations Apps Learn best practices, architecture, tools, techniques, and more

Arrow left icon
Product type Paperback
Published in Mar 2020
Publisher Packt
ISBN-13 9781789950847
Length 528 pages
Edition 2nd Edition
Arrow right icon
Authors (4):
Arrow left icon
JJ Yadav JJ Yadav
Author Profile Icon JJ Yadav
JJ Yadav
Rahul Mohta Rahul Mohta
Author Profile Icon Rahul Mohta
Rahul Mohta
Yogesh Kasat Yogesh Kasat
Author Profile Icon Yogesh Kasat
Yogesh Kasat
Sandeep Shukla Sandeep Shukla
Author Profile Icon Sandeep Shukla
Sandeep Shukla
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Introduction to Dynamics 365 Finance and Operations 2. Methodology and Initiation FREE CHAPTER 3. Lifecycle Services (LCS) and Tools 4. Architecture, Deployment, and Environments 5. Requirements and Process Analysis 6. Configuration and Data Management 7. Solution Planning and Design 8. Integration Technologies, Planning, and Design 9. Customization and Extension 10. Analytics, Business Intelligence, and Reporting 11. Testing and Training 12. Managing Go-Live and Post Go-Live 13. One Version Service Updates 14. Other Books You May Enjoy

The importance of testing

Testing is the process of validating the system and processes in order to meet business requirements. It includes testing the custom as well as the standard features, along with the migrated data, integrations, reports, and security aspects of the solution. It is an area that is most often underestimated and, as a result, hampers the success of your project.

A very common misconception is that testing starts after the development phase is over. The primary goal of testing is to provide feedback on the product as soon as possible. Identifying any issues in the requirements phase prevents them from becoming a part of the design. Similarly, identifying any issues in the design phase prevents them from being coded. The cost of fixing a defect depends on the phase where it has been detected; the cost of fixing a defect in the early phases of the Software Development...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime