| #! /usr/bin/env python | |
| #-*- coding: utf-8 -*- | |
| import json | |
| import httplib2 | |
| from datetime import datetime | |
| from apiclient.discovery import build | |
| from oauth2client.client import OAuth2WebServerFlow |
| #(define mydrums '( | |
| (bassdrum default #f -3) | |
| (snare default #f 1) | |
| (hihat cross #f 5) | |
| (halfopenhihat cross "halfopen" 5) | |
| (pedalhihat xcircle "stopped" 2) | |
| (lowtom diamond #f 3) | |
| (crashcymbal cross #f 6))) | |
| up = \drummode { hh8 hh hhho hhho hhp4 hhp } |
On the Refinery29 Mobile Web Team, codenamed "Bicycle", all of our unit tests are written using Jasmine, an awesome BDD library written by Pivotal Labs. We recently switched how we set up data for tests from declaring and assigning to closures, to assigning properties to each test case's this object, and we've seen some awesome benefits from doing such.
Up until recently, a typical unit test for us looked something like this:
describe('views.Card', function() {
| // float->half variants. | |
| // by Fabian "ryg" Giesen. | |
| // | |
| // I hereby place this code in the public domain, as per the terms of the | |
| // CC0 license: | |
| // | |
| // https://creativecommons.org/publicdomain/zero/1.0/ | |
| // | |
| // float_to_half_full: This is basically the ISPC stdlib code, except | |
| // I preserve the sign of NaNs (any good reason not to?) |