Now Available in Community - New TechTalk Videos for 2020
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
One of the failings of the UAT is the lack of performance testing, what tools are suggested and is there an expectation matrix based upon company size, complexity, users, D365 elements in use etc?
I suggest to start with the TechTalk Performance Testing Approach (infopedia.eventbuilder.com/event;source=Dynamics_365_for_Operations_-_FastTrack_Tech_Talks) to understand our guidance regarding performance testing.
In case that a customer states in the Checklist that they saw poor performance in UAT, this is what we put into the assessment report:
Sorry to hear that you are seeing poor performance in the UAT environment. Here are some things to consider and actions to take before moving to production:
• Has performance been bad across all processes and users and times?
• Are there specific actions that are especially slow?
• Have you used the Performance timer to better understand where the time is spent?
• Have you taken traces to determine what contributes to poor performance?
• Have you used Environment monitoring to see if there are any locking or blocking issues, slow queries, or missing indexes?
• Do you have your most critical scenarios documented, including performance goals?
The most important point here is to understand that Performance is not Microsoft responsibility alone, it is a combined effort since performance can be affected by variables outside of Microsoft’s influence, including but not limited to your customizations, ISV code, system configurations, timing of batch jobs and integrations.
The project will need to decide based on their parameters how much performance testing is required and on which environment (Standard Tier-2 or Tier 4 or 5 performance testing environment).
Microsoft FastTrack Solutions Architect
Hello Steve, hope I answered your question. If so, can you please mark it as answered? If no, I will be happy to provide more detail.
Cheers, Claudia Betz-Haubold
With regards to the question on tools the video does not answer that; automated testing is outside of this. I can see the link to the VSTS test automation but this seems more about code not functional volume processing to test performance. However I am functional so perhaps I am misunderstanding what is being documented.
In this instance it seems there is actually no relationship between the actual and tested. This means the user could undertake UAT at a level that does not impact performance and that is the responsibility of the customer.
I would still like to understand any recommendations on load performance for scalability, so if I have to load and process 10,000 sales lines is the suggestion the data entities? This is then difficult if you want configuration configurations, dimensions, part shipments, part stock, consolidated picking etc. Most of the scenarios discussed are manual.
I am understanding from the answer that there is no matrix of volume for performance testing against the company size/use. Ultimately if a customer performance tests at 10,000 sales line a day when the reality is 1,000,000 lines a day they have performace tested and proved an element of scalability. Naturally the partner would want the customer to undertake proper testing but it is the responsibility of the customer. There is ultimately no relationship between the potenital use of the system and how "performance" testing is undertaken in the UAT, it is the customers responsibility to functionally test and validate.
Here is a list of testing tools and scenarios where they should be used
The first two are available already and since the beginning. The third is in PU17+. The 4th option is in preview and will be listed in the October release notes.
Just wanted to post an updated link to the video as it doesn't work so here is a working version:
Business Applications communities