Add project structure and first broken spec to parse 000000000 entry
Add more more broken test cases and mimic a ruby gem structure
Parse into 1s and 0s
Parse single numbers from 0 to 9
Simplify specs and finalize User Story 1
Support reading a file with codes, let the main parser handle the end of
line
Sort Parser methods in alphabetic order and idiomatic method rename of NumberParser#to_s
to NumberParser#parse
Validate account numbers check sums
When not able to parse a number print a ?, output result file after
parsing it
Return error codes instead of a boolean, look for error type instead of
validation status
Output parsing finding with status per entry
Leverage on Rubocop to follow most of the community ruby style guide
I tend to prefer code that can be read without any comments, but if I
have to comment and I can choice how to do it I like a *literate
programming* style and a tool like *docco*
Output code coverage together with the test suite
Move the documentation to the root in order to use them with github
pages