davps / tic-tac-toe / 57

100%

push

travis-ci

Refactor tests by feature

Why? On TDD, I should start a new feature in this way, writing
aceptance tests by feature.

I did it in the inverse here, wrote the tests by feature later on,
but anyways, this will be helpful as a walking skeleton for future
features I could potentially add to this app.

So, my TDD process will start here, writing a new
src/App.test.feature.<FEATURE_NAME>.js file, then
extend the adaptors and DSL.js if I need new syntax additions on
my DSL if I need new syntax additions on my DSL, and then
start developing the feature (and writing the unit tests during
that process).

65 of 67 branches covered (97.01%)

Branch coverage included in aggregate %.

363 of 363 relevant lines covered (100.0%)

164.42 hits per line