DOC: Jest warning shown after successful frontend tests (“Jest did not exit one second after the test run”)

[JITENDRAGAHERWAR03]

What's wrong with the existing documentation

Description:
When running PictoPy frontend tests, all tests pass successfully, but Jest still prints a warning about open async handles. This can confuse contributors into thinking something is wrong even when tests are green.

Environment:

OS: Windows 11

Frontend: React + Vite

Test runner: Jest

Steps to reproduce:

Go to frontend directory

Run:

npm test

Observed output:

Test Suites: 1 passed
Tests: 6 passed
Jest did not exit one second after the test run has completed.

Observed behavior:

All frontend tests pass

Application works correctly

Warning is printed after test completion

Expected behavior:

Either:

Jest exits cleanly, or

Documentation explains that this warning is harmless when tests pass

Why this matters:

New contributors may think frontend setup is broken

Creates unnecessary confusion during onboarding

Suggestion:

Document this warning in frontend testing docs

Or investigate async handles not being closed in tests

Add ScreenShots

No response

Record

• I agree to follow this project's Code of Conduct
• I want to work on this issue

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[pranitaurlam]

Hi @JITENDRAGAHERWAR03,

Thank you for raising this issue and for the clear details. The Jest warning shown after successful test execution can be misleading, especially for new contributors.

Adding a note in the frontend testing documentation to clarify this behavior, or investigating the underlying async handle cleanup, would help improve the contributor experience.

Happy to contribute once maintainers advise on the preferred approach.