Running e2e tests on Vercel previews #3765
-
|
I'm running e2e tests (Playwright) on Vercel previews when a new version is deployed. Now comes the part where I need to signing and I'm king of blocked because my enabled OAuth providers (Google, GitHub, Facebook) don't allow dynamic return URLs and it seems there's no way to bypass the email provider. I can't use Credentials provider either because I'm using What should I do here? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
Hey @balazsorban44, sorry to ping you. I'm just completely blocked on this issue. Do you have a clue? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the ping. Unfortunately, there is not much NextAuth.js can do about it, since this is a limitation of OAuth providers (be it unintentional or not). We recently created some guides on how to authenticate users in preview environments, I hope that helps: https://next-auth.js.org/deployment#securing-a-preview-deployment Basically, you could use an environment variable to toggle between allowed providers, or even switch off the adapter when you are in a test/preview environment. Making sure that the actual login flow with OAuth will work is our library's responsibility, not your app's. Otherwise, you could try to use something like MSW and mock the requests that NextAuth.js makes. Especially the one to |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for the answer, everything makes sense now 👍 |
Beta Was this translation helpful? Give feedback.
-
|
To add, this is also one of the reasons we cannot test our provider integrations automatically (#2524). CI/CD environments are considered bots (rightfully so) and therefore providers will often show a captcha/challenge that makes their login process impossible in tests. So mocking/skipping really is the only option as far as I am aware. |
Beta Was this translation helpful? Give feedback.
-
|
If you think this is useful, would you care about opening a PR to add this to the docs so we can reference it in the future? 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I'll give MSW a try and when everything works on my end, I'll create a PR 👍 |
Beta Was this translation helpful? Give feedback.
Thanks for the ping. Unfortunately, there is not much NextAuth.js can do about it, since this is a limitation of OAuth providers (be it unintentional or not).
We recently created some guides on how to authenticate users in preview environments, I hope that helps: https://next-auth.js.org/deployment#securing-a-preview-deployment
Basically, you could use an environment variable to toggle between allowed providers, or even switch off the adapter when you are in a test/preview environment. Making sure that the actual login flow with OAuth will work is our library's responsibility, not your app's.
Otherwise, you could try to use something like MSW and mock the requests that NextAuth.js makes. …