The goal of this post is to paint a different picture of automated tests than is normally discussed: a picture where automated tests lie on continuous spectrums, rather than discrete buckets, and it’s up to each project owner to categorize them. Where tests are “just code”, subject to the same constraints and allowing for the same techniques, rather than being something special and different. Where tests are ruthlessly prioritized, and those that provide less value than their ongoing costs are culled.
Source: Principles of Automated Testing
Ed: Awesome 🙂