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

qmetry-cucumber

v1.2.2

Published

Sync cucumber automation test results with Qmetry Test Cycle

Downloads

24

Readme

qmetry-cucumber

qmetry-cucumber

Getting Started

npm install --save-dev qmetry-cucumber

How to use

Case #1 Open API

Create qmetry.config.json file in the test project's root folder and add the below configurations.

qmetry.config.json
{
    "baseUrl": "https://<your base url>",
    "apiKey": "<project api key>",
    "authorization": "<jira auth creds encoded by base64>",
    "projectId": <your project id>,
    "testCycleId": <your test cycle id>,
    "summary": "<test summary>",
    "description": "<test description>"
}

Here, testCycleId, summary and description fields are optional.

Feature
Scenario: [PRO-TC-1] [PRO-TC-2] User logs in with valid credentials
        When User login with the username "<USERNAME>" and password "<PASSWORD>"
        Then User should be logged in successfully

        Examples:
        |   USERNAME   |   PASSWORD       |
        |   admin      |   amin           |
hooks.ts
import { updateQmetryStatus } from "qmetry-cucumber";

After(async function ({ pickle, result }){
    updateQmetryStatus(pickle.name, result.status);
});

Case #2 Automation API

Submit the Cucumber test output in JSON format to QMetry using the Automation API. To achieve this, create a qmetry.config.json file in the root directory of your test project and add the following configurations.

qmetry.config.json
{
    "baseUrl": "https://<your base url>",
    "authorization": "<jira auth creds encoded by base64>",
    
    "automationApiKey": "<automation api key>",
    "automation": {
        "format": "cucumber"
    }
}

Here, baseUrl, authorization, projectId, automationApiKey, and automation > format are the only mandatory fields. For more optional fields, check below:

{
    "baseUrl": "https://<your base url>",
    "authorization": "<jira auth creds encoded by base64>",
    "projectId": 0,
    
    "automationApiKey": "<automation api key>",
    "automation": {
        "format": "cucumber",
        "attachFile": true,
        "isZip":false,
        "build":"",
        "fields":{ 
            "testCycle":{ 
                "labels": ["<your label>"],
                "status":"Done",
                "summary": "<test cycle summary>",
                "description": "<test cycle description>",
                "customFields": [
                    {
                        "name": "<field name; say., Environment>",
                        "value": "<field value; say., DEV>"
                    }
                ]
            },
            "testCase":{ 
                "labels": ["<your label>"],
                "description": "<test case description>",
                "customFields": [
                    {
                        "name": "<field name; say., Environment>",
                        "value": "<field value; say., DEV>"
                    }
                ]
            }
        }
    }
}
<your_custom_file>.ts

Invoke the sendTestResultToQmetry function immediately after executing the cucumber tests.

import { sendTestResultToQmetry } from "qmetry-cucumber";

execSync(`npx cucumber-js --config=config/cucumber.js --tags "@smoke"`, { stdio: 'inherit' });
sendTestResultToQmetry(process.cwd() + '/test-result/reports/cucumber-report.json');

Test

npm test