https://github.com/heedrox/test-commit-revert-node
A node implementation of TCR (test, commit or revert), the TDD paradigm proposed by @KentBeck
https://github.com/heedrox/test-commit-revert-node
Last synced: about 2 months ago
JSON representation
A node implementation of TCR (test, commit or revert), the TDD paradigm proposed by @KentBeck
- Host: GitHub
- URL: https://github.com/heedrox/test-commit-revert-node
- Owner: heedrox
- Created: 2018-12-26T14:51:42.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-12-30T12:20:10.000Z (over 7 years ago)
- Last Synced: 2025-03-11T02:33:33.267Z (over 1 year ago)
- Language: JavaScript
- Size: 57.6 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# TCR Node Skeleton
A NodeJS skeleton to work with TDD with TCR (test commit || revert) constraint.
It uses Mocha + Chai + Sinon.
# About TCR
TCR (test, commit || revert), is a new way of developing, with similar basics to TDD. But with added constraints.
TCR forces you to make baby steps, through one constraint: every time tests fail, you must revert your code.
Learn more about this here:
https://medium.com/@kentbeck_7670/test-commit-revert-870bbd756864
# About TCR-CLI
tcr-cli is the command line interface I developed that has all the test && (commit || revert) logic.
# Usage
- npm run tcr
- Press "p" to push
- Press "q" to quit
- While editing files, test commit revert magic will happen.
# This repo
This repo is an attempt to make this TCR work in a real environment, using GIT.
The problem of TCR is that you are supposed to revert all the changes if your test fails.
What happens with your test, then? As you have probably noted, they will disappear :(
So you need to do some kind of tweaking to make this work in real life.
This is my proposed framework to make it a reality.