My first attempt at depicting the benefits of continuous testing

Everyone says that a picture is worth a thousand words, how about a time lapse movie, is it worth many times a thousand words? 

We all know that defects that are found late in the development cycle regardless of methodology used are much more costly to fix than those found as close to the customer request or requirements as possible. This is where continuous testing comes in to save the day. Everything step in the development process has a testing phase, write a requirement and then test it to make sure it will deliver what the customer desires or values. Design the architecture, then test it to make sure that it is appropriate for the needs of the feature. Implement the first lines of code and test it to make sure at the unit level everything is returning as expected. Once committed to the branch or trunk then the continuous integration process can run those previously local unit tests and then deploy the build and do additional integration and functional automation testing. When builds are pushed to the pre-prod and even the production environments there should be tests run to ensure that everything is working just as it did in the first environment. In production there should be system health tests and other monitoring to ensure that the system is working as expected and to help identify problems early before customers start calling.