Verify data has not changed or is within thresholds
Data Shield
With Data Shield, available as part of TestShield, you can ensure that your configuration or reference data hasn’t been tampered with since it was set up or check that data in the system does not fall outside of your defined thresholds.
Setting up an Data Shield test follows the same “Four A’s” pattern as all of TestShield’s tests:
- Assemble – describes the data that you are testing
- Arrange – not usually required for Data Shield as the data being checked is already in the system
- Act – define tests for checking thresholds e.g. count records, find min/max values
- Assert – define the data being checked, or the thresholds being measured against
Data Shield tests can be executed manually, part of an automated Test Runner schedule or from Azure DevOps.
Example – xCache configuration data
The example in the images below shows how to test whether configuration data stored in xCache has changed. We take a ‘snapshot’ of the configuration data (in this case the credit score tiers for a platinum credit card) and when the test executes it compares the snapshot with the current values. Any values that don’t match will register a failure.
Assemble
Assert
Example – Subjects configuration data
The example in the images below shows how to test whether configuration data stored in the out-of-the-box Subjects has changed. We take a ‘snapshot’ of the configuration data and when the test executes it compares the snapshot with the current values. Any values that don’t match will register a failure.
Assemble
Assert
