The cucumber preprocessor(s) have about 10% the number of downloads compared to Cypress on NPM

*🔥 Cypress tip🔥 * Need some help migrating your Angular Protractor tests to Cypress. The awesome DX team here at Cypress created a migrator for you. https://migrator.cypress.io/

Hello all. The Cypress runner has a left-side black background - I struggle to see text clearly on dark backgrounds. I looked around in "settings" gear on the far-left menu but didn't see any config options there. Is there way to configure this to be a white/light background?

Not at the moment, though this has come up on #974362106822545429 before. My suggestion would be to add your voice to the growing chorus. There's also a workaround outlined here: https://discord.com/channels/755913899261296641/974362106822545429/992368527820472350

I'm trying to install version 10 with the new structural changes, does everybody in the team needs to have version 10 or they can be on the older versions?

Hi there, anyone tried running test to Safari using the Applitools Ultrafast Test Cloud ? I see that safari is not (yet ?) supported by Cypress but applitools is the one (so far) that I've seen that it's possible. The project where I'm working on wants to run it in safari, but since it's not possible, they plan to move to using Playwright instead.

Hi, can i do somethink with it https://tempail.com/en/? in cypress I mean, how can i build a function to always paste what mail i got from this website and automatically use it in the registration step?

if they have api, then you can rely on calling that api or building your own function as task ? Also, there are already few plugins integrated with cypress for email. Check out here https://docs.cypress.io/plugins/directory

also you can use wrap and provide an alias to retrieve the value in future steps

Hello All, I set up the cypress 10.0.x from scratch and currently facing below issue , any insight? I am running with cucumber framework.

Is there any way to set a config attribute inside a spec file ?

sure, but what are you trying to set?

can anybody tell me how to mock or update the context.Provider in React JS for e2e teseting with cypress . Thanks in advance

Hi, I have a problem with the video recording of tests. When I run the tests locally it works fine but when the tests run in the CI the video freesez. Does anyone have experience with this?

Could be the result of underprovisioning. Try allocating more CPU and memory to each of your Cypress machines in CI and see if that helps

I want to set the baseURL

I think you can just set it by

Cypress.config('baseUrl') = url;

Though I'd suggest setting your baseUrl outside of the spec, so that it's been set before the spec starts. If you set it in the spec, you'll have a couple of seconds where the browser is reloading

Since last upgrade I have been seeing this error, while executing script Do anyone facing the same issue?

Error code says Out of Memory . Did you try checking the memory consumption and if the system has enough memory to run tests ?

40% of memory is free

while execution utilization goes up to 60%

I would use https://on.cypress.io/configuration#Test-Configuration

Hi everyone Please I need help. Cypress is not working when we try to access Sharepoint Online Intranet because Cypress can't access the Microsoft login. We can't executed automate tests.

I dunno, but this looks like a potential solution - https://www.eliostruyf.com/cypress-testing-sharepoint-solutions/

Hello team, is this https://docs.cypress.io/api/cypress-api/custom-commands#Overwrite-type-command outdated?

Sorry, I think I dropped the message in the wrong channel. I'll use #763105090679865354

Gleb, this video speaks to me: I always felt like Cypress, despite being an excellent tool for e2e tests, was developed by developers (of course) who perhaps have not had the pleasure of coming at it from the QA e2e side. We've been through a lot of the challenges you mentioned and have come out successful with nearly 200 green tests (and on a good day, no red). Myself not being a developer, I really struggled to get developer involvement, so I went down the do-it-all-myself path (now with one other dedicated automation engineer). It's not ideal but it is very doable, all while ensuring the tests are highly readable and minimally flaky. I really like your document-first approach and your tips for involving developers; may come in handy if/when I revisit the subject.

On a related note, when writing lengthy e2e tests incorporating multiple service calls, as a non-developer I've actually found it beneficial to avoid using the API. Not because the API is difficult, but rather because unexpected changes to the API will lead to tests that break in the best case, and in the worst case tests are are no longer valid, and no one realizes it until it is too late. Imagine the following scenario: 1. Dozens of tests are written utilizing user creation API 2. Developer adds a new parameter to the user creation request, writing a new value to the user's database record 3. Developer neglects to inform QA of the updated API. QA neglects to notice. 4. Bug is introduced that only applies to users who have the new value 5. Months pass. Bug lingers uncaught. If you are relying on the API to create your users then step 4 is going to happen without you knowing it. This is, of course, a huge problem. Initially I used the API as often as possible, shaving a second off here and there, but over the months/years I was bit again and again as API changes were slipped in without my knowledge. Fortunately no catastrophic bugs were let through, but I've gone to 100% clicks now and there's no way I'll ever go back.

All I could think when reading this is that it sounds like your devs aren't taking enough responsibility for code quality. Instead it sounds like QA gets the blame when things are "slipped in" or "let through". I can understand why, based on your experience, you'd want UI steps everywhere, but I can see there being so much duplication between specs if user creation goes through the UI each time. How long do your test jobs take these days? (Also not a developer by trade. Picked up most of what I know while working with Cypress)

> I can see there being so much duplication between specs if user creation goes through the UI each time Less than you would think. User creation (and login) is a pretty quick process in our case. If it were 30 seconds UI vs 3 seconds API I would absolutely go for the savings, but it's more like 5 seconds vs 3 seconds. You have to consider that using the API is only dodging a few short page loads, while all the back end work is the same. In the case of our website the back end work takes longer than the page load, so for my situation it's not much of a benefit. Developers doing some form of TDD might be more inclined to favor quicker methods. > How long do your test jobs take these days? That really depends on the test. Many tests are 20 seconds or less, but we have some that are a few minutes long, especially tests that validate email sending and receiving, and the email itself. Split between three threads, our ~200 tests take about 25 minutes. (This is not a very relevant part of the discussion though, since numbers can be deceiving.) > it sounds like your devs aren't taking enough responsibility for code quality Maybe, maybe not, but the scenario I described is not unusual for any team. Miscommunication is common, and even in a very responsible team you will have irresponsible moments. The entire point of e2e testing is to catch issues that technically should have been caught during development. Everyone's API situation is different too. I'm in favor of doing everything you can to speed up testing as long as the testing itself is not compromised. But you really should consider your use case. Reducing my test runs from 25 minutes down to 23 wouldn't benefit me at all. And in my case there are very real problems that arise when leaning on the API.