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

cypress-qase-reporter

v2.2.3

Published

Qase Cypress Reporter

Downloads

29,845

Readme

Qase TMS Cypress reporter

Publish results simple and easy.

Installation

To install the latest release version (2.2.x), run:

npm install -D cypress-qase-reporter

Updating from v1 to v2.1

To update an existing test project using Qase reporter from version 1 to version 2.1, run the following steps:

  1. Change import paths in your test files:

    - import { qase } from 'cypress-qase-reporter/dist/mocha'
    + import { qase } from 'cypress-qase-reporter/mocha'
  2. Update reporter configuration in cypress.config.js and/or environment variables — see the configuration reference below.

  3. Add a hook in the e2e section of cypress.config.js:

      ...
      e2e: {
    +   setupNodeEvents(on, config) { 
    +     require('cypress-qase-reporter/plugin')(on, config)
        }
      }
      ...

    If you already override before:run or after:run hooks in your cypress.config.js, use this instead:

    const { beforeRunHook, afterRunHook } = require('cypress-qase-reporter/hooks');
        
    ...
      e2e: {
        setupNodeEvents(on, config) {
    +     on('before:run', async () => {
    +       console.log('override before:run');
    +       await beforeRunHook(config);
    +     });
         
    +     on('after:run', async () => {
    +       console.log('override after:run');
    +       await afterRunHook(config);
    +     });
        },
      },
      ...

Updating from v2.1 to v2.2

To update an existing test project using Qase reporter from version 2.1 to version 2.2, run the following steps:

  1. Add a metadata in the e2e section of cypress.config.js

      ...
      e2e: {
       setupNodeEvents(on, config) { 
         require('cypress-qase-reporter/plugin')(on, config)
    +    require('cypress-qase-reporter/metadata')(on)
        }
      }
      ...
    

Getting started

The Cypress reporter can auto-generate test cases and suites from your test data. Test results of subsequent test runs will match the same test cases as long as their names and file paths don't change.

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:

import { qase } from 'cypress-qase-reporter/mocha';

describe('My First Test', () => {
  qase(1,
    it('Several ids', () => {
      qase.title('My title');
      expect(true).to.equal(true);
    })
  );
  // a test can check multiple test cases
  qase([2, 3],
    it('Correct test', () => {
      expect(true).to.equal(true);
    })
  );
  qase(4,
    it.skip('Skipped test', () => {
      expect(true).to.equal(true);
    })
  );
});

To execute Cypress tests and report them to Qase.io, run the command:

QASE_MODE=testops npx cypress run

or

npm test

You can try it with the example project at examples/cypress.

A test run will be performed and available at:

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

Configuration

Qase Cypress reporter can be configured in multiple ways:

  • by adding configuration block in cypress.config.js,
  • 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 cypress.config.js config:

import cypress from 'cypress';

module.exports = cypress.defineConfig({
  reporter: 'cypress-multi-reporters',
  reporterOptions: {
    reporterEnabled: 'cypress-mochawesome-reporter, cypress-qase-reporter',
    cypressMochawesomeReporterReporterOptions: {
      charts: true,
    },
    cypressQaseReporterReporterOptions: {
      debug: true,

      testops: {
        api: {
          token: 'api_key',
        },

        project: 'project_code',
        uploadAttachments: true,

        run: {
          complete: true,
        },
      },

      framework: {
        cypress: {
          screenshotsFolder: 'cypress/screenshots',
        }
      }
    },
  },
  video: false,
  e2e: {
    setupNodeEvents(on, config) {
      require('cypress-qase-reporter/plugin')(on, config)
      require('cypress-qase-reporter/metadata')(on)
    },
  },
});

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

Requirements

We maintain the reporter on LTS versions of Node.

cypress >= 8.0.0