---
title: "Selenium | Skills We Assign For | Azendo"
description: "Selenium and WebDriver — where the standard still wins, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/selenium/"
---

[Skills](https://azendo.co/skills/) QA and delivery tooling 

# Selenium.

Selenium is the long-established browser automation framework and the basis of the W3C WebDriver standard. It drives real browsers through the same protocol every major browser implements, with bindings for Java, Python, C#, JavaScript and Ruby.

## Where Selenium fits on a long engagement.

Selenium's durable advantage is that it is a standard rather than a product. WebDriver is implemented by the browser vendors themselves, bindings exist for every significant language, and a suite written against it is not dependent on one company continuing to maintain a tool. On an estate expected to run for a decade that is a real consideration.

The trade-off is that it gives you less. No auto-waiting, so synchronisation is the test author's responsibility and badly written waits are the leading cause of flaky Selenium suites. No built-in tracing, so a CI failure has to be reproduced to be understood. Modern frameworks removed these problems; Selenium expects you to solve them.

## What an assigned team does with Selenium.

Most Selenium estates we inherit are large, slow and partially trusted, with a set of tests everyone knows to ignore. The productive first step is establishing which tests are meaningful rather than migrating the whole suite to something newer.

That assessment is test-strategy work rather than automation work, and it is where an assignment should start. How scope is agreed before anything is rewritten is described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use Selenium for.

* Maintaining a large existing suite Stabilising what is there and retiring what is not trusted, before considering a migration.
* Language flexibility across teams Tests in the same language as the application, which is what keeps them maintained.
* Grid execution across environments Distributed runs across browser and OS combinations, including hardware a cloud service does not offer.

## How Selenium capacity is assigned.

Selenium capacity is assigned under [outsource qa testing](https://azendo.co/services/qa-engineering-and-test-automation/), starting from an assessment of which tests carry signal rather than from a rewrite.

## Roles we assign Selenium for

* [Test Automation Engineer QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/test-automation-engineer/)

## Service lines it sits in

* [QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in qa and delivery tooling

* [TestRail — skill we assign for](https://azendo.co/skills/testrail/)
* [Jest — skill we assign for](https://azendo.co/skills/jest/)
* [React Testing Library — skill we assign for](https://azendo.co/skills/react-testing-library/)
* [XCTest — skill we assign for](https://azendo.co/skills/xctest/)
* [Espresso — skill we assign for](https://azendo.co/skills/espresso/)
* [Detox — skill we assign for](https://azendo.co/skills/detox/)
* [Flutter Test — skill we assign for](https://azendo.co/skills/flutter-test/)
* [Playwright — skill we assign for](https://azendo.co/skills/playwright/)

## Tell us what your roadmap needs Selenium for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)