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

v1.1.2

Published

testrail-simple TestCafe reporter plugin.

Downloads

7

Readme

testcafe-reporter-testrail-simple

Build Status

This is the testrail-simple reporter plugin for TestCafe.

Update v1.1.1: The reporter now supports uploading screenshots by default. ^^ Requires test result edit enabled in testrail.

This reporter needs only 3 configuration parameters TestRail host, username and password and does the required back tracing to collect information like project id, suite id etc that are required to publish the Test Run results to TestRail.

No need to rename/ append the TestRailCase ids into the test case name, just add the tag {testRailCaseId: CXXXXX} in the test meta and reporter will picks up the info.

Easy and Clean!

Did i say the reporter name is testrail-simple? Guess it should be testrail-very-simple LOL!!!

Install

npm install testcafe-reporter-testrail-simple

Configuration

  • TestCases should have the TestRail case ids present in the test meta in the format {testRailCaseId: 'C12345'}
test.meta({testRailCaseId: 'C239234'})
  • The reporter requires 3 environment variables to be present
TESTRAIL_HOST: https://vinay.testrail.com
TESTRAIL_USERNAME: username
TESTRAIL_APIKEY: password or api key

| ENV Variable | Default | Description | Default | Required | | ------------------------------ | ------------------ | ------------------------------------- | :----------------: | :------: | | SKIP_UPLOAD_SCREENSHOTS | false | Set this to true to Skip Uploading screenshots to TestRail | false | false |

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

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

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

Author

vinayvennela