Salesforce Tester

Sign in Subscribe

Topic

QA Thinking

A collection of 18 issues

The 'System Admin' Trap: Why Admin Testing Is Not Real Testing

The Illusion of the Green Build We have all been there. You are rushing to close out a sprint. You log into the Sandbox, run through the happy path, and everything works beautifully. The record saves, the Flow triggers, the email fires. You mark the story "Passed." Two days after deployment, a…

“It Worked in Sandbox” Is Not a Test Result

The Most Dangerous Phrase in the Ecosystem One of the most dangerous phrases in any Salesforce project is a sentence that sounds deceptively reassuring: “But it worked in the sandbox.” It feels like progress. It implies that the logic is sound and the feature is ready for deployment. But seasoned…

Configuration Is Still Logic: The Dangerous Myth of "Low Risk" No-Code

The Most Expensive Misunderstanding in Salesforce There is a pervasive lie in the Salesforce ecosystem that costs companies thousands of dollars in technical debt every year. It’s the belief that: “It’s just configuration, so it’s low risk.” We see it all the time. A developer writes five lines of…

“We’ll Fix It in the Next Sprint” Is a QA Smell

The Sentence That Quietly Kills Quality There is a sentence that quietly kills Salesforce quality long before a feature ever hits Production. It isn't a technical error message, and it isn't a user complaint. It’s a project management decision: “Let’s just fix it in the next sprint.” It sounds…

Why Salesforce Bugs Look Random (But Aren’t)

The Ghost in the Machine Every Salesforce tester has faced it. A ticket comes in with a description that makes your blood run cold: “The status update failed. But when I refreshed the page and tried again, it worked.” Or the classic: “It happens for Sarah in Sales, but never for Mike in Support.”…

The Myth of the “Simple Change”

The Most Deceptive Label in Deployment In the lexicon of Salesforce project management, there is no phrase more terrifying to a seasoned QA engineer than: “Don't worry, it’s just a simple change.” It is the prelude to every major outage. It is the justification for skipping regression testing. It…

The Admin User Is Lying to You

The First Step to Failure If you open a test case or a Jira ticket and the first step reads: "1. Log in as System Administrator" ...you have already failed. You are no longer testing the production system. You are testing a fantasy version of the application that only exists for a handful of…

When a Bug Is “By Design”: The Ultimate Conversation Stopper

The Most Frustrating Phrase in QA In the lifecycle of a Salesforce ticket, there is a specific moment where the investigation hits a brick wall. You report a defect. You describe the behavior. You attach the screenshots. And the ticket comes back with the status Rejected and the comment: “This is…

The Feature That Worked Until It Didn’t

The Time Bomb in Your Org There is a specific type of Salesforce failure that is more painful than any other. It isn’t the immediate crash upon deployment. It isn’t the obvious logic error found in UAT. It is the feature that works perfectly. It works for a week. It works for a month. The users…

The Bug Wasn’t in the Logic. It Was in the Assumption.

The Three-Week Time Bomb There is a specific kind of Salesforce bug that hates being found early. It doesn’t show up in System Integration Testing (SIT). It doesn’t appear in User Acceptance Testing (UAT). It certainly doesn't crash during the stakeholder demo. It appears three weeks after go-live,…