Tell us what’s happening:
The FCC tests for this project do not pass on replit - timeout error - but they do pass on localhost (http://localhost:3000/). But, the project does not move to completion. It stays on the same page -
Thanks for repsonding. Looks like we have to wait if this has to be tested in replit or Glitch. But, why when tested on localhost and the fcc tests pass, did the project not get marked for completion?
It is possible to get the tests to pass from replit sometimes.
Try stopping your repl and then submitting the link to FCC.
This will restart the repl and the tests MAY pass on FCC before the repl crashes again.
Alternatively, start the repl and quickly submit the link on FCC when you see the ‘Tests running…’ message in the repl console.
It sometimes takes a few tries to time it so that FCC passes the tests before the repl crashes.
I have successfully completed all of the QA projects on replit, using this method where necessary.
The functional tests seem pretty broken on Replit (chai-http and zombie). I had to use Glitch as well last when I tested one of the projects with functional tests (the library QA project).
@camperextraordinaire I haven’t tested it but I’m not sure Replit does have that same issue with the invalid request test. I remember seeing a thread where you noticed that happening on Glitch, but I don’t remember ever seeing it being an issue with Replit. It might have to do with how any server redirects are set up on the specific server (i.e. how it handles an invalid path with //)
Edit: I remember looking at that test and thinking it wasn’t really a good test for an invalid request. So maybe the test should be changed no matter what.
