Mayank Bhola psych0der

The Ultimate Unit Testing Cheat-sheet

For Mocha, Chai and Sinon

using mocha/chai/sinon for node.js unit-tests? check out my utility: mocha-stirrer to easily reuse test components and mock require dependencies

Sinon Chai
Chai
Sinon
Mocha

Status

READY/IN DEVELOPMENT/HOLD

Migrations

YES | NO

Description

A few sentences describing the overall goals of the pull request's commits.

Related PRs

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	#!/usr/bin/env python

	"""
	Modified from

	http://macscripter.net/viewtopic.php?id=26675
	http://apple.stackexchange.com/questions/90040/look-up-a-word-in-dictionary-app-in-terminal

	HowTo

	function copyFbRecord(oldRef, newRef) {
	oldRef.once('value', function(snap) {
	newRef.set( snap.value(), function(error) {
	if( error && typeof(console) !== 'undefined' && console.error ) { console.error(error); }
	});
	});
	}

	# Configuration file for runtime kernel parameters.
	# See sysctl.conf(5) for more information.

	# See also http://www.nateware.com/linux-network-tuning-for-2013.html for
	# an explanation about some of these parameters, and instructions for
	# a few other tweaks outside this file.

	# Protection from SYN flood attack.
	net.ipv4.tcp_syncookies = 1

	#!/usr/bin/env bash
	ENV_PATH="$(dirname "$(dirname "$(which pip)")")"
	SYSTEM_VIRTUALENV="$(which -a virtualenv\|tail -1)"

	echo "Ensure the root of current virtualenv:"
	echo " $ENV_PATH"
	read -p "‼️ Say no if you are not sure (y/N) " -n 1 -r
	echo
	if [[ $REPLY =~ ^[Yy]$ ]]; then
	echo "♻️ Removing old symbolic links......"

	'''
	A python script which starts celery worker and auto reload it when any code change happens.
	I did this because Celery worker's "--autoreload" option seems not working for a lot of people.
	'''

	import time
	from watchdog.observers import Observer ##pip install watchdog
	from watchdog.events import PatternMatchingEventHandler
	import psutil ##pip install psutil
	import os

	#!/bin/bash

	sudo kextunload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport
	sudo kextload -b com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport