LL-277

[KevinLemon112]

Description

In this new PR/Ticket, unit tests for the Publish and Subscribe features for the ActiveMQ notification service have been created and tested.

Subsequent # (issue): LL-277

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Steps (For Local Host):

1. Be in the server/src/notification/publish OR server/src/notification/subscribe directories to test each unit test separately
2. Run "npm i" if needed in each directory (as well as the root directory)
3. Run "npx jest" in the terminal to test the unit test for the directory you are in.

Checklist (when relevant):

• My code follows the style guidelines of this project

TypeScript
Python
Schema

• I have included a reviewer on the pull request [Replace this text with the reviewer]
• I have performed a self-review of my own 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 unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[pogi7]

@KevinLemon112 I think this request should be mocked. Please refer to this stack overflow article as an example of how to mock requests to an ExpressJS Server.
https://stackoverflow.com/a/72674717

[Verus20]

@KevinLemon112 the tests work nice job! recommendation: In the How has this been tested stage, I'd recommending adding a step to run npm i from the root directory of the server (i.e the folder before src)

This is because I was running into errors with jest and then running npm i from the root folder got the tests to work