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

vrunner

v0.4.4

Published

Executes vREST test cases on terminal and can be used with cron utility or any continuous integration server.

Downloads

14

Readme

vrunner

  1. Executes test cases on terminal which are stored in vREST Cloud.
  2. vrunner command can be used in any third party schedular like cron to schedule test cases. For more information, please read our guide.
  3. vrunner command can be used in any continuous integration server like Jenkins etc. For more information, please read our guide.

Prerequisites:

  • Node.js - Download and Install Node.js. You can also follow this wiki (https://nodejs.org/en/download/package-manager/)

Installation / Update:

sudo npm install -g vrunner
  • sudo is optional. For windows, remove sudo from the above command.

Usage:

vrunner --email=<vrest_email> --password=<vrest_password>
        --url="<vrest_testcase_list_url>" [--env=<environment_name>]
        [--nosslcheck=<boolean_value>] [--debug=<boolean_value>] [--logger=<one_of_available_loggers>]
        [--filepath="<path_of_log_file_for_logger_other_than_console>"]

Options:

    -E, --email      : Email ID through which you have registered on vREST
    -P, --password   : Password of your vREST account
    -U, --url        : Provide the test case list URL here. You can find the test
                       case list URL by going to your vREST instance and select Test
                       Cases tab. Now click on button "Copy Current Test Case List
                       URL" available in Left hand side, below the "Filters section".
                       Provide the copied URL in this option. Ensure that you enclose
                       URL in double quotes.
    -N, --env        : Provide the environment name to initialize the global variables.
                       By default environment `Default` is used.
    -D, --debug      : Should be set if you want debugging console logs.
                       By default debugging information are not logged.
    -S, --nosslcheck : If this argument is `true`, vRUNNER will process all requests,
                       without Secure Certificate Check.
                       By default Secure Certificate Check is enabled. This option is
                       useful in self-signed certificate issues.
    -L, --logger     : Your desired logging of the vRUNNER execution process and
                       result. This can be either `console` or `json` or `csv` or `xunit`.
                       By default `console` logger is used.
    -F, --filepath   : Valid if other than `console` logger is selected.
                       Absolute path of the log file, into which execution process
                       and result logs will be dumped. If path/file is not present,
                       tool will try to setup that path, and create file automatically.
                       Please note that if file already exists, that will be
                       overwritten. By default it will be the `vrest_logs/logs.[json|xml|csv]`
                       in current directory.
    -H, --help       : To see this help.