Learn More
Resend Email
22
Root
342d

Fuck Cypress. It’s a fucking goddamn pile of diseased garbage. Its design decisions actively fight against you, its methods don’t work, it’s unreliable as fuck, and it intentionally keeps stale state so your tests fuck with one another — and that even fucks up its own interface so nothing fucking works.

It’s like stepping into the shower and expecting clean water, but instead it’s just some obese guy with diarrhea shitting in your hair, and then getting all indignant that you’re upset about it.

If you consider using Cypress for something, find another project.

rant

cypress

fucking garbage

root swears oh my
Favorite
Ranter
Comments
  • 4
    342d
    Browser robot tests should be used sparingly in my experience.

    They're the most fragile type and are slow
  • 3
    342d
    @MammaNeedHummus Yep.

    But $work has been hiring almost exclusively DEI candidates for the past three years, and everything’s been slowly going to shit because of it. Over the last year, prod downtime increased 260x. So they want everything tested and triple checked before their largest client leaves. They don’t listen when I tell them what’s unstable and needs fixing because I clearly don’t know anything, so: cypress.
  • 1
    342d
    Try playwright instead of this cypress crap
  • 5
    342d
    @devRancid I would, but unfortunately they don’t listen to me.
  • 1
    342d
    @Root sounds shit sorry to hear x
  • 2
    342d
    OH SHIT one of those terrible html testing frameworks, I hate tests that target html elements with a passion bc html content changes so quickly and frequently and you’d have to change the damn tests as well, which kinda defeats the purpose of tests to begin with. They should almost NEVER change. Why not, you know, test html manually? Click the button, what do you see?
  • 1
    342d
    Too leaky like a fat hairy man’s poop hole after eating supreme ice cream nachos deluxe
  • 3
    342d
    @TeachMeCode Three hundred checkboxes that change behaviors. Releases twice a week.

    Manual testing is just not feasible.
  • 0
    342d
    @Root true, not saying it should be avoided 100 percent. That’s one good use for it
  • 0
    341d
    things done in a week and working on first try is not how business works. there are investors' funds to be spent, there are engineers to be hired. there is time to be wasted.

    imagine you do things without cypress. you're done really quickly, you don't hire more people, you don't spend money on lengthy development efforts. you don't contribute to the economy!
  • 1
    341d
    I've had an impression there is something very amiss in Cypress.
  • 2
    340d
    I liked cypres but it had huge performance issues in bigger projects. Many people faced this problem, solution was unknown back then
  • 0
    338d
    @retoor still is to this day
    We’re using cypress in a very large project and facing huge performance problems
  • 0
    338d
    @black-kite I said had..
  • 0
    338d
    @retoor ok, what?
  • 0
    335d
    Fuck count: 6

    Holy cow, you are ANGRY
  • 0
    335d
    @devRancid interesting what would you say are things that playwright improves upon (compared with cypress)?

    Have a rather complex form post too. Cypress works reliably after I removed all the violations of the documented best practices/pitfalls and race conditions in the app itself. But we don't do any fancy stuff in the tests. Tried to change one of the interceptors set in the before but that failed no matter what I tried.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment