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

morx-cha

v0.0.7

Published

Auto-creation of test suites

Downloads

280

Readme

🌵🌴A simple Experiment🌴🌵

Imagine it is possible to auto-create tests from specs defined for your Services / Endpoint routes.

A couple of assumptions about the basic things we write tests for :

  • We test to assert that required values are supplied.
  • We test to assert that required values are supplied and that they are correct e.g. valid email e.t.c.
  • We test to assert thatt required values are supplied, they are correct and the correct action taken / response gotten.

The above three form at least 65% of test coverage for any given service / endpoint / controller. Using morx, it should be pretty easy to auto create test-suites for the 3 things above (given no further customizations are needed). If further customizations are needed, the framework that will use morx to create these tests can be made flexible enough to account for the customizations.

A typical morx spec declaration looks like this:

var morx = require('morx');
var spec = morx.spec() //Begin spec-ing parameters
           .build('id', 'required:true, map:user_id')
           .build('username', 'required:true')
           .end(); //End parameter spec-ing

With the above alone, we can create a test suite that asserts the validation of required parameters for whichever service uses the spec.

Still considering this spec:

var morx = require('morx');
var spec = morx.spec() //Begin spec-ing parameters
           .build('id', 'required:true, map:user_id, eg:123, eg_invalid:abc')
           .build('username', 'required:true, eg:glentworth, eg_invalid:1111')
           .end(); //End parameter spec-ing

We can add additional properties to make our auto-test suite creation slightly easier: eg : Valid expected data for the said parameter eg_invalid_data : Sample wrong data for said parameter e.g. wuejdhsh in place where a valid email is required

Combine the above with moir to generate random values for every test suite needed. See example here