“applications” is cut off and not right aligning properly on a Nexus6p device. Note that I am using the Google “Play Books” app to read this book in .pdf format.

I don’t believe the “and” is necessary in the bulleted points

“The user’s name displayed on that page, and”

Cheers,

“these kind of built in affordances to.” should be “these kind of built in affordances too.”

“Ruby on Rails has a tonne of them.” should be “Ruby on Rails has a ton of them.”

I also don’t believe there should be an “and” starting a sentence. Maybe “Testing frameworks have these kind of built in affordances too and Ruby on Rails has a ton of them!” sounds more natural.

Cheers,

“heavy lifting and written all our selectors” maybe it can be “heavy lifting and written all of our selectors”

“People without valid credentials can’t” maybe it can be “People without valid credentials can’t login” to reconfirm the previous point

“And it’s this ‘#’ pound sign” to “It’s this ‘#’ pound sign” adding this as a suggestion as it’s a sentence beginning with “and”

Note: I am still reading through the book but will stop submitting erratum’s for beginning sentences with “and”

“And this is the assertion let’s us check to see what their name was successful set in the title of the HTML page.”

could potentially be updated to

“And this is the assertion that let’s us check to see that their name was successfully set in the title of the HTML page.”

This is more subject but you could consider removing the comma after “tests” as seen within the following:

“embedding context into your tests, and organizing them in such a way that you can reuse common setup.”

“Very handy for debugging and seeing what is going on behind the seeings”

On first read I wasn’t sure if it should have been the following:

“Very handy for debugging and seeing what is going on behind the scenes”

“sometimes use when that need need a value for something”

to

“sometimes use when they need a value for something”

“They are just saving time by by rolling four”

to

“They are just saving time by rolling four”

“HTTP get”

I am wondering if the get method should be capitalized e.g. “HTTP GET” is what I see in a lot of online tutorials.

“These are good to because”

to

“These are good too because”

The “in [xxx] (#unit).” forward reference needs a #unit definition for textual completeness.

In 3., the phrase “the less iterative and fast your development cycle.” is awkward. Somehow, “less fast” should be changed, say by replacing “fast” with “slower will be”.

The “<” and “>” should be resolved to “<” and “>”.

“Alright” is non-standard American English. “All right” is preferred.

In the first paragraph, “saying saying” should be just “saying”.

Missing page number/link

“Then at the base we’ve got these things called unit tests: small, fast, precise
code-level tests developers write to tell instantly when things are broken. These
come later, in [xxx](#unit).”

The first paragraph of “The Pyramid in Action” has an occurrence of “[xxx](#ui)” that needs resolution in the document.

The “‘can access company financials’​” method is missing a call: “get financials_path”.

The text should read:

describe ​“signin page”​ ​do​
​ \t describe ​“with valid credentials”​ ​do​
​ \t describe ​“with invalid credentials”​ ​do​
​ \t
​ \t describe ​“new super secret page”​ ​do​
​ \t describe ​“with valid credentials”​ ​do​
​ \t describe ​“with invalid credentials”​ ​do​

The code on this page is exactly the same as the previous code.

In page 123 last paragraph it seems there a reference to other page missing. It look like this:

“let’s take our create user feature from [xxx](#ui), and see what it would be like to write”.

I’ve spotted another one or two, in the meantime I’ll report them.

duplicate paragraph for Chapter 9

in CSS box example, typo in “background-color: white” (backgroud-color)

For people following along in the book, the $(“”) selection technique relies on jQuery being present in the page they are testing. If you try that on a website not loading jQuery it’ll fail — document.querySelector still works, of course, as it’s vanilla JavaScript.

The array index 0 selector syntax is incorrect — the [0] should be outside the double quotes, after the closing parens.

It’s confusing how the author compares regular, full-on CSS and regular, raw CSS. This is in fact JavaScript, but using CSS-like selector syntax. No raw or full-on. This is a niggle because it’s technically incorrect, and certain readers could be frustrated at a lack of getting the shorthand examples to work when their test page doesn’t have the jQuery library loaded.

> What would be a good end-to-end test that checks
This should be “integration test” rather than “end-to-end test” as that’s what this chapter is about.

The HTTP DELETE code block is missing syntax coloring and code style to match the other code snippets.

The topics covered in the chapter do not include inspecting network traffic with browser dev tools.

In the printed book (not PDF) the “fi” ligature in “This certificate” shows a weird character instead of the fancy ligature.

Text shown as “It didn’t happen all once.”. Missing “at”. Should read as: “It didn’t happen all at once.”

the following code snippet is confusing and probably not intended

it(“should be able to get Offsite”, function () {
expect(model.getOnsite()).toEqual([‘1’, ‘2’]);
});

it should say:
..
expect(model.getOffsite()).toEqual([‘3’, ‘4’]);

it is the same in the book and in the code from the download area

Chapter 7 starts of with a bug in the EmployeeTrackerPage, a button that doesn’t seem to be working. At page 118 the author claims to have found ‘the bug’, but this refers to a typo in the test script and doesn’t explain why initially the button didn’t work. And after fixing the test it is not run again to see where the original bug was. It seems the point of the chapter was kind of lost..? Perhaps this needs a rewrite.

At the bottom of page 26, the text " (<h1&gt;, <img&gt;, and <p&gt;) " should replace “<” with <, and so on, so it should read (

, , and

).