@adventurous-dream-20049 okay 👍

Hello, Is the cypress xpath plugin not optimal at the Gitlab CI/CD pipeline? I noticed on some specs, it fails always at cy.xpath() on my test

Why do you need this? What is wrong with the localhost:3000? Usually when you are running your devServer and are building your website, you run it on localhost. What's the purpose of baseUrl for component testing?

I'm trying to sync Cypress to TestRail via Github Actions, following this guide (https://glebbahmutov.com/blog/cypress-and-testrail/) but when I run the first

curl

command, I get the same error as this person (https://sqa.stackexchange.com/questions/32045/how-to-access-the-testrail-api-behind-basic-authentication-plus-form-based-authe), however the solution provided on SO isn't helpful given that I'm trying to follow the tutorial. Has anyone else dealt with this?

Sure! What timezone are you on?

Hi Jess, we are using nginx before Vite, that is why. With current set up nginx and Vite, we get localhost:3000 infinite reload loop and it's impossible to test. This is the main thing. The other thing is that we want to run component testing in terminal and we also need to specify custom url for that. Any ideas if this is possible?

How can I get

@cypress/code-coverage/support

to work? I tried everything now and no matter what I do, no coverage report will be created anywhere 🤔

Cypress and TypeScript

Is it possible to express optionality inside a

cy.wait()

that consumes aliases? eg.

What is a valid value for

TESTRAIL_HOST

in your environmental variables? Just the root

host.testrail.com

?

And does

cypress-testrail-simple

expect the same test case ID structure as

cypress-testrail-reporter

, ie something like

C123

in the description of each

it.()

block?

TestRail Env Values

👀 👋 @User

Ping?

Hello, I am trying to run cypress test from Jenkins Job locally. I was able to run from Jenkins if I run from QA/Dev Server, package.json script "start": "ember serve", "cypress:e2e": "start-test start http-get://localhost:4200 cypress:run", "cypress:run": "yarn cypress run --browser chrome", If I run like following command: yarn run cypress:e2e then I get error like below: I wonder if anyone has similar issue. If so, how did you resolve this? I am trying to run from my local before putting into CI build for DevOps to setup. Thanks. Error: Timed out waiting for: http-get://localhost:4200 at /var/lib/jenkins/.config/yarn/global/node_modules/wait-on/lib/wait-on.js:132:31 at doInnerSub (/var/lib/jenkins/.config/yarn/global/node_modules/rxjs/dist/cjs/internal/operators/mergeInternals.js:22:31) at outerNext (/var/lib/jenkins/.config/yarn/global/node_modules/rxjs/dist/cjs/internal/operators/mergeInternals.js:17:70) at OperatorSubscriber._this._next (/var/lib/jenkins/.config/yarn/global/node_modules/rxjs/dist/cjs/internal/operators/OperatorSubscriber.js:33:21) at OperatorSubscriber.Subscriber.next error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. cleaning up Build step 'Execute shell' marked build as failure

Actually, I was able to run after WAIT_ON_TIMEOUT=600000 (milliseconds) sets the timeout for example to 10 minutes. looks like take long time to load the application...

Hello there! I have

record: true

in my Actions; however I get the:

This project has been configured to record runs on our Dashboard.
It currently has the projectId: xxxxx
You also provided your Record Key, but you did not pass the --record flag.
This run will not be recorded.
If you meant to have this run recorded please additionally pass this flag.
  cypress run --record
If you don't want to record these runs, you can silence this warning:
  cypress run --record false

message. What's up? :/

Hello guys ! I'm trying to upload large file with cypress. im doing so with selectFile, but files above certain size makes cypress crash. I've also tried with readFile and did not succeed. if anyone already succeed uploading 1GB + files with cypress I would be happy for some guidance 🙂

Can you provide your

.yml

file redacted of any sensitive data? Additionally, is this error in Cypress or GHA?

Can you tell me what you mean by "crash"? Also, this seems to be more of a current limitation with the fixtures files as mentioned in this GitHub issue: https://github.com/cypress-io/cypress/issues/7365

Hi! We would appreciate a little help with the following situation. We're using Cypress and Mailosaur to test a critical flow in our app. The user is supposed to follow a link from the email before they gain access to the application. The email is sent using Sparkpost, and has a click tracker that wraps and encodes the actual app url. As far as we could tell, the tracker redirect works perfectly fine - we've never faced any issues with it during manual testing. Clicking the tracker link, or copy/pasting it into browser address bar, returns a 302 and redirects to the target URL with no issues. However, when using Cypress and Mailosaur, we extract the link from the email using existing documentation, but attempts to utilize that link with cypress fail. Instead of returning a 302,

cy.request

and

cy.visit

get a 200 response, and this breaks the entire flow. We've been trying to crack this issue for some time and were unsuccessful. Are there any known issues or cypress-specific behavior in URL handling that could cause such an issue?

Is it possible to get the

WAIT  Compiling...

prompt on the UI instead? Maybe the terminal used to execute Cypress (e.g.

npm run test:e22

) is not always in view ...

Cypress app just crash and exit, also in the terminal it is no longer running, the controlled chrome session just crash and shows not found page

Hi everyone! 👋 I'm running Cypress tests on https://localhost:3000, which is my CYPRESS_BASE_URL also. Navigating to / redirects to /en internally, which works fine (and which should not be the problem since webSecurity is not about the path). But the test that I'm writing is about a form which builds a new URL, like https://localhost:3000/foobar?param=value. Now Cypress throws this: Cypress detected a cross origin error happened on page load: > Blocked a frame with origin "https://localhost:3000" from accessing a cross-origin frame. Before the page load, you were bound to the origin policy: > https://localhost:3000 I do not want to disable chromeWebSecurity (which works), since I'm running this test on Firefox also. The only thing I can imagine is the way I do the redirect: window.location.href = "/foobar?param=value". The error message is about changing protocol, port or host, but I'm doing none of them, and my SSL certificate is a valid one. Could this be a bug or did I overlooked something?

hey! my name's lindsay, i worked at netlify on the dx team and was wondering if i could chat w someone on the dx team at cypress (or anyone at cypress!!) to talk about some struggles my new team and i are having. ben hong (dx @ netlify) sent an email intro to amir but i didn't hear back :'(. the core issues we're experiencing are failing/flaky tests in ci that pass locally without any issues. we've felt in the dark the past few weeks trying to debug. any help is v much appreciated!!!!!!!!!!! tysm!!!!

If an https://docs.cypress.io/guides/references/assertions#BDD-Assertions "diagnostic output" does not satisfy me, who's issue is that? Cypress' or Chai's? Compare: > expected to contain Reset Password with: > expected to have text Reset Password, but the text was Reset password.

Thanks for clarifying. That is quite a large file, but I recommend trying the workaround from this GitHub issue comment: https://github.com/cypress-io/cypress/issues/7365#issuecomment-723168127

We're having a very strange problem where clicking a button in our web app interface causes us not to be able to click other buttons. But only in cypress. This is very strange. Is it familiar to anyone?

Hello macbeccam, do you see any errors in the console?

I wanted to follow up to direct you to this newly created GitHub issue. After speaking with subject matter experts, it was determined this is an area of opportunity. I recommend commenting on the issue itself and setting a GitHub notification for real-time updates. https://github.com/cypress-io/cypress/issues/20244