On Apr 23, 2:35 pm, Gubatron gubat...@gmail.com wrote:
I've come to use Unit Tests organically.
Certainly I don't write unit tests first, I write tests to make sure
what I've coded works the way it's supposed to.
I also add more tests whenever I find bugs.
Of course not everything can be
I find that most of my problems are device or user specific issues.
So to be useful, the unit tests would have to run on the actual
hardware used by consumers, and would have to emulate the behavior of
real users.
Years ago, when I had to write a small bit of generic java code for
server side
Writing unit tests first to define exactly how a program will work is
nice if you have the luxury of knowing exactly how the program will
work ahead of time!
I often have a general structure for a program (game) but I don't have
all the little details figured out because things don't always go as
Well, except that you should apply your rule to unit tests, too.
I'm not sure why you'd put in weeks of development on a quad tree, and
not write tests for it. But if there's a question about whether you
want to be spending weeks of development on a quadtree implementation,
a simple
I've been a professional programmer since 1975. A lot of my
programming was done without unit testing. I now think that was a
mistake.
I'm fond of saying that programming is both really easy and impossibly
difficult. Testing is a good example of this.
But it depends on the size and
Ralf, I certainly agree that there are differences between lone-wolf
programming and for the large team. Scale, for one thing.
There are also differences between being a 14-year-old beginner, who
may someday go on to be on a team, and a programmer with decades of
experience, who can afford to
Hi Bob,
I absolutely agree that unit test can be a big win if done properly (as you
wrote this is not as simple as it looks like. The very specific corner cases
are the important test cases).
But I was specifically answering to the original poster.
For a 14 years old programmer who is starting
I routinely find a disproportionate number of my bugs and crashes
reside in the code set up for the purpose of testing and evaluation of
the program rather in the function of the program itself.
I'm sure this is a measure of my unfamiliarity with best practices,
but I find it more beneficial to
8 matches
Mail list logo
