Yeah this is by no means one size fits all. The appropriate mix of QA and automated testing really depends on what kind of product you're building but I can't think of any use cases where you want no automation whatsoever.
Something that's missing from this list that I find extremely useful:
An unstable environment with actual users doing real things with it. They could be internal, they could be advisors, they could be customers who are also investors or are willing to be testers for a discount.
That works really well if your code is designed to fail loudly (validations, assertions, etc...) and you have a culture of fixing issues immediately.
Something that's missing from this list that I find extremely useful:
An unstable environment with actual users doing real things with it. They could be internal, they could be advisors, they could be customers who are also investors or are willing to be testers for a discount.
That works really well if your code is designed to fail loudly (validations, assertions, etc...) and you have a culture of fixing issues immediately.