Git Stash-Driven Development
Git Stash-Driven Development
Why using Git stash in your development workflow can help improve test-driven development processes.
Join the DZone community and get the full member experience.Join For Free
I’ve found myself using a pattern quite often recently, which I’ve been calling “Git Stash-Driven Development” — that is, relying heavily on the magic of Git stash as part of my development workflow.
Normally I follow what I think of as a fairly typical TDD workflow:
- Write next test, watch it fail
- Write code to make it pass
This cycle can repeat very frequently — as often as every couple of minutes. Sometimes this cycle gets slowed down when the next test to write isn’t obvious or the refactoring needs more thought. But generally this is the process I try and follow.
Quite often having written the next test which takes me forwards on my feature I hit a problem: I can’t actually make the test pass (easily). First I need to refactor to make the problem easy. In that situation I can mark the test as ignored, commit and come back to it later. I refactor as required, commit, push; then finally unignore my test and get back to where I was before. This is a fairly neat process.
However there are a couple of times when this process doesn’t work: what if I’m part way through writing my test and I realize I can’t finish without refactoring the test infrastructure? I can’t ignore my test, it probably isn’t even compiling. I certainly don’t want to commit it in its current state. I could just bin my test and re-write it, if I’m following the 15 minute rule I’m not going to lose much work. But, with the magic of Git stash, I can stash my changes and come back once I’ve refactored the test code.
The more annoying time this happens is when I’m part way through a refactor step. This happens more commonly when I’m really going through a design-change – this isn’t really refactoring as it often happens outside of the normal TDD loop. I’m trying to evolve the design to somewhere different; sometimes this is driven by tests, sometimes its a non-feature changing refactor. But often there are non-trivial changes happening across numerous source files. At this point it is very easy to get part way through a refactor and realise that something else needed to have happened first. I could bin my change, I only stand to lose 15 minutes work — but why throw it away when I have Git stash?
So I Git stash my changes, go and make the change I needed to have happened first. Then, all too commonly, I get part way through this second change and realize something else needs to happen first. Well, Git stash again! This stack of git stashes can get quite deep, if you’re not careful. But once I’ve bottomed the stack out, once I’ve managed to commit a refactor that frees up the step above I can git stash pop, complete the next refactor, commit, Git stash pop; and so on up the stack until I’m done.
Now, arguably, I’m discovering the refactor in reverse order, but this seems to me often how I find it. I could have spent more time analysing the change in detail, of course. Spent time planning out my change on paper before embarking on it in the correct order. However, this is always time consuming and there’s still the risk that I miss something and come at a change “backwards”. I find that using Git stash in this way lets me discover the refactor that I need to make one step at a time. Each commit is kept small, I try and stick to the 15 minute rule so that no single commit loses more than 15 minutes. Ultimately the design change is completed in a sequence of small commits, each of which builds logically on the one before. They’ve been discovered by exploration, the commits were just discovered in reverse order.
The danger is always that I find a refactor step I can’t complete the way I’d imagined — now I can’t unwind the stack and potentially all the previous Git stashes aren’t committable. Whenever this happens I normally find going one or two levels up the stack will present a different approach, from where I can continue as before.
Published at DZone with permission of David Green , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.