Testing Salesforce Apps presents numerous challenges for enterprise organizations. Teams have to navigate complex architecture, integration workflows, and continuous changes in the customized SFDC implementation, as well as a wide range of different applications hosted on Salesforce Cloud. If left unchecked, these challenges can hamper critical enterprise processes like the revenue-generating Quote to Cash process.
During this webinar, you will learn how to automate functional testing and thoroughly test both the UIs and the APIs in your Salesforce applications using AutonomIQ’s AI-driven codeless tool. We’ll discuss how Aryaka Networks, a global leader in WAN transformation solutions, uses AutonomIQ to autonomously test critical business processes like Quote to Cash in their customized Salesforce application, and we’ll show you how to streamline UI testing to improve test creation, execution, and maintenance, and easily add API testing to your strategy for better coverage.
Key Takeaways:
Simplify the creation of your test scripts using plain English statements and a codeless studio
Learn how to autonomously create UI and API tests for Salesforce and integrations with other applications
Ensure the health of your end-to-end SFDC applications for key business processes like quote to cash
Simplify Salesforce Testing with AI-Driven Codeless Tools
1. Simplify Salesforce Testing with
AI-Driven Codeless platform
Venkat Ranga, Head of Business Technology,
Aryaka Networks
Raj Rao, Co-founder AutonomIQ,
a Sauce Labs company
May 12th
2021
2. 1 Introductions
2 QA Automation within Business Technology domain
3 SalesForce automation from AutonomIQ, Sauce Labs solution
4 Q&A
Webinar AGENDA
4. What Business Technology do? (CIO Organization)
Strategic
Work with business leaders
and develop a business
strategic initiatives
Establish innovation center
to prototype new
technologies
Program Mgt
Establish PMO cadence
and execute strategic
Initiatives through PMO
Establish Process
governance
Develop standards around
budget planning and report
project status on regular
basis
Process Optimization
Develop process around
• Lead to Quote
• Quote to Cash
• Issue to Resolution
• Procure to Pay
• Record to Report
• Hire to Retire
Process governance
Operational
Keep business running by
ensuring the necessary
business systems are up
and running
Continue to looks for ways
to automate to reduce the
TCO
5. Typical Business Technology - org structure
Head of Business Technology
Strategy: Become a right hand to the
business and drive business initiatives
by
● Establishing Program Management
Office
● Deliver results
● Operational efficiency
Web, Middle-Ware,
Integrations
1. eCommerce
2. EDI, Real-time and Batch
integrations
3. Payment Processor
4. Others
Back-End Business
Technology
1. Hire to Retire
2. Procure to Pay
3. Record to Report
4. Planning
Front-End Business
Technology
1. Lead to Order
2. Order to Cash
3. Issue to Resolution
Business
Intelligence
1. Key Performance Metrics
for Finance, Sales,
Marketing and Others
Each team consists of a Manager, PM/BA, Dev and QA resources; number may vary based on organization size
PMO
6. Typical Business Technology - org structure cont..
Head of Infrastructure
Strategy: Establish infrastructure that
runs the business
● Connectivity
● Protect and Assist
● Operational efficiency
Systems
1. Infrastructure (Servers)
2. Virtualization
3. Cloud/Storage
Desktop Computing
1. Desktop Management
2. Service Desk
3. Corporate Access Mgt
Security
1. Security (Physical and
Systems)
2. Compliance/Regulations
3. Governance
1. Corporate LAN and
Wireless network
Network
Infrastructure
7. Typical Project Budgeting
Business Analysts &
Program Management
~30% Resources
1. Predominantly work on
collecting the
requirements by working
closely with business
2. Execute the project
Development
~40% Resources
1. Architecture
2. Development
3. Unit Testing
QA
~30% Resources
Functional Testing
• System Testing
• Integration Testing
Non-Functional Testing
• Performance Testing
• Usability Testing
• Security Testing
With Business
• User Acceptance Testing
Before Release
• Regression Testing
After Release
• Smoke Testing
Post
Production
KTLO - Team
1. Resolve New capability
operational issues
2. Report back
Bugs/Enhancements to
Dev team
Challenges
• 8 End to End scenarios, 250+ test cases
and growing
• QA takes considerable amount of time
within sprint 🡪 Reduces the throughput
• Not sufficient time to conduct regression
testing
10. QA Automation Benefits
● Reduced overall testing effort down to half
● Reduced 2 days of regression testing to half a day for every sprint 🡪 Reduced TCO
● Added more user stories to sprint 🡪 Increased business value
● Expanded QA team responsibility to take up BA role (career progression)
12. CONFIDENTIAL
Salesforce Testing Challenges
SFDC
Testing is
challenging
Breadth &
Depth of
SFDC
products
Dynamic
application
Supports
key
business
processes
Citizen
testers
Frequent
Changes
● SalesForce testing and test automation is highly
complex due to:
○ Breadth and depth of SalesForce Products and
solutions
○ SalesForce being critical to key business
processes for an enterprise like Quote to Cash
○ Frequent and constant stream of changes
requiring constant testing
○ Citizen testers who are not skilled in testing and
test automation; and don’t know how to use
traditional test automation tools
○ Dynamic application with highly complex
technologies like classic, lightning, lightning web
components and shadow Dom capabilities
13. Opportunities to Improve Efficiency and Profitability
13
Designed for Testers Specifically
Traditional approaches have
many challenges:
Specialist: They are designed for a
test specialist, an automation expert,
someone who knows how to code
Effort: It takes too long to create
automation, because it has to be
created manually by skilled
resources
Maintenance: Maintaining the
scripts falls on testers. It takes 30%
to 40% of original effort to maintain
the scripts
Test Creation
Object Changes
Business Logic
Changes
TRADITIONAL APPROACHES
User Creates test data
User Translates That To Code
User Writes Manual Test Case
Test Executes
Test Breaks
User Looks For Change
User Identifies New Xpath
User Updates Code
Test Breaks
User Updates All Business Logic
User Writes New Code
~5-8 Hrs/script
~1 Hr/script
2-3 Hrs/script
CHANGE
-
MAINTAIN
CREATE
14. CONFIDENTIAL
Autonomous Platform for SaaS & Digital Apps
14
NLP Engine
Machine Vision
GANs / Grammars
Scenarios
Automation
Code
Synthetic
Data
Open Source
(Selenium, Python,
Robot Framework)
Sauce Labs
01
Ingest Any Application
02
Understand Intent
03
Generate, Maintain &
Repair Automation
04
Orchestrate Execution
Behavior Trees
AutonomIQ Platform
15. CONFIDENTIAL
AutonomIQ solves SalesForce automation challenges
Pain Point Solution
Breadth and depth of Salesforce One platform to address all Salesforce testing needs
Dynamic application: constantly changing object locators AutonomIQ handles dynamic application behavior
through auto-healing. This means a significant
reduction in maintenance efforts.
Supports key business processes AutonomIQ supports key business processes by
providing an end-to-end testing capability.
Citizen testers with not much testing specialization AutonomiQ is designed to handle test intent in simple
English or through recording. This allows anyone
including citizen testers to automate tests.
Frequent changes: constant stream of changes AutonomIQ is integrated with SalesForce CI/CD
frameworks, which allows to react to frequent stream of
changes.