https://cypress.io logo
Join Discord
Powered by
# cy10-feedback
  • f
    Did 
    after:run
    stop working in open-mode (given experimentalInteractiveRunEvents) with v10?
  • f
    Ouf, looks like this has been broken since v8, ref. https://github.com/cypress-io/cypress/issues/18955
  • w
    thanks for flagging this, I'll put some labels on it to raise the visibility (should be labelled "bug" for example, and be routed to the core team)
  • w
    It looks like a contributor has had the same problem and has a PR drafted (https://github.com/cypress-io/cypress/pull/22930) so that behavior may come back soon.
  • c
    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?
  • b
    they'll also need to be on v10 as well, though I guess in theory there's probably a way to construct configs/cli arguments to run both (but that sounds like an awful idea afaik)
  • c
    I have downloaded the v 10, but my teammates are using v9. is there any chance that I can downgrade to 9? I tried downgrading to v9, but it did not work out the system is getting crashed, so could you please let me know if there is any way to go back to 9?
  • b
    are you able to revert your local working state to the main branch and just npm/yarn install again from there?
  • c
    no
  • m
    clear cypress cache https://docs.cypress.io/guides/references/troubleshooting#Clear-Cypress-cache delete node_modules clear yarn / npm cache install
  • w
    Hi all I ve upgraded to cypress 10 3 0
  • p
    I have an issue to report. I recently added context(()=>{}) to my tests and now when issues are found in the CI/CD pipeline the screenshots only include the logging from the first broken test and not the actual broken test (lets say we have 5 errors in a test suite). @wonderful-match-15836 if you need more information on the issue i can share screenshots in private
  • l
    Why were plugins moved in v10? Having them in 
    cypress.config.ts
    confuses me.
  • a
    everything goes in that file now. It was initially done to get away from 
    .json
    as a config template I believe, but then ended up just being a whole re-think of the 
    plugins
    and 
    config
    folders.
  • l
    Everything? 
    commands.ts
    remained in under the 
    support
    folder (which makes more sense, doesn't it?)
  • l
    And when I write tests, I'm using both plugins and commands, so I feel I'm trying to keep track (mentally) of where the code I need to work on is located.
  • a
    Oh yeah, custom commands are still under 
    /support
    .
  • l
    Just a little more thought, if I need to write a helper function for a plugin, that goes in the config file???
  • a
    I just mean everything in terms of config / dependencies. Not things like commands or fixtures.
  • l
    The Cypress team does seem to acknowledge this isn't real:
    Copy code
    ts
    // We've imported your old cypress plugins here.
    // You may want to clean this up later by importing these.
    // setupNodeEvents(on, config) {
    // return require('./cypress/plugins/index.cjs')(on, config)
    // },
    ...but in current form, this suggestion won't work with ESM. I guess I'll have to do some experimentation, but thought the team might offer some of their thoughts here.
  • n
    GG @late-house-1562, you just advanced to level 1!
  • a
    Probably? I honestly don't know this answer.
  • a
    I don't really use any plugins. I used 
    cypress-testrail-simple
    for a while but now I'm back on pretty much vanilla Cypress.
  • l
    Do you use Cypress with any databases? That is why I'm using them. Or is there another way to seed/clean up databases?
  • a
    I don't yet, but I think this is something that's usually done via 
    cy.task()
    as an externally spawned Node process, outside the runtime of Cypress itself.
  • n
    GG @adorable-smartphone-87280, you just advanced to level 1!
  • l
    Afaik, 
    cy.task
    is what runs the code formerly known as plugins.
  • a
    I think plugins get called from 
    cypress.config.ts
    . I think 
    cy.task
    is about kicking off Node processes. And yes @late-house-1562, 
    task
    can be used to see databases. See here: https://docs.cypress.io/api/commands/task#Examples
  • w
    I have an issue to report I recently
  • f
    From https://docs.cypress.io/guides/references/migration-guide#Updated-Test-File-Locations: > Generated screenshots and videos will still be created inside their respective folders (screenshotsFolder, videosFolder). However, the paths of generated files inside those folders will be stripped of any common ancestor paths shared between all spec files found by the specPattern option (or via the --spec command line option or spec module API option, if specified). This causes problems in all libs for snapshot testing, seen EG. here: https://github.com/cypress-io/cypress/issues/22753
1...121314...18Latest