You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Challenge anonymous-message-board has an issue.
User Agent is: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
I cloned this repo, added this line of code: process.env.NODE_ENV = 'test';
and then did "node server.js".
The server runs, but the tests don't seem to, i just get stuck with the following output: http://i.imgur.com/diPR6Jy.png
I can't see what the test parameters are or how to pass them, there's no output.
ps. the "listening on port undefined" warning isn't relevant, it's still listening on port 300, it's just a mistake in the console.log code
ps2. i'm not using glitch.io, all of these tests were done on my local machine, but it seems to be bugging on glitch too
The text was updated successfully, but these errors were encountered:
I'm closing this issue as stale since it hasn't been active lately. If you think this is still relevant to the newly updated platform, please explain why, then reopen it.
Challenge anonymous-message-board has an issue.
User Agent is:
Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
.Please describe how to reproduce this issue, and include links to screenshots if possible.
I cloned this repo, added this line of code:
process.env.NODE_ENV = 'test';
and then did "node server.js".
The server runs, but the tests don't seem to, i just get stuck with the following output:
http://i.imgur.com/diPR6Jy.png
I can't see what the test parameters are or how to pass them, there's no output.
ps. the "listening on port undefined" warning isn't relevant, it's still listening on port 300, it's just a mistake in the console.log code
ps2. i'm not using glitch.io, all of these tests were done on my local machine, but it seems to be bugging on glitch too
The text was updated successfully, but these errors were encountered: