if that plugin works

I would try it on a smaller scale just to make sure the process works first

then add it when it works to the big site

Sounds good thanks! Do you think that plugin would work to add the instrumentation for cypress ?

@User thanks!

If it adds istanbul instrumentation it should be great

Ok cool thanks ! I will let you know if it works thanks again for your help!!!

🙏

Another help question! I just upgraded to the latest packages and omg - this stuff is SO fire. My tests were taking a easily over a minute before and now they take roughly 20sec. Can't believe it. Just running into a simple issue - when I try to run my e2e tests with

npx cypress run

they fail and it's due to my stylesheets I'm loading in the support file. Any idea what the fix is? I created a fresh project with cypress and just referenced a stylesheet, and the same issue. Thanks!

Oops...we found an error preparing this test file:

  tests/support/index.js

The error was:

Error: Webpack Compilation Error
./node_modules/buefy/dist/buefy.css 2:0
Module parse failed: Unexpected character '@' (2:0)
You may need an appropriate loader to handle this file type...

In 7.0, you can have 2 distinct support files one for e2e and one for ct

ahh gotcha, that would make sense. thanks!

use the e2e and component flag to configure which is which https://docs.cypress.io/guides/references/configuration#Runner-Specific-Overrides

fixed - thanks!

I have a list of scroll heights I want to screenshot and having issues with the async/sync chaining of Cypress I think to get it working...

cy.window()
      .should('have.property', ANIMATION_GLOBAL)
      .then((animations) => {
        cy.log('animations', animations)
        callPerLabel(animations, (section, label, value) => {
          cy.scrollTo(0, value)
          cy.percySnapshot(`${section}: ${label}`)
        })
      })

I think I have some time to do this finally. But I was reading through the introduction.md you mentioned and I noticed there is this section that has this line "if (config.testingType === 'component')" (and in the screenshot) as an example of how to account for using E2E tests along with CTs. This sounds like another way to accomplish what we had talked about previously. So I wonder if this method is no longer preferred or if both this and the cypress.json approach are fine and users can choose whichever they want? Seems like there is a fair amount of overlap between the "Existing end-to-end users" and "Install" sections in general, but if you just want me to add something and leave trimming anything out to someone else, that is fine with me. Just wanted to be more clear before proceeding.

Hi, has anyone had an issue with testing

canvas

on cypress? I'm using react Cytoscape and basically when I run my cypress test it would load an empty canvas, nothing would be drawn in it. But if I run cypress in headed mode, then within the cypress chrome browser I open the same URL I'm testing in a new tab, it loads the canvas perfectly. In my understanding both cases will still use mocks instead of calling the actual APIs (evidently everything in the page is just

String

String

etc instead of real data). So does anyone have any ideas why cypress behaves differently? Am I missing a config or something?

Hi, does anyone know if the "wait" behaviour has changed? I explain before I was doing this:

js
cy.wait('@Submit').then(interception => {
  if (interception.response.statusCode != 200) {
  //do something
  }
})

and something would happen when I got a 400 error for example, today 05/05 it stops at the "wait" and doesn't do the "then".

Trying to write a custom command that recursively checks an external api using

request()

but I'm struggling with cypress async/sync. > cy.then() failed because you are mixing up async and sync code. https://gist.github.com/iDVB/4c77f2160bbd6ff35067e6fd7cf647a5 Ideally, I would like the command to return the

vid

of the contact. Or fail the expect

Runtime gating it with the conditional you pasted is your best bet right now, but you don't have to change anything if you're using cypress.json. We'll possibly change the recommendation in a few months, but both of the approaches will be compatible and will likely never break. We're considering stuff like cypress.js but it's unclear when/if that'll land (4+ months prolly)

Hi all! :D, I'm having some issues with cy.request() method upon Api testing, this is the error cypress is showing me:

This is the code for it:

probably this https://github.com/cypress-io/cypress/issues/15101

Hi Gleb, I tried downgrading to 6.4 but still see the error, I'm running on local, not Ci yet

I would downgrade more or wait until the fix comes out, probably Monday

@User it largely depends on what URL you're trying to test in your baseUrl. Cypress also has support for proxies though. Here you go https://docs.cypress.io/guides/references/proxy-configuration

Hi @User appreciate your quick response. I read this documentation but I am failing to grasp what "open internet access" means. Our company maintains an explicit allow list for specific domains to be accessed from our CI/CD pipeline. Almost everything we use is internal only. Eg. Opening up access to cypress.io helped resolve the download issue. The setup is a Jenkins pipeline that runs inside AWS VPC and only internal systems can talk to each other. The URL I'm testing is internal to the network but does not work. Right now, I am unable to explain to the network / security folks what exactly is needed. Would allowing more *.cypress.io access resolve the issue? I'm doing a POC after which we would consider a business license but I have to prove it out first. I'm sure it's something simple that I'm not grasping and if I can explain what needs to happen, the network team will support. Appreciate any pointers / help.

I have a simple canvas example working here: https://github.com/lmiller1990/cypress/tree/cy-draw/my-project

Hi all, I need help outputting 2 array var's to the Cypress log. The array vars contains text from elements extracted using JQuery. Below is my code:

it("test", () => {
        cy.get('.person-item-template > .name').each(function($personName) {
            const peopleNames = $personName.text()

            cy.get('.person-item-template > .name').siblings('job-title').each(function($personJobTitle) {
                const peopleJobTitles = $personJobTitle.text()
                cy.log("Person found: " + peopleNames + ". Job Title: " + peopleJobTitles)
            })
        })
    })

I'm expecting 20

peopleNames

and 20

peopleJobTitles

but I'm actually getting 120 returns in the Cypress log

I'm assuming this is not the best way of dealing with Arrays and outputting to the Cypress log, could anyone point me in the right direction?

@User if you're trying to debug, you can actually open the devtools and look at the array within Chrome