mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4964] [bug]: test case failure of the Node.js CI / Test (lts/*) #1880
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#1880
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 @chhaviG22 on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4964
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Current behavior
I encountered an issue while working on a pull request that led to the Node.js CI / Test (lts/*) failing during the pull request checks.
To diagnose the problem further, I executed the command pnpm run test in the packages/hoppscotch-backend directory on the main branch. This test run revealed that one of the test cases failed.
For better clarity and assistance with troubleshooting, I have included a screenshot of the failed test case below:
Steps to reproduce
Logs and Screenshots
Environment
Production
Hoppscotch Version
Self-hosted
Interceptor
Not Applicable - Issue not related to network requests
Browsers Affected
No response
Operating System
None
Additional Information
No response
@mirarifhasan commented on GitHub (Apr 8, 2025):
@chhaviG22
In which branch (
main,next,patch) is the test case failing?@chhaviG22 commented on GitHub (Apr 8, 2025):
mainbranch@jamesgeorge007 commented on GitHub (Apr 9, 2025):
Hi, this is resolved on the
patchbranch. Could you verify once after pulling the latest changes?@chhaviG22 commented on GitHub (Apr 9, 2025):
@jamesgeorge007 verified. All tests are now successfully passing on
patchbranch. Thanks !@jamesgeorge007 commented on GitHub (Apr 10, 2025):
Thanks for confirming. This is now resolved on the default branch; closing.