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

@beanbag/jasmine-suites

v2.0.0

Published

Namespaced, merged suite names for Jasmine.

Downloads

19

Readme

Namespaced Jasmine Suites

Overview

This extends Jasmine 4.6+ by making it easy to create nested, reusable namespaces for test suites.

Typically, a large codebase using Jasmine will split tests into multiple files, each with a describe() call wrapping the file's tests. This works fine for small sets of tests, but on a larger codebase, it leaves much to be desired. There's no way to organize tests across files under a common suite, or to limit the test run to those tests.

Namespaced suites solve this by taking a namespaced path (something like projectname/mysuite/component) and automatically generating test suites for each component of the namespace.

It will also merge any tests in that refer to the same parts of the namespace from other files.

Usage

Switching to namespaced suites is really easy. Instead of doing this:

describe('projectname/mysuite/component', function() {
    ...
});

or:

describe('projectname', function() {
    describe('mysuite', function() {
        describe('component', function() {
           ...
        });
    });
});

You can instead do:

suite('projectname/mysuite/component', function() {
   ...
});

You can reuse any part of that namespace in as many files as you like. Their tests will be combined into the suites.

For example, say you have the following:

// tests1.js
suite('projectname/models/MyModel', function() {
   ...
});

suite('projectname/views/MyView', function() {
   ...
});


// tests2.js
suite('projectname/views/AnotherView', function() {
   ...
});

Jasmine will end up laying out the tests like:

projectname

    models

    views

        MyView

        AnotherView

Where is this used?

We use jasmine-suites at Beanbag for our Review Board and RBCommons products.

If you use jasmine-suites, let us know and we'll add you to a shiny new list on this page.

License

Jasmine Suites is under the MIT license.