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

testcafe-reporter-qase

v2.0.4

Published

Qase TMS TestCafe Reporter

Downloads

3,019

Readme

Qase TMS TestCafe reporter

Publish results simple and easy.

To install the latest version, run:

npm install -D testcafe-reporter-qase

Updating from v1

To update a test project using testcafe-reporter-qaser@v1 to version 2:

  1. Update reporter configuration in qase.config.json and/or environment variables — see the configuration reference below.

Example of usage

The TestCafe reporter has the ability to auto-generate test cases and suites from your test data.

You can also annotate the tests with the IDs of existing test cases from Qase.io before executing tests. It's a more reliable way to bind autotests to test cases, that persists when you rename, move, or parameterize your tests.

Metadata

  • qase.title - set the title of the test case
  • qase.fields - set the fields of the test case
  • qase.suite - set the suite of the test case
  • qase.comment - set the comment of the test case
  • qase.parameters - set the parameters of the test case
  • qase.groupParameters - set the group parameters of the test case
  • qase.ignore - ignore the test case in Qase. The test will be executed, but the results will not be sent to Qase.
  • qase.step - create a step in the test case
  • qase.attach - attach a file or content to the test case

For detailed instructions on using annotations and methods, refer to Usage.

For example:

const q = qase.id(1)
  .title('Text typing basics')
  .field({ 'severity': 'high' })
  .parameters({ 'browser': 'chrome' })
  .create();
test.meta({ ...q })(
  'Click check boxes and then verify their state',
  async (t) => {
    await t;
  },
);

To run tests and create a test run, execute the command (for example from folder examples):

QASE_MODE=testops npx testcafe chrome test.js -r spec,qase

or

npm test

A test run will be performed and available at:

https://app.qase.io/run/QASE_PROJECT_CODE

Configuration

Qase Testcafe reporter can be configured in multiple ways:

  • using a separate config file qase.config.json,
  • using environment variables (they override the values from the configuration files).

For a full list of configuration options, see the Configuration reference.

Example qase.config.json file:

{
  "mode": "testops",
  "debug": true,
  "testops": {
    "api": {
      "token": "api_key"
    },
    "project": "project_code",
    "run": {
      "complete": true
    }
  }
}

Check out the example of configuration for multiple reporters in the demo project.

Requirements

We maintain the reporter on LTS versions of Node.

testcafe >= 2.0.0