Salesforce QA Analyst: How to Become One in 2026

To become a Salesforce QA analyst, learn the platform as an admin first, then test design, Apex testing and one automation tool. A Salesforce QA analyst is the person who tests flows, rules, permissions and code in a Salesforce org before changes reach users. Admins and developers both move into the role.

Clientell AI, the AI Salesforce admin, scans your org read-only and returns a ranked list of risky flows, validation rules and permission sets. For a tester, that list is a ready test backlog. Start with the free Salesforce health check.

What does a Salesforce QA analyst do?

The role, also called Salesforce tester, checks that changes work and that old features still work. The job posts at the top of search show the shape of it. A federal contractor lists functional, regression, integration and release testing, plus defect tracking and user acceptance testing (ICF job post, September 2026).

In plain terms, you write test cases, run them, log defects, and re-test fixes. You also sit with business users during user acceptance testing (UAT), where the people who will use the change try it first.

There are two common flavors:

• Functional QA: you test configuration. Think flows, validation rules, page layouts, reports and permissions. This suits admins.
• Technical QA: you test code and automation. Think Apex classes, triggers, Lightning components and browser scripts. This suits developers.

What does a QA analyst test in a Salesforce org?

Five areas cover most of the work, from Flow versions to Apex test classes. Each one has its own Setup menu path and its own way to fail.

Apex has a hard rule. A production deploy fails if overall Apex code coverage falls below 75% (Apex Developer Guide). Production runs the tests again on its own data and metadata, so coverage results often differ from the sandbox (Apex Developer Guide). So a change can pass in a sandbox and fail the production deploy.

Coverage counts lines that ran. It does not prove anything was checked. A QA analyst reads the assertions. Here is a test that checks an outcome:

@IsTest
private class OpportunityTaskTest {
    @IsTest static void closedWonCreatesTask() {
        Account a = new Account(Name = 'Test Co');
        insert a;
        Opportunity o = new Opportunity(Name = 'Deal', AccountId = a.Id,
            StageName = 'Prospecting', CloseDate = Date.today().addDays(30));
        insert o;
        Test.startTest();
        o.StageName = 'Closed Won';
        update o;
        Test.stopTest();
        List<Task> tasks = [SELECT Id FROM Task WHERE WhatId = :o.Id];
        Assert.areEqual(1, tasks.size(), 'Closed Won should create one task');
    }
}

A test with no Assert line would give the same coverage number and catch nothing.

Worked example: test one validation rule

Say a rule on Opportunity blocks saves when Amount is zero or less. Write four cases and the expected result for each:

1. A value of 1: the save succeeds.
2. Zero: the save fails with the rule's error message.
3. Negative, such as -5: the save fails with the same message.
4. Blank: the save follows the rule's null handling, so confirm it matches the requirement.

Run each case as a sales user, not as yourself, because a rule can be written to skip users who hold a certain custom permission. Log any mismatch as a defect with the record link, the user and the exact message.

Why do the three yearly releases matter for QA?

New features arrive three times a year, in Spring (February), Summer (June) and Winter (October) (Salesforce Help: release schedule FAQ). Each release can change standard behavior that your flows, code and tests rely on.

Sandboxes get the release early. Preview sandboxes upgrade 4 to 5 weeks before production, in January, May and September (same Salesforce Help page). That window is your regression testing time. You re-run the saved test suite, find what broke, and report it before production upgrades.

Regression testing means re-checking old features after a change, such as the flow that sets Opportunity.Probability when the stage changes. It is the best reason to automate.

Which tools do Salesforce testers use?

Pick one automation tool for browser tests and use the Apex runner for code. Learning all of them wastes time.

Pricing differs by vendor and changes often, so check each vendor's own site. Agentforce Testing Center only covers AI agents. It does not replace testing of flows and Apex. For the difference, read Agentforce Testing Center vs real testing.

What can go wrong in testing, and how do you undo it?

Three failures show up again and again:

• A test passes in the sandbox and fails in production. The cause is often missing data or a different permission set. Run a Validate Only deploy to production first. It runs the same tests and saves nothing.
• A flow works for admins and breaks for sales users. Test with System.runAs in Apex, or log in as the persona.
• A release changes behavior. Re-run your regression suite in the preview sandbox and file the defect before production upgrades.

To undo a bad change, redeploy the last good version of the component, or deactivate the flow version in Setup > Flows. Keep a note of the version you replaced.

What skills do you need?

• Platform basics: objects such as Account and Opportunity, fields, relationships, page layouts, and the security model (profiles, permission sets, sharing).
• Test design: turn a requirement into positive, negative and boundary cases.
• Reading flows and Apex: you do not need to write big classes. You need to see what a trigger on Opportunity does when Opportunity.StageName changes.
• SOQL: query records to check data before and after a test, for example SELECT Id, StageName FROM Opportunity WHERE Id = :oppId.
• Defect writing: exact steps, expected result, actual result, and the user and org. For example: "Saving an Opportunity with Opportunity.Amount of 0 as a sales user shows no error. Expected: the validation rule message."
• Communication: in a UAT session you walk a sales manager through each test case and record their pass or fail.

Which certifications help in 2026?

No QA-specific Salesforce certification exists. These Salesforce and ISTQB credentials help, as of October 2026:

The Platform Administrator exam has 60 scored questions, a 105-minute limit and a 68% pass mark in English (exam guide). Check your readiness with the Salesforce certification quiz, and see what exam pass marks look like in this admin exam breakdown.

How do you become a Salesforce QA analyst?

1. Learn the platform. Finish the Trailhead admin path, then build a free Developer Edition org to practice in.
2. Learn to test. Study ISTQB Foundation topics: test cases, boundary values and defect reports. Practice on a validation rule such as Amount > 0 on Opportunity: test 0, 1, a negative value and a blank.
3. Learn Apex testing. Learn @IsTest, Test.startTest() and Test.stopTest(), and test data setup with Account and Opportunity records. Complete the Apex testing module on Trailhead and write tests with real assertions.
4. Test your own work. For every flow or rule you build, write a test sheet with the entry condition, the expected record changes, edge cases and a pass or fail result. Check the result in Setup > Debug Logs or the flow debug view.
5. Add one automation tool. Try Selenium for free, or ask a team that uses Provar or Copado Robotic Testing to let you shadow a run.
6. Get the certifications. Platform Administrator first, then App Builder, then ISTQB Foundation.
7. Build a portfolio. Keep two or three anonymized test plans and one regression suite in a public repository.
8. Apply. Target Salesforce consultancies, government contractors and companies with many sandboxes and release trains. Bring your test plan for one Opportunity validation rule as a sample. Search for "Salesforce QA analyst", "Salesforce tester" and "Salesforce quality assurance".

Admins can start at step 4 today. Developers can start at step 2.

How much does a Salesforce QA analyst earn?

Pay for testers in Salesforce orgs sits close to general software testing pay. Talent.com tracks the Salesforce title, and BLS tracks all software testers. As of October 2026:

Compare city by city in our Salesforce QA analyst pay guide.

Can AI help with Salesforce testing?

Yes, for the repeat work. AI can draft test cases from a flow, list the permission sets a persona holds, and flag rules that nothing tests. A human still decides what "correct" means for the business.

Clientell AI reads the org read-only first, builds changes in a sandbox, tests them, and asks before it changes anything in production. See how the AI Salesforce admin works.

Try it in Clientell AI: "Scan my org in read-only mode and give me a ranked list of the ten riskiest flows and validation rules to test, with a test case for each." Start a 14-day trial, no card.

Or run the free, read-only health check.

Sources

Salesforce documentation

• Apex Developer Guide: Code Coverage Best Practices
• Release schedule FAQ
• Platform Administrator exam guide
• Platform App Builder exam guide
• Apex Developer Guide: testing
• Agentforce Testing Center

Industry research

• US Bureau of Labor Statistics: software developers, QA analysts and testers
• Talent.com: Salesforce QA analyst salary
• ISTQB Foundation Level

Last reviewed October 2026

Last updated: October 22, 2026