2
LeMeow
4y

Okay..

So, what do I have here?
A cross platform mobile app with NO unit tests.
😕
I have to write a big new feature from scratch. (Things can't go wrong, right?)
Started working on it, pointed out problems with the UI/UX designs. The design changed multiple times, still I thought I could finish it by the expected date. And, so I did.
The feature went through testing, and they found bugs. (Surprise...?)
It's already kinda scary to touch someone's code that has no unit tests and no comments. And I think, it's all the more difficult to not introduce bugs.
Also, had to work on the weekend to fix the bugs.
I had some good learnings here, but I'm not sure how I can prevent bugs without unit tests and proper feedback cycle. :/

Comments
  • 1
    Prioritize tech debt over new features and educate your team and managers
  • 2
    Put the tests in before you add your new stuff. The least it will do is verify your changes hasn't modified existing behaviour. Obviously that takes time so if you provide estimates make sure you factor the time in. If not I'd still recommend doing it as it will save you time when you get to the end.
  • 3
    Do what you can, they can't expect perfection when they've been perfectly okay no paying for safeguards on quality.

    Sidenote: learnings is a mass noun, it's plural without the s, much like code when referred to as an entity.
  • 2
    You should chill, because a proper place should have QA people. You should not be put on the spot every time a bug happens, but small shitty companies are trying to save money and are putting all the blame on you. Fuck them, how is a developer supposed to be a tester at the same time especially when he has no time writing tests?
Add Comment