mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #4136] Revisit existing unit tests for the CLI #1485
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1485
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jamesgeorge007 on GitHub (Jun 20, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4136
Originally assigned to: @SnazofSnaz, @mikeng07, @Nicktochme on GitHub.
Description
Various unit tests exist for the CLI, but they are disabled at the moment because they were found flaky. They need to be revisited, and necessary updates (migrating to the Vitest set of APIs, resolving failed assertions, etc.) must be performed to be made part of the CI pipeline.
Also, #4095 introduced unit tests for the newly added functionality and migrated the test runner from Jest to Vitest, bringing in better ESM support.
@VISHESH0932 commented on GitHub (Oct 14, 2024):
@jamesgeorge007 , I would like to work on this issue.
@SanskritiHarmukh commented on GitHub (Oct 26, 2024):
Hey @VISHESH0932 , I wanted to check in for an update. Have there been any progress on this?
@saifkp517 commented on GitHub (Nov 4, 2024):
Hi @jamesgeorge007
I’m interested in working on this issue. I have recently started contributing to open source and would love to help revisit the existing unit tests for the CLI. Please let me know if I can take this on!
Thank you!
@SanskritiHarmukh commented on GitHub (Nov 4, 2024):
Hi @saifkp517 , thank you for your interest! Currently, the issues labeled with
codedayare reserved for a specific open-source partnership program we're collaborating with. If you’re part of that program, please let me know, and I’ll be happy to guide you. If not, please feel free to explore other open issues that are open for contributions.If this issue remains unassigned for a while, I’ll reach out to see if you’d be interested at that time.
@SnazofSnaz commented on GitHub (Nov 11, 2024):
Hey, I'm working on this with Mike Nguyen, Nick Toch, and our mentor Kevin Cardona through codeday.
Sorry @saifkp517 your Earnestness is ♥️ happy coding 🌈
@SanskritiHarmukh commented on GitHub (Nov 11, 2024):
Hi, can you mention other contributor's username, so that I can assign the issue?
@SnazofSnaz commented on GitHub (Nov 11, 2024):
Hi, sorry I don't have that information - I hope they will respond when they see this thread, will inform to if not at first meeting.
@mikeng07 commented on GitHub (Nov 11, 2024):
Hi there, It's Mike here. Thanks @SnazofSnaz
@Nicktochme commented on GitHub (Nov 12, 2024):
Hello, this is Nick one of the other people to be assigned.
@larsswenson commented on GitHub (Jan 27, 2025):
I'm working on this
@TVW96 commented on GitHub (Jan 31, 2025):
Helping out on this project, as well. Will be reviewing and fixing failed unit test with assistance from some main developers here as needed.
@TVW96 commented on GitHub (Feb 2, 2025):
@jamesgeorge007 @SanskritiHarmukh Anyone willing to meet with me and discuss this issue?
@jamesgeorge007 commented on GitHub (Feb 4, 2025):
Hi @TVW96, there is already a PR up on this front. Were you collaborating on the
CodeDaypartnership program?@TVW96 commented on GitHub (Jun 26, 2025):
@jamesgeorge007 I am or was but had issues with loading the project in my local which I solved after posting about it in the discussion board.
Would it be possible for me to continue working on this issue?
@kspoojith commented on GitHub (Jun 26, 2025):
Hi! I'm new to open-source and would love to work on this issue. Could you please assign it to me?
@mikeng07 commented on GitHub (Jun 26, 2025):
Hi @jamesgeorge007, we previously worked on this issue but could not complete it. Can I try it again?
Hi @TVW96 , can I join with you ?
@ManishPrakkash commented on GitHub (Jul 26, 2025):
Hellow guys,
Iam intrested to work on this can you assign this to me.👾
@ugec67 commented on GitHub (Jul 28, 2025):
Hi! I'd love to work on this issue . Let me know if it's available. Thanks!
@RajaVarmaGVSSR commented on GitHub (Sep 30, 2025):
Hi, I'd love to help with this issue if it's still available.
@makandcheezy commented on GitHub (Jan 28, 2026):
I'd love to work on this if still available!
@VishwaVikas2006 commented on GitHub (Mar 12, 2026):
Hi, I would like to work on this issue.
@raahthor commented on GitHub (Mar 12, 2026):
Hey, I would like to work on this issue.