Thank You!

I need to implement an execution flow from login to checkout. Each transaction needs to be separate. Each transaction's performance is needed - For example page load time, response time, and all the performance metrics(ex.first contentful paint). For this I need to integrate Cypress with Lighthouse. I already created the Cypress script from login to checkout. I used the links that were posted here for the Cypress script. Now, I need to integrate Cypress with Lighthouse. My question is - How can I use my Cypress script to integrate with Lighthouse to get all the performance metrics for each transaction. I know there is the Cypress Audit plugin to integrate with lighthouse, but I don't know how to integrate my Cypress script with Cypress audit plugin and lighthouse. Please let me know. Thanks!

slightly dated, but this should give an idea https://github.com/NoriSte/ui-testing-best-practices/blob/master/sections/advanced/performance-testing.md

Thank You Murat!

Preserve cookies is deprecated

I want to just login once in my test

describe('Some test', () => { beforeEach(() => { cy.session('random text', () => { cy.login(); // in my loging custom commend i have also cy.visity() sessionCallCount++ }) cy.visit('/') }) afterEach(() => { // clean up method somecleanup(); cy.wait(1000); }); it('checkis evertyhing fine', () => { // cy.visit('/')

I don’t know if i doing right thing

Hello, I wonder if I can install Firefox extension using

before:browser:launch

event and the

launchOptions.extensions

functionality?

@fancy-match-96032 Hi

that's it https://github.com/muratkeremozcan/auth0-cypress i did the same here, and internally as well the whole login + session meta is different now, each it block "logs in" but not really since it's all cached it is kind of going towards the direction of test isolation rather than it blocks depending on each other , which is fantastic

try it out and let us know 🙂 grab a sample repo, so that if there is an issue, you can get help from outside your company

I don't want to use the cy. session command everywhere, therefore I can leave this in my code for some specific spec files where my tests reside. So this strategy in my test is acceptable?

yessir

Can anybody help me with this error? cy.task('lighthouse') failed with the following error >You probably have multiple tabs open to the same origin.

I have two tests, one test results in a page that generates a unique string. the next test requires that string. is there any way to store the string from the first test as a variable to pass to the second test?

I can get the string and store it as a variable within the first test, but I cant figure out how to make the value accessible to the second test

well, now you have introduced a dependency between the tests which is bad. But if you really want it, either use a local variable or place it into

Cypress.env

i tried using a local variable, but it doesnt seem like the scope allows for it

variables set in one test cant be read from another test

variables set in a suite look like they can be read by tests but not changed

im just not sure how to get the data out of a test so that it can be read by another test

why... 😭

js
let name
it('gets the name', () => {
  cy.get('#name').invoke('text').then(t => name = t)
})
it('uses the name', () => {
  expect(name).to.be.a('string')
})

@rapid-application-21794 are you saying the above does not work? @magnificent-finland-58048 avert your eyes

once you see it, you can't unsee it

yeah it doesn't work for me. in this case, the second test doesn't see a value associated with name

the tests can read the name variable, but they don't seem to be able to change the value

@rapid-application-21794 are you maybe running in parallel? I would think test A assigning and test B reading would be a problem for parallelization anyway.

do you visit different pages? Like different domains in two tests?