• I think I’ve blocked out most of the bad ones, and most of my coworkers have been good or okay.

    This one guy I remember though. This might only be relevant for people who live in software.

    He refused to name his tests. Normally with jest or mocha you have tests like

    describe(“user settings page”, () => { it(“allows the user to change their name”, () => { etc

    But he refused. He’d put empty string in both spots. So you’d open a test file and there’d just be a dozen anonymous unlabeled tests and you’d have to puzzle out what they were trying to do.

    He was a reasonably nice person when we talked, at least. But this drove me crazy.

      • He said that the test names were essentially comments, and “comments quickly become lies”. Which, fine, we’ve all seen bad comments. But the test names are more like file names than comments, and no sensible person is going to suggest we get rid of file and folder names. Except the other guy who responded to me with the shell scripts with no names that each call each other, maybe.

        He was on a different team at a large company so I didn’t get wind of this right away. We had a meeting scheduled to hash it out, but then there were mass layoffs that day and I left shortly after. For all I know he’s still there

    •  legios   ( @legios@aussie.zone ) 
      link
      fedilink
      English
      110 months ago

      I once worked with a team who would have useful tests like (it’s been years since I used Jasmine so not going to try), but things like if true === true.

      Yeah thanks dipshit.