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

newman-reporter-ros-scenario

v1.0.0

Published

A modified JUnit Newman reporter for use with GTest and ROS

Downloads

1

Readme

newman-reporter-ros-scenario

A modified JUnit newman reporter designed for use with ROS and C++ GTest

Overview

This reporter is to help produce Newman JUnit output which aims to be closer in syntax to the JUnit XML produced by GTest, and to help facilitate the generation of test reports which emulate external manipulations of a long-running stateful machine (like a robot)

The main difference between this reporter and the stock JUnit one is with what Postman elements match to which JUnit elements.

| JUnit Tag | Stock reporter | ros-scenario | ROS GTest | | --------------- |-------------------|------------------|-------------------------| | testsuites | Collection | Collection | All Tests in a ROS Test | | testsuite | Folder/Request | Folder | TEST(__Suite__, Name) | | testcase | Each pm.test | Request | TEST(Suite, __Name__) | | failure | pm.test details | Failed pm.test | EXPECT*, ASSERT* |

To allow for this sort of match up, this reporter requires your collection to conform to a Collection structure. Each Request must be contained in a Folder, which is contained in the root of the Collection. Your Collection should look something like this:

|_____ Folder1 _____ Request11
|             |
|             |_____ Request12
|             |
|             |_____ Request13
|
|_____ Folder2 _____ Request21
              |
              |_____ Request22
              |
              |_____ Request23

Any requests that don't fit this structure will still be executed, but their results will not be recorded.

Given that HTTP API manipulations in ROS are likely emulating control from a C&C server or user signals from an external application, these Folders can sensibly represent a long running external interaction process you wish to test. This was the intended use case for its use in this CI project.

Options

--reporter-ros-scenario-export {PATH}.xml or just --reporter-export {PATH}.xml will allow you to set the output destination file, same as the original.

Acknowledgements

The original JUnit reporter which this was derived from.