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

qase-javascript-commons

v2.2.5

Published

Qase JS Reporters

Downloads

134,721

Readme

Qase JavaScript Commons

This module is an SDK for developing test reporters for Qase TMS. It's using qaseio as an API client, and all Qase reporters are, in turn, using this package. You should use it if you're developing your own test reporter for a special-purpose framework.

To report results from tests using a popular framework or test runner, don't install this module directly and use the corresponding reporter module instead:

Installation

npm install qase-javascript-commons

Configuration

Qase JS Reporters can be configured in multiple ways:

  • using a config file qase.config.json
  • using environment variables

All configuration options are listed in the table below:

| Description | Config file | Environment variable | Default value | Required | Possible values | |----------------------------------------------------------------------------------------------------------------------------|----------------------------|---------------------------------|-----------------------------------------|----------|----------------------------| | Common | | | | | | | Mode of reporter | mode | QASE_MODE | off | No | testops, report, off | | Fallback mode of reporter | fallback | QASE_FALLBACK | off | No | testops, report, off | | Environment | environment | QASE_ENVIRONMENT | undefined | No | Any string | | Root suite | rootSuite | QASE_ROOT_SUITE | undefined | No | Any string | | Enable debug logs | debug | QASE_DEBUG | False | No | True, False | | Enable capture logs from stdout and stderr | testops.defect | QASE_CAPTURE_LOGS | False | No | True, False | | Qase Report configuration | | | | | | | Driver used for report mode | report.driver | QASE_REPORT_DRIVER | local | No | local | | Path to save the report | report.connection.path | QASE_REPORT_CONNECTION_PATH | ./build/qase-report | | | | Local report format | report.connection.format | QASE_REPORT_CONNECTION_FORMAT | json | | json, jsonp | | Qase TestOps configuration | | | | | | | Token for API access | testops.api.token | QASE_TESTOPS_API_TOKEN | undefined | Yes | Any string | | Qase API host. For enterprise users, specify full address: api-example.qase.io | testops.api.host | QASE_TESTOPS_API_HOST | qase.io | No | Any string | | Qase enterprise environment | testops.api.enterprise | QASE_TESTOPS_API_ENTERPRISE | False | No | True, False | | Code of your project, which you can take from the URL: https://app.qase.io/project/DEMOTR - DEMOTR is the project code | testops.project | QASE_TESTOPS_PROJECT | undefined | Yes | Any string | | Qase test run ID | testops.run.id | QASE_TESTOPS_RUN_ID | undefined | No | Any integer | | Qase test run title | testops.run.title | QASE_TESTOPS_RUN_TITLE | Automated run <Current date and time> | No | Any string | | Qase test run description | testops.run.description | QASE_TESTOPS_RUN_DESCRIPTION | <Framework name> automated run | No | Any string | | Qase test run complete | testops.run.complete | QASE_TESTOPS_RUN_COMPLETE | True | | True, False | | Qase test plan ID | testops.plan.id | QASE_TESTOPS_PLAN_ID | undefined | No | Any integer | | Size of batch for sending test results | testops.batch.size | QASE_TESTOPS_BATCH_SIZE | 200 | No | Any integer | | Enable defects for failed test cases | testops.defect | QASE_TESTOPS_DEFECT | False | No | True, False |

Example qase.config.json config:

{
  "mode": "testops",
  "fallback": "report",
  "debug": false,
  "environment": "local",
  "captureLogs": false,
  "report": {
    "driver": "local",
    "connection": {
      "local": {
        "path": "./build/qase-report",
        "format": "json"
      }
    }
  },
  "testops": {
    "api": {
      "token": "<token>",
      "host": "qase.io"
    },
    "run": {
      "title": "Regress run",
      "description": "Regress run description",
      "complete": true
    },
    "defect": false,
    "project": "<project_code>",
    "batch": {
      "size": 100
    }
  }
}