Automated Tests

[HSAR]

While the current lack of tests is acceptable given the speed at which Ficlatte was written, I would dearly like @ethel-t-frog to not have to do firefighting every time a new version is deployed. Now that he is no longer the sole developer it is only fair to push the burden of preventing failures onto each contributor; the best way to do this is to start up some automated testing.

Required:

• Investigation of an automated testing system
• Investigation of a (free) cloud-based continuous integration service
• Setting up infrastructure for developers to write tests
• Some documentation for contributors

[ethel-t-frog]

Sounds like a good idea. Django has a testing infrastructure built in, but I haven't investigated it at all.

[HSAR]

I've previously used a package called nose for testing with some success, and I know that there is a service called Travis which provides a free cloud-based CI for open-sourced projects such as this one.

[stitzelj]

This is somewhat of a new concept for me, so I expect I'll need some handholding until I become more familiar.

[HSAR]

We'll make it work. It should, ideally, be quite simple to understand.

[HSAR]

I intend to look at this so I can verify https://github.com/ficlatte/main/issues/4 under the "definition of done". Please assign to me.