.svg "Leapwork")
Knowledge base
Tips and tricks Best practice guides, FAQ & more
Dynamics 365 One Version is a strategy introduced by Microsoft that implicates D365 business applications. The aim is to have all customers operating on one version of Microsoft’s products, as this will have a positive impact on the quality and ability to service those products. However, it also has the effect of increasing the need for software testing. To some businesses, this means a shift in their testing approach. Learn why in this article.
Skip to:
What is D365 One Version?
The QA challenges of moving to D365 One Version
What tool can you use to automate D365 testing?
The One Version strategy was introduced by Microsoft with the aim of ensuring that their customers are operating on the latest version of their Dynamics 365 applications, including Finance, Sales and Business Central. This helps create a better user experience, with fewer compatibility issues and greater overall quality.
Being on the latest version means customers always use the most up-to-date security patches and features, helping to protect against cybersecurity threats and data breaches.
|
Why One Version? It helps provide a seamless and consistent experience for Microsoft D365 users |
What is it? A series of initiatives, including regular, mandatory updates with new features, bug fixes, and security enhancements |
How does it work? D365 customers automatically receive regular, scheduled updates to the applications |
A recent and significant step in the One Version journey has been to introduce what are known as Proactive Quality Updates (PQUs): these occur monthly and are automatically applied to all of the applications in the portfolio of D365.
A key thing to take into account is that these updates are mandatory – customers are automatically enrolled and cannot postpone or reject them. Customers can, however, choose to test functionality a week ahead of the update in a sandbox environment.
Despite the benefits the One Version strategy brings to its customers in the long run, there are implications for QA teams here and now. In order to accept the latest and greatest version with new features and capabilities, QA teams will need to increase testing to ensure coverage in time for each update.
Because One Version’s PQU’s are mandatory, they will have the effect of raising the average quality of Microsoft’s software. However, every time new code is released, it brings the risk of impacting existing code. This means customizations and integrations across the business’ IT landscape are at risk of breaking with each update.
The alternative to increasing testing is a risk-based approach, where QA accepts low coverage and heightened risk while also accepting that they don’t have the resources to do otherwise.
Many teams rely on this approach, because they have been unable to successfully adopt a scalable test automation strategy.
Often, regression testing in Dynamics is what’s compromised as a result of a risk-based approach. Not because it isn’t important, but because it’s extremely time-consuming for businesses with large and complex IT environments.
But with a solid test automation solution, QA can increase test coverage, test for regressions with every release, reduce risk, and accept each update with full confidence in the quality of their software.
The dependency on manual testing is currently counteracting the most important mission of using software in enterprises: driving efficiencies, improving productivity, and delivering software at speed to improve competitive position in the marketplace.
Businesses that rely solely on manual testing will be at risk of falling behind their competitors who are using test automation to increase efficiency and productivity.
The right Dynamics 365 testing tools need to allow testers to quickly automate with an approach where they can learn, build, maintain and scale automation quickly. This will enable teams to increase test coverage and thereby secure high quality with each update.
This is what Leapwork’s test automation platform offers. With its visual testing approach, the tool offers a way for those without programming skills to automate D365 testing. Leapwork-built tests don’t require developers to build or maintain automation, making heavy maintenance of broken UI tests a thing of the past.
This enables teams to scale test automation at speed and reduces the reliance on developer-skills to achieve test automation.
Become fully equipped to handle your D365 testing challenges. In this solution brief, you can learn how to build test automation for Dynamics 365, how to address the challenges brought about by testing Microsoft D365, and presents the Leapwork solution as a way to meet those challenges.
