Bit more feedback accumulated as I’ve been reading (as time allows) All these are for the e-pub version.
Some of the sample text is very small at the smaller font size choices on the nook. (fortunately 7 font size choices are available on the nook simple touch)
pg 67 of 367: Header is cut off and does not wrap.. shows as “Replacing Given / When / Then with Bul-“ when using Amasis font in the 4th size (of 7 available) on the nook. If I bump the text size, then it wraps correctly, if I drop the size, doesn’t need to wrap. (not sure if this is your formatting, or a bug in the nook?)
pg 68 of 367: spelling error “..using Guven steps to set up” (Guven is in italics)
pg 72 of 367: examples show using a switch “–i18n” but the text says “..to the –i18 switch” which is correct?
pg 82 of 367: The contents of Figure 4 “Cucumber ignores keywords…” is nearly impossible to read, I can barely make out the words like ‘given’ but the highlighted text to the right of that is pretty much impossible to make out. As the figure does not scale, changing font size makes no difference.
pg 117 of 367: minor quibble, but given that the 1 and l are so close to one another visually, perhaps using the number 2 in the password examples (instead of 1) would make the objective of the examples just a tiny bit more apparent to the reader.
Also the tester in me points out that you really ought to have an example of
e.g all numbers, in the section for letters and numbers, and maybe change abcd1 to 432a to show an example that has only one letter.
pg 124 of 367: presenting both versions of how to organize directories in the style of
would better allow the reader to contrast the two approaches. Having the directories listed in the middle of the text (in ‘do your organize by feature type’) just makes it hard for the reader to visualize the directory structure.
Also: “If you think about your features as a book that describes what your system does, then the sub-folders are like the chapters in that book…“ I experienced a total lightbulb, face-smack, I could have had a V8 moment when reading that. It’s a great way to view how to organize the features that also guides you in terms of where to put new work as well (make it part of the story, not tacked onto the end). little gems like that make this ride worth the price of admission. Bravo and hats off to whoever came up with that analogy.