This article provides advice on how to test a Lumary release in your sandbox.
A sandbox is a testing environment that does not use or affect the live data in your production environment. Lumary uses sandboxes to provide access to releases for testing prior to updating production environments.
A sandbox may also be referred to as a user acceptance testing (UAT) or pre-production (pre-prod) environment or org.
When we deploy a release to your sandbox, we encourage you to test the new features and improvements against your usual business processes. New features and improvements may not appear to directly affect the parts of the system you use. However, it’s worth running through common scenarios to make sure that they still function as expected.
Failing to test a release before it’s applied to your production environment may expose your live data to issues that impact on your business processes and/or claims.
To start testing, we recommend that you:
Log into your sandbox
To log into your sandbox, you use a different URL than when you log into your live production environment. The URL for sandboxes is usually https://test.salesforce.com/. When you log into your sandbox, you’ll see a banner at the top of the page that reads Sandbox: UAT or something similar.
Refresh your sandbox
Before you begin testing, we recommend that you refresh your sandbox. This will align your sandbox's data to the data in your production environment.
Find out how to refresh in Salesforce's Refresh Your Sandbox help article.
Top testing tips
We understand that it takes time to test and it can be tough to know where to start. We've put together some tips to help you make the most out of your testing time.
Don't try to test the entire system with each release. Focus on the parts of the system that:
To find out what's new, check out the release notes in the releases section of the Help Centre.
If you find an issue during testing, make sure you capture as much information about the problem as you can. Our Submit a support request article includes a handy list of the information you should aim to gather before you tackle the request form.
If you’re testing something that occurs at the end of a process, for example, an extract, we recommend using fresh data to recreate the whole process. Set up a new client and service agreement, deliver some services, and then perform the extract.
If you use batch processes to automatically generate records, make sure you have the same processes set up in your sandbox. Make sure that these processes have run during your testing and produced the expected results.
Find out more about how to raise an issue about a release.