https://cypress.io logo
Join Discord
Powered by
# cypress-cloud
  • m
    anyother Buildkite users?
  • b
    Hello everyone, I wonder if it's possible for Cypress For Jira plugin to create Jira issues for failure tests automatically from Cypress Dashboard. Could anyone please help?
  • b
    I just double-checked with an engineer on the dashboard after noticing that it was not documented on https://docs.cypress.io/guides/dashboard/jira-integration#Creating-a-Jira-issue-for-a-test-case. This is not a current capability of the integration with Jira. There is a button to create the Jira from within the failing test's results panel, but not to do so automatically upon failure.
  • b
    Thank you!
  • w
    hey, does anybody knows where did the "run all tests" button went after the big update to v10?
  • f
  • w
    thanks for the quick reply!
  • e
    Here is a solution from Gleb with v1à: https://glebbahmutov.com/blog/run-all-specs-cypress-v10/
  • h
    Hi team we in our current engagement with Cypress planning to achieve parallel test execution Does any one have real experience on how the distribution of tests is done by dashboard to various containers to achieve parallelization Any insight and help is greatly appreciated
  • m
  • g
  • i
    Hi there, When looking at the "most common errors" and "flaky tests" section of the dashboard, I see the message that I need to upgrade to Cypress 5 or greater. I am using Cypress 10 though. Is this a problem for anyone else?
  • f
    Not a problem on our implementation. Could be a bad placeholder? How long have you been connected to the dashboard?
  • i
    Hi Liam, Only about 3 to 4 days
  • f
    Hmm. Could just be that it doesn't have enough information yet. Also, the dashboard doesn't make this very clear, but for flake analysis to work you have to have retries enabled on your tests You can define this globally or on a per-spec level https://docs.cypress.io/guides/guides/test-retries
  • i
    re-runs are enabled, and I see some tests in the overview section that have the label "flaky"
  • i
    The most odd thing about this is that the message says I need to upgrade my cypress version.
  • f
    Yeah, that is weird. I think the Cypress team has the day off today, but I'm sure someone will take a look tomorrow
  • a
    hey, wonder if anyone from cypress is available to help us with the grace period of our cypess dashboard subscription. It ended unexpectedly today. We reached out to our contact and get no response yet (probably because it's a US holiday).
  • a
    Did anybody notice that the cypress dashboard is not working? Had this morning 500 Internal server error and now I see the login page but cannot login. Also this page says everything is fine and up and running while it's not. https://www.cypressstatus.com/
    • 1
    • 1
  • f
    Can you tell me roughly what time you first saw this? UTC preferably. Also, how were you authenticating?
  • f
    @important-diamond-61614 could you please contact our support team with this and give them your organization and/or project id and exact cypress version? this definitely should not be happening
  • b
    Hi there, we are running our Cypress project in GitLab, how do you see how many machines are enabled for record running, because currently we only have one. I'm not sure how to add more machines for parallelized runs, if that is to be configured on Cypress dashboard itself or GitLab. Can anyone point me a proper documentation for this? Much appreciated
  • m
    https://github.com/muratkeremozcan/angular-playground this repo is in gihub and circleCI, but it comes with the gitlab files . You could just drop it to gitlab, update the runners and you'd be set with a meta setup
  • m
    it's the repo tied to the combined coverage blog post https://dev.to/muratkeremozcan/combined-unit-e2e-code-coverage-case-study-on-a-real-life-system-using-angular-jest-cypress-gitlab-35nk I'm sure you'll find what you need somewhere in there
  • b
    Thanks for this @magnificent-finland-58048 , this will take some research for me, never experienced creating Machines for Cypress use, hopefully we can reduce our 15 mins run test because we only have 1 machine (CI) running. 🥺
  • m
    at my old company (Siemens) we believed in "cost cutting" too 🙂 we had 2 EC2 instances, a runner each, and 100 + engineers shared them 2-3 machines is ok, unless everyone is pushing pipelines together. If so, I recall gitlab had a semaphore concept where only one CI execution would happen at a time in a single repo, and the next would wait in queue. It should be somewhere in their docs.. it will help in your case
  • f
    That sounds painful
  • m
    constrained resources promote innovation 😅 we could release to prod in 90 minutes, technically... And I ninja'd that many times without process overlords knowing, many times... but with PROCESS, it would take 3 months to release a todo app 😂
  • f
    New channel for this server: #test-confessions
12345...14Latest