Watch tutorials on writeitnow how to#
In the case of a system of people, I have to think harder on how to implement that. Numerical and banking ledgers are "easy" in the sense you can use simple arithmetic. In implementation, The school is harder to see. It is only an imperfect analogy, and it assumes that each recursive iteration is a "pass." Again, just an opinion. It may be harder to actually keep track of it in your head, but in reality, the hardest part is knowing, when the recursion "breaks," when to stop (my opinion, of course.) So I have to think about what stops the Recursion first. I liken this to thinking about Recursion. If I can make a test fail, I know why it fails, but this presupposes I can make it pass. I then create the class "Student." Maybe "School" I do not know.īut, in any case, the TD Design is forcing me to think through the story. In doing so I design a test Class for class X (maybe Student), which will fail.
The User says, We have people enroll for school and pay registration fees. From here, I take those User Stories, and I create a test to test the User Story. In my design, I have an architecture I want to start with, User Stories, so on and so forth. There seems to be different ideas on what I was asking or confused about, and maybe there is, but what I was asking was, say I have an application for building a school. When do I go back and write the real code? And how much real code do I write before I retest? I'm guessing that last one is more intuition.Įdit: Thanks to all who answered. If I have a fairly complex object with a complex method, and I write my test and the bare minimum to make it pass (after it first fails, Red).
But what I don't see if how I do the "real" code after I get green. All the examples I've read and seen on training videos have simplistic examples.
0 kommentar(er)
