Test: unit test for features controller and services

[Ajen07]

Description

• Unit tests for Feature controller and Services

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

[github-actions]

@cherylli
One business day has passed since the review started. Give priority to reviews as much as possible.

[timDeHof]

All tests passed. But I added a suggestion for the dates for createdAt and updatedAt

[cherylli]

thanks. went through the code and ran all the tests, no issue.

[timDeHof]

Everything looks great. Thank you for making that change.