A second complaint about Python Unit Test Automation...

and some recent, similar books I have encountered:

This book includes a very large number of screen shots and copies of the output of running some command or other. Now certainly, a bit of this can be useful. But truly great programming books, such as Software Tools, Programming on Purpose, or Programming Pearls, include (almost?) nothing of this sort. It is as though the authors had plenty to convey without dumping the screen output of every command or program discussed into their works.

Again, I don't claim that any inclusion of such output should be forbidden. But I suggest that, say, for a series of very similar tests, it is enough to put in, "Here is an example of the output of test A," and not also show the nearly identical output for tests B, C, D and E. And, once again, I have the sneaking suspicion the publisher who asks for the output of B, C, D and E is trying to pad out a volume they fear may otherwise be too slim to sell.


Popular posts from this blog

Central Planning Works!