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

@miqro/test

v0.2.9

Published

```npm install @miqro/test --save-dev```

Downloads

7

Readme

@miqro/test

npm install @miqro/test --save-dev

require mock

function requireMock(path, mocks, [wipeCache], [clearCache]): any

  • path: string path to the module file
  • mocks: object where the keys are the mocks path relative to the module file and as a value the module implementation.
  • wipeCache: string path that clears the require.cache before mocking
  • clearCache: boolean to clear require.cache the changes made before importing the module.

example

lib.js

module.exports.libFN = () => {
  console.log("real function");
}

file.js

import {libFN} from "./lib";

module.exports.someFunction = function someFunction() {
  libFN();
}

file.test.js

import {requireMock} from "@miqro/test";

const mockedFile = requireMock("./file.js", {
  "./lib": {
    libFN: () => {
      console.log("fake function")
    }
  }
});

mockedFile.someFunction(); // prints "fake function"

const notMockedFile = require("./file.js");

notMockedFile.someFunction(); // prints "real function"

clearRequireCache

import {clearRequireCache} from "@miqro/test";
import {resolve} from "path";

clearRequireCache(resolve(__dirname, "src/"));

fake function

import {fake} from "@miqro/test";

const cb = fake(() => {
  return 1;
})

strictEqual(cb(), 1);
strictEqual(cb.callCount, 1);
strictEqual(cb.callArgs[0].length, 0);
strictEqual(cb.returnValues[0], 1);

// cb.reset(); // resets callCount, callArgs and returnValues

test runner

npm install @miqro/test --save-dev

example

example.test.js

import {strictEqual} from "assert";

describe("some category", () => {
  describe("some other category", () => {
    before(async () => {

    });
    after(() => {

    });
    setTestTimeout(10000);
    setIsolate(true); // this will run "some test" in it's own node process
    it("some test", async () => {
        strictEqual(true, false, "todo empty test");
    });
  });
  it("some other test", async () => {

  });
})

cli arguments

recursive run *.test.js files

npx miqro-test test -r test/

run test files

npx miqro-test test/*.test.js

run test isolated into its own node process

npx miqro-test test/*.test.js -i

run test named tests

npx miqro-test test/*.test.js -n "testname"