How to use getTags method in Cypress

You probably should use a request handler.

cy.intercept('pageUrl', (req) => { 
  req.destroy();
})

See the official doc here https://docs.cypress.io/api/commands/intercept#Controlling-the-response

I found a useful setting to resolve this - followRedirect can be set to false to capture the 302 and fragment data.

Documentation link: https://docs.cypress.io/api/commands/request.html#Options

Eg:

cy.request({
  url: '/dashboard',
  followRedirect: false // turn off following redirects
})
  .then((resp) => {
    // redirect status code is 302
    expect(resp.status).to.eq(302)
    expect(resp.redirectedToUrl).to.eq('http://localhost:8082/unauthorized')
  })

This is a known issue after Chrome 67 enabled by default the site isolation security feature, and it gets reflected in any frameworks that use Chromium releases that include it (e.g. Electron 5+)

http://www.chromium.org/Home/chromium-security/site-isolation

When debugging with --disable-web-security, it may also be necessary to disable Site Isolation (using --disable-features=IsolateOrigins,site-per-process) to access cross-origin frames.

Here are some open issues regarding it

https://github.com/electron/electron/issues/18214
https://github.com/cypress-io/cypress/issues/1951

In Electron 5+, until this is solved you can add this line before app 'ready' event

app.commandLine.appendSwitch('disable-site-isolation-trials');

It looks like known issue in Cypress versions starting from 7.3.0: https://github.com/cypress-io/cypress/issues/235#issuecomment-1009912083

As a workaround try using Electron instead of Chrome, it works for me.

This has been asked a few times, and the short answer is to use jQuery, e.g

cy.visit(...)
cy.wait(1000)  // in case the page is initially slow to load

const text = Cypress.$('div').text();
if (text.trim().startsWith('Processing') {
  cy.wait(1000)
  cy.reload()
}

That gets you one reload, but I guess you want to repeat that until 'Success...', for which recursion seems to be the only way to repeat stuff until the right DOM appears.

function waitForText(attempt = 0) {

  if (attempt > 100) {   // choose cutoff point, must have this limiter
    throw 'Failed'
  }

  cy.wait(1000);
  const text = Cypress.$('div').text();
  if (text.trim().startsWith('Processing') {
    cy.reload();
    waitForText(attempt + 1) 
  }
}

cy.visit(...)
waitForText()

From the above code, it doesn't look like you are preserving the cookie once logged in. Cypress automatically clears all cookies before each test to prevent state from building up. You should be able to do something similar to this:

before(() => {..cy.login() })

beforeEach(() => {
    Cypress.Cookies.preserveOnce('session_id', 'remember_token')
})

This cypress doco should provide more context https://docs.cypress.io/api/cypress-api/cookies.html#Preserve-Once

Solved: I found this that explains how to put cy.preserveOnce('<name-of-your-cookie>') in the beforeEach loop at start.

I'm putting this here for future reference.

You can do this by overwriting cy.visit() command. Try this:

Cypress.Commands.overwrite('visit', (originalFn, url, options) => {
  originalFn(url, options);
  // make sure to add a return here!
  return cy.get('body').then($body => {
    if ($body.find("[text='Got it']").length > 0) {
      cy.contains('Got it', { matchCase: false }).click();
    }
  });
});

source: https://docs.cypress.io/api/cypress-api/custom-commands#Overwrite-visit-command

You can simply use should to assert it doesn't exist, and Cypress will wait for the element until it's removed from DOM. If you need to override the default 4s timeout, you can pass it to the previous command:

cy.get( selector, { timeout: 10000 }).should("not.exist");