Excellent article. A pragmatic approach to testing is usually needed to get a good cost/benefit ratio imo. This may include testing different parts of the syste

Excellent article. A pragmatic approach to testing is usually needed to get a good cost/benefit ratio imo. This may include testing different parts of the system in different ways and also test differently over time. For example, it can be worth skipping automated tests altogether from start and then revisit a month later to add tests to parts that have now "proven" themselves to be useful and central.