You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we can just replace toHaveURL with waitForURL. I mean the test should fail if waitForURL does not resolve, therefore no need to expect on top of waitForURL, right?
Final word, I'm not saying to replace all expect(page).toHaveURL with await page.waitForURL. The ones after await page.goto are fine
also the timeouts are too short. I need to set globaly at least timeout: 20 * 1000. and for the onboarding test reset password with a short code I need to set it to test.setTimeout(30 * 1000);
The text was updated successfully, but these errors were encountered:
good catch @kentcdodds indeed the timeout for expect is different. I only modified the timeout for tests.
This also made me realise my tests are taking longer due to how I configured i18next instantiation. I'll be closing the issue and will add my findings to rperon/epic-stack-with-i18n#8
On my 2019 16" mac, the tests do not run fast enough.
I cannot expect the url to have changed after a test clicks a button.
For example, in
onboarding.test.ts
this code won't work:epic-stack/tests/e2e/onboarding.test.ts
Lines 46 to 48 in 9741885
however this code does work:
we can just replace
toHaveURL
withwaitForURL
. I mean the test should fail if waitForURL does not resolve, therefore no need toexpect
on top ofwaitForURL
, right?Final word, I'm not saying to replace all
expect(page).toHaveURL
withawait page.waitForURL
. The ones afterawait page.goto
are finealso the timeouts are too short. I need to set globaly at least
timeout: 20 * 1000
. and for the onboarding testreset password with a short code
I need to set it totest.setTimeout(30 * 1000);
The text was updated successfully, but these errors were encountered: