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-tm4j-reporter

v1.4.1

Published

TM4J Cloud Reporter for Cypress.io

Downloads

165

Readme

cypress-tm4j-reporter

Install

$ npm install cypress-tm4j-reporter --save-dev

Usage

Cypress Reporter Plugin

Not recommended for use. See Known Issues.
Example: cypress.json

{
  "projectId": "cypress-example",
  "reporter": "cypress-tm4j-reporter",
  "reporterOptions": {
    "baseUrl": "https://api.tm4j.smartbear.com/rest-api/v2",
    "authToken": "[READACTED]",
    "projectKey": "AQA"
  }
}

Cypress Module API

Programmatic execution example: cypress-cli.js

const cypress = require('cypress')
const {Tm4jUtils} = require('cypress-tm4j-reporter')

cypress.run({
    spec: './cypress/integration/example.spec.js'
}).then(results => {
    let tm4jutils = new Tm4jUtils(results.config.reporterOptions)
    tm4jutils.publishCypressCliResults(results).then(testRuns => {
        console.log("TM4J results published")
        testRuns.forEach(run => {
            console.log(run)
        })
    })
})
$ node cypress-cli.js

Reporter Options

Following reporter options are available:

  • baseUrl - base URL for API calls
    Example: https://api.tm4j.smartbear.com/rest-api/v2
  • authToken - Auth Token for TM4J for Cloud
  • projectyKey - Jira project key for test cases and test cycles
  • defaultTestCaseFolderId - Folder ID for automatically created test cases
  • createTestCases - create new test case if existing test case key not found
  • createTestCycles - create new test cycle if existing test cycle key not found
  • specMapping - define how *.spec.js files mapped to TM4J entitiesv
    Example: execution, cycle
  • cycleName - test cycle name for specMapping=execution
  • environmentProperty - populate Environment for execution with value from property with set name
    Example: environment (cypress run --env "environment=envcode")
  • debugOutput - debug output for reporter

Known Issues