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-testrail-publisher

v1.2.0

Published

testcafe-reporter-testrail-publisher TestCafe publisher / reporter plugin.

Downloads

1

Readme

testcafe-reporter-testrail-publisher

This is the testcafe-reporter-testrail-publisher reporter plugin for TestCafe.

Install

npm install testcafe-reporter-testrail-publisher

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 testrail-publisher

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

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

Prerequisites

  • All test cases should have a valid mapping between TestCafe and TestRail.

Formatting your TestCafe test descriptions

test("<Test Type> | <Test Name> | <TestRail Test Case ID>", async t => {
  // Your test code goes here as usual.
});

Replace the following segments of the example above with your test case details:

  • <Test Type>: The type of test (like "smoke" or "regression").
  • <Test Name>: The name of your test, a description of what it does.
  • <TestRail Test Case ID>: The test case ID from TestRail that will link with your TestCafe test.

Configuration

Configuration can be provided via:

  • ENV variables

| ENV Variable | Config | Description | Default | Required | | ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :-------------------------: | :------: | | TESTRAIL_HOST | host | URL of the TestRail instance. | | true | | TESTRAIL_USER | user | Account name which will be used to push results. | | true | | TESTRAIL_PASSWORD | password | Account password. | | true | | PROJECT_NAME | projectName | Project name in which test cases are stored. | | true | | PLAN_NAME | planName | Plan name in which test cases are stored. | TestPlan | false | | RUN_NAME | runName | Run name in which test cases are stored. | Run_ + date (browser + OS) | false |

Author

Adil Ben Moussa (adil[dot]benmoussa[@]gmail[dot]com)