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-atm

v1.1.3

Published

atm TestCafe reporter plugin.

Downloads

5

Readme

testcafe-reporter-atm

Build Status

This is the atm reporter plugin for TestCafe.

Install

npm install testcafe-reporter-atm

Environment Variables

Set following environment variables on your machine:

  • JIRA_BASE_URL=baseurl (e.g. --> jira.abcdef.com)
  • JIRA_USERNAME=username
  • JIRA_PASSWORD=password
  • JIRA_TEST_RUN=ATMrunid
  • PROJECT_ID=XYZ

Usage

When you run tests from the command line, specify the reporter name by using the --reporter option:

testcafe chrome 'path/to/test/file.js' --reporter atm

When you use API, pass the reporter name to the reporter() method:

testCafe
    .createRunner()
    .src('path/to/test/file.js')
    .browsers('chrome')
    .reporter('atm') // <-
    .run();

How to pass test ID & test environment from your test file

Fixture sample below demonstrates how test environment and test case id information can be passed from fixture file. If the test environment passed has an exact match in Kanoah's list of test environment for the project, environment information also be updated with the test execution status against corresponding test id.

example of environment from sample below :

  • local_desktop_chrome_latest_sampleapp_en

Test environment information depicted below is only suggestive.

fixture`Scenario description`
    .page`${sUrl}`
    .meta({ 
        Env: Destination + '_' + Breakpoint + '_' + Browser + '_' + Version + '_' + ApplicationName + '_' + Locale
    })
test
    .meta({ID: 'TEST-T1'})
    .before(async t => {
        // before test code
    })('Test description', async t => {
        // Test code
    });

Note:

  • If test environment is not provided, test execution result will still be uploaded minus environment information.
  • Screenshot for failed step will be attched to the result id of the test scenario in ATM