ReadMe.md

FizzBuzz TCR

Provoked by this post

Initilaization

• npm init .
• npm i -D mocha chai standard
• touch index.js and index.test.js
• package.json scripts for test, lint and pretest
• wrote a first test to check that tools works
• pbpaste > .gitignore
• git init and initial commit

Setting up commands for TCR

"commit": "git add -A; timestamp=$(date \"+%c\") && git commit -m \"TCR @ $timestamp\";",
"revert": "git reset --hard",
"tcr": "npm test && npm run commit || npm run revert"

/* global describe, it */
const assert = require('chai').assert

describe('Testing', () => {
  it('should work', () => {
    assert.isTrue(true)
  })
})

First test

Test:

describe('FizzBuzz', () => {
  it('returns "1" for 1', () => {
    const result = fizzBuzzer.single(1)
    assert.equal(result, '1')
  })
})

Production code:

module.exports.single = (number) => {
  return '1'
}

Feeling before tcr-command: NERVOUS! Will it run? Result: Passed and commit

Second test - fail

Feeling before tcr-command: Cocky! This will work... Result: Ah well...

• Set up the whole test. Pretty sure of myself... failed and reverted.
• No production code changed... Hence I returned a constant of 1. *And I even thought that I didn't change any production code to get this to work... hmmm... this feel strange
• Lost documentation too.

Second test - second run

Test:

  it('returns "2" for 2', () => {
    const result = fizzBuzzer.single(2)
    assert.equal(result, '2')
  })

Production code:

module.exports.single = (n) => {
  return n.toString()
}

Feeling before tcr-command: Careful optimistic but still held my breath during the run. Result: Passed and commit.

Refactor tests

Test:

  it('returns "1" for 1', () => {
    assert.equal(fizzBuzzer.single(1), '1')
  })
  it('returns "2" for 2', () => {
    assert.equal(fizzBuzzer.single(2), '2')
  })

Production code:

module.exports.single = (n) => {
  return n.toString()
}

Feeling before tcr-command: Very confident Result: Passed and commit.