Reaction SDK (JS): Add Jest & Unit Tests to the Reaction SDK

[amansinghoriginal]

⚠️ Contributor & GSoC Rules ⚠️

To ensure a fair and manageable process for all contributors (including Google Summer of Code applicants), please follow these rules:

1. Do NOT open a Pull Request unless you have been assigned to this issue. Unassigned PRs will be closed without review.
2. To get assigned: Leave a comment below explaining where in the codebase you will implement this, and a 1-2 sentence description of your approach. The maintainers will assign it to the first coherent proposal.
3. You may only be assigned to one "good first issue" at a time.
4. If there is no update within 4 days, we may have to reassign the issue to another contributor.

---

Area for Improvement

If you look at the package.json for the JavaScript Reaction SDK (reactions/sdk/javascript/package.json), running npm test currently just echoes "Error: no test specified".

The JavaScript SDK is entirely missing automated test coverage. This is a critical gap for an SDK that users rely on to build their own Drasi Reactions.

Desired behavior

The JavaScript Reaction SDK has jest installed, properly configured, and contains unit tests covering the core networking and utility classes.

[Acuspeedster]

Hey @amansinghoriginal
I’d like to work on this issue.
My plan is to implement the test setup in reactions/sdk/javascript by adding a Jest configuration and updating package.json so that npm test runs the test suite.
After setting up the test infrastructure, I will add unit tests for the core SDK classes:

• src/management-client.ts
• src/result-view-client.ts
• src/utils.ts

Network calls will be mocked so that both success and failure paths are covered.
The scope of the PR will be limited to test infrastructure and unit test coverage only, without modifying the existing SDK logic.

[Acuspeedster]

Also I have already opened #414 for #402.

[1Ninad]

Hi @amansinghoriginal sir, I would be happy to work on this issue.

My plan – install Jest with TypeScript support (ts-jest), add a minimal jest.config.js file, and write test files for all 4 SDK source files (utils.ts, management-client.ts, result-view-client.ts, index.ts). The tests use Jest's built-in fake functions in place of real network calls and real file reads.

[amansinghoriginal]

Thanks for the detailed proposal @1Ninad — assigning this to you!

Please keep us updated on your progress. As a reminder, if there is no update within 4 days we may need to reassign.

[amansinghoriginal]

Thanks for the proposal @Acuspeedster! Since you're currently assigned to #402 (with PR #414 open), we'll hold off here per the one-good-first-issue-at-a-time rule. Once #402 is merged, feel free to comment on any other open issue you'd like to pick up!

[1Ninad]

Thanks for the detailed proposal @1Ninad — assigning this to you!

Please keep us updated on your progress. As a reminder, if there is no update within 4 days we may need to reassign.

Thanks @amansinghoriginal sir for assigning this.
I have created a PR (#419) to address the issue. Please review.