What is Provar? Salesforce test automation explained, and when it fits

What is Provar? Salesforce test automation explained, and when it fits

In short: Provar is a test automation tool built for Salesforce. It reads your org’s own setup, so tests point at Salesforce fields and objects instead of at the page code. That makes tests less fragile when Salesforce changes its screens. It fits best when Salesforce is core to your business and changes often. You still need to plan for test upkeep.

Salesforce changes three times a year, and your own team changes it every sprint. Each change can break a flow that worked yesterday. Testing that by hand every release takes days, so most teams look at automation sooner or later. Provar is often the first name they hear. We’re a Provar partner and use it every week, so we’ll be open about that. We’ll also say where it fits less well.

What is Provar?

Provar is a commercial test automation tool made for Salesforce. You use it to build automated tests for the work people do in Salesforce. Think of creating a lead, converting it, or closing a case. The main difference with general tools is how Provar finds things on the screen. A general tool looks at the page code to find a button or a field. Provar uses the metadata of your org. Metadata is the description of how your Salesforce is set up: which objects, fields, page layouts and rules exist. So a Provar test says “fill in the field Amount on the Opportunity”, not “click the third box in this part of the page”. When Salesforce changes the look of a screen, the field is still the same field. Testers can build most tests without writing code, and the tests can run in a CI/CD pipeline. Provar Manager adds test management and reporting on top.

Provar helps you automate tests, but it doesn’t choose them for you. You still decide which flows matter, what data the tests need and who keeps them working.

How is Provar different from Selenium or Playwright?

General tools such as Selenium and Playwright see a web page. Provar knows it is looking at Salesforce. That matters, because Salesforce pages are built in a way that makes it hard for general tools to find fields and buttons reliably. With a general tool, your team writes and maintains that extra layer itself. The table sums up the main differences.

Provar Selenium or Playwright
Built for Salesforce. Any web application.
How tests find fields From Salesforce metadata. From the page code.
Coding Mostly low-code. Code, written by engineers.
Cost Licence fees. Free and open source.
Best for Orgs where Salesforce is core. Wide landscapes with many apps.

If you are still choosing between the two general tools, our comparison of Playwright vs Selenium helps.

What should you plan for when you test Salesforce with Provar?

Plan for upkeep, timing and reporting. A good tool makes tests sturdier, but it can’t stop your org from changing. What we see in Salesforce projects is that small changes do the most damage. Renaming a field or tweaking a validation rule can make flows and test scripts fail further down the line. Our post on why Salesforce tests break after small changes goes into that. Three more things are worth planning for with any UI test tool, Provar included.

  • Screen changes still need test updates. Lightning updates or a changed page structure can mean a test has to be adjusted. Metadata helps a lot, but test maintenance stays real work.
  • Integrations bring timing problems. Links to marketing automation or product data systems can be slow or limited in how many calls they accept. Tests then fail now and then, and those failures are hard to repeat.
  • Results need translating. A test report shows passes and fails. A product owner wants to know if the release is safe. Plan time to turn one into the other.

Seasonal releases add a fixed rhythm on top. Salesforce lets you try each release in a sandbox, a test copy of your org, weeks before it reaches production. Our post on Salesforce release testing explains how to use that window.

When does Provar fit, and when doesn’t it?

Provar fits best when Salesforce is a core system, your org has a lot of custom setup, and changes go live often. In that case the tests you save from breaking pay back the licence. It also fits teams where testers know the business well but aren’t all programmers. We saw that at a lease company where our tester was the only tester on a Salesforce Service Cloud project from the start. Our tester introduced Provar there, and the company later used it on other Salesforce projects. You can read the Lease Company case on our site.

Provar fits less well when Salesforce is a small part of a wider landscape. If your key customer journey runs through a webshop, an app and three other systems, a general tool may already cover it end to end. Adding a second tool for one step is not always worth it. A small org with few changes may not need heavy automation at all. Because we’re independent, we’ll say so when another tool fits your org better. And no tool replaces people. Acceptance testing by business users stays essential, especially after a big change to how they work.

What this means for your team

Choosing a tool is the easy part. Keeping the tests running through three Salesforce releases a year and your own changes every sprint is the work. Someone has to update tests after each change, chase the ones that fail on timing and report results in a way the business understands. In many Salesforce teams that lands on an admin or a tester who already has a full week.

That is the work our Salesforce testing team does alongside yours. We run your Salesforce regression tests every release, automated with Provar, and keep them running. They’re ready for every seasonal release, and your team stays in control of what ships.

A first step you can take this week: list the five Salesforce flows your business can’t do without. Then note which of them you still test by hand before each release.

Salesforce regression tests that keep up with every release.

Salesforce testingTalk to our team

Frequently asked questions

Is Provar only for Salesforce?

Provar is built for Salesforce, and that is where it is strongest. Tests can also take steps outside Salesforce, but for applications without Salesforce a general tool is usually the better fit.

Do you need to code to use Provar?

Not for most tests. Testers build them in a low-code way. Some complex cases still need a developer, and a good test design matters more than coding skills.

Can Provar run in a CI/CD pipeline?

Yes. Provar tests can run from common CI/CD tools, so they run automatically after a change or every night.

Is Provar free?

No, Provar is a commercial tool with licence fees. Compare that with the time your team would spend building and maintaining tests with a free tool.