About testing in Salesforce 🤔

Hmmm...

• Customized features in Salesforce may orchestrate actions in several development/configuration tools: Apex, Flow, Process Builder, Workflow Rules, ... There is no out-of-the-box testing functionality that covers all these tools.

• Using Apex test coverage % as a quality KPI may be OK for unit testing Apex. But only if you know what the tests validate and how they do it. In a laissez-faire development model this KPI is not a valid indicator for the quality of the Apex code base.

• Apex Test Classes and tests in After Save Flows can validate "behind-the-curtain" transactions.

  • Unfortunately, these may be low level Unit Tests that test the implementation details.

  • In some cases Unit Tests are written only to pass the test coverage %

---

Materials by Salesforce

Automation Learning Map

• https://help.salesforce.com/s/articleView?id=platform.flow_get_started_learning_map.htm

Just like a waterfall?

• Assess & Plan ➔ Design ➔ Build ➔ Test ➔ Deploy ➔ Manage and Maintain

---

architect.salesforce.com

• Resilient - Testing Strategy:

  • https://architect.salesforce.com/well-architected/adaptable/resilient#Testing_Strategy

• Point of the view of technical architecture?

---

Help

• Testing Your Flow

  • https://help.salesforce.com/s/articleView?id=platform.flow_concepts_testing.htm

• Troubleshoot Flow Errors

  • https://help.salesforce.com/s/articleView?id=platform.flow_troubleshoot_email.htm

---

engineering.salesforce.com

• Josh Meier (2024): Tester Augmentation, Not Test Automation

• Prantap Bedi (2024): Automating Complex End-to-End Tests

• Jae Taylor (2024): 6 Ways We Deliver on Our Promise of Availability and Performance

  • "Throughout our development lifecycle, we continuously create and run tests. In fact, within the development phase alone we run over 1.2 million automated tests."

• Dmitry Melanchenko (2024): What is observability?

• Ian Varley (2024): Configuring It All Out

---

Salesforce Developers

• Salesforce Developers Blog

  • Philippe Ozil (2022): Run End-to-End Tests with the UI Test Automation Model (UTAM)

  • Dan Stead (2021): Automated Testing with the Salesforce Mobile App & Appium

  • Jonathan Au (2020): UI Test Automation on Salesforce

  • Georg Neumann ( 2019): Automated Testing of Global Search in Lightning UI

• Salesforce Developers Podcast

  • Episode 201: Test Automation using MaxTAF with Alex Delic

• Georg Neumann

  • (2021): UI Test Automation for Salesforce

---

Other Solutions

About other solutions

---

Other Sources

• CRMCOE (2021) : Salesforce Test Automation (1 hour video)

---

Testing in Trailhead

Trailhead

• Flow Testing: Step-by-Step

  • https://trailhead.salesforce.com/content/learn/modules/flow-testing-and-distribution

  • 15 mins = 100 points = woohoo!

Trail: Explore Software testing

• https://trailhead.salesforce.com/content/learn/trails/explore-software-testing

Module: Overcome Testing Challenges with Automation

• https://trailhead.salesforce.com/content/learn/modules/salesforce-app-testing-with-provar/overcome-testing-challenges-with-automation

Testing Challenges:

1. Challenge #1: Complex DOM Structure

2. Challenge #2: Internal Framework Changes

3. Challenge #3: Objects Behind Shadow DOM

4. Challenge #4: 3x Releases Every Year

---

Module: Build Processes and Unit Tests for Salesforce B2C Commerce Technical Architects

• https://trailhead.salesforce.com/content/learn/modules/b2c-build-processes-and-tests-for-technical-architects

• SFRA Testing Technologies

  • https://developer.salesforce.com/docs/commerce/sfra/guide/b2c-testing-sfra.html

  • Supported testing technologies include these kinds of tests:

    • Controllers are tested with integration tests. Salesforce B2C Commerce uses mocha, chai, and request-promise for integration testing.

    • Models are tested with unit tests. B2C Commerce uses mocha, chai, sinon, and proxyquire for unit tests.

    • Views are tested with functional tests. B2C Commerce uses mocha, chai, and webdriver.io for functional tests.

---

Test Automation in Production

• Probably it's not a good idea to create test records in Production.

• "Observation only" tests might be OK:

  • like "check that latest Currency Exchange Rates were updated in Salesforce"

• There are security concerns.

---

Deleting test records

• tagging test records makes it easier

  • not to mix them with production records

  • to delete test records

// ONLY IN SANDBOX / DEV ORG / TRAILHEAD HANDS-ON PLAYGROUND
List<Opportunity> oppoList = [SELECT Id FROM Opportunity WHERE Account.Name LIKE '!TEST%'];
delete oppoList;

List<Contact> contList = [SELECT Id FROM Contact WHERE Account.Name LIKE '!TEST%'];
delete contList;

List<Account> acctList = [SELECT Id FROM Account WHERE Name LIKE '!TEST%'];
delete acctList;

---

NO-CODE UI TESTING: Guide for testRigor & Salesforce