Hi I faced the unknown issue with the

Hello everyone I want to enable Test

hi

Seams like is missing something from core-js, but I have the latest version

can anyone here help me out in generating random date.

Moment.js is probably the most popular package for handling dates.

Its deprecated though so a lot of people are migrating to date-fns

Google! 🙂 https://stackoverflow.com/a/9035732/5746360

I used

faker

in the past with great success. https://fakerjs.dev/api/date.html#between

Anyone know how to modify the build process of Cypress on github? I had to use the flag **'npm install --legacy-peer-deps' **to get my build working but now Cypress seems to also require the flag in order to deal with dependency conflicts. I've looked into my actions/workflows and don't see anywhere where I can change it from npm ci to npm install --legacy-peer-deps

Hello folks. I have a quick question. How can we import the compiler options from a

jsconfig.json

file so we can get the right import aliasing for cypress component testing? Do I need to write a custom

webpack.config

for this even if we are using CRA? Where else can I read about how the devserver is built and set up?

Hello, I need some help with Cloud Flare authentication. I implemented a test where I run two Cypress test runners at the same time based on @gray-kilobyte-89541 's blog post using socket.io. It works well locally when I connect through VPN from my laptop to the server. However, when I am trying to put this into our CI pipeline, I am running into the problem where I get the following message: "[187:0713/174146.255608:ERROR:cert_verify_proc_builtin.cc(681)] CertVerifyProcBuiltin for .cloudflareaccess.com failed: ----- Certificate i=0 (OU=Cypress Proxy Server Certificate,O=Cypress Proxy CA,L=Internet,ST=Internet,C=Internet,CN=.cloudflareaccess.com) ----- ERROR: No matching issuer found I need to bypass the Cloud Flare authentication, which I am trying to do by having a beforeEach hook in each test file and where I am doing this: beforeEach(() => { cy.intercept(${Cypress.config('baseUrl')}**, req => { req.headers['CF-Access-Client-ID'] = '***' req.headers['CF-Access-Client-Secret'] = Cypress.env('CF_SECRET') }) }) And I am setting Cypress.env for CF_SECRET in the run.js file where I run both Cypress test runners like this: return cypressAction({ configFile: process.argv[3], env: { CF_SECRET: process.argv[4] }, and I pass the CF_SECRET from the .yaml file that runs in Github. I am not sure why it's not bypassing the CloudFlare certification, any help or ideas would be greatly appreciated! It looks like the headers are not getting set?

When running on CI, it does not use the VPN, so it is not the same connection as you have locally

yes exactly, that's why I am trying to bypass this cloudflare by setting the headers for each request, but that doesn't seem to be working for some reason. Is it possible to implement this in CI?

setting the request headers works the same way. Are you sure you have the

Cypress.env('CF_SECRET')

? How do you pass it to the test runner? Read https://glebbahmutov.com/blog/keep-passwords-secret-in-e2e-tests/

Hello there, is there a way to turn on/off using fixtures when intercepting, so that when I develop the tests it uses fixture data but when I deploy the app it tests using live data?

you can probably do conditional commands based on some env variable to turn cy.stub

const isProd = Cypress.env('PROD')
if (isProd) {
  cy.spy('...').as('foo')
} else {
  cy.stub('...', {fixture: }).as('foo')
}
cy.wait('@foo')

In the test runner I have this:

const cypressAction = args['--open'] ? cypress.open : cypress.run
const firstCypress = cypressAction({
  configFile: process.argv[2],
  env: {
    CF_SECRET: process.argv[4]
  },
}).then((results) => {
  console.log('First Cypress has finished')
  return results
})

// delay starting the second Cypress instance
// to avoid XVFB race condition
const secondCypress = wait(5000).then(() => {
  console.log('starting the second Cypress')
  return cypressAction({
    configFile: process.argv[3],
    env: {
      CF_SECRET: process.argv[4]
    },
  })
})

And then in the GitHub .yaml file I have this, which I thought would be passing CF_SECRET to the test runner as the 4th parameter:

npm run ${{ matrix.test }} cypress-dev-user1TipChatNotice.config.js cypress-dev-user2TipChatNotice.config.js ${{ secrets.GHA_CF_SERVICE_ACCESS_TOKEN }}

Also, tried this: removed from test runner:

env: {
      CF_SECRET: process.argv[4]
    },

and in .yaml in Gitghub have this:

CYPRESS_CF_SECRET=${{ secrets.GHA_CF_SERVICE_ACCESS_TOKEN }} 
 npm run ${{ matrix.test }} cypress-dev-user1TipChatNotice.config.js cypress-dev-user2TipChatNotice.config.js

I also upgraded to 10.3.0 and now the certification error is gone but in both ways above I am getting a cross-origin error for https://google.com. Am I supposed to use` cy.origin` somewhere when I am trying to bypass the cloudflare authorization?

you can probably do conditional commands

from the test you can throw an error right away if the

Cypress.env('CF_SECRET')

is not set

Hi all, I'm running into this issue with the `cypress-example-recipies`: https://github.com/cypress-io/cypress-example-recipes/issues/553. The

after(sendTestAttributes)

doesn't appear to run?

> Plan Limit Reached: You've reached 102% of your test results for this usage period. I want to delete the test results. What should I do?

Hi all. I want to run .feature in cypress, but i received this error message instead. Everything was fine before. The error happened after i set up the global variable inside cypress.env.json and after i add cy.visit(Cypress.env('homepage_url')) inside step_definitions. What should i do? Thank you.

kindky assist

Hey, I think you can try to delete the AppData\Local\Application Data symlink

Hey @melodic-jordan-92756, share the contents of

cypress.config.js

in particular the part where you added the new variable.

Hi all! I need some help... I'm sending a request to endpoint A with a body with content-length of 56, endpoint A adds some data to that body (content-length 86) and sends to enpoint B, but it throws and error. My request never reaches endpoint B and throws timeout expecting a body of 86 length (I think cypress does not allow that body adition that endpoint A) Do you know any solution for this? Like allowing changes in bodies or something like that? Thanks!