-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
refactor: cleanup preview items on drops page #10344
Conversation
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Deploying koda-art-prod with
|
Latest commit: |
e28f564
|
Status: | ✅ Deploy successful! |
Preview URL: | https://430211a8.kodaart-production.pages.dev |
Branch Preview URL: | https://refactor--cleanup-preview-dr.kodaart-production.pages.dev |
linking: |
…cleanup-preview-drop-items
* refactor(e2e): modify nft-name test to check the first element in collection.spec.ts
… TIMEOUT * feat(playwright.config.ts): add expect timeout setting * refactor(tests/e2e/collection.spec.ts): remove redundant waitForLoadState * refactor(tests/e2e/collection.spec.ts): simplify nft-name text expectation
…s array for it.each test function
did some mints using auto-teleport on canary and was unable to reproduce the issue, any ideas? |
…g in CI environment * refactor(explore.spec.ts, sidebar.spec.ts): remove explicit timeout from toBeVisible assertions
@preschian sidebar.spec.ts is failing on other PRs as well, investigating. |
I tried to increase the timeout in the playwright global config. Should we increase it again? currently 12s. On local, |
uh, not sure if i understood i would leave the global test timeout at 1 min, meaning that, if a single test takes more than one minute, it would automatically fail(i try to keep each test below 1min) retries i would also leave at 1, otherwise the test will take a long time to fail (imagine if a test takes 50s and it retries it 3 times) if you were willing to change the expect timeout(5s default) we have to use: i think sidebar.spec.ts is failing for another yet unknown reason |
Oh sorry, yes this one correct. Not 12s but to 2 min
Yes, this is the one I add. Right now, the config: const TIMEOUT = 2 * 60 * 1000
const config = {
// ...
timeout: TIMEOUT,
expect: {
timeout: TIMEOUT,
},
// ...
} |
…e and retries from 3 to 1
as i said in dm, tests were failing due to an RPC error, that's why it failed across many PRs feel free to revert config or timeout changes in tests, or test the 12s global timeout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the only thing is that now we won't be able to see NFT previews while mass-minting , if @exezbcz approves let's go
@hassnian that is the thing, we dont show any previews because what you get is random now |
…cleanup-preview-drop-items
let me check |
Code Climate has analyzed commit e28f564 and detected 0 issues on this pull request. View more on Code Climate. |
|
interesting, how about now @exezbcz , probably due to error on rpc side |
Thank you for your contribution to the Koda - Generative Art Marketplace.
👇 __ Let's make a quick check before the contribution.
PR Type
(please remove design and QA checks below if not needed)
Needs Design check
Needs QA check
Context
Did your issue had any of the "$" label on it?
Screenshot 📸