Sorry, it took a hard time to understand what are you exactly describing, it seems that you are describing what the programmer is doing manually at each step. I am wrong?
Anyway, if you are expressing that unit tests are useless, I am with you. You should never test the implementation details, but the program behavior, or in other words, the business requirements and the business value. It makes no sense to test anything else.
You can read more in my other articles:
- Start Writing Tests as They Were Documentation
- A quick puzzle to understand testing and refactor
- Everyone knows how to do great testing (I believe that this one focuses directly into your concern, the step five is the Business Value)
Thanks for your contribution, I hope that it will help.