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

min-karma

v3.0.0

Published

Minimal Karma Runner setup

Downloads

123

Readme

min-karma

Minimal Karma runner Setup and Package — Start testing now!

npm version Build Status Code Climate Dependency Status Commitizen friendly

PRs Welcome MIT License npm downloads

js-standard-style

Other minimal setups

And their combinations:

Karma

Karma is a JavaScript Test Runner, one of the most popular and friendliest for beginners. The most notable advantage of Karma is testing in real browsers. See my StackOverflow answer for more information about Karma usage.

On the AngularJS team, we rely on testing and we always seek better tools to make our life easier. That's why we created Karma - a test runner that fits all our needs.

Why?

  • Many setups are bloated with unnecessary options and packages.
  • Start clean and minimal and extend as you go.
  • Add single package to your project instead of many, to get your tests up and running.

Use cases

Features

  • [x] Minimal functional Karma config file.
  • [x] Use as repository (git clone) or package (npm install).
  • [x] Installs all testing packages as dependencies, no need to install them manually.
  • [x] Includes Chrome and Firefox launchers (but many other browsers are also supported).
  • [x] Automatically and gracefully (without overwriting) copied to your project directory via gently-copy:
    • [x] Basic testing example inside demo folder.

    • [x] Minimal functional configuration file karma.conf.js (will not install if karma.conf.js is already present):

      module.exports = function (config) {
        config.set({
          frameworks: ['jasmine'],
          files: [
            'demo/**/*.js'
          ],
          browsers: ['Chrome']
        })
      }

If you are new to Node

Download and Install Node.js, see How do I get started with Node.js for more information.

To use as separate Repository:

Clone

git clone https://github.com/dmitriz/min-karma

or simply Download this Repository, unzip it and cd min-karma-master.

Install dependencies

npm install --save-dev

To use as Package (add to your project):

In your main project directory (should contain package.json):

npm install min-karma --save

Getting started

Run your tests:

karma start

Now try to edit files inside demo folder and see how karma is watching and updating your test results.

Basic testing demo — inside demo folder

// function to test
function add (a, b) {
  return a + b
}

// the test
describe('Addition', function () {
  it('should add numbers', function () {
    expect(add(2, 4)).toBe(6)
    expect(add(2, 4)).not.toBe(2)
  })
})

Tip. Keep your tests next to their testees for better cohesion. Avoid putting them into separate folders (like tests) away from your code.

Enjoy! :tada: