rockerest’s avatarrockerest’s Twitter Archive—№ 20,398

    1. Decided yesterday to follow my own advice and test my app exclusively with E2E tests with Cypress. I am inexperienced with Cypress and the paradigm is fairly unique, but overall, it has gone very smoothly (full support for Shadow DOM) and it has been extremely effective.
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Sep 22 Mood +4 🙂
  1. …in reply to @rockerest
    The primary question is: "Who are your tests for?" In my case, the answer is always "The application's end users." My tests are there to ensure the application works for the user, and they get what they want/expect. Component/Unit tests are completely useless self-soothing.
    On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Sep 22 Mood 0
    1. …in reply to @rockerest
      Only fully E2E tests actually show that the thing is working as expected for a user. I've been loving it so far.
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Sep 22 Mood +2 🙂
      1. …in reply to @rockerest
        The app is a very "first draft" so the tests have caught a few known defects, but they've also exposed: - 1 actual unknown defect - a class of defects introduced by refactoring / abstraction In both cases the components/units are working as expected, but the workflow isn't.
        Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Sep 22 Mood -10 🙁