-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
WIP: parallel tests + rmrk stats #4006
Conversation
✅ Deploy Preview for koda-nuxt ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
SUCCESS @petersopko PR for issue #3681 which is assigned to you. Please wait for review and don't hesitate to grab another issue in the meantime! |
SUCCESS @petersopko PR for issue #3841 which is assigned to you. Please wait for review and don't hesitate to grab another issue in the meantime! |
Test summaryRun details
View run in Cypress Dashboard ➡️ Failures
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
I need to ask for help from the pros here, I'm not making much progress on the parallelization part of the PR: In order to parallelize the tests with cypress (not locally) cypress test needs to be recorded (happening with secret key which is saved in our GH repo already - it can be accessed through However, here's what I'm getting when trying to record our tests to Cypress dashboard: Is it possible to start passing those keys to forked builds? this way, we can get to a point where the @kkukelka @preschian I know you guys have worked with both workflows and Cypress before 🙏🏻 I'm trying couple workflows there, feel free to push in any ideas you might have straight to the PR. |
i believe you have to set this CYPRESS_RECORD_KEY in the repository as well since we don't push our |
hhmm, interesting 🤔. maybe for cypress, we use another platform for CI (https://buildkite.com/ for example) and put that I need to test it out |
Code Climate has analyzed commit 6391c89 and detected 0 issues on this pull request. View more on Code Climate. |
it is set as this (kodadot/nft-gallery) secret, I've tried to set it in my fork as well, that didn't do the job |
seems quite tricky 🤔 some alternative methods:
|
This would also enable the native Cypress solution 😄 I'd rather stick with that then
Generally speaking, it would be better in my opinion to stick with one solution for E2E tests -> from actual tests to parallelization. @yangwao could we pass the cypress secret (saved in this repo) to other forks? This would be the solution here, without requiring another CI/CD service (just Cypress + GH) |
expanding e2e test suite makes no sense without parallelization, this needs to get revisited once somebody manages to do that |
Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type
What's new?
Before submitting Pull Request, please make sure:
Optional
Had issue bounty label?
Community participation
Screenshot