
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
@cucumber/compatibility-kit
Advanced tools
Test data used to validate a Cucumber implementation
The CCK - aka. Cucumber Compatibility Kit - is a set of features and Messages. It aims to validate an implementation of the Cucumber Messages protocol.
The kit is composed of features and messages:
.ndjson
files - are the reference: a given feature
from the kit, executed using its dedicated step definitions, must emit the
corresponding MessagesAfter running npm install --save-dev @cucumber/compatibility-kit
, the kit is
available in your node_modules
in node_modules/@cucumber/compatibility-kit/features
.
You will find there some folders. Each folder owns a feature with its corresponding Messages.
You can execute the features with your implementation. For example with cucumber, it would look like the following:
npx cucumber-js node_modules/@cucumber/compatibility-kit/features/**/*.feature
Here's we have been able to run our features. However it did not find the step definitions. It is up to you to implement your step definitions compatible with your own tool.
In order to make some experiments, the kit comes with step definitions compatible with
fake-cucumber and written using TypeScript.
You will find also a few assets which may be required for some features. For example,
the attachments
feature is using an asset cucumber.png
to test the possibility
to attach images to the Messages.
Each feature available in the kit comes with a .ndjson
. That file is the expected
Messages related the execution of the corresopnding feature. For convenience, the
messages are serialized using the ndjson format.
The idea is to execute the features of the kit using your tool, to generate the corresponding messages, and to compare your messages with the ones from the kit.
The Cucumber Compatibility Kit is part of the development tools of Cucumber. It allows us to make sure that all our implementations are properly supporting our internal protocol and thus are compabitle with each other and with our common tools like the html-formatter.
It can be a valuable tool if you are developing integration with cucumber, or your own implementation of it.
Join us on github/cucumber/compatibility-kit to get more help if you need to.
You can also take a look on cucumber-js to see how the kit is used there.
FAQs
Test data used to validate a Cucumber implementation
We found that @cucumber/compatibility-kit demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.