Heard a fun quote from a project manager today:

"Naaah we don't need tests, that project is so small it wouldn't be worth it"

Seconds later: "Why does this keep breaking all the time and we only notice it once deployed?"

Wonderful 😄

Ok but shouldn't the devs decide whether to test or not?
That's how I know it.

@Lensflare No, you don't always need to deliver software that is 100% tested and uses every design pattern ever, that's simply one of the decisions you have to make at the start of a project.

You have to consider development speed, development quality and feature completeness but can't have them all

Like my sênior dev here.

@alexbrooklyn Yes, but that's not what I meant to say at all. I wanted to say that this decision should be made by developers and not by the project manager.

@Lensflare Yeah, devs (whether senior or lead) should make that decision not the PM.

The manager from the last project that I worked on had an swd background so he actually asked for us to set test even some tiny scripts that we would make.
I think that it depends on the work background of who's taking care of the project.
If the PM has background on managing civil contruction projects he'll probably skip the tests. Hehehe

@Lensflare @alexbrooklyn The guys on the project previously just neither think it would be useful as originally the project was intended to be a very small thing only in use for a few weeks. And it grew slightly, was copied over to a different project of the same kind, then repeat that process 10x until two weeks ago when I finally started properly modularising it...

Now there even are some tests, at least for the core features.
But as you rightfully said, that decision wasn't really made by a pm. I just started adding tests without asking... Because I knew the answer if I would have asked.

And even if we only have 10 tests now, we already had a case where we found a regressen with it, so know I have a selling point for tests.