Managing changes with Salesforce or across the enterprise often requires tight turnarounds — and in some cases must be done within hours. In these situations, testing the changes and their impact on business processes is critical and must be completed faster because update and upgrade schedules can’t be controlled. Automated testing can make balancing quality control and rapid completion much easier. In this technical webinar, you will learn: - Why automated testing is essential - How automated and manual testing work together - The ways automated testing leads to higher quality products. - How to maintain and scale testing processes over time Watch today to learn how automated testing can take your enterprise solutions to the next level.

2. ● Who is CodeScience?
● Introductions
● Why test automation is important
● Recommendations
● Patterns and processes
● Testing activities streamlined
● Recap
Agenda

3. Who is CodeScience?
● Founding partner of the Salesforce Product
Development Organization (PDO) Program
since 2008 - named Master PDO in 2017
● We build Salesforce AppExchange solutions
for our clients.

4. Client success: 10% of the AppExchange

5. CodeScience client focus:

6. Today’s Speakers:
Pat Meeker
Quality Lead
Radhika Manne
Quality Lead

7. Overview

8. Big Picture
● Apps built on Salesforce will have faster build schedules
● The same features need to be tested in multiple environments
● Testing and quality are continually evaluated and promoted as part of
the process from the very beginning
● Better quality product for two main reasons
○ Manual testing team can spend time in exploratory testing which
can result in finding new bugs
○ Preparedness for P0/hot fixes

9. Deliver Test automation Continually

10. Tips and Tricks

11. Recommendations
● Automate the test cases that are
repetitive and monotonous
○ Smoke Tests
○ Regression Tests
○ End- End Tests
○ Multi-Browser Tests
● Build tests that are independent of
each other
● Hook up tests to CI/CD process
● Create Test data
● Sanity check is complete on a feature
before building automated test cases
● Have a seperate Environment to
execute automated tests

12. Processes and Patterns
● Org authentication can have implications for your CI approach.
○ Will your CI use a cloud service like CircleCI?
○ Will your tests auth via SFDX JWT?
○ Will you be scripting the creation of scratch orgs?
● Abstraction is the single best thing you can do for maintainability.
○ Fix it in one place
● “Make it work, make it right, make it fast”
○ For test results which are timely

13. Streamlined Testing Activities

14. Current Challenges with Manual testing
● Time: Comprehensive tests take days depending on the size of the
test suite and complexity of tests. Time is the constraint
● Coverage: Sometimes testers may opt for priority based testing
● Repetitiveness: Repetitive smoke tests and regression tests
● User configurations: Supporting multiple versions of multiple
browsers, on multiple platforms and devices
● Speed: Test automation increases speed in the product delivery
process

15. Address Challenges with Test Automation
● Time: Automated test can perform test steps faster than a human
● Coverage: When time is limited for a given test run, automated tests can
cover more than human
● Repetitiveness: Humans gain little value from running the same test
again
● User configurations: Manual testers may limit testing scope by
browser/configuration when time is limited
● Speed: completing regression sooner, can mean sign off sooner,
packaging sooner, starting next sprint sooner, etc

16. Recap
● Why automated testing is essential
● How automated and manual testing work together
● The ways automated testing leads to higher quality products
● How to maintain and scale testing processes over time

17. Contact Us:
Thank You
info@codescience.com