Ashgrove Veterinary Partners' specialist has to explain to a new hire why the team keeps a written library of Testing Center cases in version control rather than only in the Testing Center UI itself. What is the strongest reason for keeping that external copy?
Select an answer to reveal the explanation.
Short Explanation
Testing Center is where cases run, but a version-controlled copy is the paper trail. If a case gets edited or deleted, or the org changes underneath it, you still know exactly what was tested and why.
Full Explanation
Keeping test cases in version control alongside the Testing Center UI gives the team a durable, auditable record independent of the live org: what scenarios were validated, what the expected outcomes were, and a history of how the test suite evolved over time. That record survives someone accidentally editing or deleting a case, or the org's configuration changing in ways that could otherwise obscure what had actually been verified at a given point. This is not because Testing Center cases are unreadable once created — they remain viewable and editable within the tool, which is a separate concern from durability and audit history. There is no Salesforce behavior that auto-deletes Testing Center cases on a 30-day cycle; that claim invents a constraint not grounded in how the platform works. And claiming no real benefit to an external copy ignores the genuine risk of relying on a single, live, editable source with no independent history — exactly the risk a version-controlled copy is meant to mitigate. The broader lesson: treating test cases as an artifact worth versioning, not just as ephemeral configuration inside one tool, is sound lifecycle discipline.