https://cypress.io logo
Join Discord
Powered by
# help
  • g
    you could look at the status of the test in the 
    after
    block. I think I have a video that you can find by searching for "after" at https://cypress.tips/search
  • g
  • f
    Thank you!
  • f
    May i know is this channel is for free service or its going to expire in some days?
  • w
    One additional difference between what is mentioned in the documentation and what I want is that, I want to listen to every request globally and save output. I wan to configure this once. I have over 100 tests and I don't want to write 
    cy.intercept
    and 
    cy.wait
    in every test and multiple times in a single test. Each test makes multiple requests.
  • g
    yeah, I guess a new lesson is in order
  • g
    @gray-kilobyte-89541 is there a way I can save the logs generated in a Cypress run?
  • g
    what logs?
  • g
    API calls made and all
  • g
    by the application?
  • g
    Yes
  • g
  • g
    Thanks
  • g
  • g
    I have created a lesson for my (paid) network course, it shows what I think the problem is and how to solve it by spying on the network calls using 
    cy.intercept
    command https://cypress.tips/courses/network-testing/lessons/bonus70
  • c
    I m upgrading to Cypress 12 and each it
  • m
    In my 
    cypress.env.json
    I set the 
    baseUrl
    variable, with the URL that I want to use, and I call it in a 
    beforeEach
    by doing 
    cy.visit(Cypress.env('baseUrl')
    . Unfortunately is throwing me an error. The URL exists (it's an URL I created for a mock server). If I attempt to visit 
    https://3dd78cb3-70ab-4481-9209-4372df167733.mock.pstmn.io/users
    is going to show me a response. If I set the URL in the 
    cypress.config.ts
    file, it works (but I don't want to set the URL in there). How can I fix this issue? I attached other images of how I set the env variable, and how I use it.
  • c
    Thanks @gray-kilobyte-89541 but these elements that we remove are not triggering any network calls :/ "good news" is that when our CI environment woke up again I reran the test and it worked.. the more test we add the more flake (especially in CI) we get. And it's frustrating to fix as it's exceptionally rare it happens on a local machine
  • m
    I would suggest you to use www.google.com in your environment file for debug purposes, if it works then you can use your mock server. Also the url you have mentioned in the msg is url/users but in the cypress, you are providing url. Are you sure that your mock server is running? 🤔
  • h
    Hello community, I have a problem with the latest version 12.3.0 of cypress and I get a Webpack Compilation Error. After a migration from old version to the new version of cypress the cypress.json would changed. I the scope of the project i have installed the Ntlm Plugin. Now iam getting this error ( see pic). It's a bit frustrating. I tried some things but it's doest work. Who have a hint for me? Maybe I can't see the wood because of all the trees. Thanks 🙏
  • r
    Hello community, I have intergated Cypress in github actions and the tests which are passing in my local environment are failing in github action. I am getting jquery not defined error. I am using Cypress 12.2.0 and Jquery 3.0.1 in my code. Are they incompatible ? What else might be the reason ?
  • c
    Hello All, Can someone help me in this issue. I am visiting 1 application url using cy.visit() & then in cy.origin() I am passing the login.microsoftonline.com but cy.visit() itself calling the login.microsoftonline.com. Any Idea how we can resolved it?
  • a
    I am trying to get the element highlighted in the snap but the shadow dom is closed. Can someone help.
  • t
    https://docs.cypress.io/api/commands/get Check the part about adding an option "includeShadowDom"
  • t
    e.g.
    Copy code
    cy.get('element', {includeShadowDom: true})
  • g
    so you have to wait for something else to occur after each click
  • c
    no, nothing chain from onClick->reducer function (react.useReducer) and eventual removal from the list, but right now seems more stable, and moving from Chrome -> electron has sorted out all my other issues from yesterday where (local) cypress open => all specs passing (local) cypress run => specs touching our PIXI integration failing with WebGL error (ci) cypress run => flaky tests
  • g
    well, just like in my lesson, check if the button is removed before clicking on the next one
  • c
    yes, thank you, adding the assertion should at least help removing flakyness
  • g
    The more assertions, the better https://on.cypress.io/retry-ability
1...248249250251252Latest