Tests/teams unit tests

[JoshuaHinman]

Description

Unit tests for teams controller and services

Issue link

Fixes # 86azu6kwr

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:unit

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]

looks good, all new and existing tests passed, I suggest updating toHaveBeenCalled to toHaveBeenCalledWith() in a couple of places

[cherylli]

Thanks. re-run the tests with the new changes, all passed

[timDeHof]

Looks good! All unit tests passed!