Need advice about which tool to choose?Ask the StackShare community!

Cucumber

762
715
+ 1
25
Selenium

11K
8.4K
+ 1
519
Add tool

Cucumber vs Selenium: What are the differences?

Developers describe Cucumber as "Simple, human collaboration". Cucumber is a tool that supports Behaviour-Driven Development (BDD) - a software development process that aims to enhance software quality and reduce maintenance costs. On the other hand, Selenium is detailed as "Web Browser Automation". 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.

Cucumber and Selenium are primarily classified as "Testing Frameworks" and "Browser Testing" tools respectively.

Cucumber and Selenium are both open source tools. Selenium with 14.9K GitHub stars and 4.97K forks on GitHub appears to be more popular than Cucumber with 2.54K GitHub stars and 501 GitHub forks.

According to the StackShare community, Selenium has a broader approval, being mentioned in 777 company stacks & 443 developers stacks; compared to Cucumber, which is listed in 58 company stacks and 39 developer stacks.

Advice on Cucumber and Selenium
Needs advice
on
WebdriverIOWebdriverIOSeleniumSelenium
and
JestJest
in

we are having one web application developed in Reacts.js. in the application, we have only 4 to 5 pages that we need to test. I am having experience in selenium with java. Please suggets which tool I should use. and why ............................ ............................ .............................

See more
Replies (1)
Prashanth Marappa
Senior Software Engineer at Mphasis · | 1 upvotes · 102.6K views
Recommends
SeleniumSelenium

with the help of selenium we can automate react js for functional testing

See more
Decisions about Cucumber and Selenium

We use Selenium for our FDA validation testing.

For those not familiar with FDA and NASA quality control initiatives and testing requirements, suffice it to say that the federal government tends to talk in terms of 'validation and verification testing' in many of its' regulations. There's decades of history behind this term, and the three important takeaways are the following:

First, a project has to have two or more testing strategies, so as not to fall into a bias with a single testing strategy. Second, one of those testing strategies has to be user-centric, commonly known as validation testing. Examples include crash test dummies and end-to-end software acceptance tests. Third, most any other testing strategy can qualify as verification testing.

So, we use Selenium for our FDA validation testing, because it simulates a user walking through the software.

It's big and bloated and slow, and the legacy version runs on Java, and it's brittle and doubles the amount of code we have to write, and is otherwise a total pain in the ass. But it's like folding your parachute before skydiving or having a depth gauge when SCUBA diving or placing bolts when climbing a wall. There are simply some tasks that you don't want to do without safety gear.

And for all its' pain to use, Selenium is like safety gear for building your tech stack. We've migrated across a half a dozen user interfaces, two entirely different back-end languages, three or four data protocols, and countless utilities over the years. And Selenium warns us when we're in danger and it catches us when we fall.

See more

As bioinformaticists, we regularly get asked to develop apps or websites which are HIPAA compliant, connect to an EHR, or are ready for FDA regulation.

Regarding the last, the FDA has built up best practices over the past 40 or 50 years regarding "validation and verification" testing. Without going into a lengthy history of FDA regulations, suffice it to say that there are two important distinctions about validation and verification testing - the first of which is that there has to be more than one testing methodology, so that manufacturers or developers don't get a sort of biased tunnel vision; and the second is that at least one of the testing methodologies has to be user-centric. So, it's not enough to test the engine of a car, a manufacturer also must have crash test dummies.

In the world of software written for hospitals and clinical environments, we interpret the verification and validation testing requirements in terms of requiring more than one testing framework, one of which is an end-to-end testing harness using a technology like Selenium. It's not enough to have unit testing, but we also need e2e acceptance testing. Selenium has traditionally been the only game in town, and has been a struggle to work with at times. But it's a tank, and keeps on rolling. We particularly like recent incarnations using Chromedriver and WebDriver protocols, which is slowly reducing the reliance on the legacy Java server.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Cucumber
Pros of Selenium
  • 18
    Simple Syntax
  • 3
    Simple usage
  • 2
    Nice report
  • 2
    Huge community
  • 169
    Automates browsers
  • 154
    Testing
  • 101
    Essential tool for running test automation
  • 24
    Record-Playback
  • 24
    Remote Control
  • 8
    Data crawling
  • 7
    Supports end to end testing
  • 6
    Functional testing
  • 6
    Easy set up
  • 4
    The Most flexible monitoring system
  • 3
    Easy to integrate with build tools
  • 3
    End to End Testing
  • 2
    Integration Tests
  • 2
    Comparing the performance selenium is faster than jasm
  • 2
    Record and playback
  • 2
    Compatible with Python
  • 2
    Easy to scale
  • 0
    Integrated into Selenium-Jupiter framework

Sign up to add or upvote prosMake informed product decisions

Cons of Cucumber
Cons of Selenium
    Be the first to leave a con
    • 7
      Flaky tests
    • 2
      Slow as needs to make browser (even with no gui)

    Sign up to add or upvote consMake informed product decisions

    What is 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.

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Cucumber?
    What companies use Selenium?
    See which teams inside your own company are using Cucumber or Selenium.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Cucumber?
    What tools integrate with Selenium?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Cucumber and Selenium?
    RSpec
    Behaviour Driven Development for Ruby. Making TDD Productive and Fun.
    TestNG
    It is a testing framework designed to simplify a broad range of testing needs, it covers all categories of tests: unit, functional, end-to-end, integration, etc.Run your tests in arbitrarily big thread pools with various policies available (all methods in their own thread, one thread per test class, etc.
    JUnit
    JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.
    Celery
    Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
    Mockito
    It is a mocking framework that tastes really good. It lets you write beautiful tests with a clean & simple API. It doesn’t give you hangover because the tests are very readable and they produce clean verification errors.
    See all alternatives