Salesforce Tester (Page 1)

Salesforce Tester

Sign in Subscribe

Latest — 25 Jan 2026

Why Salesforce QA Is Not the Same as Manual Testing?

A short story about learning a platform that refuses to behave like normal software. When I started working as a Salesforce tester, I was convinced I understood what I was getting into. Testing is testing — you click, compare expected vs actual, and report bugs. A normal job, just with Salesforce

More issues

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

Case Study: How One Checkbox Triggered a Major Incident

Some Salesforce bugs come from code. Some come from automation. This one came from the most dangerous thing in every project: A checkbox no one understood. The Incident A Sales Manager reported: “All our discounts disappeared. Every Opportunity now requires executive approval.” This was not good. This was the definition

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.

The Five Requirement Categories Every Salesforce Tester Must Master

If you’ve ever opened a Salesforce requirement that looked perfectly clear — and then spent two hours wondering what it actually meant — congratulations: you're officially a Salesforce tester. But here’s the good news. Every requirement you will ever test, no matter how messy, vague, incomplete, or chaotic,

Test Analysis 101: The Six Questions That Change Everything

Most junior testers write test cases by reading requirements. Most senior testers write test cases by analysing requirements. The difference? Analysis reveals what the requirement doesn’t say. Here are the six questions that every professional Salesforce tester must ask — every single time. 1. Who? Not a person. A role,

The Invisible Wall: Why Access Testing Is the Superpower of Salesforce QA Because half the bugs in Salesforce are not bugs — they are permissions.

If you want to see a Salesforce architect panic, show them a user who can suddenly see a field they shouldn’t. If you want to see a tester panic, show them a bug report that makes no sense because it “works for Admin.” Every Salesforce tester eventually learns: Nothing

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