Skip to content

How to set the global timeout before findBy/queryBy queries fail? #460

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

Closed
wardellbagby opened this issue Jul 25, 2022 · 2 comments · Fixed by #461
Closed

How to set the global timeout before findBy/queryBy queries fail? #460

wardellbagby opened this issue Jul 25, 2022 · 2 comments · Fixed by #461
Labels

Comments

@wardellbagby
Copy link

Recently ran into a dramatically slow Github Workflow macOS Runner day which caused me quite a few headaches as my app was running so slowly on CI that my test assertions would fail. I'm hoping to alleviate any future pain there by changing the global timeout to be something higher on CI, but I can't quite figure out how to do it.

I've tried using the @testing-library/dom asyncUtilTimeout via its configure method, but that doesn't seem to do anything.

Is there anyway to accomplish this?

@jrolfs
Copy link
Member

jrolfs commented Jul 25, 2022

Hi, @wardellbagby thanks for creating an issue! I'm sorry you spun your wheels a bit here, technically the only option we supported until now via the configure() function that's exposed from playwright-testing-library was testId. I went ahead and added support for asyncUtilTimeout since it was pretty easy. I'll have a release out soon and you should be good to go 🙂

@github-actions
Copy link

🎉 This issue has been resolved in version 4.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants