3 ms·
Isn't the normal process, roughly, to: 1) Use unit tests to move quickly through to implementing The Feature 2) When The Feature is complete, run in a local en
by rlayton2 5y ago
Isn't the normal process, roughly, to:
1) Use unit tests to move quickly through to implementing The Feature
2) When The Feature is complete, run in a local environment to confirm it works
3) When that works, move The Feature to a development environment that more closely mimics Prod
4) Deploy to Prod
Each one of those steps takes an order of magnitude longer than the previous one, so should be done an order of magnitude less often. However if you are finding inconsistencies between steps, then alter local/dev to ensure more consistent testing. (i.e. if it works on Dev, it should just work on Prod, however there are always little issues).
- meheleventyone 5y agoRight but 2 often ends up being perfunctory whereas if you can test routinely against the local environment you’ll see a lot more and for example course correct earlier. It depends on what you’d consider an iteration as well. I don’t think the loop is closed until you’ve seen your code running in situ. Unit tests might let you have more confidence that things will work at that point. Running in situ could also be integration testing FWIW. Depends on what it is you’re making.