Ah, there's a task hook I can use

But that doesn't trigger when you stop a test in the UI or close it... ugh

Are you talking about https://docs.cypress.io/api/plugins/before-run-api?

yeah!

Hello to all. I'm coming to you to ask for help, because I haven't found a way to enable or disable network stubs depending on the configuration. If this functionality does not exist, I will create an issue on github. To clarify my need: We need to develop a microservices application with total separation of frontend and backend(s). So, our frontend developers need to be able to mock the APIs in order to create the service contract and move forward directly. On the other hand, we still want to do final end-to-end tests in the deployment pipeline on the staging environment. Hence the need to be able to activate certain intercepts during development, and to deactivate them in the pipeline via a configuration (on/off) But maybe we are wrong in our strategy? Thanks in advance for your help

Can't you use a node ENV variable and conditionally enable intercepts?

I opened this issue 5 months ago and it's not getting any responses: https://github.com/cypress-io/cypress/issues/17532 A new issue was opened and did receive a response, but no action has been taken. If someone can point me to where the logic for this hook lives, I'm more than willing to open a PR for a fix (if I can find the issue).

Hola! I ran into the same issue as this person on stackoverflow: https://stackoverflow.com/questions/68307782/cypress-test-not-finding-element-when-ran-in-gitlab-ci Locally, my test runs just fine. Also after clearing my npm-cache, reinstalling dependencies etc. A colleague of mine also faces no issue with running the tests locally - all tests succeed. Only in the GitLab pipeline one single test can't find an element by

data-cy

- even tho it succeeds locally. It results in an assertion error, as stated in the Stackoverflow post. Any ideas on what the issue could be? We already tried to clear the GitLab runner cache and re-ran the pipeline but it didn't help... #763105090679865354

Yes, that's what we'll do, thanks for the tip. I'm going to do an issue to see if it can be handled directly at the cypress level. Like a flag on the intercept for example Wishing you a good day

hey there!

I have an issue regarding file upload https://github.com/cypress-io/cypress/issues/19452

if any one have the way to figure out that be a much help! Thanks

Assertion fails in CI pipeline but not locally

Issue still persists, need help 🙂 Any ideas?

Hi All! 🎄 I have an issue with Firefox in Docker image. I use cypress/included:8.5.0 (https://github.com/cypress-io/cypress-docker-images/blob/master/included/8.5.0/Dockerfile) as base image, and add MSEdge to that image so that I have one image to use for all my tests in CI. At least, that's my goal. The image builds and works well in CI with Edge and Chrome as browsers. However, when I try to run with Firefox as browser in CI, I get an error as shown here. Starting the image locally and running tests there in Firefox works 🤯 As can be seen in the 2nd image - Edge, Chrome and Firefox are all detected as browsers in the docker image. Anybody got any idea why I'm not able to run Firefox in CI? 🤔

I hope I'm not too far out of scope for this community with this request but I'm trying to determine which test management tool to use at my company.. we use a ton of headless cypress scripts and I'm trying to decide between Testrail (popular expensive), Qase (cheaper so far I like it) and Testpad (very basic, easy, no coding and most expensive). I'm thinking of going with Qase (we use github for issue tracking and deployments) but I'm wondering if anyone here has any long-term experience and would recommend something else? Thank you so much - I'll delete this question or move it to a more appropriate spot if requested! Basically is there a test management tool that just blows everything out of the water and you never want to go back? lol 🙂

How to contact pre-sales related to Cypress dashboard?

The only obvious option might be the contact us for the enterprise pan on the pricing page ;-)

Ah thanks! It is in the public pricing page… I went to the pricing page under dashboard’s billing. Got it thx !

Hey guys, any idea how can i click two elements? Cuz i couldnt figure out how. The line 22 deletes just one task but idk why in the first each(tasks) it does click on the 2 checkboxes

Hey guys! Can I somehow open tests in my own browser? The problem is that I have an extension installed without which I cannot enter my personal account

click two elements

Hi all! My question is about code coverage support for the dependant npm package. I have a system with multiple Vue.js apps sharing a common npm package with generic logic, features, and components. My team also manages this shared package. I’ve successfully integrated Cypress e2e tests and code coverage for Vue.js apps, but all code coming from my package is ignored in the code coverage report. Does anybody face similar problems? Some tech details. I use babel-plugin-istanbul for code instrumentation for both: app and shared package. Versions: "cypress": "9.2.0", "@cypress/code-coverage": "3.9.12", "babel-plugin-istanbul": "6.1.1"

Hi! I'm upgrading to 9.2.0 and I'm seriously struggling with types for

Cypress.Commands.overwrite('visit', ...)

Is there any decent explanation of how to proceed? 🙏

I am witnessing unexpected cypress run command behavior in that when there is a test retry, even if the retry succeeds, the npm task does not complete...it just hangs. There is a message that all specs passed but the task won't exit. Has anyone else experienced this?

Is the issue with the spread operator in general? https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax

Hi @User Can you provide a screenshot of the error your are getting or explain a little more?

Hi. I was wondering if anybody has run into issues setting up Cypress to use Okta. I am getting some strange errors and I am wondering if the article to set up Okta is missing some requirement, like installing Okta components locally or something. I followed the instructions from this article (https://docs.cypress.io/guides/testing-strategies/okta-authentication#Setting-Okta-app-credentials-in-Cypress), but I get errors that the module is not found. Error: Webpack Compilation Error ./cypress/support/commands.js Module not found: Error: Can't resolve '@okta/okta-auth-js'....

Hey, how to change the size of the whole window (blue rectangle marked as "2"), which contains the browser with app (green rectangle marked as "1")?