The LEAP

Automation insights and productivity tips from LEAPWORK.

All Posts

Test Automation Tool for Salesforce: Selenium vs. LEAPWORK Comparison

When looking for a way to test Salesforce integrations and connections you will probably come across quite a few options.

The most popular starting point for many is Selenium. Many select Selenium because it is free and readily available, and perhaps also because Salesforce use Selenium to test their own software.

If you too are considering using Selenium to test Salesforce, or if you’ve already chosen Selenium but you’ve subsequently found that it doesn’t meet your needs, you’ve come to the right place.

Below is a complete overview of what you can expect from Selenium in terms of usability, adoption, documentation, governance, test execution and integrations.

Use the Selenium column to see what Selenium can and cannot do, and compare it to the LEAPWORK column to find out if a no-code platform might be a better solution for you.

Read on or download the comparison as a PDF.

New call-to-action

Usability and Adoption

 

Using Selenium WebDriver with hand-written code

Using LEAPWORK, which uses Selenium under the hood

Programming needed

Can only be used by programmers, who get low-level access to browser behavior and actions through using any programming language (C#, Java, Python, PHP, etc).

Can do the exact same thing with easy-to-use building blocks, and without having to read or write a single line of code. Perfect for non-technical users – or anyone who just doesn’t want to spend time on programming.

Enterprise support

No enterprise support exists, the Selenium project is run by the open source community.

On-demand live support from automation specialists.

Data-driven automation

Data-driven automation requires sophisticated programming and separate management and storage of data assets.

Data-driven automation is included out of the box. It is done by visually connecting data sources such as databases, API endpoints and Excel files with other building blocks.

Finding web elements

Uses highly complex CSS or XPath “selectors”, which require deep technical knowledge.

Point and click to capture any web element. Smart algorithms then automatically find the best way to locate it again in the future.

Road-map influence

Although Selenium is open source, the only way to influence the road map is to actively participate in the community programming effort for Selenium itself.

All enterprise users have direct access to live chat and product team representatives. About a third of all product development is a result of this dialogue.

Training materials

A good ecosystem and lots of code samples exist on the internet for professional programmers to use. Some tutorials on YouTube and many professional courses exist but require technical skills.

All users have access to a comprehensive learning center with many hours of free videos. Enterprise users can participate in a professional certification program.

Speed of adoption

Typically takes 3-6 months for an initial project, then another 6-12 months for framework programming.

Most users are able to adopt within 3-5 days, using a structured learning and on-boarding program.

Documentation and Governance

 

Selenium WebDriver

LEAPWORK

Reporting and dashboards

No reporting or dashboard solution is included. Programmers can custom-build their own reporting framework (typically takes 3-6 months).

Reporting and dashboards are included out of the box. Results can also be pushed to other tools such as JIRA.

Automatic video recording

Video recording is not included and is very difficult to achieve, even with a custom-built solution. Programmers are typically limited to saving screenshots with no retention policy.

Everything is automatically recorded on video, and a retention policy can ensure old videos are automatically deleted.

Object repository and version history

An object repository is not included, but programmers can custom-build their own and decide on implementing code patterns such as Page Object Model. Version history can be achieved using source control systems such as Git, which most non-technical users find impossible to navigate.

All assets such as web element locators and flows are structured and stored in an encrypted database with built-in version history.

Access control

No access control is included and is difficult to achieve with a custom-built solution.

Access control, both locally in the encrypted database and through Active Directory is included.

Tamper-proof audit trails

No audit trail capability is included and is difficult to achieve with a custom-built solution.

All data is stored in an encrypted database with no direct access. Even administrators cannot change the audit log.

Test Execution and Integrations

 

Selenium WebDriver

LEAPWORK

Scheduling

 

 

No scheduler is included. Programmers can use a unit-test framework in combination with a custom-built scheduler or build pipeline.

Scheduling and ad-hoc running is included out of the box. Flows can also be triggered from a build pipeline or other third-party system.

Parallelization

Can run in distributed, parallel environments, but requires programmers to build a custom automation framework (typically takes 6-9 months).

Can run in distributed, parallel environments out of the box, including on BrowserStack, Sauce Labs and Selenium Grid as well as on LEAPWORK agents, where web, desktop and virtual applications can be automated together.

Built-in REST API

No REST API is included, but the WebDriver wire protocol is open source, and custom-built REST APIs can be made by programmers.

A full-fledged REST API is included out of the box, making it easy for DevOps to integrate with any third-party system.

Built-in CI/CD plugins

Any CI/CD platforms can be used by custom-built solutions. A good ecosystem and lots of code samples exist on the internet for professional programmers to use.

All popular CI/CD platforms can easily be integrated by DevOps using plugins or the REST API.

 

New call-to-action

Maria Homann
Maria Homann
Content Marketing Manager

Related Posts

Why Choose a No-code Automation Tool for Regression Testing?

Two of the major challenges in automating regression tests are setup and maintenance. This is because many test automation tools require coding, which requires time and capabilities that not all testing teams have.

How Frequently Should You Run Your Regression Tests?

Deciding how often to perform regression tests can be a challenge. Particularly when you've automated your regression suite, and are more free to decide the frequency.

Building Automated Regression Tests: What to Include

Over time, as your application grows or changes, your regression test suite will grow as well, numbering into perhaps hundreds or thousands of regression test cases. This is why automation will inevitably become part of your testing process at some point.