describe('login scenario using task', () => { before(() => { cy.task('getSession', {username:’xx.hhhh, password: ‘xxxxxxx’, url: Cypress.env("login_url")}) .then(session => { cy.restoreSession(session); }) }) Cypress.Commands.add('restoreSession', function ({cookies, lsd, ssd}) { const wList = []; cy.clearCookies(); cookies.forEach(cookie => { wList.push(cookie.name); cy.setCookie(cookie.name, cookie.value, { log: true, domain: cookie.domain, path: cookie.path, expiry: cookie.expires, httpOnly: cookie.httpOnly, secure: cookie.secure }); }); Cypress.Cookies.defaults({ preserve: wList }); cy.window().then(window => { Object.keys(ssd).forEach(key => window.sessionStorage.setItem(key, ssd[key])); Object.keys(lsd).forEach(key => window.localStorage.setItem(key, lsd[key])); }); });

We're running into issues with

visit()

with our Vue app. Locally, or against a dev install works fine, but when testing against the app when deployed on S3, we'll get a page not found. I'm assuming this has something to do with the routing when hosted on S3. Would anyone have any links to point me to for workarounds to this? For the moment, I'm just replacing them by clicking through the app.

how would you guys recommend catching a bad request that is only printing to the console and not being caught by cypress?

guys, do you know if the cypress can record the puppeteer process, calling in a test of cypress?

is anyone getting issues with chromeWebSecurity again? I set it to false and it stopped working again

yeah if I understand correctly if you want to record your test theres some documentation on it here https://docs.cypress.io/guides/dashboard/runs#Run-details

if you wanted to record like a separate puppeteer part im not too sure

for me that's ok

yeah it works in the electron browser but not chrome

idk why

what is your version on your cypress?

and for this, let me explain my situation.. on a test, i want to do a scenario, where the user received the invite to login the first time in a system, but i need to take a generic password that he received on email. for this part, i use the puppeteer, to take the password, and at the final, i pass to cypress, and finalize with the login. But sometimes when i run on the pipeline, this part to take the password is failing, and i need to see the error, so i want to record. so my doubt is, can cypress record this task that puppeteer is already making?

I'm certainly no professional with cypress, but have you tried using "npx cypress open" instead of run so you can see the GUI ? I believe you should be able to see the entire process with the GUI

yeah, if i run locally i can see the log, but the error is giving only when i run on pipeline

so, i need to record this error, but probably the cypress could not do this

That's what the Dashboard is all about

Just updated this in 8.3

Hi All, please can you help me resolve the issue i reported earlier. It seems setting cookie and local storage isn;t a good idea in case of scenarios involving SAML / Oauth

it seems like its broken in 8.3

New since 8.2, Have you looked in using cy.session? https://docs.cypress.io/api/commands/session

I'm using cy.clearCookies(); and cy.clearLocalStorage(); but sessions are still not being fully cleared on external URLs

hi guys. does anyone knows if i can use cy.session in git lab ci process ??? im getting a error hen i try to login using cy.session >>>

cy.wait()

timed out waiting

30000ms

for the 1st request to the route:

login

. No request ever occurred.

Thanks for this @User I'll have a read of this straight away.

Hi @User I did solve my issue. I did not end up using this feature. But it's great feature to be aware of. Thanks very much for your response.

Have you cleared session storage too?

The snippet you using is developed by me. I am preserving the cookies as defaults. So, the cookies never get deleted actually. Use preserve once instead

Is this is the repo you used ? https://github.com/vrknetha/cypress-thirdparty-login

After reading the new session API docs, I want to try it. But I wanted to check if anything obvious might not work with our pretty non-standard login flow. We use Playwright to login much like this https://github.com/estruyf/cypress-msteams-sample This is the code I adapted for our use, since MS Active Directory is the auth service behind the app. So through a task, Cypress initiates Playwright, which logins, saves the cookies and local storage, then passes it back to cypress. Then the cookies/items are set in the Cypress spawned browser in the login command. The only difference I can really think of is that I believe I need to do cy.visit() after setting the cookies/items to truly finalize the login (make sure it is valid with the server and all is hunky dory). So I guess I would do cy.visit at the end of the 'setup' within cy.session, instead of at the beginning. None of this raises any immediate red flags for cy.session usage for anyone, does it?

Hi @User Yes this is the one. It's working now. I had to reorder few things in my test. Thanks for this. It's very helpful. I was looking at how I can extend this to a few tests that are in a single Js file .

Session API issues