Testing Breaks Due to Page Redirect

Current behavior:

I must go through a login of a different app in order for my own app to be working, I can’t mock that. So the first line I do is as described below - I use cy.visit(..) to go to that page an log in. However, often when it starts the test, instead of visiting that page and fill the form to login, the entire Chrome tab goes redirects there (rather than just the app on the righthand side panel) and the testing panels are gone as if I just opened a new tab in Chrome and went to that page. I have to kill the cypress process and restart it. That usually fixes it, if not I just restart it a couple more times.

Desired behavior:

Testing proceeds as normal.

Steps to reproduce:

Maybe try to visit a different domain?

cy.visit(`https://different.app.com/session?redirect=${encodeURIComponent(myAppUrl)}`);

Versions

Cypress: 2.1.0 OS: MacOS High Sierra 10.13.3 Browser: Chrome 66

[ghost]

@brian-mann i’m not sure why this is closed. this is a really big blocker for us as well and can’t get passed this redirect bug. Already wrote a LOT of tests for Cypress and would hate to have to move to something else because of something so silly.

Usecase: /page immediately redirects to /page/hi but there is no way to test that this redirect happens. Cypress throws a 404 for some reason when the browser clearly redirects for the end user.

   it('properly load menu url', () => {
   	// Page should probably redirect to a default landing if plugged in randomly.
   	cy.visit('/page')
   		.location('pathname', { timeout: 10000 })
   		.should('eq', '/page/hi');
   });

[ricovitch]

Hello,

We are actually evaluating which solution to use for end2end testing in our project. Cypress seems great, it has a nice developer experience, and good documentation/examples/etc.

But we hit a wall with the login step of our backoffice application because of the iframe/multiple domains restrictions. I know there are a lot of informations and even a sample on how to get this kind of scenario working, but as we are not the team developing the backend and the authentification services, this is just a show stopper for us…

That and a straight forward way of running multiple test suites in parallel without a docker master degree

Sorry i don’t want to seem rude, but i’m actually sad that we can not go further with cypress, as i feel it has great potential. I just wanted to share that.