https://cypress.io logo
Join Discord
Powered by
# general-chat
  • s

    sparse-insurance-21987

    05/02/2022, 8:51 AM
    No, I am not getting this error when visiting the site manually in incognito mode.
  • l

    loud-market-37318

    05/03/2022, 2:34 PM
    Does anyone else have issues trying to create jira tickets from the cypress dashboard?
    a
    • 2
    • 8
  • l

    loud-market-37318

    05/03/2022, 2:34 PM
    Certain fields not able to be updated with error messages on screen?
  • a

    adventurous-dream-20049

    05/03/2022, 2:47 PM
    Does anyone else have issues trying to
  • r

    rough-van-84956

    05/04/2022, 8:42 AM
    https://ethereal.email seems to be offline. Does anyone know what's happening?
    • 1
    • 1
  • r

    rough-van-84956

    05/04/2022, 10:46 AM
    httpsethereal email seems to be offline
  • l

    little-byte-59792

    05/04/2022, 2:04 PM
    I may or may not have used it to book tickets which have become very rare
  • l

    loud-vase-48777

    05/04/2022, 3:45 PM
    hi, i use to use a static function from an imported class in test file
  • l

    loud-vase-48777

    05/04/2022, 3:46 PM
    i want to access the fonction in cy.origin but it throw a reference error
  • l

    loud-vase-48777

    05/04/2022, 3:46 PM
    Copy code
    cypress_utils_1 is not defined
  • l

    loud-vase-48777

    05/04/2022, 3:47 PM
    cypressUtils is my imported class
  • l

    loud-vase-48777

    05/04/2022, 3:47 PM
    thanks in advance
  • l

    loud-vase-48777

    05/04/2022, 3:48 PM
    Copy code
    ts
          cy.origin('http://localhost', {args: {}}, () => {
            let userInfo = {username: 'superadmin', password: 'superadmin'}
            CypressUtils.login(userInfo, () => {
    
            });
          });
  • l

    loud-vase-48777

    05/04/2022, 4:58 PM
    up 🙂
  • a

    astonishing-alarm-77244

    05/04/2022, 8:33 PM
    The DX Team has released two new plugins to help our users get quick access to our docs. One is a VSCode extension the other is an extension for Raycast. VSCode Extension: https://marketplace.visualstudio.com/items?itemName=RobertGuss.cypress-command-docs Raycast Extension: https://www.raycast.com/robertguss/cypress-docs
  • b

    bored-dinner-46643

    05/04/2022, 9:01 PM
    where is the best place (Channel) to ask a question
  • b

    best-flower-17510

    05/04/2022, 9:21 PM
    You can try #763105090679865354 for you questions. @nutritious-restaurant-91514 and @magnificent-finland-58048 are also some Ambassadors I would recommend reaching out to.
  • p

    purple-afternoon-2408

    05/05/2022, 4:59 AM
    Hello team, I have wrote a detailed experience for us here at https://github.com/cypress-io/cypress/issues/15590#issuecomment-1118165438 , if you guys tend to believe that we can reach a middle ground where we can positively get Cypress to work again, please let me know and I'll try to re-involve Cypress again in our project.
  • l

    loud-vase-48777

    05/05/2022, 8:11 AM
    hi, any way to use a global function implemented by in the cy.origin callback? thanks
  • g

    gray-kilobyte-89541

    05/05/2022, 10:42 AM
    as the person who wrote code coverage plugin and who runs 500 e2e tests at his large co now, I am not sure I understand the issue and the comment. Cypress provides Docker images, works on every OS, can give detailed logs, etc So I am not sure what else the Cypress team can do to help you run the tests on CI the same way you run them locally. As far as speeding things up via parallelization. Yup, the money for the dashboard service goes to ... developing the test runner so it has new features, fixes, etc. Plus whatever money you save but NOT doing parallelization you certainly lose 10x in trying to debug the CI runs without the dashboard's insights. It seems like flaky tests are a problem, so I would level up your training a little to write more robust tests that are not tripped up by the changed timings on CI (start with reading https://cypress.io/blog/tag/flake/ and http://on.cypress.io/retry-ability) and you need faster feedback from CI (read how we do it in https://glebbahmutov.com/blog/tag-tests/ and https://glebbahmutov.com/blog/faster-ci-feedback-on-circleci/)
  • m

    mammoth-fall-22117

    05/05/2022, 10:50 AM
    Not a part of this conversation really but I love your feedback and blog posts man 🙂
  • m

    mammoth-fall-22117

    05/05/2022, 10:51 AM
    I am working on multi-stage pipeline that will test few apps and this message is in perfect timing for me
  • g

    gray-kilobyte-89541

    05/05/2022, 10:52 AM
    It's all about running the changed tests and even tests by feature like we do now https://glebbahmutov.com/blog/pick-tests-using-pull-request/
  • m

    mammoth-fall-22117

    05/05/2022, 11:00 AM
    Nice!
  • m

    mammoth-fall-22117

    05/05/2022, 11:00 AM
    I came to the conclusion that what you run in CI should not necessarily equal your local tests.
  • m

    mammoth-fall-22117

    05/05/2022, 11:00 AM
    I believe that CI tests should be simpler and more streamlined whereas locally you can do whatever you want really.
  • m

    mammoth-fall-22117

    05/05/2022, 11:01 AM
    Also troubleshooting or debugging from CI is really difficult as you said. I will dig in to what dashboard's insights offer here as I wasn't aware of this.
  • c

    creamy-minister-50636

    05/05/2022, 12:59 PM
    I'm troubleshooting some requests that our app is making, and I'm not sure what are these markings in Cypress Why is there a spinner and what is this gray dot? (sometimes it's blue, some times it's just an outline). Also, requests that go without a problem have a port 8060 displayed before /graphql, but this one has dashes? Does anyone know what these markings are and why is the port missing sometimes?
  • p

    purple-afternoon-2408

    05/05/2022, 1:39 PM
    I'm not sure how/based on what u came up with judgements that flaky tests are being written. I hope that this comment didn't become personal to you. I can delete it if its causing any issues. The issue we experienced been shown to one of the cypress teams and experts in Cypress. We are hoping to look forward for more open minded troubleshooting instead of taking the easy road of closing issues without walking extra miles just simply because of no reproductive samples. The issue that we shared was simply closed the second someone took ownership and responded. Obviously it demonstrates either the least interest to help or too overloaded to walk the extra mile. I don't know the reason tbh.
  • g

    gray-kilobyte-89541

    05/05/2022, 1:44 PM
    I do not feel personal either way, since I am a Cypress (happy) user. But as a maintainer of 300+ repos, if there is no reproducible example... it is not much one can do
1...394041...127Latest