develwoutacause’s avatardevelwoutacause’s Twitter Archive—№ 1,203

        1. Finally got around to trying #Jest today, but I still don't completely get it. It feels 95% identical to #Karma / #Jasmine, without many clear benefits over them. I'm genuinely curious, what is it that people like about Jest so much? Why do you use it?
          Permalink On twitter.com Twitter logo develwoutacause’s avatar ❤️ 1 Favorite Mood +6 🙂
      1. …in reply to @develwoutacause
        The biggest advantage I've found is snapshot testing, which is a pretty different way of testing UI components, and I can absolutely see value there. However, I'm not convinced it's an objectively better way of writing most component tests. jestjs.io/docs/snapshot-testing
        Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +4 🙂
    1. …in reply to @develwoutacause
      jest.mock() seems like it *might* be more powerful than Jasmine spies, but it looks just as weird and magical that I don't see it as a clear winner, just a different syntax. You can mock a constructor at least, which is one advantage over Jasmine. jestjs.io/docs/es6-class-mocks
      Permalink On twitter.com Twitter logo develwoutacause’s avatar Mood +5 🙂
  1. …in reply to @develwoutacause
    I know it uses a #JSDom implementation rather than a real browser, but I don't see that as a clear advantage either. It just sounds like I'll occasionally run into compatibility issues I don't want to deal with. What am I missing here? Why do y'all like #Jest?
    On twitter.com Twitter logo develwoutacause’s avatar Mood +4 🙂