https://cypress.io logo
Join Discord
Powered by
# general-chat
  • f
    What you mean?
  • f
    🤔
  • i
    Probobly still have your env file locally with URI defined somewhere and it is still used somewhere in the test code
  • f
    I have only 3 tests and none use the env var 😔
  • g

    https://www.youtube.com/watch?v=f5UaXuAc52câ–¾

  • p
    I have a test that only fails in headless mode with electron. If I run the same test in chrome the test passes. What could be the reason for this?
  • f
    Should write this env var like this or like cypress? 🤔
  • g
    these are two different ways of putting variables into 
    Cypress.env()
    object
  • f
    Hey guys, why I get this error only in one test file?
  • f
    In another file it doesn't happen
  • f
    Idk why it recognizes cy like Jest when I have this on the top
  • a
    I don't know the real answer, but if I was your IDE, I would throw errors until you moved from 4-space to 2-space indents. 🤣
  • c
    hello
  • c
    Has anyone renamed a screenshot taken with the cypress-plugin-snapshots
  • c
    i try it so: module.exports = (on, config) => { on('after:screenshot', (details) => { const newPath = path.resolve(__dirname, '../reports/mochareports/assets/'+details.specName+'/'+details.specName+'(failed).png') fs.renameSync(details.path, newPath) return { path: newPath } }) }
  • c
    the screenshots was renamed, but also i becomes this error
  • f
    @User How can I make actions to recognize my cy.env variable? I can't make it work
  • f
    I'm using vite btw if that helps
  • r
  • f
    where?
  • r
    Your second screenshot looks like a docker-compose file... try it there. The prefix is s signal to Cypress that you want that variable to be available in your test runs. > Any OS-level environment variable on your machine that starts with either CYPRESS_ or cypress_ will automatically be added to Cypress' environment variables and made available to you. > > Cypress will strip off the CYPRESS_ when adding your environment variables.
  • f
    My second image its github actions
  • r
    Same principle...
  • c
    hello can anyone please help me
  • c
    renamed a screenshot taken with the cypress-plugin-snapshots i try it so:
    Copy code
    module.exports = (on, config) => {
  on('after:screenshot', (details) => {
    const newPath = path.resolve(__dirname, '../reports/mochareports/assets/'+details.specName+'/'+details.specName+'(failed).png')
    fs.renameSync(details.path, newPath)
    return { path: newPath }
  })

}
  • p
    I'm writing tests for a website that has multiple modules for each customer. Some customers use just a few modules, and others have more. I'm looking for ideas on how to configure tests for each customer so that I can test just the modules they have activated. I want to be able to set some inital data for each customer, and then have cypress run the corresponding tests. Ex. customer 1 is using module A,B, C - customer 2 is using module D,E,F. Does anyone have examples of how this can be achieved?
  • o
    I had some issues with another plugin recently with a similar error. The problem might be, that your export has to return the configuration object. Yours doesn't do that. It might be that a simple 
    return config
    before the closing bracket might just solve it.
  • o
    Copy code
    module.exports = (on, config) => {
  on('after:screenshot', (details) => {
    const newPath = path.resolve(__dirname, '../reports/mochareports/assets/'+details.specName+'/'+details.specName+'(failed).png')
    fs.renameSync(details.path, newPath)
    return { path: newPath }
  })
  return config;
}
  • h
    Hi all, I am new in Cypress and, I have a question that I'm not sure what is the correct answer cypress searching the element inside the DOM or in the screen? if I have cy.contains('Apply) Because of a bug in THE UI, the button is not rendered to the screen like it should (buttons overload) well, but the button exists in the DOM. Does Cypress should find the element or not?
  • o
    Not sure if I understand your question, but there are checks for visibility of elements. https://www.tutorialspoint.com/cypress/cypress_hidden_elements.htm contains() should probably return true because the button is in the dom.
1...323334...127Latest