This version of the coding / testing / release cycle of software development is one derived from personal experience, other developers horror stories, and a need to laugh at development pitfalls. As with any contract, please be sure to read all the fine print.
The blue section focuses on the new code, which is the interesting part. Purple focuses on regression testing, which is usually really really boring, and so a lot of people feel is optional. Any red path means more work for you, so avoid that at all costs.
- Create new code
and corresponding unit tests / update old code and old unit tests.
- Sometimes the code just needs to get out; go to step 8.
- Just had an idea? Go ahead and add it in! No one will really mind!
- If you write your code right, you really don't need unit tests.
- Install code into test environment. This lets you show off your awesome skills.
- Test functionality of the new code:
- If QA complains enough, you should probably change something.
- They might complain, but probably not enough. Stand strong!
- Perform regression tests:
- If the regression tests pass, continue to step 8.
- If you accidentally run all the regression tests, and they actually pass, go to step 7.
- If not all the tests pass, but no one else sees this, then nothing really failed! Go to step 8.
- If not all the tests pass, and someone does see, go to step 6.
- Refactor the regression tests.
- If your new units tests started failing, re-read step 2 then go to step 3.
- If old unit tests are the ones failing, that is not your fault. And if you comment out those unit tests, then they aren't failing anymore, are they?
- Better go to step step 3 to make the person from step 5d happy.
- Tell everyone how cool your code is.
- Check in the code. you're done, start working on the next feature.
Copyright © 2017 Adin H. Baber, all rights reserved.