in a nutshell, I want to run different test cases for different users

Hey everyone we stumbled into an issue in our CI after updating to v9.x.x, locally everything works as expected but on CI something goes wrong and doesn't really help us to figure out what is going on.

The function exported by the plugins file threw an error.

We invoked the function exported by `/home/runner/work/web/web/migration/cypress/plugins/index.cjs`, but it threw an error.

 Error: Not supported
    at module.exports (/home/runner/work/web/web/migration/cypress/plugins/index.cjs:2:5)
    at /home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:90:12
    at tryCatcher (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/util.js:16:23)
    at Function.Promise.attempt.Promise.try (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/method.js:39:29)
    at load (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:87:7)
    at EventEmitter.<anonymous> (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/lib/plugins/child/run_plugins.js:198:5)
    at EventEmitter.emit (events.js:210:5)
    at process.<anonymous> (/home/runner/.cache/Cypress/9.2.0/Cypress/resources/app/packages/server/lib/plugins/util.js:19:22)
    at process.emit (events.js:210:5)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:81:21)

This is on

latest-ubuntu

on GitHub Actions though when using

latest-mac

the response is even stranger

Platform: darwin-x64 (20.6.0)
Cypress Version: 9.2.0
    at /Users/runner/work/web/web/node_modules/cypress/lib/errors.js:330:17
    at tryCatcher (/Users/runner/work/web/web/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/runner/work/web/web/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/Users/runner/work/web/web/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/Users/runner/work/web/web/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/Users/runner/work/web/web/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/Users/runner/work/web/web/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/Users/runner/work/web/web/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/Users/runner/work/web/web/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/runner/work/web/web/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:439:21) {
  known: true
}
Error: The cypress npm package is installed, but the Cypress binary is missing.

We expected the binary to be installed here: /Users/runner/.cache/Cypress/9.2.0/Cypress.app/Contents/MacOS/Cypress

Reasons it may be missing:

- You're caching 'node_modules' but are not caching this path: /Users/runner/Library/Caches/Cypress
- You ran 'npm install' at an earlier build step but did not persist: /Users/runner/Library/Caches/Cypress

Properly caching the binary will fix this error and avoid downloading and unzipping Cypress.

Alternatively, you can run 'cypress install' to download the binary again.

hi team, we are upgrading yarn to v2, it working locally but no in the pipeline using image

cypress/browsers:node16.5.0-chrome94-ff93

. Is there a cypress image with higher node version

v16.13.1

?

Cypress has no idea your component is NOT ready to process the input - it sees the input box which is enabled and starts typing. See https://www.cypress.io/blog/2019/01/22/when-can-the-test-click/ and https://glebbahmutov.com/blog/flaky-cy-type/ A very fast user can hit the same problem when the first part of the entered test disappears. You should disable the input box by default and enable it when the component attaches the event handlers.

testFiles in cypress.json

new video: Visit Two Domains In The Same Cypress Spec

I have a new post up! I discuss patterns for selecting DOM nodes in your tests by ranking different methods and why interacting with your DOM like a user should be your guiding principle. https://www.capocaccia.dev/posts/testSelectors

Is there anyway to use cypress to test for datatest ids before integration tests?

at Object../node_modules/is-ci/node_modules/ci-info/index.js (webpack:///node_modules/is-ci/node_modules/ci-info/index.js:5:1) at __webpack_require__ (webpack:///webpack/bootstrap:19:1) at Object../node_modules/is-ci/index.js (webpack:///node_modules/is-ci/index.js:3:18) at __webpack_require__ (webpack:///webpack/bootstrap:19:1) at Object.eval (webpack:///node_modules/cypress/lib/util.js:21:14) at Object../node_modules/cypress/lib/util.js (http://localhost:37869/__cypress/tests?p=test/e2e/support/index.js:87250:31) at __webpack_require__ (webpack:///webpack/bootstrap:19:1) at Object.eval (webpack:///node_modules/cypress/index.js:9:14) at Object../node_modules/cypress/index.js (http://localhost:37869/__cypress/tests?p=test/e2e/support/index.js:82972:31) at __webpack_require__ (webpack:///webpack/bootstrap:19:1) From previous event: at runScriptsFromUrls (http://localhost:37869/__cypress/runner/cypress_runner.js:177985:98) at Object.runScripts (http://localhost:37869/__cypress/runner/cypress_runner.js:177999:11) at $Cypress.onSpecWindow (http://localhost:37869/__cypress/runner/cypress_runner.js:167733:19)

can anyone help me in this

How to continue test execution with the rest of the data from the fixture file when an assertion fails with one of the test data. Ex: I have this json file as fixture, when I assert "email" from the first fixture data which is invalid cypress throws an error and stops execution. But I would like it to continue with the 2nd and 3rd fixture data and not stop execution at the 1st

[ { "name": "valid1", "email": "invalid1" }, { "name": "valid2", "email": "valid2" }, { "name": "valid3", "email": "valid3" } ]

thank you

Hi @Ceciliacreates. This issue has been open awhile. https://github.com/cypress-io/cypress-docker-images/issues/555 related to the issue above. It seems to be new in the 9.* cypress docker images. Seems like a lot of others are seeing similar issues. I think my original thought was the dbus warnings were an issue but it looks like it's the error on mkdir that @User is referencing

Hey, as my original question was about a problem (with using aliased

cy.request()

with

cy.wait()

) that i solved, eventually i thought that i might ask about improving docs a bit by clarifying the case with aliased

cy.request()

and

cy.get()

i described on #763105090679865354 channel (which i think it is better to discuss on this channel) https://discord.com/channels/755913899261296641/763105090679865354/930928075032645662 So, would such clarification be helpful enough to put in the docs around the mentioned example?

It sounds useful, you could make a PR for the addition in the docs repo and get more concrete feedback: https://github.com/cypress-io/cypress-documentation

oh, i am glad it'd be useful 🙂

i'll try to contribute with this

Hey all! I am trying to migrate from cypress-file-upload to new selectFile. However, I can't just replace a basic attachFile with selectFile as it doesn't work with any of the browsers I tried except Firefox. Has anyone encountered this problem?

For reference it doesn't work for Chrome, Electron, Edge

hi all, do you know how I use cy.intercept to check that NO requests are made to a specific url?

Well I figured out an alternative, I can throw an error from the route handler if it gets called 🤷‍♂️ not too fancy but gets the job done

Hello all

Hello

how you doing

🤣

I will answer, so it's a bit more responding here ^^ I'm fine Just worked 11h today on a to vitest migration 🥳 @User What did you today? 🙂

well trying to figure out how to type a const into a input field in cypress lol