JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 3
  • Score
    100M100P100Q14943F
  • License MIT

use cucumber to execute tests using jest

Package Exports

  • pekel

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (pekel) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

< pekel >

A jest runner for writing tests using the cucumber framework. It is best used for integration testing.

Getting Started

Use the following steps to modify your jest configuration:

  1. set pekel as your runner:
    {
        "runner": "pekel"
    }
  2. add the path to your entry component (App), and any window polyfills you want to use:
    {
        "setupFiles": [
           "path/to/my/jest-canvas-mock",
           "path/to/my/polyfill.ts",
           "path/to/my/app.tsx"
       ] 
    }
  3. add the path to your steps, setWorldConstructor, or any other cucumber related files:
    {
        "setupFilesAfterEnv": [
           "path/to/my/steps.ts",
           "path/to/my/hooks.ts",
           "path/to/my/world.ts"
       ] 
    }
  4. add a glob pattern for your feature files:
    {
        "testMatch": [
           "path/to/my/features/*.feature"
       ] 
    }