npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

flowbuild-coverage-calculator

v1.4.3

Published

Test workflows and calculate its coverage

Downloads

9

Readme

flowbuild-coverage-calculator

flowbuild-coverage-calculator is a plugin to test a workflow and analyse its history of processes. Also this plugin calculate tests node and connection coverage. It uses Cucumber to run automated tests and builtin scripts to calculate tests coverage.

Installation

Run the following command in your terminal:

npm install --save-dev flowbuild-coverage-calculator

Usage

Add the following folder structure in your repository root:

├── tests
|   ├── features
|       ├── support

Then, inside the folder 'support' create a file 'world.js' with the following code inside:

// tests/features/support/world.js
const { world } = require("flowbuild-coverage-calculator");

Finally you need to add the following variables to your .env file (the values will depend on what environment and database you are using for the tests):

FLOWBUILD_URL=http://localhost:3000
POSTGRES_HOST=localhost
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_DATABASE=workflow

// these are just examples of variables values

Running cucumber automated tests

As soon as you have all the dependencies and files as above, you need to create your test file inside the 'features' folder always with the extension '.feature' and using Gherkin sintaxe. Then, run the following command:

npx cucumber-js tests/features/testBlueprint.feature

// in this case 'testBlueprint.feature' is the test file created and has the same name as the blueprint (testBlueprint.json)

After this it will appear in the console the tests results. Besides that a file called 'worldData.json' will be created with the properties you chose to save in it. Also, inside the folder 'support' a new folder called 'coverageReports' will be created with json files. These files have the tests results coverage that you can check whenever you want.

Publish cucumber reports quietly

And, if you don't want to publish your tests into cucumber's platform you can simply add a file on your repository root called 'cucumber.js' with the following code in it:

// cucumber.js
module.exports = { default: "--publish-quiet" };

Extending CustomWorld

If you need to change or add new methods on CustomWorld you can simply add in your 'world.js' file the following code:

// tests/features/support/world.js
const { world } = require("flowbuild-coverage-calculator");
const { setWorldConstructor } = require("@cucumber/cucumber");

class CustomWorld extends world.CustomWorld {
  ...
  // add your new methods here
  ...
}

setWorldConstructor(CustomWorld);

Note: if your methods have dependencies like 'logger', 'axios' or env variables, remember to add them at the top of your file as well.

Adding new steps

In case you need to add new steps for your tests you can add a file called 'steps.js' in your 'support' folder and simply put your new steps in it like the example:

// tests/features/support/steps.js
const { Given } = require("@cucumber/cucumber");

Given("an user with claim {string} is logged in", { timeout: 60 * 1000 }, async function (claim) {
  await this.getTokenClaim(claim);
  return;
});

Note: this is just an example and if you use a new method, like 'this.getTokenClaim(claim)' you need to add the method inside the file 'world.js'.

Printing a coverage table on console

Having a lot of files in the folder 'coverageReport' make it difficult to read one by one to see the results. To make it easier you can add the following script on your 'package.json' file:

// package.json
"scripts": {
  ...
  "report": "node ./node_modules/flowbuild-coverage-calculator/scripts/report.js",
  ...
}

And then run the following command to print the coverage table on console:

npm run report