Tests

[elijahverdoorn]

We should have them. That requires someone to write them.

[rye]

Other people are welcome to self-assign.

@elijahverdoorn and I spoke a bit today about putting together something using Jest for the frontend, and didn't really decide about Mocha + Chai vs Jest. I'd be down to use either; Jest in both places would probably be nicer.

Whatever solution we choose should probably have support for mocking—I'm not yet familiar enough with Jest to know one way or the other which is the better option. I've used a bit of Mocha in the past and it was somewhat nice.

Also, we should test as much as possible, and I think our general philosophy should be pessimistic as to what kinds of contexts we're in.

It'd be nice to put in some pending tests (just specs, no body) and then to actually write the body.

[rye]

Reading further, it looks like Mocha + Chai is more robust for business logic. We should, however, use Jest to test the client.

[rye]

For now, though, I'll try implementing the tests in Jest. It seems simpler and less convoluted than adding two separate dependencies.

[elijahverdoorn]

Take a look at supertest