5.5K
4.1K
+ 1
461

What is Selenium?

Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
Selenium is a tool in the Browser Testing category of a tech stack.
Selenium is an open source tool with 17.3K GitHub stars and 5.6K GitHub forks. Here’s a link to Selenium's open source repository on GitHub

Who uses Selenium?

Companies
1129 companies reportedly use Selenium in their tech stacks, including N26, Typeform, and MIT.

Developers
4270 developers on StackShare have stated that they use Selenium.

Selenium Integrations

BrowserStack, Sauce Labs, Nightwatchjs, WebdriverIO, and Targetprocess are some of the popular tools that integrate with Selenium. Here's a list of all 23 tools that integrate with Selenium.

Why developers like Selenium?

Here’s a list of reasons why companies and developers use Selenium
Private Decisions at about Selenium
Private to your company

Here are some stack decisions, common use cases and reviews by members of with Selenium in their tech stack.

Selenium
Selenium

Web UI testing Selenium

See more
Tim De Lange
Tim De Lange
at Multimobile · | 1 upvotes · 0 views
Selenium
Selenium

Testing apps before release. Selenium

See more
Kane Blueriver
Kane Blueriver
Selenium
Selenium

Using Selenium in Django tests to automate browser test. Selenium

See more
Selenium
Selenium

Used Selenium web-driver for automated QA testing in continuous integration and continuous deployment. Selenium

See more
Praveen Pavithran
Praveen Pavithran
CTO at Yatis Telematics · | 1 upvotes · 0 views
Selenium
Selenium

Selenium was used for web scraping. Selenium

See more
Selenium
Selenium

가장 강력한 웹 UI / UX 테스트 툴 이지만, 문제도 많다. iframe 안에 있는 건 잘 select 가 안되기도 하고, 화면이 작아 컴포넌트가 화면에 보이지 않으면 또 select 할 수 없다. 하지만 브라우저를 있는 그대로 제어 할 수 있다는 게 가장 큰 매력이다.

ps. selenide 와 같이 쓰면 코드가 많이 개선된다. Selenium

See more
Public Decisions about Selenium

Here are some stack decisions, common use cases and reviews by companies and developers who chose Selenium in their tech stack.

Kamil Kowalski
Kamil Kowalski
Engineering Manager at Fresha · | 26 upvotes · 212.5K views
atFresha EngineeringFresha Engineering
Selenium
Selenium
Java
Java
Ruby
Ruby
Elixir
Elixir
JavaScript
JavaScript
Cypress
Cypress

When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Benjamin Poon
Benjamin Poon
QA Manager - Engineering at HBC Digital · | 8 upvotes · 222.9K views
Nightwatchjs
Nightwatchjs
Selenium
Selenium
JavaScript
JavaScript
Cucumber
Cucumber
GitHub
GitHub
GoCD
GoCD
Docker
Docker
ExpressJS
ExpressJS
React
React
PostgreSQL
PostgreSQL

For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

See more
Simon Bettison
Simon Bettison
Managing Director at Bettison.org Limited · | 7 upvotes · 215.2K views
atBettison.org LimitedBettison.org Limited
PostgreSQL
PostgreSQL
Elasticsearch
Elasticsearch
Sidekiq
Sidekiq
Redis
Redis
Amazon ElastiCache
Amazon ElastiCache
Rails
Rails
RSpec
RSpec
Selenium
Selenium
Travis CI
Travis CI
Ruby
Ruby
Unicorn
Unicorn
nginx
nginx
Amazon CloudFront
Amazon CloudFront
Amazon SES
Amazon SES
Amazon SQS
Amazon SQS
Amazon Route 53
Amazon Route 53
Amazon VPC
Amazon VPC
Docker
Docker
Amazon EC2 Container Service
Amazon EC2 Container Service

In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

See more
Kevin Roulleau
Kevin Roulleau
QA Engineer Freelance at happn · | 5 upvotes · 66.1K views
athappnhappn
WebdriverIO
WebdriverIO
Appium
Appium
Selenium
Selenium

I chose WebdriverIO and Appium to implement a E2E tests solution on a native mobile app. WebdriverIO goes well beyond just implementing the Selenium / Appium protocol and allows to run tests in parallel out of the box. Appium has the big advantage of supporting iOS and Android platforms, so the test codebase and tools are exactly the same, which greatly reduces the learning curve and implementation time.

See more
Iakov Markov
Iakov Markov
Cloud Solutions Product Owner at Ataccama · | 1 upvotes · 15.2K views
atAtaccamaAtaccama
Selenium
Selenium

Selenium is a great way to automatically test if a build is sane and can be deployed. Selenium

See more
Owen Miller
Owen Miller
Senior Software Engineer at Narrativ · | 1 upvotes · 8.5K views
Selenium
Selenium
  • Navigating our site for tests
  • Navigating other sites that discriminate against non-human visitors Selenium
See more

Selenium Alternatives & Comparisons

What are some alternatives to Selenium?
Protractor
Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
Cypress
Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.
Nightwatchjs
Nightwatch.js is an easy to use Node.js based End-to-End (E2E) testing solution for browser based apps and websites. It uses the powerful Selenium WebDriver API to perform commands and assertions on DOM elements.
Puppeteer
Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.
Cucumber
Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs.
See all alternatives

Selenium's Followers
4113 developers follow Selenium to keep up with related blogs and decisions.
Avinash Nirmal
meyian
sadak ali khan
José Nuno Ferreira
Flo Tek
Ray Shi
anjali kondapalli
Andrei Popa
서 기
Zhicheng Wang