where i write my stuff
As the title clearly states, difficult terrain is going to be hard. It will involve a replacement of the ‘get distance’ code that takes into account that strict distances are not the same as movement distances – the idea that four inches of distance may cost five, six or more inches of movement (which is …
Continue reading “Learning Unit Testing XI – Difficult Terrain Is Difficult”
Last time, I got the tests for Charging out of the way, and got through a raft of simple checks for Hiding. This time, a few of the more complicated checks. First off, a model can move around while hiding as long as it remains out of sight. I’m not sure how to be checking …
Continue reading “Learning Unit Testing X – Finishing Hiding”
Having gotten those knotty problems with world management, distances, directions, etc all out of the way I can finally move off of page 10. So what’s next? Page 11! Hooray! It begins with a description of a charge move. A charge works like a run, at double-move rate, with the model (hopefully) ending up in …
Continue reading “Learning Unit Testing IX – Moving On With Movement”
I’ve been bracing myself for this moment since I started the project – I’m coming to believe that I’ve been heading in a slightly wrong direction. Part of TDD is the idea of ‘emergent design’, and letting the correct design emerge from the process of writing minimal code to pass tests. At the same time, …
Continue reading “Learning Unit Testing VIII – Emergent Design”
I can see this page 10 being a pretty big thorn in my side. After stating fairly clearly models can move up to their move rate under the ‘Moving’ heading, it then says A running fighter can move at double speed: 8″ rather than 4″, for example. This is going to have a fairly large …
Continue reading “Learning Unit Testing VII – Running and Redesigning”
Before I get into finally finishing off that blasted page 10, I thought I’d go through a code coverage run to see how I was doing. Test Driven Development, see, everything should be covered by a test. 7.41% of the code is not covered by tests! I must be doing this wrong… Phew, that was …
I implied in the last post that I had made a mistake when I moved the MoveModel code into the Model class from the MovementManager class. Now, tests on the MovementManager class are actually testing functionality in the Model class. I also discovered that I am not properly testing the ‘GetDistanceFrom’ method with known data …
Continue reading “Learning Unit Testing V – Refactoring Mistakes”
Programming uses maths. It’s hard to ignore sometimes, especially when modelling something that is inherently graphical and position based such as a game. I’ve decided to give the models three different position indicators – PositionX, PositionY and PositionZ. This will describe their exact position anywhere on the board – including on a ladder, a walkway …
Continue reading “Learning Unit Testing IV – Diagrams and Mathematics”
So having seen the answers on my own StackOverflow question on TDD Design, I’ve decided to go ahead with the ‘emergent design’ crowd and see what happens. It appears that the refactoring and mid-stream redesigning is an integral part of the TDD process. It’ll all, of course, be described here (the process might be a …
Continue reading “Learning Unit Testing III – Emergent Design”
As you can see, I’ve only done a small amount of Test-Driven Development so far. I notice that for small classes – so far, there’s only a very simple turn tracker – it’s easy to write a test first when there’s only very little code and no interaction with other classes. When things get a …
Continue reading “Learning Unit Testing II – TDD vs. Traditional Design”