Update auth tests to more closely match signup requirements #2142
Conversation
|
Writing these tests was much more involved than I was planning on originally. To get this to work, I had to add an nginx container in development to serve static content to both the tests (http://localhost:8888) and the docker containers (http://test-web-content). I also had to make the e2e tests always run in sequence vs. parallel, because the auth/signup tests depend on shared user accounts, and updating the data in parallel tests at the same time leads to random test failures. cc @birtony, who is thinking about configurations for Jest, and @c3ho who has to write tests for the parser service. The way I'm hosting the blog/feed in this PR could be used to test the parser service too, since it can connect to this web host running in docker to simulate download content. You can easily add more and different types of static content for new tests. |
Debugging the new signup flow with @PedroFonsecaDEV and @DukeManh last night made me realize I should expand the signup e2e test to better match what we do in the front-end.
I'm not 100% sure if this will work on all platforms, since I have to use http://host.docker.internal vs. http://localhost in the test. I want to see how it performs on CI.