• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle

  • It’s very hard to start writing tests for a codebase that was not tested while it was being written.

    “Be more careful” is obviously just wishful thinking, but the pain apparently hasn’t become bad enough for the need to better quality to have become apparent to everyone.

    When people say “we can’t test the UI”, there’s often a reason that they are reluctant. One reason can be that they think you want to test through the UI, and write slow and cumbersome end-to-end tests. Those tend to become unmaintainable at record speeds, and if you’ve experienced the amount of work and aggravation that can cause, you tend to become reluctant. When you ask for ‘integration tests’, this might be the thing people are hearing.

    That being said, there’s plenty of ways to test UI code locally, at the unit and component level. Depending on your tech stack, of course. Those types of tests you can just start creating without a big investment. In a codebase that’s not tested, that can be difficult, but try and make the changes you need to make to isolate logic, so it can be tested as a unit test. It’ll give you better code, and teach you a lot about structuring code so that you separate responsibilties.






  • It’s a term coined by Cory Doctorow, Sci-Fi writer and ex-EFF, who has been writing about (tech) monopolies, and in particular monopsonies, and how those types of two sided markets originally grow by given users something they need, often for an artificial low price or even free, until they dominate that side of the market, after which they focus mostly on the other side of the market, in this case advertisers, and step by step, slowly dismantling the reason users originally liked their product… Enshittification.

    Doctorow has lots to say, so here’s a link.