Apex Testing Deep Dive

#SalesforceApexHourswww.ApexHours.com
Salesforce Apex Hours
Farmington Hill Salesforce Developer Group
Apex Testing Deep Dive
#SalesforceApexHours
#SalesforceApexHours
Speaker
Date
Venue/Link
Adam Olshansky
Saturday, JUN 6, 2020 10:00 AM EST ( 8:30 PM IST )
Online
www.apexhours.com

Who I am
Amit Chaudhary (Salesforce MVP)
• Active on Salesforce Developer Community
• Blogging at http://amitsalesforce.blogspot.in/
• Co-Organizer of – FarmingtonHillsSFDCDug
• Founder of www.ApexHours.com
• Follow us @Amit_SFDC or @ApexHours

Our Speaker
Adam Olshansky
• Salesforce MVP, Salesforce Engineer,
630 14X
• @adam17amo
• AdamToArchitect.com
• bit.ly/lightningmigration

Agenda
• Intro to Testing
• Testing Basics
• Types of Tests
• Test Apex Class/Async
• Testing Callouts
• Debugging Failed Tests
• Recap

Intro to Testing

Why Test?
• Ensure code is working
• 75% Code Coverage Required for Production
• Catch bugs early
• Prevent Regression

Structure of a Test
• Create Test Data
• Run Code
• Assert Results

How to Create Test Data
• Manually create it for each test
• Load data via CSV Static Resource
• Test Setup
• Test Factory

Code: Intro to Testing

Manually Create

Load Via CSV

Test Setup

DEMO: Test Factory
• What happens to all our tests when a new field is required?
• How many places do we have to make updates?

Test Factory

Test Setup with Test Factory

How to Create Test Data
• Manually create it for each test
• Pro: Variables in context
• Con: Lots of duplicate code
• Load data via CSV Static Resource
• Pro: Don’t need to make code updates for record creation
• Con: Might be harder to track changes to static resources
• Test Setup
• Pro: Reduce repetitive code
• Con: Variables out of context
• Test Factory
• Pro: Single location to update schema in code
• Con: Variables out of context

Testing Basics

Asserts in Tests
• Confirm that code works as you expect it to
• System.assert(condition, msg)
• System.assertEquals(expected, actual, msg)
• System.assertNotEquals(expected, actual, msg)
• What controls whether or not your tests pass

Code Coverage
• Controls whether code can go to production
• Calculated by tests running through your code
• Triggers automatically fired
• Classes and methods called manually or via code

Tips to Increase Test Coverage
• @TestVisible
• Test.isRunningTest()
• Test Driven Development (TDD)

Bad Habits for Tests
DON’T DO THIS
• No asserts in your tests
• Asserts that don’t cover the part that
was tested
• Fake code in your classes

Test Suites
• Collection of tests
• Useful to cover entire application
• Help unrelated prevent regressions

Different Types of Testing
• Unit Tests
• End to End Tests
• Integration Tests
• User Acceptance Tests

DEMO: Asserts and Coverage

Types of Tests

Positive vs. Negative Tests
• Positive
• Confirm expected cases
• Test code works when users
behave as expected
• Negative
• Test unexpected cases
• Test bad inputs
• Test boundary conditions

System.runAs()
• Code needs to be tested as different users
• Create/find a user and test on their behalf
• Only applies to sharing, not FLS
• Useful for avoiding Mixed DML errors
• Useful for testing a specific version of managed package

DEMO: Test Types and System.RunAs

Code

Test Apex Class

Avoiding Limits in Tests
• Test.startTest() and Test.stopTest()
• Bulkifying record creation
• Creating records without DML
• Split up tests by use case

Asynchronous Testing
• @future
• Batchable
• Queueable
• Schedulable
• Will only schedule but won’t run the job
• Runs on Test.stopTest()
• Verify it properly ran
• Verify results

Other Test Class Uses
• Test.setCreatedDate()
• Test.setCurrentPage()

DEMO: Test Class

CaseReassignmentBatch
• Take all cases owned by the Temp Queue
• Assign them to specified user

Testing Callouts

Mock Tests
• Can’t make callouts in Apex tests
• Mock responses
• Test.setMock()

Generating Mock Data
• Model after actual API responses
• Test for multiple response codes
• 200
• 403
• 500
• Create map to hold multiple responses

DEMO: Mock Testing
• Custom Object: Purchase Order
• External System to sync data back to Salesforce based on external Id
• Need to handle different responses from API

Different Ways to Mock
• Constructor
• Static Resource
• Map

Debugging Tests

Debug Failing Tests
• Sanity check data after @testSetup
• Compare before/after values rather than hardcoding
• Include try/catches
• System.debug is your friend

Apex Replay Debugger
• Set unlimited breakpoints
• Set up to 5 checkpoints
• Replay your failed tests step by step and find errors

DEMO: Debugging Testing

Recap

Summary
• Why We Test
• Types of Tests
• “Test” Class and Async Testing
• Mock Tests for Callouts
• Apex Replay Debugger

What’s Next?
• Lightning Component Tests
• force:lightning:lwc:test:create
• force:lightning:lwc:test:run
• force:lightning:lwc:test:setup

Follow us
#SalesforceApexHours @ApexHours
@adam17amo
www.ApexHours.com
https://trailblazercommunitygroups.com/farmington
-mi-developers-group/
Bit.ly/ApexHours
AdamToArchitect.com
Github.com/adam17amo/apextesting

Apex Testing Deep Dive

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Apex Testing Deep Dive

Ähnlich wie Apex Testing Deep Dive (20)

Mehr von Adam Olshansky

Mehr von Adam Olshansky (8)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Apex Testing Deep Dive

Hinweis der Redaktion