Skip to main content

Automation testing implementation for Salesforce Field Service Project

Successful automation testing implementation on the ongoing Salesforce Field Service project for order and billing processes

Published by jetbi
24 November 2022

Project description 

Client, a company providing home repair services for individual and corporate customers across London (UK), has implemented the Salesforce Field Service solution. To save time on some trivial scenarios for the smoke testing it was decided to automate some of them.

 

Goals 

  • Save time on testing efforts and improve its efficiency;
  • Have daily system health reporting;
  • Quickly check the system after deployments and Salesforce releases

 

Tasks

  • Identify the same type of test scenarios that spend the most time of QA per year;
  • Write automation tests;
  • Optimize the hardware;
  • Run tests daily

 

JET BI services performed

  • Implemented 14 Android automation tests using mobile device emulators;
  • Developed 46 Customer Community web automation tests to test the most popular scenario of order booking;
  • Corrected tests for upgraded Customer Community UI;
  • Configured scheduler for a daily test run;
  • Created reports to be sent to the customer and team members at the end of the test run;
  • Configured hardware, and installed all necessary software;
  • Configured CI process;
  • Ongoing maintenance and support services.

automation-testing-iplementation-1

Picture 1: Test Result Report

 

automation-testing-iplementation-2

Picture 2: Running of Android automation test using an emulator

 

Results:

  • The time spent on testing iteration has been reduced by 50%;
  • Over 10 defects were found during automation testing iterations before the defect caused production downtime;
  • Continuous quality reports are available for the customer and team daily without manual testing iterations.

 

Start your project now
JET BI TEAM
  • 1 Automation testing QA Engineer
  • 2 QA Engineers
  • 1 Salesforce Consultant/PM
TECHNOLOGIES
  • Java
PROJECT TIMELINE
  • 6 months
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026