Test/e2e tests for users

[Ajen07]

Description

• e2e tests for api/v1/users

Issue link

Fixes # (issue)

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?

Tested with yarn test:docker

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

[JoshuaHinman]

All tests passed

[cherylli]

thanks! everything looks good and all tests passed

[timDeHof]

Looks Great! All tests past.

on a side note: I wonder if it would be a good idea to update the PR template testing section to include a comment that remind reviewers to install new packages if the branch includes new packages.

[Ajen07]

Looks Great! All tests past.

on a side note: I wonder if it would be a good idea to update the PR template testing section to include a comment that remind reviewers to install new packages if the branch includes new packages.

Great suggestion , we can definitely do that.