04.01.01 — Standard vs Custom Objects: What QA Must Understand
💡 The Problem: “Standard” Does Not Mean “Safe” In Salesforce, everything starts with Objects. They are the foundation of the entire data model and the…
💡 The Problem: “Standard” Does Not Mean “Safe” In Salesforce, everything starts with Objects. They are the foundation of the entire data model and the…
💡 The Problem: Fields Are Not Just Containers In Salesforce, a field is not just a place to store data. Its definition — data type, constraints, and…
💡 The Problem: Relationships Define Behavior In Salesforce, relationships are not just links between objects. They are behavioral switches that define how…
Lesson goal This lesson explains why Record Types must be treated as logic drivers, not just UI selectors. After completing this lesson, you should be…
Lesson goal This lesson explains how Salesforce security layering really works and why QA must test effective permissions, not configuration in isolation.…
Lesson goal This lesson explains how to test CRUD permissions in Salesforce correctly, focusing on effective access rather than configuration assumptions.…
Lesson goal This lesson explains why Field-Level Security (FLS) is the ultimate authority on field access and how UI configuration can create dangerous…
Lesson goal This lesson explains how record visibility is calculated in Salesforce and why testing Profiles and Permission Sets alone is not enough. After…
Lesson goal This lesson introduces structured testing of Salesforce Flows as declarative automation, treating them with the same rigor as custom code.…
Lesson goal This lesson explains how QA can safely and effectively test Apex-based automation without reading Apex code. After completing this lesson, you…