Skip to content
CodeceptJS E2E Framework with Cucumber, SauceLabs
JavaScript Gherkin
Branch: develop
Clone or download
gkushang chore(release): publish
 - codeceptjs-cucumber@2.0.11
 - codeceptjs-shared@2.0.7
Latest commit f35b9ba Oct 11, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.idea Support for Parallel Executions (#4) Aug 18, 2019
packages chore(release): publish Oct 10, 2019
.gitignore
.travis.yml
CHANGELOG.md changelog Sep 15, 2019
CO-LOCATE.md co-locate Jul 10, 2019
LICENSE re-org Jun 10, 2019
README.md badge Aug 27, 2019
codeceptjs-cli.gif Add files via upload Aug 27, 2019
lerna-debug.log codeceptjs e2e with Cucumber & Saucelabs Jun 8, 2019
lerna.json Support for Parallel Executions (#4) Aug 18, 2019
package.json Feature/manage secrets (#7) Aug 27, 2019
yarn.lock add localhost support for saucelabs Oct 7, 2019

README.md

CodeceptJS E2E

CodeceptJS E2E Framework with Cucumber and Saucelabs cloud

Build Status Maintainability lerna License e2e-framework.png

This framework contains Gherkin BDD Tests with CodeceptJS & uses Should.JS assertion library. Intgrated with Saucelabs to run on Multibrowsers in Parallel

  • Why BDD? Read my Medium post here

  • Run All feature files in Parallel

  • Run All feature files on Multi-Browsers - run them all in Parallel

  • Scenarios are written in Cucumber Ghernkin BDD Syntax, a.k.a .feature files. Prefer writing Declartive Test Scenarios

  • Run on SauceLabs. Single browser or Multibrowsers in Parallel

  • Uses Should.js Assertions Library. Various assertions with examples are available here

  • Reduces Flakiness with RetryFailedSteps plugin and a Webdriver's SmartWait

  • Page objects follow <name_of_page>.page.js naming pattern, and created under pages directory

  • Step Definitions files follows <name_of_step>.steps.js naming pattern, and created under step_definitions directory

Interactive CLI: How to get Started?

This framework comes with the Interactive CLI which will setup the entire framework in one-go.

Follow the below steps to launch CLI, and follow the CLI instructions. CLI also runs the Sample Github tests to test your setup (this step is optional)

Yarn is required. Install Yarn

    git clone https://github.com/gkushang/codeceptjs-e2e.git
    cd codeceptjs-e2e/packages/codeceptjs-cucumber
    yarn
    npm run cli

CodceptJS-Cucumber : E2E Framework

CodeceptJS E2E Framework with Cucumber and Saucelabs Integration

  • Interactive CLI to get started
  • Run Cucumber Scenarios on local browsers or chrome:headless
  • Run all the Feature files in Parallel
  • Run tests on Saucelabs
    • Single Browser
    • Multi Browsers. Runs all the Feature files in Parallel on Multibrowsers
  • Launch HTML report

To get started, follow the instructions on codeceptjs-cucumber

CodeceptJS-Saucelabs : Single or Multibrowsers in Parallel

CodeceptJs Integration with Saucelabs. Ease of Configuration!

  • Easy to run tests on Saucelabs with command
  yarn acceptance --profile sauce:chrome
  • Easy to run tests on Multibrowsers / Cross-Browsers. All tests in Parallel with command
  yarn acceptance:multibrowsers --profile sauce:chrome,ie,safari

To get started, follow the instructions on codeceptjs-saucelabs

CodeceptJS-Shared : Shared Master Configurations and Helpers

Shared Master Configurations & Helpers

To get started, follow the instructions on codeceptjs-shared

You can’t perform that action at this time.