💡 The Problem: Relationships Define Behavior In Salesforce, relationships are not just links between objects. They are behavioral switches that define how data behaves when records are deleted, who can see related records, and what kind of automation is possible. The chosen relationship type directly affects: * data integrity * security and sharing

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 able to: * identify where Record Types influence system behavior * design test cases that validate both execution and exclusion paths * avoid common QA mistakes related to

Lesson goal This lesson explains how Salesforce security layering really works and why QA must test effective permissions, not configuration in isolation. After completing this lesson, you should be able to: * understand the relationship between Profiles and Permission Sets * identify common conflict and override scenarios * design security test cases that

Lesson goal This lesson explains how to test CRUD permissions in Salesforce correctly, focusing on effective access rather than configuration assumptions. After completing this lesson, you should be able to: * design CRUD test cases for Salesforce objects * validate access across Profiles, Permission Sets, and Sharing Rules * identify high-risk CRUD misconfigurations

Lesson goal This lesson explains why Field-Level Security (FLS) is the ultimate authority on field access and how UI configuration can create dangerous false assumptions during testing. After completing this lesson, you should be able to: * understand how FLS interacts with Page Layouts and Lightning Pages * identify common UI illusions

Lesson goal This lesson explains how record visibility is calculated in Salesforce and why testing Profiles and Permission Sets alone is not enough. After completing this lesson, you should be able to: * understand how Salesforce determines who can see which records * test Organization-Wide Defaults, Role Hierarchy, and Sharing Rules together

Lesson goal This lesson introduces structured testing of Salesforce Flows as declarative automation, treating them with the same rigor as custom code. After completing this lesson, you should be able to: * test when a Flow runs and when it must not run * design test cases that cover all decision paths

Lesson goal This lesson explains how QA can safely and effectively test Apex-based automation without reading Apex code. After completing this lesson, you should be able to: * apply black-box testing techniques to Apex Triggers and Classes * design test cases based on inputs, outputs, and side effects * identify logic defects, performance

Lesson goal This lesson explains how to test Salesforce automation that changes record state, especially when those changes are irreversible or trigger external side effects. After completing this lesson, you should be able to: * identify high-risk state transitions in Salesforce processes * design tests for irreversible status changes and record locks

Lesson goal This lesson explains why the Salesforce Order of Execution (OOE) is critical for QA and how automation components interact during record save operations. After completing this lesson, you should be able to: * understand how Salesforce processes a record save step by step * identify high-risk interaction points between Flows,