I will try it. Thanks.

hello everyone, I'm migrating my Cypress tests from v11.x to 12.x and i'm reading this https://docs.cypress.io/guides/references/migration-guide#Test-Isolation On my website, let's say that I have to test a pretty huge KYC-validation process. It's a process that goes on 7 differents steps. Each steps is a different page, with differents things to fill or not. At this very moment I have 18

it()

to cover the whole process. With the 11.x I just had to do one

.visit()

to go to the fist step. Then I fill the inputs I need, then I submit the form from this first step and boom, second step without a new visit, since the page changed with the validation of the form. How I am supposed to do with the 12.x version? I think I can't do a

beforeEach() => cy.visit()

since I don't know the URL of the differents steps. I have some concern about the duration of the test too if I have to login, visit the page, etc. before each of my 18

it()

. What should I do? Thank you for your answers.

when there were 18 it blocks, could you run each of them with .only? If not, that was the first mistake, because it means the tests were order-dependent You can put everything in 1 it block. You can abstract away substeps to functions or commands to make that large it block more manageable You can do some of it via the api, or the browser (app actions) if it's a repeated form filling Gleb has an example repo (and a matching blog somewhere) https://github.com/bahmutov/cypress-example-forms He also has a paid course, the main example is here https://github.com/muratkeremozcan/fastify-example-tests/blob/4da614c8aa764bbcd99488d2bdbf656d7ae755f8/cypress/e2e/bonus41-43-multiPartForm-FormData-Cypress.Buffer-cy.document-invoke-write.cy.js should make more sense if you take the course

hello, thank you for your answer and your time. No I can't run each one of them with .only(). Maybe it comes from a misinterpretation of the utility of

it()

on my side. I use them like one

it()

is one thing to test on my page. Like on it() to fill this input, an other for an other one, etc. So yes, it's absolutely order-dependent. I understand my mistake, indeed. Thank you very much for the rest of your comment, I will watch this out very carefully. have a nice day and an happy new year!

I have a svelte frontend and directus backend. I register a user via the front end and the status is set to "invited". The idea is an admin receives a notification, finds the new user in the directus app, sets status to "active" and user can then log in. And doing this manually works. But if I do this via cypress there is some unexpected behaviour. The cypress script registers the new user via the browser, then uses the directus rest api to log on as admin, get the new user id, update the status for the new user and logs out. The script then continues to log in as the newly registered user. But this login fails with invalid credentials. If I then try to login via the browser or curl then same error. User is now locked out effectively. If I do all of the above via the rest api, it works so it does seem to be cypress centred. If I split the cypress into two tests and manual step then it also works. So first script registers user. Then manually via the app as admin, find user, change status. Then second script logs on as new user and logs out. Is the problem centred around tryiong to log in as two different users within the same script, once as admin via request and once as new user via the browser? But if that is the problem, why then the user is unable to login out outside of cypress?

Hello All, I am working on SMS Automation using mailosaur, while automating I am using async...await in spec file Reference : https://mailosaur.com/docs/sms-testing/ I am able to see the new SMS on mailosaur account, but I am not able to fetch the SMS in Cypress. (whatever the code which written in async is no picked for exeuction) Can someone help me here?

Question: Should Cypress be able to run e2e tests without your application running locally from another terminal?

Don't use

async/await

, use

cy.request

and

.then

to then do X or Y after said request is finished. If you want it to be a function you call, make it a command, and wrap the request response in

cy.wrap

at the end of the commend, which you can then call and use

.then

to get the wrapped response.

that is not how you use cypress-mailosaur, read the plugin's README and/or blog post https://glebbahmutov.com/blog/cypress-mailosaur/

Question: Can I configure Cypress to use a local running instance of my application vs compiling with Webpack? I'm struggling to get Cypress' webpack config to compile our application, but my application runs without a hitch.

hello everyone,

how can I use with cy.contains: if element exists, do this, if not, do this normally i can use bahmutov "if-plugin" but its not working with allure report

How to handle app re-rendering in background even after the UI elements are visible. Unable to assert using intercept as my project is using firestore API

Can anyone help me👆

how do you know as a user that the app has finished rendering?

After the activity indicator closes

cy.get(activity indictator).should(not.exist).then()

I’ll elaborate my issue here 1. Navigation to order list page 2. Added assertion to indicator not exist 3. Clicking on create order button 4. Entering new order details While entering data the fields are getting cleared as there is still background re-rendering happens and unable to save form as fields are cleared

cy.wait()

might be your only option here.

if you can't use intercept.

Yea I’m managing with cy.wait() but still looking for better approach

all I would suggest is

intercept

. Sounds like your UI needs to not clear that spinner until it's truly ready for form input.

So thought of hearing from experts like you

But intercept can’t be applied here as the app is using firestore apis

@melodic-sandwich-17161 hey will you be my help for Cypress again

Hello does anyone have an idea how I can skip a whole test suite conditionally based on the current environment? I got the recommendation to use

this.skip()

but apparently this only works for a single test but no the whole suite... Below is the code I currently have but that fails.

describe("TESTING-365 ...", () => {

    //Conditional skip
    if(["DEVE","INTE"].includes(Cypress.env("name"))) {
        this.skip()
    }
}

I would be using test tags for it, like using

@bahmutov/cy-grep

plugin