-
Notifications
You must be signed in to change notification settings - Fork 4
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
Error: Cannot prepare tests due to an error. #30
Comments
Hey @DanielHabenicht! Thanks for the issue -- it looks like you're using the latest beta version of this SDK. The docs for how to use the latest (beta) version can be found here: https://github.com/percy/percy-testcafe#usage There are a lot of big changes made to the SDK. One being the first argument to You'll want to update your test to remove that first arg: test("Finish intro screens", async (t) => {
const nextButton = Selector("a").withAttribute("role", "button").child().withText("Weiter");
const websiteText = Selector("html").textContent;
const titleForIntro1 = "Willkommen bei der CovMap";
await t.expect(websiteText).contains(titleForIntro1);
await percySnapshot("Final Site");
}); The docs on docs.percy.io haven't been updated yet, you'll want to refer to the README for setup & config. |
Thanks for the lighting fast feedback. Good to know that I should just read the master :) Unfortunately your solution is bringing me back to #4 but this time if changed to
There would be the option of calling If run as |
So it looks like we inadvertently released the beta on the latest channel which is why you accidentally found yourself on the beta following the docs. I've since deprecated the first beta, released a new "previous" version to be tagged as latest, and now the new beta.2 lives on the Feel free to continue using the beta to help us vet out any bugs, but now you are able to install Back to the beta discussion, those types are found here and look to be valid as well as the type tests are passing without issue. Curious what might be going on to cause those type issues? 🤔 |
I have looked into it a bit but I don't get it. |
Baaam, made it. So it seems that testcafe has its own {
"tsConfigPath": "./tsconfig.e2e.json"
} The key is to include {
"compilerOptions": {
"esModuleInterop": true
}
} As this is an extension solely for |
Back to the error from the beginning :( |
I think I answered the map question via support -- is that right? :D I want to double check. If not send over a build link and we can take a closer look |
yep, you did :) Thx again. Any idea how to investigate the error? |
This issue is stale because it has been open for more than 14 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 28 days with no activity. |
I am getting the following error while doing mostly the same as in the tutorial/example.
Am I still doing something wrong?
http-server
If you more context is needed, this is the branch I am working on: https://github.com/CovOpen/CovMapper/tree/chore/percy-integration/testcafe
The text was updated successfully, but these errors were encountered: