Tests

[jbrooksuk]

Since Cachet is being developed to be deployed live (straight from master) it should at least go through some tests.

• Create test suite
• Link Travis CI

I'm not too worried about 100% coverage straightaway. We can spend time writing tests later on.

[Ehesp]

How far are we going in order to test the actual application, say via unit testing?

[jbrooksuk]

PHPUnit, mock tests, test for expected outputs etc.

[jbrooksuk]

The guys at @codeclimate have an awesome system for showing code coverage too.

[Ehesp]

Okay, quite a bit of work to do then on the controllers, DI etc.

[jbrooksuk]

Yeah, it's not a high priority but it would help catch any silly mistakes.

[Ehesp]

I think as the code has already been written I'll config Mockery to only allow existing methods on Mocked classes... Mockery::getConfiguration()->allowMockingNonExistentMethods(false);

[jbrooksuk]

@Ehesp I've setup Travis and the tests are now running.

[jbrooksuk]

We have a test suite coming along let's close this and just add tests as we go now.