Feature/sprints test

[JoshuaHinman]

Description

• Added tests for all sprints routes
• Added jest-extended dependency to provide expect.toBeOneOf() and other useful functions

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature updates / changes
• Tests
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

yarn test:e2e sprints

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the change log

[cherylli]

Very thorough tests, all passed locally here. thanks!
just need to resolve that changelog conflict

[timDeHof]

very good structured tests but maybe label the test suites and specs to convey clearer intention of each unit test. I have added some suggestions for the describe and it blocks. I think it would make it easier for new developers to understand the intention of the unit tests.

I found this unit testing style guide that could help us keep a consist style to the tests.

changed

[timDeHof]

It's looking great. I have spotted a couple of it statements that could be written in a way that newcomers could understand the tests better.

[curtwl]

Looks good!

done