v.1.0 homework - Quality

[basilesimon]

See issue #29 for guidelines.

• We need tests. Proper tests.
• The program must follow the conventions.

[basilesimon]

Refers to #21 and #19

[jlevesy]

https://github.com/jlevesy/datastringer/tree/RestDS
Introduces some tests and refactor stuff.
Still work in progress.
Please have a look :)

[iaincollins]

@jlevesy This looks great :)

[jlevesy]

Cool !
Please keep an eye, because I'm doing a lot of split / refactor... So if you see something weird or bad, just tell me !
Do you want me to open a pull request ? To keep you informed of my work ?
Cheers !

[basilesimon]

@jlevesy Yes, if you could keep us updated when something major happens and when it's ready to go, it would be great, mate!

[jlevesy]

@basilesimon Sure I'll, but what about some code review just now ?
At the moment I'm making choices on my own and I think this is not the right way to work together, and I don't want all this work to be screwed up because I made bad / not understood choices.

For instance:

• Is the formalism (BDD, mocks, stubs and so on...) I chose for unit tests sounds ok to you ?
• What do you think about splitting utils module into assets one(to manage local assets and maybe one day a database) and contents (to fetch content form a remote source) ?

... and so on :)

So, please, can I have some review when you get some time ?
(ping @Cgg too)

BTW, what do you think about organizing some Datastringer coding session ?

Cheers !

[basilesimon]

Let's summon @iaincollins !

[jlevesy]

Ping ?