Salesforce Tester

Sign in Subscribe

Topic

Case Study

A collection of 9 issues

The Most Dangerous Sentence in Salesforce Testing

The Sentence That Should Stop the Meeting There is one sentence that should immediately raise a red flag in any Salesforce project. It sounds harmless. It sounds efficient. It sounds like the voice of experience. “We don’t need to test this, it’s just standard Salesforce.” You hear it

Salesforce Is Deterministic. People Are Not.

The Most Unfair Complaint in the Ecosystem One of the most unfair things people say about Salesforce during a crisis is this: “The system is behaving randomly.” It’s the go-to excuse when a bug appears, disappears, and then reappears three days later. It comforts the team to believe that

The Test Case That Passed and Still Broke Production

The Silence After the Release There is a special kind of silence that falls over a project team on a Monday morning. The release went out on Friday. The dashboard shows 100% test pass rate. The stakeholders signed off. And yet, Production is currently exploding. Users are stuck, data is

The Ticket That Wasn’t a Bug (But Cost 6 Hours Anyway)

Some bugs are loud. Some bugs are dramatic. And some bugs… never existed in the first place — but still consume half your day, three people’s sanity, and the last bit of trust the business has in the system. This is a story about the third type. The Defect That

Case Study: When a Missing Validation Rule Cost a Full Sprint

Sometimes bugs are complex. Sometimes bugs require deep investigation. And sometimes bugs exist simply because no one asked a basic question: “Should the user even be allowed to save this?” The Setup The client had a strict rule: “Opportunities must have a Contract Start Date before they can be marked

Automation Chaos: Why Flows Break Even When Everything Looks Fine

Every Salesforce tester has experienced this moment: A business user raises a ticket saying, “The system is broken.” You open the record, click the same button… And everything works perfectly. Welcome to the wonderful world of Salesforce automation, where things break silently, inconsistently, and only when you’re not looking.

Case Study: The 100-Product Opportunity That Hit Governor Limits

Some Salesforce bugs are subtle. Some are dramatic. And some are so catastrophic that the platform itself steps in and says: “No. Absolutely not. Stop what you’re doing.” This is a story about the third kind — a real project, a real failure, and a lesson every Salesforce tester must

Case Study: When Process Builder Migration Almost Broke Production

This is one of those Salesforce stories that starts innocently… and ends with half the system refusing to work. It’s also one of the best lessons about the difference between Process Builder, Flow, and Apex execution context. Background The client had around 40 Process Builders running various parts of

The Myth of the “Quick Fix” in Salesforce Projects

There are few phrases that make Salesforce testers more nervous than: “It’s just a quick fix.” Every time someone says it, a validator breaks, a flow collapses, and somewhere in the distance an Integration Lead feels a disturbance in the Force. Let me tell you why “quick fixes” almost