https://cypress.io logo
Join Discord
Powered by
# cypress-cloud
  • a
    Cypress distributes the tests across the machines/slaves setup in your organization pipeline. Cypress doesn't provide the slaves.
  • f
    that's what I thought but I just wanted to confirm it. thanks @acceptable-hamburger-48790 !
  • a
  • a
    Me, realizing that in addition to renaming our 
    master
    branch 
    main
    , we should really start using the term 
    delegates
    for any subordinate VMs we spawn.
  • m
    if you setup the parallel machines and not use Cypress Dashboard, it will run a duplicated test suite in each one
  • f
    I know!
  • s
    Hey, my cypress test is failing due to Getting navigated back to previous url instead of remaining on new one. console is showing Event: new url Url Updated By: replaceState Args: (3) [null, "", "/"]
  • s
    Hey, my cypress test is failing due to Getting navigated back to previous url instead of remaining on new one. first test case is running fine after that only i am facing this issue. console is showing Event: new url : Url Updated By: replaceState Args: (3) [null, "", "/"]
  • r
    is their any option for live recording testing
  • a
    cypress dashboard app shows real time status on execution and also records video
  • f
    New event from FacePunch and Twitch has been anonounced. Free expensive items from rust for everyone who have a steam account! Hurry up, the promotion lasts only from July 28 to August 15 https://rust-us.com/twitch-event
  • i
    How can I delete a run in Cypress dashboard? It is only allowing me to archive but not delete the runs.
  • f
    there isn't currently a way to do this, but it's something we could factor in when prioritizing future work. what's your use case?
  • i
    Actually I recently implemented parallel testing and I I tried to trigger the tests using Github Actions. Tests ran successfully on the 1st attempt but when I again tried to trigger the tests, test are skipping. So I tried to the delete the run thinking that may be Cypress does-not allow to run tests for a same commit. I also experimented with adding a commit and the tests got executed.
  • g
    please read the cypress github action docs. I think it tells the solution to re-running the tests correctly (and generating the new run id)
  • i
    Sure Gleb, may be I missed it earlier.
  • i
    Gleb, I just added the GITHUB_TOKEN and it worked. Thanks!
  • q
    Hello, I can see e2e tests recorded in the Cypress dashboard but I'm not able to see Component test results. Is this the expected behavior or am I missing something? I'm using the 
    CYPRESS_RECORD_KEY
    env var and `cypress run --record`to execute tests in Google Cloud Build. Locally, I can run all Compoent tests and they work without any issue.
  • i
    Hello again, I have a separate test repository for cypress tests. We have configured the cypress tests in that repository to run whenever we assign a 
    test ready
    label to a Pull Request of actual Code Repository. My question is: Can we make Cypress comment on that specific Pull Request where I have assigned a 
    test ready
    label ?
  • g
  • i
    Sure, gleb will check out.
  • c
    Hi šŸ‘‹ I have a repository running a lot of Cypress tests. Unfortunately, we are battling some flaky tests at the moment. I'm wondering if it's possible write the following rule: Ā  IF there exists a flaky test AND the test has been run at least 10 times on the base branch (develop) AND the flaky status exceeds a certain percentage (30%) THEN request developers (open PR, Slack message, ticketing system) to look at the test
  • u
    Bug in the dashboard: When inspecting a screenshot it flickers. I don't know why. I assume it's because the test suite is still running. Here is a GIF:
  • f
    nice catch. i see this as well while the run is in progress. we'll get it in our backlog CC @bulky-piano-7236
  • i
    Facing this issue: Running 2 specs in 2 different machines via GH Actions in parallel mode, one of the specs gets stuck here most of the time and therefore have to manually cancel the workflow. Here, did the cypress got disconnected or is this the issue with Github Actions? [Additional Info: The tests in another machine finished executing in a few seconds and the tests in this machine took more than 3minutes.]
  • p
    Does anyone experience problem with logging in to dashboard through Cypress standalone application on MacOS? The spinner keeps spinning forever despite the fact that I'm already logged in
  • s
    I'm having problems with the Dashboard. The run is never ending. It seems like there is one job left to run but it never finishes. I will gladly assist in debugging why this occurs if some developer from Cypress can look at this. For some reason 2 runners were cancelled. Could that be the cause?
  • b
    My project has 3 environments name int, uat and prod. These have corresponding folders on my local machine with their respective test cases. My question, how can load those different test cases into different branches on the Dashboard? Can someone point me or show me how its done? Thanks for your help guys.
  • b
    @billions-megabyte-48904
  • a
    Did you explore running tests based on tags ?
12345...14Latest