Become a Dynamics 365 expert with Syvantis Learn
Provide additional details about the offer you're running.
Excel Workbook - Release Wave Testing Resource
Regular price
$0.00 USD
UPDATE TESTING: WHY?
It’s important to test your system to ensure the update will not interfere with your processes and, most importantly, system customizations and extensions. It is crucial to test the transactions that use any of your customizations or extensions early in a sandbox environment, lest they break in production and halt your business processes.
The best way to validate your version update is to run through critical business processes in your sandbox environment, including extensions, customizations, printing reports, posting journal entries, creating orders, and so forth. After you validate the update in the sandbox, your production environment can be safely updated, as well.
It’s also best to perform update testing earlier rather than later because if you do run into any hiccups that need to be fixed, you need time to correct the issues before Microsoft automatically updates environments, which could occur within 60 days or less after the release wave has become generally available.
We know that prepping for an update can feel a bit overwhelming, so to support thorough testing, we’ve created a few different resources—all of which can help an organization prepare for these semi-annual release waves. Read the descriptions below to see which resource may be best for you, and then use whichever you want!
Excel Workbook
Designed for:
- Small businesses
- One team member conducting the full update testing
- Teams needing high customizability of testing actions and/or who need a straightforward workbook with little to no chance of breaking when it is adjusted
What is it?
This is an Excel Workbook version of the checklist. It is straightforward in design and doesn’t include too many formulas, but is satisfyingly color-coded, filterable, and sortable. This resource is highly adjustable: add or remove or hide test actions to match the needs of your company. You can also make copies of the test tab if several team members conduct testing (which we recommend!).
What’s in this workbook?
- Introduction Tab: A summary of the workbook’s purpose and general instructions to guide your release wave testing.
- BC Update Test Tab: This is where your test items are housed. You’ll notice a header including fields to enter the version/update number, the team member conducting the tests, and the testing date. It includes several columns, including the area of BC being tested, the test action, the status of the test, and notes. The columns are sortable, filterable, and satisfyingly color-coded.
Looking for more release wave resources or information?
Looking for more info about Release Waves? Check out our Microsoft Release Wave blogs: Microsoft Dynamics Release Update | Syvantis Blog – Syvantis Technologies, Inc.
Is this resource not quite right for your needs? We have other testing resources! See the other resources, plus additional considerations for your testing: Release Wave Testing Resources for Business Central – Syvantis Technologies, Inc.
UPDATE TESTING: WHY?
It’s important to test your system to ensure the update will not interfere with your processes and, most importantly, system customizations and extensions. It is crucial to test the transactions that use any of your customizations or extensions early in a sandbox environment, lest they break in production and halt your business processes.
The best way to validate your version update is to run through critical business processes in your sandbox environment, including extensions, customizations, printing reports, posting journal entries, creating orders, and so forth. After you validate the update in the sandbox, your production environment can be safely updated, as well.
It’s also best to perform update testing earlier rather than later because if you do run into any hiccups that need to be fixed, you need time to correct the issues before Microsoft automatically updates environments, which could occur within 60 days or less after the release wave has become generally available.
We know that prepping for an update can feel a bit overwhelming, so to support thorough testing, we’ve created a few different resources—all of which can help an organization prepare for these semi-annual release waves. Read the descriptions below to see which resource may be best for you, and then use whichever you want!
Excel Workbook
Designed for:
- Small businesses
- One team member conducting the full update testing
- Teams needing high customizability of testing actions and/or who need a straightforward workbook with little to no chance of breaking when it is adjusted
What is it?
This is an Excel Workbook version of the checklist. It is straightforward in design and doesn’t include too many formulas, but is satisfyingly color-coded, filterable, and sortable. This resource is highly adjustable: add or remove or hide test actions to match the needs of your company. You can also make copies of the test tab if several team members conduct testing (which we recommend!).
What’s in this workbook?
- Introduction Tab: A summary of the workbook’s purpose and general instructions to guide your release wave testing.
- BC Update Test Tab: This is where your test items are housed. You’ll notice a header including fields to enter the version/update number, the team member conducting the tests, and the testing date. It includes several columns, including the area of BC being tested, the test action, the status of the test, and notes. The columns are sortable, filterable, and satisfyingly color-coded.
Looking for more release wave resources or information?
Looking for more info about Release Waves? Check out our Microsoft Release Wave blogs: Microsoft Dynamics Release Update | Syvantis Blog – Syvantis Technologies, Inc.
Is this resource not quite right for your needs? We have other testing resources! See the other resources, plus additional considerations for your testing: Release Wave Testing Resources for Business Central – Syvantis Technologies, Inc.
