Test: e2e tests for features

[Ajen07]

Description

• e2e test for features controller

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

[cherylli]

everything looks fine, just one minor suggestion so the error response matches the forbidden error

Also just a note all forbidden stuff will need to be moved to our CASL authorization, but shouldn't affect the tests. In fact it's good to have these tests now, so we know we don't mess up when updating it

[JoshuaHinman]

All tests passed - looks good

[cherylli]

thanks!

[timDeHof]

Looks good! All tests passed and swagger works.