Using a cached endpoint (

Cache-Control

header with a

max-age

and

must-revalidate

), Cypress does not seem to be able to

cy.wait

for the alias I setup: * When running with cache disabled in chrome dev tools, my tests run fine * With cache enabled however, the test fails because it does not record any of the calls made to this particular endpoint. What's the correct way to handle this?

Hey all, I have a question about fixtures in relation to GraphQL. We're using AWS amplify for our app and fully rely on queries/mutations and subscriptions in our app. We're thinking about using one of the Cypress graph plugins to stub out all graph related calls based on the schema, but we're wondering if anyone has experience with subscriptions at all? We feel stubbing out the whole server is quite a bit of work, but really worth it for development and testing, but we're wondering if this is indeed a good approach and/or if people have experience with Amplify specifically?

Whenever I try to intercept a cognito call and return my own stub (with or without use of a fixture) it ends up as a CORS error. Can't seem to find the documentation on this though. What am I doing wrong?

ts
    cy.intercept('OPTIONS', 'https://cognito-idp.us-east-1.amazonaws.com', { statusCode: 200 })
    cy.intercept('POST', 'https://cognito-idp.us-east-1.amazonaws.com', {
      statusCode: 200,
      headers: {
        'access-control-allow-origin': window.location.origin,
        'Access-Control-Allow-Credentials': 'true',
      }, body: {
        // stuff
      }
    })
  })

Oh looks like the preflight needed to return headers

Can't you use fixtures for failed requests? Seems like a pain to have to specify

statusCode

manually for failed requests and only being able to load fixtures for 200's?

Ok you can, but you need to still specify the statusCode :/

Wait is it bad to have to specify the status code? When I've been doing stuff with failures I've wanted to specify the status code since that's part of what our app uses to decide what to do. Here's a tiny little helper we use at work:

Cypress.Commands.add('interceptApi', (endpoint, fixturePath, statusCode = 200) => {
    cy.intercept(INTERCEPT_API_URL + endpoint, {
        statusCode,
        fixture: `/${fixturePath}.json`,
    }).as(fixturePath);
});

And we do stuff like

cy.interceptApi('/yourEndpoint', 'lil-fixture-path/500-error', 500);

then make our assertions.

Well in our case we use AWS cognito and they jumble around 200/400's. Sometimes they even return a 200 on an error

so I have to specify a statusCode manually in some cases

ooh I've worked a place that had a lot of 200-but-it's-an-error situations, it's a pain

Now I run into an issue where there are 3+ calls to the same endpoint and I need to intercept them in sequence

aliassing doesn't work... ugh... this has been a pita tbh

ts
  it.only('Should login successfully', () => {
    cy.intercept('POST', 'https://cognito-idp.us-east-1.amazonaws.com', { fixture: 'cognito/email-valid.json' }).as('baz')

    cy.get('input#email').type(LOGIN_EMAIL_VALID)
    cy.get('[data-login-email-submit]').click()

    cy.wait('@baz')

    cy.intercept('POST', 'https://cognito-idp.us-east-1.amazonaws.com', { fixture: 'cognito/auth-result.json' }).as('1')
    cy.intercept('POST', 'https://cognito-identity.us-east-1.amazonaws.com', { fixture: 'cognito/id-1.json' }).as('2')
    cy.intercept('POST', 'https://cognito-identity.us-east-1.amazonaws.com', { fixture: 'cognito/id-2.json' }).as('3')
    cy.intercept('POST', 'https://cognito-idp.us-east-1.amazonaws.com', { fixture: 'cognito/auth-2.json' }).as('4')
    
    cy.get('input#verification').type(LOGIN_CHALLENGE_VALID)
    cy.get('[data-login-code-submit]').click()

    cy.wait('@1')
    cy.wait('@2')
    cy.wait('@3')
    cy.wait('@4')

    cy.location('pathname', { timeout: 10000 }).should('include', 'profile')
  })

It never waits for

@1

I have a feeling Cypress can't deal with multiple requests to the same endpoint

It only ever uses the last one

my god this is annoying

the

times

param also doesn't do anything

it's also firing them in the wrong order. This shouldn't be difficult lol

Yup, they need to be declared in reverse order. That must be a bug, right?

Well, finally got it working, but files a bug report for the intercept issue

Hello everyone, is there anyway for me to wait for page load?

Guys, I am really stuck because of this issue here https://discord.com/channels/755913899261296641/755913900024791046/865250071804379176

hey guys im just curious how you guys are able to test a login that is using 2FA

hello guys, is there any environment variable that stores the cypress dashboard url after the run has been completed in CI? eg. this url: https://dashboard.cypress.io/projects/7s5okt/runs/4730/specs My use case is: I am writing a custom slack bot, that will notify a slack channel after every run. I know there is a slack integration built into the Cy dashboard, but that not my requirement.

after some mocking around, I found it. Its

cypress.run(config).then(results => {
    console.log(results.runUrl)
})

Hello ! I know it's pretty basic. I installed cypress yesterday.I ran few tests. App preview window is not displayed on my runner I was wondering what could be the issue Tests run okay. I see all of them have passed. It's just that i don't get to see the Video of how test progressed as App preview doesn't display 😫

version?

7.7

Hi @User , are you online?