Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
All 34 API scenarios, same run, same message, no exceptions:
apiRequestContext.get: connect ECONNREFUSED 127.0.0.1:3000Yesterday they passed. I have not touched the features. Do I start bisecting the suite or is this something else?
Accepted answer
Do not bisect. Two signals in your paste say this is not the suite:
Nothing is listening on that port. Either the application is not running, or baseUrl in envs/local.yaml (or whichever env you selected) points somewhere the app no longer is. Start the app, or check the env file, and run again.
A suite that fails on assertions is telling you about the product. A suite that fails on connections is telling you about the environment, and that distinction saves an hour every time you respect it.
Adding the third category, since these three cover almost everything:
The workshop suggests stopping the application on purpose once, precisely so you recognise the second shape when it turns up at 3am.
If this keeps happening on a merge gate rather than locally, take the environment out of the equation: tag the scenarios @har:<name> and run with --har-replay --strict. Strict aborts any request that is not in the HAR, so the run is genuinely offline and a gate stops depending on somebody's staging box being awake.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.