Discussion about this post

User's avatar
Judy Mosley's avatar

Thank you for your patience! Let's see what we can do.

Hmm, I'm not sure exactly. Since you just created the new directory, it might be helpful to try a super simple test. It sounds like Cypress is working correctly, which is great. If you comment out the test code and use "cy.visit('google.com')", what results do you get?

If that test passes and you can see that the test is going to google.com, then we can start troubleshooting my code.

FYI, I'm no longer writing on Substack. Feel free to follow me on over at Beehiiv: https://failureisfeedback.beehiiv.com/

You've also made me realize that it would be a good idea to have a github for examples. I'll work to get that up and running. Thank you for for your comment!

Expand full comment
Danni's avatar

I updated to Cypress 14.3.1, created a new directory, let Cpress create the initial test case. THat ran successful. Then I added a new spec and pasted your code there. I ran it and it brought this message:

(uncaught exception)Error: Script error. Cypress detected that an uncaught error was thrown from a cross origin script. We cannot provide you the stack trace, line number, or file where this error occurred. Check your Developer Tools Console for the actual error - it should be printed there. It's possible to enable debugging these scripts by adding the crossorigin attribute and setting a CORS header.

Do you know why?

Expand full comment

No posts