https://cypress.io logo
Join Discord
Powered by
# general-chat
  • p
    How can I select a div that does not have a given inline style attribute (background-color)? something similar to this (except have.css doesnt work): cy.get("div") .not("have.css, "background-color: X X X"
  • g
    is it inline 
    style="background-color: X X X"
    attribute, or a computed style?
  • g
    My suggestion is to use 
    cy.get
    + 
    cy.filter
    combination like I show here https://glebbahmutov.com/cypress-examples/9.5.0/recipes/computed-style.html
  • b
    I would check out checking the docs for 
    .each()
    . You need to fix your implementation of it.
  • f
    @yes
  • f
    Please share details
  • r
    I'm using the axe plugin to test accessibility. I have sitemaps with 500+ urls with monthly additions. I'm iterating through every url and testing with axe, but is there anyway I can separate this out so each URL is its own .it() ? Maybe this is ridiculous . Otherwise I have to create 1000s of .it()s or contain it all in one .it() where it iterates through them all, but if it's fails it fails them all.
  • r
    Maybe with node I can somehow dynamically create a test file before it runs?
  • g
    you can run the tests in parallel (by spec) following https://glebbahmutov.com/blog/testing-timezones/ and the easiest way to generate the specs (or really have N specs that are the same) is by using cypress-each, see https://glebbahmutov.com/blog/test-sitemap/#data-driven-tests and https://glebbahmutov.com/blog/refactor-using-each/#parallel-testing
  • g
  • f
    Thanks
  • r
    Thank you this is perfect.
  • l
    Hi everyone, do we have channel about api testing?
  • a
    No, but one would be nice.
  • a
    Hi, I've got a test that intermittently fails, but appears to be a real failure (response code 409 when it happens). I can see the failing line in the Cypress Dashboard and watch the video, but what I really need is access to the response during that failure when it happens. So far, I've only see this occur in CI, and can't reproduce the failure with the runner open locally. Any log dumps I can attach to our GitHub action to get more information on the failure when it happens? Or a feature of the Dashboard that I'm ignorant of?
  • f
    Not that I’m aware of, sadly. It would be helpful to be able to access the developer console output on the dashboard, but that’s a feature request for now
  • a
    Drat! Thank you, Liam
  • f
    Though if you’re using Chrome then there is this plugin: https://www.npmjs.com/package/cypress-log-to-output I haven’t used it myself though
  • r
    Hi Folks, I am facing a problem when I execute the cypress, I tried delete the register as the site said, https://docs.cypress.io/guides/references/error-messages#Cypress-detected-policy-settings-on-your-computer-that-may-cause-issues and. But not works at all
  • m
    100 % sure it does try another repo, upgrade to 18 you can use this https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress or a simple cra https://github.com/muratkeremozcan/multi-stage-caching
  • m
    At the moment we can use a Cypress plugin for timestamps https://github.com/bahmutov/cypress-timestamps and correlate something to like DataDog or anything that stores the data you can combine that with cy.task console logging and cy.screenshot
    Copy code
    on('task', {
    log(x) {
      // prints into the terminal's console
      console.log(x)

      return null
    }
  })
    and then in the spec file it shows how to use it
    Copy code
    it('calls into plugins process via cy.task', () => {
    cy.task('log', 'Hello Node!')
  })
    so yours would be just
    Copy code
    cy.task('log', someVariableYou'reDebugging)
cy.screenshot()
  • m
    you may have deleted the wrong registry settings, it is different by company for now restore the registry backup, and perform trial and error. For my old company I had to perfect this and run it on a bat file on startup.
  • a
    Well, i'll be damned; that'll work! Pretty simple solution, assuming one has DataDog or a similar service in place on one's test environment. Thank you!
  • r
    No, I didn't. In fact those are the regustries from the company. Are they right? Have other solution for that?
  • m
    unfortunately no the registry settings pushed by companies are very tedious because they impact the browsers, which in turn impact your development environment... Which in turn in impacts how you provide value to the customers. you just have to use trial & error, wrestle and hack it until it works the way you want
  • g
    Hello Everyone. I am new to cypress and I am trying to install cypress, I am getting below one added 165 packages, and audited 166 packages in 42s 27 packages are looking for funding run 
    npm fund
    for details found 0 vulnerabilities However, cypress. exe file is not getting installed. cypress open is not opening up the Cypress . Can someone help me on this?
  • g
    And this is my Package.json file
  • g
    Copy code
    {
  "name": "modivcare_cypress",
  "version": "1.0.0",
  "description": "Testing Angular Application",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "ModivCare Labs",
  "license": "ISC",
  "dependencies": {
    "cypress": "^9.5.4"
  }
}
  • q
    While I was creating an account on 
    cypress.io
    , but it's telling me I need an organization. Even though I do work for a company, why do I need to enter an organization when it's just me?
  • a
    No worries, it's not exactly an Organization in that sense. Essentially it's the name of your Dashboard. Let me know if that clears things up!
1...363738...127Latest