Tomasz Teodorowicz

Lesson goal This lesson explains how Salesforce Governor Limits translate into QA responsibilities. After completing this lesson, you should be able to: * understand why Governor Limits are QA requirements, not developer trivia * design test cases that expose bulkification and performance risks * validate synchronous vs asynchronous execution strategies * identify scalability defects

Lesson goal This lesson explains how QA should test and document integration failures in Salesforce environments where multiple systems interact asynchronously. After completing this lesson, you should be able to: * identify common integration failure modes * design test cases for partial and asynchronous failures * verify compensating logic and recovery paths * validate

Lesson goal This lesson explains how QA validates data consistency in integrated Salesforce environments. After completing this lesson, you should be able to: * understand why latency is unavoidable in integrations * test whether synchronization delays are acceptable to the business * verify retry and recovery mechanisms * detect data overwrite and conflict scenarios

Lesson goal This lesson explains why Governor Limits are a critical QA concern, not just a developer problem. After completing this lesson, you should be able to: * understand how Salesforce Governor Limits impact integrations and automation * design bulk tests that expose non-bulkified logic * detect inefficient SOQL and DML usage * identify

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,

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 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 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 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 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