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-made-by-margarit

v2.1.0

Published

made-by-margarit TestCafe reporter plugin.

Downloads

33

Readme

testcafe-reporter-made-by-margarit

Build Status

This is the made-by-margarit reporter plugin for TestCafe.

Install

npm install testcafe-reporter-made-by-margarit

Usage

Before using Testrail publisher, You need to set testcase description in specific format as per below.

Format:
test('<< Group Name>> | << Test Name >> | << Testrail Case_ID >> ', async t => { .... });

<< Group Name >> - It can be any like smoke, sanity, functional.
<< Test Name >>  - Test name of the test case
<< Testrail Case_ID >>  - case ID of testrail's test case (The testcase should be present in the given PROJECT_NAME). Case id-s can be found in testrail

Example:

test('Regression | Verify the Login Page | C875986 ', async t=> { ... });

If you want you can also add test steps in the comment field every time tests are run. You can do it the following way:

const LoiginTest_Steps =[];
test.meta({ steps: LoginTest_Steps })('<< Group Name>> | << Test Name >> | << Testrail Case_ID >> ', async t => {
    await t.click(x_button);
    LoginTest_Steps.push("I click on x button);
});

The result will look like this in Testrail: Steps in Testrail

Environment Variables

You need to add a file with .env extension into your project and define all the environment variables there.

TESTRAIL_ENABLE : set true to enable Testrail api | default: false
TESTRAIL_HOST : the url to your testrail api
TESTRAIL_USER : username
TESTRAIL_PASS : password or api key
RUN_ID : the id of the testrun where the reesults will be added

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 made-by-margarit

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

testCafe
    .createRunner()
    .src("path/to/test/file.js")
    .browsers("chrome")
    .reporter("made-by-margarit") // <-
    .run();

Author

Margarit Holm