3rd party authentication scenario: lighthouse runs for the landing/login page and not the app itself about cypress-audit HOT 8 CLOSED

Hello and first of all, thank you for this very detailed issue 🙏🏻 .

I'm going to check this one on my spare time. Concerning the tab that opens, it's "normal", lighthouse opens a new tab when running its audits.

Concerning the third party verifications, I'm not sure how to handle this since it's not a scenario I'm very familiar with Cypress. I'm going to try to find time for this.

Thank you again 🙏🏻

from cypress-audit.

Oh great to hear 😊 . Can we consider this issue to be closed or are you expecting something particular in order to be okay with the behavior?

And again, a huge thank you for the time spent investigating here 🙏🏻

Yup. This is something we will have to retry when Cypress has multi domain support.

from cypress-audit.

@muratkeremozcan can you try with this workaround?

Fantastic! The workaround helped!

Thank you so much for commenting on this closed thread. Words aren't enough to express my appreciation.

from cypress-audit.

Hello and first of all, thank you for this very detailed issue 🙏🏻 .

I'm going to check this one on my spare time. Concerning the tab that opens, it's "normal", lighthouse opens a new tab when running its audits.

Concerning the third party verifications, I'm not sure how to handle this since it's not a scenario I'm very familiar with Cypress. I'm going to try to find time for this.

Thank you again 🙏🏻

I gave it a repro attempt here with auth0-cypress demo + cypress audit. It is working though. Might need a more complex example.

from cypress-audit.

Oh great to hear 😊 . Can we consider this issue to be closed or are you expecting something particular in order to be okay with the behavior?

And again, a huge thank you for the time spent investigating here 🙏🏻

from cypress-audit.

Thank you 🙏🏻

from cypress-audit.

@muratkeremozcan can you try with this workaround?

from cypress-audit.

Hi guys,
Thank you so much for all of your effort in this issue. Great work there!
I tried to look into this guide (and many similar ones on the internet) but still cannot resolve my issue.
Basically, I am writing performance test cases in Cypress for my website.
It launches from a third-party Amazon Cognito sign-in page.
So when I go to my website, at first it will redirect me to the Cognito sign-in page, and then after signing in, I will be redirected back to the home page of my website.
What I want to test is the performance metrics of different actions performed on my website. But no matter what, I have to go through the login process.
Here's the problem that I encounter:

• If the current browser hasn't yet previously signed in to my site, and so there's no cache (relating to this site) being stored in the browser, when I go to the site, the Cognito page will have a button allowing me to sign-in through my organization's SSO.
• But if the current browser already has been previously used to sign in to my site, and so there's cache storing the previous sign-in data, when I go to the site again, the Cognito page will look different. It will have a button allowing me to Continue to my site (ie. the button shows something like 'Continue with <my organization>'). After clicking on it, I need not to enter passwords from the SSO again, and I am directly signed in.
• I understand that lighthouse() command in cypress-audit first performs whatever actions I would like to test against, and then opens a new tab in order to estimate the performance metrics, and finally the new tab closes and resumes the Cypress test. So I encounter the "Continue button" mentioned above in this step, in the new tab (that lighthouse() tries to open).

So my question here is:

• On the new tab, my testing script could not proceed further, because there isn't any sign-in button appearing on the new tab opened by lighthouse(), but instead, there's a "Continue button".
• So the lighthouse() command got stuck there, causing the metrics measured to be 0. (Kinda frustrating because it obviously does not pass any threshold.)
• My workaround: manually click the "Continue button" whenever the test script encounters that page.
• Is there any way to have lighthouse() command automate this step?

Thanks. Feel free to comment.
PS Since my codes are private, I am unfortunately unable to share in the community, but feel free to arrange meetings with me to review and solve it together.
Look forward to any solutions! 💯

from cypress-audit.