Looks like the Travis build failed. Can you run tests locally and see what the issue is?

Not sure. Running tests locally seems to be fine. Note - I'm pretty new to javascript so I hope the below output looks right....

pi@raspberrypi ~/node/node_modules/elkington $ npm test --verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'test',
npm verb cli '--verbose' ]
npm info using npm@1.4.28
npm info using node@v0.10.32
npm verb run-script [ 'pretest', 'test', 'posttest' ]
npm info pretest elkington@0.1.0
npm info test elkington@0.1.0

elkington@0.1.0 test /home/pi/node/node_modules/elkington
mocha --reporter spec

messaging
#getWordCommands
✓ should return an array (46ms)
✓ should return an array of two for 'intruder alert' (55ms)
#writeTextDescriptionsMessage
✓ should return the right message formated for type and zone

parser
#parseMessage
✓ should return unknown for '9999999999999999999'
✓ should parse 'Request Ethernet test' message ok
✓ should parse 'Arming Status' message ok
✓ should parse 'Alarm Reporting' message ok
✓ should parse 'Zone change update' message ok
✓ should parse 'Control output change update' message ok
✓ should parse 'User code areas report data' message ok
✓ should parse 'PLC change update' message ok
✓ should parse 'Text string description report data' message ok

towords
#calc
✓ should return a single word for a single digit (49ms)
✓ should return a single word for a 10 to 19
✓ should return a single word for a 20, 30, 40...90
✓ should return two words for 22 and 84
✓ should return 'one hundred one' for 101
✓ should return 'one hundred twenty one' for 121
✓ should return 'two thousand four hundred eighty three' for 2483
✓ should add a point for decimals

20 passing (659ms)

npm verb unsafe-perm in lifecycle true
npm info posttest elkington@0.1.0
npm verb exit [ 0, true ]
npm info ok