I don't see how this is related to Cypress. @best-flower-17510 , I think this is spam

I dont see any relevance to it being used for cypress., it looks like a funny project but does not have any value in the cypress general chat.

This is not on Cypress road map https://github.com/orgs/cypress-io/projects/13/views/1 And you can achieve mobile simulation by starting your test with the correct mobile User-Agent values, as Gleb has demo'ed here https://glebbahmutov.com/blog/mobile-tests/

Thanks a lot , very useful information. Appreciate it.

This is my approach https://discord.com/channels/755913899261296641/763105090679865354/1037312156095496223 utilising multiple config files and a clever Node package called

defu

to allow inheritance from our main cypress.config.ts, so then only need to list the values we need changing i.e. userAgent, viewportWidth, viewportHeight, device etc

@gray-kilobyte-89541 Would be nice to see some lessons and examples of how to run node programs(cy.exec or other) or use them as tasks inside cypress config in your tutorials. Sorry if you already have. I'll jump and subscribe now 🙂

I would not run Node programs using

cy.exec

- too many shell quirks. I would use NPM modules for anything. Anything in particular causing problems?

I'm fucking stuck at trying to test a react application built by my team.

i am new to cypress

i need to select a value from dropdown

tried targeting class,id,data-testid but nothing worked.

Can someone help please?

In order for one of us to help you, you need to think about what information we'd need to give you an informative answer Currently you haven't provided much to go off of. For example, what is the html of the element you are trying to select? Is it contained within an iframe?

Hello Cypress community, I've been using Cypress for a while now and been using cy.request & @gray-kilobyte-89541 's cy-api for my backend related stuff. Now I'm working on an open-source project (RunSidekick) and we are developing a Cypress plugin to collect detailed information from backend. It will have two main features: - First it will allow you to collect stacks at any time from backend & define e2e tests based on them. This will allow you to better understand the state of backend, a more detailed alternative to cy.request & cy.api. - Second is it will also allow you to collect stacks whenever an error happens at the backend and include those errors in your Cypress runs for you to examine. I’m looking for anyone who is interested giving early feedback and join our beta programme

There's a good chance that the drop-down is a

<select>

element. In that case, a

cy.click()

won't work. https://docs.cypress.io/api/commands/select

im using

cypress-react-selector

package and able to select some cypress element with some success at google chrome, can install

React Developer Tools

extension, and inspect will have a tab that will show the react component name

but i also have an issue on selecting dropdown

above screenshot is my react component i want to select. what does the 'key=...' thingy means at there? its not a prop right? i try to select it this way or by prop also cypress fail to get the element

Hey, guys is anyone working on parallel execution using more than 2 docker containers in an onshore virtual machine for cypress execution? if yes how many containers are you using? and how is the performance of the execution ? and would you mind sharing the configuration of the virtual machine?

Not exactly this but related. I am looking for a best practice solution here. I’m running cypress in three virtual machines: WSL, macOS, and win11, all hosted on a windows 10 machine. I’m doing this specifically to run some accessibility test under different system themes in those OSs. Should I be using docker containers inside these VMs rather than install Cypress traditionally? I don’t seem to have any trouble installing, but it does seem overly redundant.

Yes definitely agree that it could be redundant. To reduce this u can have a custom image created and can directly use the image to create containers and if any thing u need to change with simply update the custom image and If you are planning to achieve parallel execution it is better to have containers 6 vm *2 containers = 12 tests can be executed parallel. hope i have not take you off track

Thank you, that’s very helpful! So then should I modify the cypress containers (cypress/included in particular) or create from scratch?

Yes, i would suggest you to do it from scratch take base image like cypress/browser on top of this install your project specific node modules and cypress through a docker file and keep building it every now and then based your development model hope this helps you

Team is there any way to stop all nested describes in case of one of the Iterations (Test case) is failing inside one of the nested describes there by making sure not to effect other specs

Sounds more like an issue with the approach. Why are the scenarios dependent on the previous ones passing? They should be able to run independently

We are grouping few of them in nested way there by dividing test cases like UI/Functionality/Issues etc., Per SPEC so this group of testing and nested are related so approach is always tunable 🙂

Grouping related scenarios makes sense, but that doesn't mean there should be interdependency between the scenarios. Ideally, each one should be able to pass in isolation. For example, what happens if you isolate one of the middle scenarios in a spec with an

only()

?

if i use IT.Only then i think i need to write this for all the ITS in the spec file .... hmmm ok let me think how to make this work in simple way .....

> if i use IT.Only then i think i need to write this for all the ITS in the spec file no, I'm not suggesting this as an answer to your initial question. I'm asking if your scenario is capable of passing if the scenarios before haven't run. If not, then there's an issue with the way the spec is designed (if you added

only

to all

it()

statements, you might as well add it to none of them)

Yah as my all specs are independent and by nested Describes are dependent so my intension was to stop all Its in current spec on failure ok i will try to check by adding only to it blocks please correct me if i didnt understood your intension correctly?