[skydhash]

> When a person becomes a manager, they do or do not have enough time and expertise to review all of the code that they trust the team to produce.

> Managers usually get into automated testing; unit tests, integration tests, acceptance tests, and maybe also BDD syntax

I can see managers getting involved into acceptance tests, but never in the other type of tests. And the verification mostly is involved into a quick manual testing/watching a demo. Code is not their concern. When there's a bug, they expect you to investigate and fix it.

[westurner]

Given that it's so easy to generate better than test stubs with a model and manually review what it thinks covers, I think it's fair to expect a manager to run and add to the tests.

If devops has done their job, it should be trivial for a manager to contribute to the tests and run the build on git push (or manually re-run the build with the web UI).

If a manager has deploy rights, they should be able to run the tests.

[astrange]

Managers often still have code and team-lead responsibilities IME. First-line managers, that is.

And then sometimes you report a memory leak and it gets fixed by a VP and you wonder if he doesn't have something better to do.

[brabel]

If the memory leak could cost the firm its reputation with important customers, then I doubt the VP had something better to do.