Software Engineering discussion

A beautiful chapter! If I had to pick only one article to have students read to learn something about software testing, this would be the one. The thought process illustration is as valuable as the test examples themselves.

I like this chapter, but I would rather see the author walk through creation of tests for code with unknown bugs. Concentrating tests for areas with known bugs isn't beautiful, but recognizing areas of risk in untested code and testing those areas thoroughly is beautiful. The first few points about keeping smoke tests speedy and simple are words we all need to hear. I liked the author's point about using little known features in the code. Even though you may save a few characters the true test of beauty is if someone else can see it too.

I thought this chapter was very easy to follow and contained great subject material. This chapter advocated its solution without getting preachy.

I have never used JUnit, but it looks so simple to use. A previous chapter mentioned intuitive API; this chapter covered intuitive testing.