https://cypress.io logo
Join Discord
Powered by
# e2e-testing
  • p
    i'd say its a bad approach, it will increase time on tests and has no actual utility for testing purposes
  • s
    There's a test where I click an object on a page and it loads some information by doing some javascript work in the frontend and a receiving the information via a XHR request. I want to make it click a specific button, but the page I'm testing does not allow that information to be seen in the frontend. I'm thinking of intercepting the XHR request and changing the properties of it, would that be a good way of handling things or is there a better way?
  • a
    I am doing POC for both cypress and playwright. can I ask a playwright - lighthouse integration question here?
  • m
    probably not, because most likely we don't know the thing about playwright is... it's made for microsoft by microsoft. If it works for you, great. If not, good luck 😄
  • a
    Thank you Murat
  • b
    I don't think puppeteer is a browser.
    b
    g
    • 3
    • 4
  • b
    Hello, curious how many people use cy.request when entering a new page to check the status code?
  • g
    I do it, and show how in Bonus lesson 24 of my https://cypress.tips/courses/network-testing
  • b
    Thank you. Is this a pretty standard practice you implement in all tests?
  • g
    no, only if the page is often flaky
  • w
    Hi everyone 😀 I am looking for a solution for covering Safari in my automation. What is the current solution you are using? Please advise me on any temporary/weird workaround that might be useful. I am currently manual testing Safari and wish to invest some time to automate it even for short-term.
  • f
    Unfortunately, they don't currently support Safari and I'm not aware of any workarounds to do this in Cypress There's a proposal on Github to add it to the supported browsers, so you may wish to add your support there https://github.com/cypress-io/cypress/issues/6422
  • w
    I am looking for what cypress users do to support Safari in their tests, as I guess they don't simply ignore this browser.
  • f
    Some manual testing, but our user stats show that only a small percentage of our user base uses Safari. Hence we haven't spent too much time on finding a way to automate
  • c
    Hi everyone , I having trouble with in mocking node-ipc in cypress which i am using in electron app. Please some help ASP
  • m
    try visual testing with Applitools or Percy, they cover cross browser for you
  • w
    Can I run them without wrapping of another framework like cypress?
  • m
    they add on to test frameworks
  • w
    So the test would have to initially run on Safari, they only support test that are already running, right?
  • m
    the test can be on any browser, then they take visual snapshots cross browser
  • w
    But I am looking for a solution to run my tests on Safari in the first place. Cypress is not covering it. I am looking for additional solution.
  • m
    cross browser testing is overrated but if you must use Safari, Playwright is an option
  • m
    I had an ex colleague, they had the same requirement, they had to use Playwright (hating it) , and found a way to use cy.task together with Cypress Dashboard, running playwright tests...
  • m
    but the same weirdos also weren't npm/yarn installing anything , instead using docker to setup the local app environment
  • g
    one man's weirdo is another man's genius
  • g
    Hello everyone, I have a quick question for you all and really appreciate your feedback. Is it possible to run different group of specs based an environment variable that you read on runtime?
  • l
    > I had an ex colleague, they had the same requirement, they had to use Playwright (hating it) , and found a way to use cy.task together with Cypress Dashboard, running playwright tests... Too funny 😄 Would honestly be a killer feature to help people who wish Cypress would handle _______ edge case.
  • l
    Not using environment variables per say, but through other means, sort of. Officially, you can use a complicated glob pattern in your 
    --spec
    command line parameter. Unofficially, people have implemented their own solutions (Google reveals blog posts about this).
  • l
    Here's one example that actually does use environment variables. https://www.mariedrake.com/post/using-tags-to-filter-your-cypress-tests
  • m
1...666768...192Latest