did you find an answer to this?

Hey Guys, is there a workaround for CYPRESS_NO_COMMAND_LOG=1 in Cypress 10?

did you get this to work in the end?

Hi all, since using v10 I'm having issue with test sync. I have a Cypress opened, run some tests, then go back to my IDE and edit them, Cypress detects well that I've changed something and reload... but redoes the exact same tests, without my changes. I've tried to deactivate cache in Electron's console and reload the page, but nothing changed, it loads some cached test from I don't know where. Any idea what could be going wrong?

hi there, I am upgrading to v10x, and having trouble with the specpatterm. under 9.x i had testFiles": ["**/*.feature", "**/*.spec.js"].... the upgrader moved (most ) of my folders to \e2e instead of integration. https://gyazo.com/deb808754792c53a6f1dedfee70170cb the two I am worried about the most at the moment are the cucumber, which has *.feature files and the laminar which has *.spec.js files. I am not able yet to create a specpattern in the ts file that will show both sets in the gui like i could in 9.x. any pointers appreciated!

Nope. I abandoned it for the time being.

I have a PR up to get it working again, it should come out in one of the upcoming releases, not sure which one yet though.

Anyone facing this issue after installing cypress 10.0 version

Hi team, Do we config "TypeScript aliases in Cypress" in 10.x version? If yes, please share me the link. Many thanks

report

hi

Hi anyone can help me work this through, I wish to create a cypress commands for this multiple parameters.. anybody? thanks in advance ❤️

I have created a custom commands i feel like im missing something here like declaring a variable in global how should i do it ? thanks

Hi, my test fails when I minimize the window of testing, theres any way to fix that?

where are these parameters coming from?

describe

does not take any parameters, so those values are all undefined. Are you trying to run the same tests with different data and thus you need those parameters passed in? Take a look at https://github.com/bahmutov/cypress-each

Hey everyone! I'm trying to learn how to test in Cypress, but I've gotten a problem. I create an object in a db with a post request using cy.request, and in response I get an ID of the object created. The next step is using this ID as a variable in the test (searching certain columns etc). However, as the request is asynchronous. do I need to run my whole test inside the .then after the request or is there another way to store and use the returned ID?

Hi everyone! I need your help please. I am using Cypress version 9.6.0 and getting the error while running the Cypress automation tests in GUI as well as headless mode. The error message is as below:

Error: Webpack Compilation Error
./src/assets/icons/yat-hand.svg 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

Hi, my test fails when I minimize the window of testing, theres any way to fix that?/why it happens?

Hi Everyone, does anyone faced this kind of issue while trying to fetch code-coverage "Code coverage Cypress and Storybook, can't instrument my code" facing the similar problem as below https://stackoverflow.com/questions/61059917/code-coverage-cypress-and-storybook-cant-instrument-my-code any suggestions

How can I run my testcases in a specific order?

"testFiles": [ xcv.js,vbn.js] ] .Including this in cypress.json will execute files as per the order

I dont think testfiles works anymore for Cypress 10? dont it?

well I am still using 9.5.4 so not sure

I am unable to preserve session/cookies in headless mode while I am able to preserve the session via the test runner.Has anyone encountered this before?

If I understand you correctly, I think that this is expected behaviour Session and cookies shouldn't be preserved between scenarios. The fact that Cypress was doing this in

open

mode is the main reason why

run all specs

was removed in Cypress 10

then should we login everytime before a test runs to stay in session?

That's what I do for my tests currently, yeah. If you can log in via an api, it doesn't add too much time to the execution. Though if you're doing it via the UI that would be painful Otherwise, the Cypress team is working on a

cy.session()

api that allows you to save session cookies between scenarios and reuse them. That might be useful for you. It's got some great documentation so it shouldn't be too difficult for you to get up and running

Hi, welcome to the Discord! Couple of things: Please don't post the same question multiple times on channels. It just generates noise The reason you've probably not had much luck with an answer is that your question is pretty vague. Are you running tests with

cypress open

? If you're going to minimise the window anyway, wouldn't

cypress run

be a better option for you?

Hello everyone, please advise. I installed the new CYPRESS 10.3.0. and when I run .\cypress open it gives me an error (Cypress failed to start. This may be due to a missing library or dependency. https://on.cypress.io/required-dependencies Please refer to the error below for more details. ---------- [0711/171842.821:FATAL:v8_initializer.cc(508)] Error loading V8 startup snapshot file ---------- Platform: win32-x64 (10.0.19043) Cypress Version: 10.3.0). Maybe someone know some solution for this problem? Thanks in advance and have a nice day

Hey @elegant-river-87347 , as for custom commands with multiple parameters, Cypress has a whole page on such which I recommend, but this example specifically shows what that looks like: https://docs.cypress.io/api/cypress-api/custom-commands#Download-a-file But it seems like your question/problem isn't with that, it's with variable contexts. For that I recommend this entire page: https://docs.cypress.io/guides/core-concepts/variables-and-aliases. But specifically, what you're probably looking for is using an alias to store a value to be used later: https://docs.cypress.io/guides/core-concepts/variables-and-aliases Personally, I like using aliases with the

cy.get()

syntax instead of

this

. But you can always have a custom command return a value and access that value with

.then

or store it for later on in your test with

.as

as the articles show