6
huskut
58d

FUCK JEST. ITS ALL SHIT. I CANT HAVE A DIFFERENT MOCK RESULT FOR ONE TEST AND KEEP THE OTHERS THE SAME WITHOUT REWRITING THEM.

THIS IS THE REASON NOBODY REALLY WANTS TO DO TESTS, NOT BECAUSE THEYRE STUPID BUT BECAUSE THE FRAMEWORKS ARE THE PINNACLE OF CANCER THEMSELVES.

Comments
  • 3
    I literally thought someone went after @jestdotty
  • 2
    I can understand your frustration.
    But I’m sure what you’re describing as not possible IS in fact possible
  • 0
    Try Jasmine, it's literally impossible to mock a function
  • 1
    @jestdotty haha, surely wasnt targetted against you! unless you also will be annoying as the jest testing framework...... jk ;)
  • 0
    I've... oddly been having decent luck with jest recently...

    but only because I've been using it purely in the unit test sense -> single unit of 'something' (class or function) under test

    i agree as soon as you start doing anything in the direction of integration, you need mocks, etc. etc. then it indeed goes all to cancer

    people argue mocks are a testing code smell, but those people also don't know what integration tests are / real software looks like

    🤡🤡🤡🤡🤡
  • 0
    I'm down tho :D
  • 2
    I by the way wrote this after an 9 hour workday in which I was struggling on tests for like 6-7 hours. I eventually found a way to do what I wanted and that I was somewhat reasonable with, however I still hate it that I have to do it in such a way and that its not well documented.

    so still, fuck jest. (the testing framework not the person)
Add Comment