ReferenceError: `Cypress` is not defined

Question

ReferenceError: `Cypress` is not defined

TheJoeSchr opened this issue 4 years ago · comments

Trying to start this via codesandbox (to fiddle around) I get this error right out the gate:

ReferenceError
Cypress is not defined
evaluate
/src/index.js:7
   4 | const { createMarkdown } = require('safe-marked')
   5 | const markdown = createMarkdown()
   6 | 
>  7 | Cypress.Commands.add('runExample', options => {
   8 |   const { name, description, html, test } = options
   9 |   const testTitle = name || cy.state('runnable').title
  10 | 
View compiled

Link for reproduction: https://codesandbox.io/s/github/cypress-io/cypress-fiddle

Gleb Bahmutov · Answer 1 · Mon Mar 23 2020 23:19:44 GMT+0800 (China Standard Time)

The code examples are meant to run only inside Cypress test runner https://github.com/cypress-io/cypress and cannot be executed from a website.

TheJoeSchr · Answer 2 · Mon Mar 23 2020 23:52:26 GMT+0800 (China Standard Time)

Ah, gotcha, thx!

TheJoeSchr · Answer 3 · Mon Mar 23 2020 23:54:18 GMT+0800 (China Standard Time)

are you open for a PR that has a docker-compose service with cypress already installed?

Gleb Bahmutov · Answer 4 · Mon Mar 23 2020 23:59:44 GMT+0800 (China Standard Time)

Sure - but what’s the situation there? How would it work?

…

Sent from my iPhone

On Mar 23, 2020, at 11:54, JoeSchr ***@***.***> wrote: are you open for a PR that has a docker-compose service with cypress already installed? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

TheJoeSchr · Answer 5 · Tue Mar 24 2020 00:05:11 GMT+0800 (China Standard Time)

I imagined it that then it would just work on online editor services like: codepen.io, codesandbox.io and coder.io and I would just have copy & pasted my already written docker-compose configuration. But I just realized you have to expose `$DISPLAY` for `cypress open` and then your actual machine had to have a port open from public to route $DISPLAY to your xhost. That seems like a lot more hassle then I imagined when I wrote that. Sorry about that! But let me say, I really love love what I have seen so far from cypress.io. Thank you for building it! I'm really looking forward converting all my e2e and frontend unit tests to it! On Mon, Mar 23, 2020 at 5:00 PM Gleb Bahmutov <notifications@github.com> wrote:

…

Sure - but what’s the situation there? How would it work? Sent from my iPhone > On Mar 23, 2020, at 11:54, JoeSchr ***@***.***> wrote: > > > are you open for a PR that has a docker-compose service with cypress already installed? > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6WSHRYZJHP3ZEVNYPRSNTRI6BQBANCNFSM4LRXVT2Q> .

Iqra Ali · Answer 6 · Mon Dec 07 2020 12:10:11 GMT+0800 (China Standard Time)

Hi @JoeSchr,

Any lead on this issue, did you find a workaround? I'm new to Cypress. I faced the same issue when I imported a react project with testing implemented in Cypress to CodeSandbox, it was working all fine locally; however, on import to CodeSendbox, I was unable to run my tests.

I have read the complete thread and understood the reason behind this behavior, but still, I want to know if you found out any working hack to this issue.

TheJoeSchr · Answer 7 · Mon Dec 07 2020 16:25:54 GMT+0800 (China Standard Time)

@Iiqra sadly no

My "workaround" was to get a free trial at one of the Dev cloud providers like linode or Digitalocean . There you have more control over your environment and can either install a minimal X11 Server or pass $Display along to your local machine via ssh