With Cypress, you can easily create tests for your modern web applications, debug them visually, and automatically run them in your continuous integration builds.

Cypress Community

no, maybe take a Cypress workshop to see many practices in action, here is 100% open source one https://github.com/bahmutov/cypress-workshop-basics

trying to use custom command to pass through randomly generate user data from chance,js

Can you paste the definition of the `checkout` class? That's surely where your problem lies. I might not be much help myself (I know how to chain custom `cy` commands, but I fumble through js promises), but I bet someone else would be able to spot the issue.

yh I'm trying to figure out when to use prevsubject

wrap just allows me to chain a cypress command right

The way it works: the subject of the last `cy` command you ran is what is yielded by your custom command. So that can be `cy.wrap()` or can even be `cy.get()`. It's whatever you invoked last.

so someone helped me make this custom command

it lets me chain on click and wait in my spec file

`prevSubject: true` is what makes your command chainable. It means it will accept the yield of the previous command in place of the first argument in the list. In this case that's `subject`.

and what is the yield of the previous command in this example

~~`cy.wrap()` might not be necessary. It depends on what was yielded. If it yielded a cypress object then you don't need `cy.wrap()`. `cy.wrap()` would be needed if something agnostic like a string were passed in.~~

That's a good question. Without seeing the previous command's definition I don't know what the yield would be.