can you show what your console log shows when you have

console.log(interception)

undefined sir. this my code cy.intercept('**/beneficiary/file-upload?*').as('uploadfiles') pic.uploadKTP('attachment/8. KTP Pemegang Saham 1.pdf') cy.wait('@uploadfiles').then((interception) => { console.log(interception) })

That doesn't make sense. If it's as you've written, then the console should log the output from your wait statement If the intercept didn't pick up anything, then the

wait()

would fail Could you do the following: 1) Change the console.log to `console.log("wait result:" + interception) 2) Send a screenshot of the spec code, rather than just that snippet 3) Show the full page of test output, rather than that small section

More information has been requested here https://discord.com/channels/755913899261296641/763114122065739818/1040234240782127216 by @fresh-doctor-14925

I have a lesson about it at https://cypress.tips/courses/cypress-plugins (paid course)

Thanks for the reply , is it available on learning platform like udemy ?

yah, i think this doesn't make sense, because im trying find this problem 2days. In another API no problem, but this Upload API got problem.

I'm baffled by this. Would you mind showing me the expanded Response from this intercepted call

I think so too, is it possible because routehandle : undefined?

Maybe. According to this doc, it should be there whenever a request is matched https://docs.cypress.io/api/commands/intercept#routeHandler-lt-code-gtFunctionlt-code-gt Could you expand the Response object so I can see the contents?

do you need i open respond.body? or this enough?

No, I can see enough here Your approach seems reasonable to me. Sorry, friend, but I am stumped. If it's possible for you to push a repo where I can try running locally I can try to take a look. Otherwise, maybe someone else will have an idea what's happening

thank you for your response liam

Of course. Thanks for the additional information. Sorry I wasn't able to help

No, it is strictly mine

Could someone point me to the location of artifacts that get sent to the dashboard? I need to show our security admin what if any proprietary code is shared with the cloud service in an attempt to get approval to use the dashboard

The stack trace blurb on the site makes me think this is a nonstarter https://www.cypress.io/dashboard/#:~:text=The%20Cypress%20Dashboard%20Service%20is,and%20run%20significantly%20faster%20tests.

When I had to go through that, I was able to get assistance from sales@cypress.io

Hello everyone, I was wondering if some one here has any guide for cypress-github integration and list of important commands for pushing and pulling requests from-to github

Docs https://docs.cypress.io/guides/dashboard/github-integration and the Git Bible https://git-scm.com/book/en/v2

Thanks

Does someone know -if- and what the OS is that is used in the cypress/base docker image?

Probably linux right?

I would say this is a pretty big clue

ah. It states linux/arm64 on this page: https://hub.docker.com/layers/cypress/base/18.11.0/images/sha256-2c5aeb2d30e5d6217263e3bcc2a0870c9903cad4b5276c0a9753c3309b1fdb06?context=explore But then the distro that is used is Debian as it seems

Good morning everyone. I was hoping to get some insight on what could be going on with my Cypress UI not being able to connect to Chrome. This is occurring on a fresh project. Essentially this is a project that so far contains only

Percy

as dependency. The message I am receiving in the console is

Still waiting to connect to Chrome, retrying in 1 second (attempt 62/62)

. Assumptions: - Node 18.10.0 installed - NPM 8.19.2 installed - Yarn installed Notes: - This was failing in Cypress 10.10 and 11.0.1 Steps to reproduce: 1. Create a new project directory and

cd

into it 2. call

npm init

3. call

npm install cypress --save-dev

4. Open Cypress for the first time to setup the project. 5. Navigate all the way to

Choose a browser

in the Cypress UI 6. Choose

Chrome

or

Edge

(this issue doesnt seem to affect

Electron

) 7. Wait until

Chrome

or

Edge

show up (unfortunately they dont) Any assistance will be appreciated. My company currently uses Selenium for our automation but I am looking into Cypress for building our new project. Hopefully this is something we can use

Hey @gentle-thailand-10072 , sorry to revive such an old message, but I was hoping to find out if you were able to resolve that issue you had? I'm currently having that same issue

Hello, I noticed recently that our selects don't seem to work with Cypress. A sequence of commands like this fails:

cy.testId('office-selector').eq(1).select('1417')
    cy.testId('office-selector').eq(1).should('have.value', '1417')

When running our app in the browser, it seems to work fine. But when selecting the pinned log event for the .select command in the test runner and switching to the "after" state, the expected value is not shown in the . Any idea what could be going wrong?

If I put in a cy.pause() before the assertion, the displayed page is correct. And inspecting the element and storing it as a variable in the console and then calling temp1.value also gives the right value.

Then when I press resume, the value retrieved by looking up the selector is still

null

. And again the dropdowns are rendered incorrectly.