Building Enterprise JavaScript Applications

Laying out our step definitions

With the help of Gherkin, we now have our specification written in plain English. Next, let's try to use Cucumber to run our specification.

By default, Cucumber will look for a directory called features in the project's root directory and run the .feature files it finds inside. Since we have placed our main.feature file inside the spec/cucumber/features directory, we should pass this path to Cucumber:

$ npx cucumber-js spec/cucumber/featuresUUUUUUWarnings:1) Scenario: Empty Payload   ? When the client creates a POST request to /users       Undefined.   ? And attaches a generic empty payload       Undefined.   ? And sends the request       Undefined.   ? Then our API should respond with a 400 HTTP status code       Undefined. ? And the payload ...