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).
New Features Available in D365 v9
- Improved User Experience
- No more white space
- Improved forms
- Field Wrap
- Color of Sub grids
- Enhanced editing tools
- Preview emails
- Site map edits without coding
- Create a model-driven app without coding
- Multi select
- Advanced Find – Can figure out if an activity doesn’t have a related record
- Advanced Find – Multi Select Option Sets are available as a field type
- Social Pane becomes improved “Timeline”
- Select which items the users want to see
- Filter options that users can simply click on to show specific records.
- Auto Numbering
- Auto Numbering in any entity can be customized and add date or company code
- Virtual Entities
- If you have data in other databases, you can make them visible within D365. Virtual Entities allow you to create an entity in D365 that connects to an external data source and pulls in data to display within your D365 system.
- New Marketing Grid
- There is support for multiple LinkedIn member accounts, as well as the ability to customize your lead matching strategies to track and analyze your leads
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:
Types of Testing
- New V9 features work as expected
- Any new enhanced custom features do not break the system
- Improved functional changes do not impact existing functionality
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.
- Execute Regression Test Cases
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:
- Browse the application and perform random tests
- Perform CRUD operations on all the entities
- Validate the application in different browsers like IE, Chrome, and Firefox
- Validate User Experience and Usability of the application and cover:
- Navigations, Site maps
- Dynamics 365 Controls
- Form level UI Practices
- Custom ASPX UI Practices
- Web Portal UI Practices
- Reports UI Practices
- Email Templates UI Practices
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.
- Create solution in v8.2 and deploy to v9 environment
- Create Solution in v9 and deploy to another v9 environment
- Create Solution in v9 and deploy to another v8.2 environment
- Create records for all the existing main entities in D365 and then validate Workflows; plugins should run appropriately
- Validate all the D365 features
- Creating new Custom Entities, fields, creating relationship between entities
- Export and Import Data
- Create and Run Reports
- Create Email templates
- Create Dashboards
- Create Activities – Phone call, Appointments, Notes, Emails, Tasks
- Create and Modify Duplicate Detection rules and jobs
- Create Bulk Delete rules
- Create Bulk Record Deletion Jobs
- Outlook Integration
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/dyn...admin/readme-9
Don’t forget to subscribe to our blog
for more tips and tricks!
Happy Dynamics 365 Upgrading!
The post Scope for Dynamics 365 v9 Upgrade
appeared first on Microsoft Dynamics 365 | PowerObjects