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

log2qtest

v0.1.7

Published

Submit automation logs (JUnit) to qTest qtestnet.com

Downloads

6

Readme

log2qtest

This is CLI app that allow parse JUnit xml file then submit to qTest via rest API

Config file: config.json

{
  "host": "<qTest url>",
  "username": "<qTest username>",
  "password": "<qTest password>",
  "project": <qTest project>,
  "suite": <qTest test suite>,
  "module": <qTest parent module>,
  "cycle":"<qTest parent test cycle>",
  "dir": "<folder that contains junit xml file>",
  "pattern":"<File pattern to filter JUnit xml pattern>",
  "methodAsTestCase": <true|false>, //if true then each junit method as a qTest testcase, default is false
  "status": {/*mapping pass and fail status*/
    "pass": "PASSED",
    "fail": "FAILED"
  },
  "exeDate": null //must be formatted as yyyy-MM-dd,
  "modules":[] //module names
}

Usages

  • -C: to generate config file, then you should see and update config.json at current working directory

  • -c: to parse from xml file

  • -s: to submit logs to qTest

  • -d "<dir>": to parse xml files in dir

  • -r: to filter file by pattern: .xml or TEST-.xml

  • -M: each method as test case

  • -n: submit with new API

Examples

  • Parse junit xml file in config file:');
  • log2qtest -c
  • Parse and submit logs to qTest with API v3.1:');
  • log2qtest -c -s
  • Parse and submit logs to qTest with API new:');
  • log2qtest -c -s -n