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

oj-test-runner

v1.2.1

Published

OJ test cases runner

Downloads

2

Readme

oj-test-runner

JS test cases runner for OJ things.

Install

  • npm install -g oj-test-runner

Usage

Folder mode

run-test YOUR_SCRIPT TESTS_FOLDER

  • YOUR_SCRIPT: your solution js file
  • TESTS_FOLDER: folder that contains all test cases

test cases & answers inside folder are formed as:

  • ${testCaseNumber}: test case
  • ${testCaseNumber}.a: expected output

all intergers are valid, doesn't need to be in sequence

e.g: folder tests contains four files 1, 1.a, 2, 2.a.

when executing run-test ./my-solution.js tests

tests/1 will be piped to ./my-solution.js's stdin and it's stdout will be used to diff with 1.a to check if the output is valid.

then tests/2 with tests/2.a

Stress test mode

run-test CORRECT_SOLUTION FAST_SOLUTION TEST_CASE_GENERATOR PRINT_TESTCASE

  • CORRECT_SOLUTION: the slow but correct solution script
  • FAST_SOLUTION: your fast final solution script
  • TEST_CASE_GENERATOR: a script that exports a function that will generates a new test case per execution.
  • PRINT_TESTCASE_DESC: if true, print out test case, regarded as false if not given