Never Print Magazines


    1.2.64 • Public • Published

    Cucumber Test

    Sauce Test Status -

    Made easy - Cucumber testing using, instead of writing complicated test code that only developers can understand, Cucumber maps an ordinary language to code and allows to start with the test process in the early stages of your product development. cucumber-test is a fork of cucumber-boilerplate.

    Quick start

    Sample code are inside example folder example/quickstart

    1. npm install -g cucumber-test
    2. ccct -g -c        // ccct for creating automation test in current folder
    3. cct -f google -d  // cct for running automation script(s)

    Example below is a runnable Cucumber-test script under folder features. other features that worth to checkout is a fits folder, please read section Fits (Feature in tight scenario).

    # features/google/google.feature
        Search on Google
    Scenario: Navigate to Google
        Given I open the url ""
         Then I expect that the title is "Google"
    Scenario: Search cucumber-test
        When I set "cucumber-test" to the inputfield "[name=q]"
         And I expect that element "input.lsb" becomes visible
         And I click on the button "input.lsb"
        Then I expect that element "a[href='']" becomes visible

    when run show some warnings, might be behind proxy / VPN, please check section Behind proxy or vpn below.

    Extended tags

    Extended tags will simplify how to write cucumber with different browser & environment, those information are available on the browser object, utilize during execution of the cucumber file:

    // Browsers
    @__firefox  ><  @__non_firefox
    @__chrome   ><  @__non_chrome
    @__safari   ><  @__non_safari
    @__edge     ><  @__non_edge
    @__ie       ><  @__non_ie
    // Mobile specific
    @__android  ><  @__non_android
    @__mobile   ><  @__non_mobile
    @__ios      ><  @__non_ios
    // url related
    @__url           ex: =>  @__url:/search
    @__mainUrl       ex: =>  @__mainUrl:/search
    @__non_url       ex: =>  @__non_url:/search
    @__non_mainUrl   ex: =>  @__non_mainUrl:/search
    @__waitForUrl    ex: =>  @__waitForUrl:/search
    // Selector, it can be css or xpath (without `@`)
    @__$             ex: =>  @__$://*[class='dialog']//button
    // cookies
    @__cookies       ex: => @ __cookies:user=alex,locale=US
    // for development

    Sample usage can be seen on the example below Search on Google, when it get executed on the desktop browser like chrome, firefox or IE, it will pickup scenario with:

    @__non_safari @__non_mobile and the @__mobile will be filtered

    and viceversa will happened when it get executed on mobile.


    Android device

    please check the developer tools security options, ensure them to be checked.

    • USB debugging
    • USB debugging(Security settings)
    Feature: Search on Google
        Search should be on the google website
        and the first should be
    Scenario: Navigate to Google
        Given I open the url ""
         Then I expect that the title is "Google"
    @__non_safari @__non_mobile
    Scenario: Search cucumber-test on desktop browser
        When I set "cucumber-test" to the inputfield "[name=q]"
         And I expect that element "input.lsb" becomes visible
         And I click on the button "input.lsb"
        Then I expect that element "a[href='']" becomes visible
    Scenario: Search cucumber-test on mobile browser
        When I set "cucumber-test" to the inputfield "[name=q]"
         And I expect that element "[name=btnG]" becomes visible
         And I click on the button "[name=btnG]"
        Then I expect that element "a[href='']" becomes visible
    # Install appium server 
    npm install -g appium appium-doctor
    # run appium & connect your android device using USB 
    # check deviceName - adb devices & pass to deviceName:android version 
    cct -f google -d --android f344ee26:7.0

    Fits (Feature in tight scenario)

    Enhancement on how to write cucumber-test, this feature will make developer much faster to produce automation, as simpler to write the tests. -d / --dev is the option to trigger compiling from fits folder to feature folder.

    When run in the jenkins job, usually folders are readonly, make sure -d is excluded from job.


    Feature: Share Scenario
        To be share during automation
    Scenario: Navigate to Google
        Given I open the url ""
        Then I expect that the title is "Google"
    @__non_mobile @__chrome @__non_url:localhost
    Scenario: Search cucumber-test
        When I type "cucumber-test" to the inputfield "${g.q}"
         And I expect that element "${g.btnG}" becomes visible
         And I click on the button "${g.btnG}"
        Then I expect that element "a[href='']" becomes visible
    @__non_mobile @__non_chrome
    Scenario: Search cucumber-test
        When I type "cucumber-test *" to the inputfield "${g.q}"
         And I expect that element "${g.btnG}" becomes visible
         And I click on the button "${g.btnG}"
        Then I expect that element "a[href='']" becomes visible
    Scenario: Search cucumber-test
        When I type "cucumber-test mobile" to the inputfield "${g.q}"
         And I expect that element "${g.btnM}" becomes visible
         And I click on the button "${g.btnM}"
        Then I expect that element "a[href='']" becomes visible


    Feature: Search on Google
        Search should be on the google website
        and the first should be
    Scenario: Navigate to Google
    Scenario: Search cucumber-test
    $ cct -f google -d -b safari

    Config & Variables

    Setting up browsers capabilities and adding variables that can be use inside steps statement. Put config.js in the current folder (above features folder) where you will run cucumber-test.

    config.js will automatically pickup by runner or you can provide the fullpath in CLI:

    cct -f google -d --config ./config.js -b chrome
    cct -f google -d -b chrome,safari,firefox

    Integration with SauceLabs

    Add these env variables from your Saucelabs user & key:

    export SAUCELABS_ACCESS_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    export SAUCELABS_USERNAME=your-username
    cct -f google -d -c saucelabs:connect
    cct -f google -d -c saucelabs

    Integration with BrowserStack

    Add these env variables from your BrowserStack user & key:

    export BROWSERSTACK_USERNAME=your-username
    cct -f google -d -c browserstack

    Integration with TestingBot

    Add these env variables from your TestingBot user & key:

    export TESTINGBOT_ACCESS_KEY=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    export TESTINGBOT_USERNAME=your-username
    cct -f google -d -c testingbot

    Integration with CrossBrowserTesting

    Add these env variables from your CrossBrowserTesting user & key:

    export CROSSBROWSERTESTING_ACCESS_KEY=xxxxxxxxxxxxxxxx
    cct -f google -d -c crossbrowsertesting

    Behind proxy or vpn:

    npm install -g selenium-standalone@6.15.0
    selenium-standalone install
    selenium-standalone start
    cct -f google -d

    This env vars can be keep into bash/zsh profile/rc



    Selenium-standalone known problem

    ERROR: Unable to create new service ... driver.version: unknown need to down-grade selenium-standalone to ~6.15.0

    Safari known problem

    Safari Technology Preview to get the latest update of the webdriver included in Safari.

    Enable "Allow Remote Automation", go to menu "Develop > Allow Remote Automation" & make sure it is checked.

    Hang or Error(from selenium-standalone): safaridriver could not launch because it is not configured correctly, need to open a terminal console and manually configure as a super user: "sudo safaridriver --enable".

    Firefox known problem

    cannot access dead object, the open ticket was filled on April 8, 2017. should be careful if plan to create scenario involved with iframe.

    element#id is not supported in geckodriver, the open ticket was filled on Nov 2, 2017. see locator strategy in

    Edge known problem

    Element is obscured, fund in TestingBot cloud service, need to down-grade Edge from 17 to 16

    Dev Mode

    cd ~/.nvm/versions/node/v8.8.1/lib/node_modules
    ln -s /Users/wharsojo/Dev/cucumber-test cucumber-test




    Big Thanks

    alt SauceLabs   BrowserStack   TestingBot CrossBrowserTesting

    Cross-browser Testing Platform and Open Source <3 Provided by:

    Sauce Labs + BrowserStack + TestingBot + CrossBrowserTesting


    npm i cucumber-test

    DownloadsWeekly Downloads






    Unpacked Size

    543 kB

    Total Files


    Last publish


    • cucumber-test