Ken Johnston (the HWTSAM author that isn't me or Bj) has started his own blog. Ken's blog will primarily cover issues in testing software plus services, but I'm sure he'll respond to comments and talk about whatever you?d like if you ask nicely enough.
His blog is here - http://blogs.msdn.com/kenj.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5
Linda Wilkinson has finally posted her review of HWTSAM. Like most of Linda's blog posts it's completely on the money - especially her questions (many of which are probably worth a follow up blog post). Read her review here! (oops - Thanks Phil)
I?d really love to hear what more of you think about the book. Keep those blog posts and amazon reviews coming.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5
I've discovered that either live writer, blogengine.net, or the interaction of the two causes some problems with the display of quotes (and the o umlaut in Konisberg.
I was going to fix it manually, but it looks like I have some debugging to do on the web site first.
Sorry for the inconvenience - for now, if the display problems bother you, you can read this content (except for this post) over on http://blogs.msdn.com/alanpa
Ed. Fixed (manually) for now. We'll try to figure out why live writer is having problems another day
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5
No book on testing would be complete without a bug list. HWTSAM is no exception! Some "book people" call this stuff errata, but let's just call a bug a bug.
There are two distinct types of bugs: Author bugs, and Production bugs. The Author bugs are those where we, as authors, made mistakes. The Production bugs were introduced after our final sign off. To you, the end user, it doesn't matter - these are bugs. If we ever do a second edition, we'll take care of all of these.
Here's what we know about so far:
1) In the intro, I state that Ken approached me in the fall of 2007. On reflection, it was actually late fall 2006. I began writing the first chapter in January 2007 (chapter 4 to be exact). Minor issue, but an Author Bug nonetheless.
2) The table on p. 19 is missing a line between USA (California) and Hyderabad (Production Bug)
3) There's a bit of weirdness with the code coverage data on page 119. Bj explains it in detail on his blog here. (Author bug)
4) On page 125, the text refers to the Int.Parse() function, but it doesn?t exist in the code fragment (oops - Author Bug)
5) In the code sample on the bottom of page 235, I have mismatched quotes in two of the lines. (definite Author Bug).
6) The story about testing on page 227 has the phrase "as shown in the following graphic" For technical reasons, we pulled that graphic, but missed that bit of referring text (Author Bug)
7) Figure 14-2 on page 327 reads "Browsers (IF, Firefox, Mozilla)". The IF should be IE or Internet Explorer but not IF (Author Bug)
8) Part IV starts on p. 363, but the section text at the top of the pages changes to part IV at the beginning of chapter 14. (Production Bug)
9 )In the index (p. 413), Königsberg has garbage characters in place of the ö (Production Bug)
10) We forgot to include a bibliography (or forgot to think thoroughly about including one). Although we reference a lot of books via footnotes in the text, one tester in particular is quite annoyed that we didn't reference the writing that inspired us in the first place. I'll post a bibliography sometime and include one in the 2nd edition.
I'm sure I'm missing a few more. I'll add them as I find or hear about them.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5