💥 Mock WebSockets and create chaos 💥
JavaScript HTML
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
demo Add demo gif Nov 4, 2016
src Pass options down to runloop Oct 27, 2016
test Improve coverage Oct 27, 2016
.gitignore Wip Oct 23, 2016
.travis.yml Setup Travis CI Oct 27, 2016
README.md Change motto Nov 4, 2016
package.json Change motto Nov 4, 2016

README.md

Build Status npm version 💣 ⚡️ 💥 🔥 😈

Mock WebSockets and create chaos DEMO

The motivation of this project is nothing but being able to receive predefined socket messages. Why this? usually when integrating and testing web sockets in your app it happen that you have no control over the messages you are getting. This leads to slow iterations, like having to test you app against a real source of messages (production) or not doing it at all...

Chaosocket aims to provide you a set of tools to test this sort of behaviours, also it respects the WebSocket interface, making this transparent to you, this means that you don't have to modify your code at all when you introduce the library in your app. So it's perfect for simple scenarios like what happen when the user name is longer than 50 chars? to complex ones in which you want to stress your UI with 20 messages per second.

Defining chaos boundaries 📐

Chaos registration

const chaos = require('chaosocket');

chaos.register(() => {
  return {
    type: 'connection',
    user: {
      name: 'Hector'
    }
  };
});

chaos.listen();

Socket usage

const socket = new WebSocket('ws://0.0.0.0:8080');

socket.onmessage = function(e) {
  const msg = JSON.parse(e.data);

  console.log(msg.type, msg.user);
};

Chaosocket will call your message callback by time to time depending in some factors with the result of your registration.

Frequency

Sometimes you want to receive more events from a specific type, you achieve that by specifying the frequency of the registration. Default value is medium and the available ones are low, medium and high. Based on it chaosocket will emit events more or less often.

chaos.register(() => {
  return {
    type: 'connection'
  };
}, 'low');

chaos.register(() => {
  return {
    type: 'typing'
  };
}, 'medium');

chaos.register(() => {
  return {
    type: 'message'
  };
}, 'high');

Delay

This will change the default delay (2000ms) to 500ms forcing the app to handle x4 more events.

chaos.listen({
  delay: 500
});

Stop chaos ⛔️

Tired of chaos? just close it and the socket will stop to recieve fake messages.

chaos.close();

## Using Faker 👻 Chaosocket comes with Faker, a library to generate fake and random data easily, it's passed to the register method.

chaos.register((faker) => {
  return {
    create_at: faker.date.recent(),
    event_name: faker.random.arrayElement(['connection', 'typing', 'message']),
    first_name: faker.name.firstName(),
    last_name: faker.name.lastName(),
    bio: faker.lorem.text()
  };
});

You can find all Faker methods here https://github.com/marak/Faker.js/#api-methods

Demo 🚀

Just a simple chat using the library

Installation 🔧

$ npm i chaosocket -D

Dependencies 🙇

## Author 👱

Hector Zarco @zzarcon