How did "things got shipped nearly every day" work in practice? A common version of this is "the automated tests are passing, therefore it's good to go". But

How did "things got shipped nearly every day" work in practice? A common version of this is "the automated tests are passing, therefore it's good to go". But is your project manager actually on board with this, and if not where do their concerns lie? It's possible that if you were to wave a copy of "The Phoenix Project" at them, they'd come back next week with the zeal of the converted. But I do think that there are valid arguments for not saying that everything that passes automated tests is releasable, especially when dealing with more interactive user-facing tools. Manual testing, especially when it's relatively exploratory rather than focussed on the "correctness" of specific features can be really valuable for making sure that the user interfaces are coherent and pleasant to use, and finding odd interactions which are hard to imagine when looking at the code. Perhaps your PM wants to see more of that? Is there a way to fit this in while maintaining a release frequency which everyone is happy with?