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

@newrelic/continuous-automated-testing

v0.1.3

Published

CLI and library package for running New Relic Synthetic tests in CICD pipelines

Downloads

7

Readme

continuous-automated-testing-ci

CLI and library that adds Synthetics Continuous Automated Testing directly into your CICD pipeline!

Installation

To install the package for use as a library, use your favorite npm-based package manager:

npm install @newrelic/continuous-automated-testing

For use as a CLI package, install it globally:

npm install @newrelic/continuous-automated-testing -g

Usage

CLI

To run a batch of tests when using the package as a CLI, use the run-tests command:

newrelic-cat run-tests -a <new-relic-api-key> -c <json-config-file-path -v

The run-tests command will start a batch of tests based on the config file input. The results will be displayed once the tests have finished running.

The command has the following options:

  • -a, --api-key <value>: Your New Relic API key. We suggest using a secrets manager during CI to avoid hardcoding and exposing your API key.
  • -c, --config-file-path <value>: Relative path to a JSON CAT configuration file. See an example here.
  • -v, --verbose: See more detail on test results in STDOUT. When not enabled, only blocking tests will have all details displayed. Can also be added in the config file.

Library

After installing the package, import the runTestBatch function:

import { runTestBatch } from "@newrelic/newrelic-continuous-automated-testing"

The function takes the following parameters:

  • apiKey: A New Relic API key.
  • config: A JSON CAT configuration file. See an example here.

Configuration File Example

{
    "accountId": 12345,                     // Required
    "region": "US",                         // Required, options: US, EU
    "verbose": true,                        // Optional, default: false
    "tests": [                              // Array of tests to run
      {
        "monitorGuid": "monitor-GUID-1",    // Required
        "config": {                         // All config fields optional
          "isBlocking": true,
          "overrides":{
              "startingUrl": "example.com"
          }
        }
      },
      {
        "monitorGuid": "monitor-GUID-2"     // Required
      }
  ],
    "config": {                             // All config fields optional
        "batchName": "Test Batch"
    }
  }