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

@bugbeater/reporter

v0.0.1-rc.3

Published

## Overview

Downloads

2

Readme

@bugbeater/reporter

Overview

This project...

Setup

  1. Install package with

    yarn add @bugbeater/reporter
    npm install @bugbeater/reporter
  2. You must to add Test Case IDs to your tests. You can do this by adding the following to your tests title:

  • For Jest:

    import { describe, test } from '@jest/globals';
    
    describe('Jest example describe', () => {
      test('@TC-4 jest example test', async () => {
        await new Promise((resolve) => setTimeout(resolve, 1000));
        expect(false).toBeTruthy();
      });
    
      test('@TC-5 jest example test', async () => {
        await new Promise((resolve) => setTimeout(resolve, 1000));
        expect(true).toBeTruthy();
      });
    
      test('@TC-6 jest example test', async () => {
        await new Promise((resolve) => setTimeout(resolve, 1000));
        expect(true).toBeTruthy();
      });
    });
  • For Playwright:

    import { expect, test } from '@playwright/test';
    
    test.describe('Playwright', () => {
      test('@TC-4 has title', async () => {
        await new Promise((resolve) => setTimeout(resolve, 2000));
        expect(true).toBeFalsy();
      });
    
      test('@TC-5 get started link', async () => {
        await new Promise((resolve) => setTimeout(resolve, 2000));
        expect(false).toBeFalsy();
      });
    
      test.skip('@TC-6 is awesome', async () => {
        await new Promise((resolve) => setTimeout(resolve, 2000));
        expect(false).toBeFalsy();
      });
    });
    ```
  1. Configure you tests to use the reporter.
  • With Jest, add the following to your jest.config.js file:
module.exports = {
 ...
 reporters: [
   'default',
   ['@bugbeater/reporter/jest.js', {
     apiKey: process.env.BUGBEATER_API_KEY,
     baseUrl: process.env.BUGBEATER_BASE_URL,
     environments: ['dev', 'staging'],
   }],
 ],
 ...
}
  • With Playwright, add the following to your playwright.config.js file:

    import { defineConfig } from '@playwright/test';
    import dotenv from 'dotenv';
    dotenv.config();
    
    export default defineConfig({
      reporter: [
        ['list'],
        [
          '@bugbeater/reporter/playwright.js',
          {
            apiKey: process.env.BUGBEATER_API_KEY,
            baseUrl: process.env.BUGBEATER_BASE_URL,
            environments: ['dev', 'staging'],
          },
        ],
      ],
    });
  1. Set the following environment variables (or use a .env file):
  • BUGBEATER_API_KEY: Your Bugbeater API key.
  • BUGBEATER_BASE_URL: The base URL of Bugbeater main API.
  • DEBUG: Set to bugbeater:reporter:* to enable debug logs. Example: bugbeater:reporter:*. See debug for more information.
  • BUGBEATER_ENVIRONMENTS: A comma separated list of environments to report to. If not set, it will be empty. Example: "dev,staging,prod".

    Note: you can pass environment variables into reporter through the reporter options instead of using environment variables. Reporter options take precedence over environment variables.

License

This project is licensed under the terms of the license found in the LICENSE file.