Dissatisfied with their existing testing provider working on the Dynamics 365 implementation, the wholesaler asked Planit to conduct a review of the testing process and to provide suggestions for improvement. As a result of this review, Planit was selected to become their new quality assurance partner and to implement the changes defined in the review.

One reason for Planit’s selection was our approach for working with their subject matter experts (SME). This included eliciting the information needed so that we could execute most of the testing, but also coaching the SMEs in how to test, and what was expected of them when doing it. This close collaboration was key to filling in gaps in documentation and enabling us to learn about the wholesaler’s processes.

We also liaised with the system integrator on behalf of the SMEs. In most cases, we would pre-test modifications and configuration changes prior to updating test cases and then assist the SMEs with their testing. This helped to reduce the SME time required to work through integration issues and provided faster turnround time for the integrator when defects were discovered.

SME involvement and participation were critical goals for the wholesaler, not just to leverage their knowledge, but also to gain their buy in to the solution. Therefore, we did our utmost to make the SME experience as productive as possible.

We worked out the technical bumps in new releases, provided documentation for SMEs to follow, and provided training on the product where needed. This helped the SMEs to use their time efficiently while still meeting the business goals for the project.

As with most projects, time was constrained and the staged go-lives had to occur at specific times of the year when risk of disruption to the business was lower. If a go-live date was missed, the release would move at least six months and, in some cases, an entire year.

Because of the time constraints, a risk-based approach was used for the testing. This concentrated the testing on the changes made specifically for the wholesaler rather than broadly testing the Dynamics 365 product itself. This focus helped to reduce the time required for testing and helped to drive out the highest risks as early as possible.

Another goal for testing was to build a repository of test cases that could be reused for manual regression testing of later releases and for future test automation. Because Dynamics 365 releases must be installed at a regular cadence, having an established regression suite is imperative to reduce the risk of these releases.

We documented all the test cases to a level where they could be run by anyone with a good understanding of the business processes. In addition to being used for the manual testing of the quarterly releases and monthly minor releases, these test cases also became the basis for the automated regression test suite that we implemented.

In addition to the functional testing and test automation, we also provided data migration and performance testing. We sought to fill all the testing needs for this project, both in the short-term to facilitate the go-live, but also the long term by building maintainable test cases with full traceability back to the requirements.

We implemented a test automation framework to ensure the automation scripts were standardised and easily maintained for the life of the product. To further support their testing, we also conducted training sessions for new testers employed by the wholesaler to allow them to take over the maintenance of the test automation.