[TEST] Add API client tests for request timeout and abort behavior

[utksh1]

Problem

The frontend API helper owns request timeout and abort behavior, but there is no focused coverage for timeout cleanup, abort propagation, or non-OK HTTP errors.

Expected behavior

The API helper should have direct unit tests for timeout/abort and failed response paths so future fetch changes do not regress cleanup or error handling.

Acceptance criteria

• Add tests around frontend/src/api.ts request behavior through exported API functions.
• Cover a successful response, a non-OK response, and an aborted/timeout path.
• Use fake timers where appropriate and restore mocked fetch/timers after each test.

[HitanshiThakar]

hi @utksh1 , I would like to work upon this issue under GSSoC'26.
I recently contributed to this project and I'm familiar with the codebase .
Kindly assign it to me.
Thank you!

[eshaanag]

Hi @utksh1, I can work on this under GSSoC if it is available.

I checked frontend/src/api.ts and the existing frontend test layout. The helper currently creates an AbortController, sets a 10s window.setTimeout, passes controller.signal into fetch, and clears the timeout only after fetch resolves. There is also 401/non-OK handling in the same helper, but I do not see focused tests around those request paths yet.

My plan would be to add a dedicated unit test file around exported API functions such as getHealth() / listPlugins() so the private helper is still tested through public API behavior:

• mock global.fetch and use fake timers for the timeout path;
• verify successful JSON responses clear the timeout and return parsed data;
• verify non-OK responses reject with the expected status error;
• verify timeout-driven abort calls the fetch signal path and does not leak fake timers;
• restore fetch and timers after each test so the rest of the frontend suite stays isolated.

I will keep the PR scoped to tests unless the tests expose a small cleanup bug in the helper itself.

[Rakshak05]

Hello @utksh1, i would like to work on this. Can you please assign it to me under GSSoC'26 contributor!?

[ask-z4ch]

/assign

Hi @utksh1, I would like to work on this issue under GSSoC 2026.

To resolve this, I plan to:

• Add focused unit tests for the internal request<T> function in frontend/src/api.ts:86-98, which currently lacks coverage for timeout cleanup (setTimeout/clearTimeout), abort propagation (AbortController.signal), and non-OK HTTP error paths.
• Create frontend/testing/unit/api.test.ts with three test cases (successful JSON response, non-OK response throwing Request failed: {status}, and abort/timeout via AbortController), using vitest, vi.stubGlobal('fetch'), vi.useFakeTimers(), and cleanup in afterEach.
• Ensure the code matches the project's formatting and styling rules without adding redundant imports.
• Manually verify and test the updated execution path to guarantee zero regressions.

I will have a clean pull request raised within 24 to 48 hours!

[vyshali-arc]

Hi @utksh1, I reviewed this issue and would be happy to work on it under GSSoC '26 if it is available. Thank you!