[GH-ISSUE #631] [DevTaskl] Add unit test coverage info #190

Closed
opened 2026-10-31 22:09:52 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @robinjhuang on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/631

Used to be in jest.config.ts but now is not generated in vitest.

┆Issue is synchronized with this Notion page by Unito

Originally created by @robinjhuang on GitHub (Jan 16, 2025). Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/631 Used to be in `jest.config.ts` but now is not generated in vitest. ┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-631-DevTaskl-Add-unit-test-coverage-info-17d6d73d365081ee9b58ee3d1e68c251) by [Unito](https://www.unito.io)
Author
Owner

@webfiltered commented on GitHub (Jan 16, 2025):

Context: Migration of this required additional effort, and the jest impl. was throwing errors. Original task to reimpl. was created offline but has not been progressed.

<!-- gh-comment-id:2594754935 --> @webfiltered commented on GitHub (Jan 16, 2025): Context: Migration of this required additional effort, and the jest impl. was throwing errors. Original task to reimpl. was created offline but has not been progressed.
Author
Owner

@dosubot[bot] commented on GitHub (Apr 17, 2025):

Hi, @robinjhuang. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You raised a concern about the absence of unit test coverage information after switching from Jest to vitest.
  • User webfiltered mentioned that migrating this feature required additional effort due to errors with the Jest implementation.
  • An offline task was created to address the issue, but there has been no progress yet.
  • You reacted positively to the comment about the offline task.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the desktop repository by commenting here.
  • If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

<!-- gh-comment-id:2813431723 --> @dosubot[bot] commented on GitHub (Apr 17, 2025): Hi, @robinjhuang. I'm [Dosu](https://dosu.dev), and I'm helping the desktop team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You raised a concern about the absence of unit test coverage information after switching from Jest to vitest. - User webfiltered mentioned that migrating this feature required additional effort due to errors with the Jest implementation. - An offline task was created to address the issue, but there has been no progress yet. - You reacted positively to the comment about the offline task. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of the desktop repository by commenting here. - If there is no further activity, the issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/desktop#190
No description provided.