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

v1.1.2

Published

testrail-integration TestCafe reporter plugin.

Downloads

39

Readme

testcafe-reporter-testrail-integration

This is the testrail-integration reporter plugin for TestCafe.

Install

npm install testcafe-reporter-testrail-integration

Setup

This package uses environment variables, make sure required variables are accessible by the process.

TESTRAIL_ENABLE=<bool - optional> [default true]
PUSH_TEST_RUNS=<bool - optional> [default true]
PLAN_NAME=<string>
TESTRAIL_HOST=<string> [format - https://org.testrail.io]
TESTRAIL_USER=<string>
TESTRAIL_PASS=<string> [password or api key]
PROJECT_NAME=<string>
SUITE_NAME=<string - optional> [default "Master"]
RUN_NAME=<string - optional> [default "TestAutomation_Plan"]
UPDATE_TEST_CASES=<bool - optional> [default true]

For the reporter to be able to update testcases with run results, you must define testcases in the following format:

test('<Section name>|<Testcase>|<Testrail case code>', func => {

}

//EXAMPLE:

test('Home Page|User is able to click on something|C567', func => {

}

Optional

If you have any skipped test cases, you will need to make a custom Skipped status in your testRail project, otherwise the reporter will fail to publish results.

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

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

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

Improvements

Please PR any improvements / fixes. A lot of this code is from another broken + deprecated testRail reporter for TestCafe which I quickly fixed up.

Author

Chris Simpkins