⭐: Unit Tests / TDD

[paulywill]

User Story

There are some on-going unit tests / or some TDD taking place behind the scenes

Acceptance Criteria

Every run/build some unit tests are run to ensure we're keeping working state as we're building features; integration tests to also ensure major components are tied together correctly

Definition of Done

This would ideally on-going through the rest of the project and epic, however, if there are unit tests and integration tests for each of the following below that should cover at least a few bases:

• React unit/integration testing (Jest/Enzyne? )
• Expressing testing?
• MongoDB testing?
• hosting?
• usage limits? free tier?
• traffic monitoring?

[paulywill]

The short time period I'm not sure introducing TDD into the mix is ideal.

There's some ideas I thought we could try from obeythetestinggoat.com

This is a rather new way of coding for me other than looking at a tutorial and diving right in. At least having or learning to create a few unit test and maybe an integration test would be useful later on.

[paulywill]

Research:

• https://blog.usejournal.com/jest-vs-mocha-whats-the-difference-235df75ffdf3
• https://semaphoreci.com/community/tutorials/a-tdd-approach-to-building-a-todo-api-using-node-js-and-mongoldb
• https://medium.com/@jodylecompte/express-routes-a-tdd-approach-1e12a0799352
• https://github.com/FrontendMasters/api-design-node-v3

[paulywill]

The consensus appears to be that Jest is easy to start using immediately, and Moch/Chai takes a bit of setting up.

[paulywill]

@patricktownley Are you interested writing up some unit test with me?

[paulywill]

I would to take a stab at this again with Jest.

[paulywill]

Just starting to make tests for another project.

Once I complete a few tests there I'll start generating some here.