https://cypress.io logo
Join Discord
Powered by
# cypress-cloud
  • s
    There are 14 machines operating in parallel. While serial execution works fine, parallel testing deteriorates over time until everything fails. I checked the CPU and memory usage (for the web app), and both are under 20%. There are no dependency between spec files. Any idea?
  • b
    community feedback request Hey everyone! I am working with the product team here at Cypress to assist with Dashboard onboarding for new users. What are some helpful resources you would like to see for new dashboard users? Thanks!
  • a
    Hi @shy-van-7331. Can you confirm your Cypress version, browser, and CPU resources? Typically video performance issues are form a lack of machine resources, but can also be other factors as well.
  • a
    Can you confirm your CI Provider and CPU allotment for each machine? Can you also provide your Cypress version and browser?
  • g
    Will the cypress dashboard be FedRamp approved in the future?
  • a
    We do not currently have FedRamp on our roadmap, however, I recommend adding this feedback to the #958170373139079218 channel to be considered for future consideration.
  • g
    Will do! Thank you
  • m
    Hey there cypress dashboard team. Just FYI - you're currently spamming dashboard users with the feedback form. It re-renders basically every single time i click a button inside the dashboard. I must have filled this out about 12 times already today. 😛
  • a
    Test run duration times break the chart if you ever have runs that stall out and reach very large time durations.
  • s
    Latest Cypress version (our CI always installs the latest version on every run), problems occur with Electron as well as Chrome, our CI runs a Google Cloud n1-standard-2 (https://cloud.google.com/compute/docs/general-purpose-machines) and locally I'm running Ubuntu 22.04 on an Intel i7-1165G7 with 32GB RAM (ThinkPad T14s gen 2). So it's not a problem of lack of machine resources.
  • b
    Darn! I will talk to the team about this. Thank you so much for the feedback
  • c
    Can you actually create a loom that evidences this? None of our systems are indicating that this happening.As those requests only go out every 90 days.
  • c
    Very possible there's some weird edge case occurring. Thanks for sharing here though!
  • a
    Can you send me a PM with a link to your Dashboard?
  • i
    is there any feature in plan by Cypress to integrate its Dash Board into Azure Devops Board plugin using market place ? the intent is if everything stays at one place like even cypress staying in Azure dev ops board as plugin it will help project to have everything at once place
  • a
    We don't currently have an Azure integration on our roadmap, but, you should definitely add this to the #958170373139079218 channel to be considered for future consideration.
  • c
    For new users (like myself) How can I see what user RAN the test? I'm trying to improve adoption of the dashboard but the one comment I am hearing is "how can I see who ran a particular run?"
  • c
    I couldn't see this listed....But I would also like to echo the sentiment for DevOps integration
  • e
    Is there any place in Cypress dashboard which just lists the cases in all the specs?
  • a
    I'm not sure if this is visible from the Cypress Dashboard. We use Github Actions to trigger our runs on CI, and you can see who kicked those off. For any Dashboard-reported runs that were triggered on local machines, I think all you see is the committer of the most recent change to the branch that was run (generally master).
  • a
    Hi @clean-toddler-29623. @adorable-smartphone-87280 is correct. There is not a current implementation to specifically mention who kicked off a run accept by utilizing the git commit info in the Cypress Dashboard. Certain environment variables can be passed directly in the command line such as 
    COMMIT_INFO_AUTHOR="akselsoft" npx cypress run --record --key YOUR_SECRET_RECORD_KEY
    , but that may not be scalable: https://docs.cypress.io/guides/continuous-integration/introduction#Git-information I recommend setting up a CI Provider so that the runs will be kicked off with each commit and that git information can be obtained automatically: https://docs.cypress.io/guides/continuous-integration/introduction
  • c
    Thanks - I'm not using a key but I am using a tag which works fairly well.
  • m
    We are debating between Cypress vs katalon ( why use cypress over katalon)
  • a
    wrong channel + you're spamming the same question in multiple channels. Please don't do this.
  • f
    Just wondering: does anyone else get this when trying to link a project with a Github repo? GH's twitter says they're not having any issues at the moment; wondering if it could be something on the Cypress side?
  • m
    try reproducing from a personal laptop, the company might be blocking something
  • f
    Good idea. Thanks! Unfortunately I got the same result on my personal laptop. I'll ask around to see if I can figure out what's up
  • h
    Hello there, would anyone know how to set CI provider in Cypress Dashboard? If there is some environment variable or something like that. I haven’t found answer in docs. I tried to set COMMIT_INFO_REMOTE, but it haven’t helped. It started to happen when we started to use Docker in pipeline instead of plain NodeTools in Azure Devops.
  • f
    Hej, I can't reset my password. I'm not getting any error, but I also don't receive an email to reset my password. Who can help here?
  • f
    Someone else had this issue yesterday. Try emailing support@cypress.io
1...678...14Latest