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

tbob

v0.14.0

Published

Create example data for test cases. Inspired by rosiejs/rosie

Downloads

13

Readme

tbob

tbob is a test data builder inspired in particular by Rosie.

However, at some point tbob evolved into a different direction. We needed it to do more than "just" create test data. In our particular workflow, factory definitions serve as reference model of our data structures. From this model we want to create other stuff, like mappings for Elasticsearch. We want to be able to express type constraints, and a way to attach arbitrary metadata to any document type or attribute. Rosie's factory inheritance is fine, but we wanted something more flexible. All this comes at the cost of added complexity.

If generating test data is your primary concern, you are almost certainly better of with Rosie.

Disclaimer: This is work in progress. Before releasing v1.0.0 we need to

  • Document the DSL and the CLI

  • finalize and document the scenario formats

  • Give some examples of @meta-Annotations, and how those can be used to create ElasticSearch Mappings and other cool stuff.

Usage

First, you need to tell tbob what kind of documents it should create. You do this by defining factories, using tbob's own DSL:


module.exports = ->
  @factory "TodoList", ->
    @attr "owner"
      .type ->
        @attr "name"
          .type @string
          .fill "(owner name)"
        @attr "email"
          .type @optional @string

      
    @attr "items"
      .type @list @ref "TodoItem"
      .fill [{},{},{done:true}]

  @factory "TodoItem", ->
    @attr "id"
      .type @number
      .fill [], ->@world.docCount "TodoItem"
    @attr "title"
      .type @string
      .fill ["id"], (id)->"Title for item #{id}"
    @attr "done"
      .type @boolean
      .fill false

Next, you can run tbob like this

tbob -w examples/ '["TodoList"]'

it will create a json document populated with defaults:

{
   "items" : [
      {
         "done" : false,
         "title" : "Title for item 0",
         "id" : 0
      },
      {
         "title" : "Title for item 1",
         "id" : 1,
         "done" : false
      },
      {
         "done" : true,
         "title" : "Title for item 2",
         "id" : 2
      }
   ],
   "owner" : {
      "email" : null,
      "name" : "(owner name)"
   }
}

Let's assume for your test case you need a todolist with some particular values in it. You only specify the values that are different from their respective defaults:

tbob -w examples/ '["TodoList", {"items":[{"title": "Find better examples"},{},{"done":true}]}]'

The result would be:

{
   "owner" : {
      "email" : null,
      "name" : "(owner name)"
   },
   "items" : [
      {
         "title" : "Find better examples",
         "id" : 0,
         "done" : false
      },
      {
         "done" : false,
         "id" : 1,
         "title" : "Title for item 1"
      },
      {
         "title" : "Title for item 2",
         "id" : 2,
         "done" : true
      }
   ]
}