@g_package/jest-cucumber-fusion 1.0.0

package/.prettierignore

@@ -0,0 +1,16 @@
+# Ignore artifacts:
+.git
+.github
+build
+coverage
+docs
+node_modules
+
+.gitignore
+.npmignore
+.prettierignore
+.prettierrc.json
+LICENSE
+package.json
+package-lock.json
+README.md

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,165 @@
+# Jest Cucumber Fusion
+
+Write 'pure' cucumber test in Jest without syntax clutter 
+
+[![Build Status](https://github.com/b-yond-infinite-network/jest-cucumber-fusion/workflows/Continuous%20Integration/badge.svg)](https://github.com/b-yond-infinite-network/jest-cucumber-fusion/actions?query=workflow%3AIntegration)
+[![Codecov](https://codecov.io/gh/b-yond-infinite-network/jest-cucumber-fusion/branch/master/graph/badge.svg)](https://codecov.io/gh/b-yond-infinite-network/jest-cucumber-fusion)
+[![Publish](https://github.com/b-yond-infinite-network/jest-cucumber-fusion/workflows/Publish/badge.svg)](https://github.com/b-yond-infinite-network/jest-cucumber-fusion/actions?query=workflow%3APublish)
+
+[![npm downloads](https://img.shields.io/npm/dm/jest-cucumber-fusion)](https://www.npmjs.com/package/jest-cucumber-fusion)
+[![npm latest](https://img.shields.io/npm/v/jest-cucumber-fusion/latest.svg)](https://www.npmjs.com/package/jest-cucumber-fusion)
+[![semantic-release](https://img.shields.io/badge/%20%20%F0%9F%93%A6%F0%9F%9A%80-semantic--release-e10079.svg)](https://github.com/semantic-release/semantic-release)
+
+
+## Overview
+Build on top of [Jest-cucumber](https://github.com/bencompton/jest-cucumber), Jest-Cucumber-Fusion handle the writing of the corresponding Jest test steps using an uncluttered cucumber style.
+Instead of using `describe` and `it` blocks, you instead write a Jest test for each scenario, and then define `Given`, `When`, and `Then` step definitions inside of your Jest tests. 
+Jest-Cucumber-Fusion then allows you to link these Cucumber tests to your javascript Cucumber feature steps.
+Adding a `Fusion`call, the links between your Feature definition and your Steps definition is handled automatically and the necessary scaffolding for jest-cucumber is build behind the scene.
+Now use jest naturally in your project like you would use the native Cucumber library.
+
+## Motivation
+
+Jest-cucumber is an amazing project but forces you to write a lot of repetitive scaffolding code to setup the link betwen Jest and Cucumber.
+With Jest-Cucumber-Fusion, it really takes only the minimal code possible:
+ - a Cucumber Feature file with gherkin sentences
+ - a Cucumber Step definition file with your javascript validation code, ended with the `Fusion` function to link the two
+
+
+
+## Getting Started
+
+### Install Jest Cucumber Fusion:
+
+```
+npm install jest-cucumber-fusion --save-dev
+```
+
+### Add a Feature file:
+
+```gherkin
+###filename: rocket-launching.feature
+Feature: Rocket Launching
+
+Scenario: Launching a SpaceX rocket
+  Given I am Elon Musk attempting to launch a rocket into space
+  When I launch the rocket
+  Then the rocket should end up in space
+  And the booster(s) should land back on the launch pad
+  And nobody should doubt me ever again
+```
+
+### Add the following to your package.json configuration:
+
+```javascript
+"jest": { "testMatch": [ "**/*.steps.js" ] }
+```
+
+
+### Add a your Cucumber Step definition file and load Fusion
+```javascript
+//filename: rocket-launching.steps.js
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+```
+
+### Load any dependency you need to do your test
+
+```javascript
+//filename: rocket-launching.steps.js
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+const { Rocket } = require( '../../src/rocket' )
+let rocket
+
+```
+
+### Add steps definitions:
+
+```javascript
+//filename: rocket-launching.steps.js
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+const { Rocket } = require( '../../src/rocket' )
+let rocket
+
+Given( 'I am Elon Musk attempting to launch a rocket into space', () => {
+    rocket = new Rocket()
+} )
+
+When( 'I launch the rocket', () => {
+    rocket.launch()
+} )
+
+Then( 'the rocket should end up in space', () => {
+    expect(rocket.isInSpace).toBe(true)
+} )
+
+And( /^the booster\(s\) should land back on the launch pad$/, () => {
+    expect(rocket.boostersLanded).toBe(true)
+} )
+
+But( 'nobody should doubt me ever again', () => {
+    expect('people').not.toBe('haters')
+} )
+```
+
+### Adding the Fusion() call at the end of the Step definition file
+You have to match it with your Cucumber Feature definition file:
+```javascript
+//filename: rocket-launching.steps.js
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+const { Rocket } = require( '../../src/rocket' )
+let rocket
+
+Given( 'I am Elon Musk attempting to launch a rocket into space', () => {
+    rocket = new Rocket()
+} )
+
+When( 'I launch the rocket', () => {
+    rocket.launch()
+} )
+
+Then( 'the rocket should end up in space', () => {
+    expect(rocket.isInSpace).toBe(true)
+} )
+
+And( /^the booster\(s\) should land back on the launch pad$/, () => {
+    expect(rocket.boostersLanded).toBe(true)
+} )
+
+But( 'nobody should doubt me ever again', () => {
+    expect('people').not.toBe('haters')
+} )
+
+
+Fusion( 'rocket-launching.feature' )
+```
+
+## Adding coverage
+Since we're using jest, it is very easy to generate the code coverage of your Cucumber test:
+```javascript
+"jest": {
+    "testMatch": [
+      "**/*.steps.js"
+    ],
+    "coveragePathIgnorePatterns": [
+      "/node_modules/",
+      "/test/"
+    ],
+    "coverageDirectory": "./coverage/",
+    "collectCoverage": true
+  }
+```
+
+ 
+## Additional Documentation 
+
+  * [Gherkin tables](./docs/GherkinTables.md)
+  * [Step definition arguments](./docs/StepDefinitionArguments.md)
+  * [Scenario outlines](./docs/ScenarioOutlines.md)
+  * [Re-using step definitions](./docs/ReusingStepDefinitions.md)  
+  * [Configuration options](./docs/AdditionalConfiguration.md)
+  * [Running the examples](./docs/RunningTheExamples.md)
+  * [Language](./docs/Language.md)

package/codecov.SHA256SUM

@@ -0,0 +1 @@
+28641437b42ff7296a1ff494cfa9441a0b19902016218b0926b55870ee533a54  codecov

package/codecov.SHA256SUM.sig

@@ -0,0 +1,16 @@
+-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEEJwNOf9uFDgu8LGL/gGuyiu13mGkFAmpOv5sACgkQgGuyiu13
+mGnmcg/+MYVRFlzf4Y9D81qxf82xfWuzJhcEY0cUqCdCB98p1nwVIAqTshRCWPLn
+bhosCZFAsUp2HrIxseiddcnu/q57S3ARhz/jxxTtr5Z6mezFsdQ7rUZlky9n9Jm7
+4WT5+XWpQsjLvVWBW5JQ/xQOkszmKvdyyDTtlsqCvGrObUuThjMkGIupImCgFk4Z
+zRAkJ/W3MHJLl+SDVvYqh+dwh9POJlUs6dsV7LNAztmV3Dg4w8SDc4WHrm/VVh5y
+nSzCk2c8DeGJN5pe+uH02EvG81xdYVurLsit/Z5DWGlNbWzy54Uo7UAVgQGxDvGo
+YEag/k85BJJiTFDw67n5ITIQsj908T5VNvQPTGyg5LEnZyGDbbPDCYNdWeikTow7
+Fl2dhpJ+lTgF+bp5Z25KS0lrzcVeO5G0zZSYKSjvB3KgU/oAjw+cLX+LtHjE6AAZ
+guXMyCQ2FJ73KegSSIBAg91S5DBz9zrLlhgzvdRqd0JuiSM/+0GGQ/+HVxwAntVB
+uCbKvZLigHpJfxDz1wIQ3cdhds4/Jxh4T+7s+wPFJplqBq09i8vZv7czLAu/47o4
+SlXWZKWqwPm2q3Vmm3v5dIrHXO8ixnZB5wHeGv1Od4q78GKBbCyOJISVYy0rDwRu
+gG6Uy2BgytqP81NPbnoyNI4U8KD2pDEWRpeywH2SSWWHVq4s578=
+=8mH/
+-----END PGP SIGNATURE-----

package/docs/AdditionalConfiguration.md

@@ -0,0 +1,155 @@
+# Configuration Options
+
+## Disabling scenario / step definition validation
+
+Cucumber's approach is to start with your feature file and execute the step definitions in the order defined in the feature file. In contrast, jest-cucumber scenarios are merely Jest tests. In order to provide the same ability as Cucumber to keep the feature files and step definitions in sync, jest-cucumber validates your step definitions against the feature file.
+
+By default, this step definition / feature file validation is enabled. If you have scenarios that are defined in the feature file, but not in your step definitions for that feature file, jest-cucumber will raise an error (and provide starter code). If you have scenarios defined in your step definitions for that aren't in your feature file, jest-cucumber will also raise an error. Additionally, jest-cucumber also validates that the steps you define within your scenarios match the steps that are defined in the feature file, and are in the same order. 
+
+If you would prefer not to have more control over what validation occurs the following options are available:
+
+```javascript
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+
+//your javascript tests
+//....
+//Given( ...
+// 
+
+
+Fusion( 'rocket-launching.feature', {
+  errors: {
+    missingScenarioInStepDefinitions: true, // Error when a scenario is in the feature file, but not in the step definition
+    missingStepInStepDefinitions: true, // Error when a step is in the feature file, but not in the step definitions
+    missingScenarioInFeature: true, // Error when a scenario is in the step definitions, but not in the feature
+    missingStepInFeature: true, // Error when a step is in the step definitions, but not in the feature
+  }
+} )
+```
+
+## Tag filtering
+
+You can specify a tag filter. Tag filters will cause any scenario that is filtered out via a tag filter to be skipped.
+
+For example, consider the following feature file:
+
+```gherkin
+Feature: Tagged scenarios
+
+  @included
+  Scenario: Tagged scenario that is included
+    Given my scenario has a tag that is included in my jest-cucumber step definitions tag filter
+    But I don't have that scenario defined in my step definitions
+    When I execute my jest-cucumber scenarios
+    Then jest-cucumber should show me an error
+  
+  @excluded
+  Scenario: Tagged scenario that is not included
+    Given my scenario has a tag that is NOT included in my jest-cucumber step definitions tag filter
+    But I don't have that scenario defined in my step definitions
+    When I execute my jest-cucumber scenarios
+    Then jest-cucumber should NOT show me an error
+```
+
+Consider the following step definitions file:
+
+```javascript
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+
+//your javascript tests
+//....
+//Given( ...
+// 
+
+
+Fusion( 'rocket-launching.feature', { tagFilter: '@included and not @excluded' } )
+```
+
+In this case, the scenario tagged `@included` will be run, and the scenario tagged `@excluded` will be skipped. The tag filtering expressions are very powerful and can include `not`, `and`, `or`, as well as parenthesis.
+
+## Scenario title templates
+
+In some cases, having more control over the scenario titles is desired. For example, imagine scenarios that are tagged with with issue ids like so:
+
+```
+Feature: Tagged scenarios
+
+    @issue-1234
+    Scenario: Scenario tagged with issue
+        ...
+        ...
+        ...        
+```
+
+Use a `scenarioNameTemplate` function to be provided to generate the scenario title as desired. For example:
+
+```javascript
+const { Given, When, Then, And, But, Fusion } = require( 'jest-cucumber-fusion' )
+
+
+//your javascript tests
+//....
+//Given( ...
+// 
+
+
+Fusion( 'rocket-launching.feature', {
+    scenarioNameTemplate: (vars) => {
+        return `${vars.scenarioTitle} (${vars.scenarioTags.join(',')})`
+    }
+} )
+```
+
+The output scenario title in this case would be `Scenario tagged with issue (issue-1234)`.
+
+The following info is available in the `vars` argument:
+
+* `featureTitle` - string
+* `featureTags` - string[]
+* `scenarioTitle` - string
+* `scenarioTags` - string[]
+
+## Relative feature file paths
+
+It might feel more natural to load feature files with paths relative to the file loading the feature, instead of relative to the project root. This is possible with help of the `loadRelativePath` flag:
+
+```javascript
+Fusion( 'rocket-launching.feature', { loadRelativePath: true } )
+```
+
+Please note that the path will be relative to the file that calls `Fusion`, so if you use helper files which call `Fusion` for you this might lead to unexpected results.
+Like all other flags you can set the flag globally to always use relative imports.
+
+## Global configuration
+
+To avoid repeating the same configuration settings in every step definition file, it is also possible to specify configuration parameters globally. Note that configuration settings specified in step definition files take precedence over global configuration.
+
+To enable global configuration, you have to use the jest-cucumber global configuration.
+First specify a configuration JavaScript file in your the `setupFiles` section of your Jest configuration like so:
+
+```javascript
+{
+  ...
+  "setupFiles": [
+    "./jest-cucumber-config"
+  ],
+  ...
+}
+```
+
+And setup the configuration JavaScript file, like so:
+
+```javascript
+//jest-cucumber-config.js
+
+const setJestCucumberConfiguration = require('jest-cucumber').setJestCucumberConfiguration;
+
+setJestCucumberConfiguration({
+  tagFilter: '@ui and not @slow',
+  scenarioNameTemplate: (vars) => {
+      return ` ${vars.featureTitle} - ${vars.scenarioTitle}}`;
+  }
+});
+```

package/docs/GherkinTables.md

@@ -0,0 +1,61 @@
+# Gherkin tables
+
+```gherkin
+Feature: Todo List
+
+Scenario: Adding an item to my todo list
+  Given my todo list currently looks as follows:
+  | TaskName            | Priority |
+  | Fix bugs in my code | medium   |
+  | Document my hours   | medium   |
+  When I add the following task:
+  | TaskName                              | Priority |
+  | Watch cat videos on YouTube all day   | high     |
+  Then I should see the following todo list:
+  | TaskName                              | Priority |  
+  | Watch cat videos on YouTube all day   | high     |
+  | Sign up for unemployment              | high     |
+```
+
+```javascript
+const { Before, After, Given, When, Then, Fusion } = require( 'jest-cucumber-fusion' )
+
+const { TodoList } = require( '../../src/todo-list' )
+let todoList
+
+
+Before( () => { todoList = new TodoList(); } )
+
+Given( 'my todo list currently looks as follows:', table => {
+    table.forEach(row => {
+        todoList.add( {
+            name: row.TaskName,
+            priority: row.Priority
+        } )
+    } )
+} )
+
+When( 'I add the following task:', table => {
+    todoList.add({
+        name: table[0].TaskName,
+        priority: table[0].Priority
+    })
+})
+
+Then( 'I should see the following todo list:', table => {
+    expect(todoList.items.length).toBe(table.length)
+
+    table.forEach((row, index) => {
+        expect(todoList.items[index].name).toBe(table[index].TaskName)
+        expect(todoList.items[index].priority).toBe(table[index].Priority)
+    } )
+} )
+
+After( () => {
+    const emptyTodo = new TodoList()
+    emptyTodo.add( { name: 'Empty on purpose', priority: 'so low' } )
+} )
+
+
+Fusion( '../features/using-gherkin-tables.feature' )
+```