After reload inside of a test error "TestingLibraryDom is not defined" thrown. about testcafe-testing-library HOT 10 CLOSED

@rssfrncsrenishaw I have released a new version (3.0.0) that should support your issue. The breaking changes are that addTestcafeTestingLibrary has been removed in favor of clientScripts which is now supported in testcafe 1.4.x.

To test this, you will need to update to testcafe 1.4.x (if you haven't already) and then do npm i -D @testing-library/testcafe@next

see the docs here: https://testing-library.com/docs/testcafe-testing-library/intro#for-v3x-requires-testcafe-140-or-greater

from testcafe-testing-library.

Interestingly if I manually add after the reload it works...

await t.eval(() => location.reload(true));
await addTestcafeTestingLibrary(t)
await t
    .expect(getAllByTestId("foo")).ok()

This is not ideal.

from testcafe-testing-library.

Thanks for reporting! I will look into this

from testcafe-testing-library.

I posted it on stackoverflow and was told to look into https://devexpress.github.io/testcafe/documentation/using-testcafe/common-concepts/inject-scripts-into-tested-pages.html

from testcafe-testing-library.

Yes they just added that feature. The fix will probably involve that

from testcafe-testing-library.

@rssfrncsrenishaw feel free to give this issue a 👍 as it will help fix your problem cleanly. :)

from testcafe-testing-library.

nice work!

from testcafe-testing-library.

Does that mean it works for you? 🙂

from testcafe-testing-library.

Unable to upgrade to 1.4.X at the moment so can't test it...

from testcafe-testing-library.

ok, well I added a test for your use case and the new client script injection should fix this, so closing for now, but if you do run into issues again feel free to reopen.

Fixed in https://github.com/testing-library/testcafe-testing-library/releases/tag/v3.0.0%40next

from testcafe-testing-library.