-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically run E2E tests suite when manually deploying on production #116
Conversation
✅ Deployment SUCCESS |
✅ Lighthouse report for https://nrn-v2-mst-aptd-at-lcz-sty-c1-exad9lxx6.vercel.app |
❌ E2E tests FAILED |
✅ Deployment SUCCESS |
✅ Lighthouse report for https://nrn-v2-mst-aptd-at-lcz-sty-c1-ad1b67uiu.vercel.app |
✅ E2E tests SUCCESS |
✅ Deployment SUCCESS |
✅ Lighthouse report for https://nrn-v2-mst-aptd-at-lcz-sty-c1-7row5bjzt.vercel.app |
❌ E2E tests FAILED |
✅ Deployment SUCCESS |
✅ Lighthouse report for https://nrn-v2-mst-aptd-at-lcz-sty-c1-7row5bjzt.vercel.app |
✅ E2E tests SUCCESS |
…d deploy and run E2E tests automatically (meant to avoid human mistake) + update CI prod script
@Demmonius FYI, I'm about to merge this. |
✅ Deployment SUCCESS |
✅ Lighthouse report for https://nrn-v2-mst-aptd-at-lcz-sty-c1-bdi5w26h8.vercel.app |
✅ E2E tests SUCCESS |
Automatically run E2E tests when running
yarn deploy:customer1:production
to ensure immediate feedback after deploying to production. (helps devs notice if something isn't working properly)CI shouldn't run E2E this way though, as they run E2E in their own subprocess already.