balderdashy / balderdashy/sails

Port in use when trying to run tests

Open
#6,883 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

helpful info or workaround question
Dominant language
JavaScript
Stars
22.8k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

Node version: v10.16.0
Sails version (sails): 1.2.3
ORM hook version (sails-hook-orm): 2.1.1
Sockets hook version (sails-hook-sockets):
Organics hook version (sails-hook-organics):
Grunt hook version (sails-hook-grunt): 4.0.0
Uploads hook version (sails-hook-uploads):
DB adapter & version (e.g. sails-mysql@5.55.5):
Skipper adapter & version (e.g. skipper-s3@5.55.5):


Hey y'all,

My issue is when running the app I can't run my tests as it kept failing saying the PORT is in use. I believe that should not be the case as running the tests should lift(if it needs to be) on a different PORT, but unfortunately there is no documentation about it.
Matter of fact the documentation about kickstarting a SailsJS project is quite poor IMHO.

How can I fix that tests issue?

Thanks in advance

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or test entry points are named. Reproduce the failure with Node v10.16.0, Sails 1.2.3, and the reported test command, then trace how the test app obtains its port and determine whether the port conflict requires a configuration change or documentation update.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.