In this blog, we highlight a lesson learned when we used a Dynamics 365 Customer Engagement online data source connector, called Instance Web API, for Power BI reports.
Today's blog post is devoted to Dynamics 365 v9. We'll describe the new features available in v9, define the scope of v9 upgrade testing, and discuss the types of testing that will cover an upgrade from v8.2 to v9 (also called Potassium).
When you are planning to upgrade your older version of a Dynamics 365 instance to new version, i.e., Dynamics 365 v9, it is imperative that you plan your testing for a successful Go Live. You must plan the upgrade and Go Live efficiently, as new versions are being released frequently. Validation strategy is similar across upgrades. The upgrade strategy is to ensure that the system is up and running once it is completed. The goal is that when enhanced custom features are implemented in a v9 version, there are no blockers in lower environments, thus allowing you to proceed with moving to the production environment.
Focus of this testing effort in B2C is to validate:
The following types of testing should be planned by the Quality Assurance team to provide signoff in lower environments:
Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after the v9 upgrade. All existing Test Suites should be executed manually or run automated test scripts.
These tests are intended to be run on Ad-hoc scenarios to find defects. Ad-hoc Testing, also known as Random Testing, is a method of software testing without any documentation. It does not follow any structured way of testing; it is randomly conducted on any part of the product.
Application Configuration & Deployment Testing:
In this testing, the team focuses on preparing solution and exporting to target environment. Different CRM customizations and Configurations will be done on Dynamics 365 features to check if there is any impact because of v9 upgrade.
Upgrade the lower environments, like Development, and test to v9. Perform all planned testing and execute the test cases. The goal is to find bugs, set the severity, discuss with stakeholders on priority for fixes, and once fixed, provide signoff to higher environments.
Test cases will be created for Application Configuration and Deployment Testing and updated PASS/FAIL in VSTF. Any bugs found during execution will be tracked and mapped to the corresponding test cases
Any bugs found during this v9 Upgrade Testing will be created in VSTF for tracking and the testing team will provide the severity of the bug. The team will let the stakeholders know the impact and set priority to be fixed.
Additional testing involves validating known issues already reported by Microsoft and perform Impact analysis. https://docs.microsoft.com/en-ca/dynamics365/customer-engagement/admin/readme-9
Don't forget to subscribe to our blog for more tips and tricks!
Happy Dynamics 365 Upgrading!