Salesforce testing gotchas: When playing it safe can backfire for charities
Blog
At Giveclarity, we work with nonprofits to deliver Salesforce solutions that are robust, scalable, and tailored to real-world needs. And testing is a critical part of that journey. We advocate for involving testers early in the process, not just at the end. Because their insights help shape a solution that works in real-world conditions. Early engagement reduces surprises and builds confidence in the final product.
“Did we just break Salesforce?”
But there’s a moment in almost every project where testing throws up something unexpected. The client’s internal tester flags it: “I ran a test and got some unexpected results. Can you please fix this?”
It’s a fair question. But as consultants, we have a responsibility to pause and ask: “Is this a real issue, or just a test scenario issue?”
The problem with test environments
Test environments are rarely perfect mirrors of a live system. They’re often:
- Compressed: test scenarios are sometimes executed on an artificially compressed timeline. For example, a process which will only run once per month in real life might be run several times per day during a simulated test.
- Synthetic: test data is recycled, unrealistic, or incomplete.
- Manual: processes that would be automated in live operations are simulated by hand and therefore more error prone.
- Out of sequence: events unfold in ways they wouldn’t in real-world usage.
- Not fully connected: some systems might not have test environments available, which means some Salesforce test environments may not be fully integrated which complicates end-to-end testing.
These factors can produce false test results. This may be issues that look serious in testing but are unlikely to occur in the real world. At Giveclarity, we’ve seen how these artificial conditions can sometimes lead to false alarms. And we’ve learned that our role isn’t just to do as we are told. It’s to challenge.
The cost of saying ‘Yes’
If we were to address every anomaly seen in testing, our clients would pay for it twice:
- Immediate cost: Budget and time spent fixing a problem that may never occur.
- Long-term cost: Maintenance overhead and system complexity that grows over time.
Every fix adds weight. And in the nonprofit sector, where resources are precious, that weight matters.
Our responsibility as consultants
Consulting isn’t just about delivery output. It’s about exhibiting good judgement and reading between the lines. That means helping clients distinguish between real risks and testing noise. It means asking the hard questions, even when the impulse is to say “I’ll get right on that”:
- Does this issue reflect real-world usage?
- Is it a product of the test environment?
- What’s the cost of solving it, and of not solving it?
None of this means ignoring genuine issues. Listening to clients is non-negotiable. Our role is to separate the real signals from the noise, not to dismiss concerns. And to ensure fixes are proportionate and necessary. The goal isn’t to avoid the work. It’s to avoid unnecessary complexity that doesn’t serve the organisation’s mission.
Final thoughts..
So, here’s the takeaway; good consulting for us isn’t about doing everything the client asks. It’s about helping charities make the right decisions. And sometimes the hardest thing to do, is to do nothing at all.
About the author:
Aske Bong-Saxe is our Solutions Architect