[Customer Support] Coverage test with real data#2997
Merged
Conversation
jlimatampersand
changed the title
jlimatampersand
commented
May 14, 2026
laurenzlong
approved these changes
May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Initially, our approach when testing Apex coverage was to use dummy data to cover the test. However, each different field has a different field integrity setting, e.g., eg) some fields are required and some are not, and we could not account for that fact with dummy data.
This PR is updating the test script to use real existing data from the actual org's instance so that we don't run into failures related to dummy data.
Test Result