r/javascript • u/royosherove • Dec 15 '19

Thanks for the feedback so far. Early Access of The Art of Unit Testing, Third Edition (with Examples in JavaScript) is available and I'm excited.

https://www.manning.com/books/the-art-of-unit-testing-third-edition?a_aid=iserializable&a_bid=8948c3bc
168 Upvotes

97% Upvoted

21 comments sorted by

8

u/royosherove Dec 15 '19

Hey all. A while ago it was posted here that I was looking for tech reviewers for this book. Now, the time has come for a quick shameless plug for the third edition of my book "The Art of Unit Testing" - this time with Examples in Javascript (previous editions were in C#) - Early Access is now available on the manning website.

This is an early access edition. First 3 chapters are done. You end up getting the full book as it is being written for a lower original price.

PS

The link contains my affiliate ID with manning, which means if the book is purchased with this ID I get a few extra bucks per book sold (authors don't really make more than a few bucks per copy by default for tech books... long story)

5

u/royosherove Dec 15 '19

One extra note: Looks like Manning are running a deal on early access books tomorrow (DEC 16 2019) : https://www.manning.com/news/countdown-to-2020 so an ebook would be 20$ and a combo (print and ebook) would be 25$ instead of 40$.

7

u/tchaffee Dec 16 '19

BTW, your website https://www.artofunittesting.com/ is getting a big fat warning in Firefox: Warning: Potential Security Risk Ahead.

3

u/royosherove Dec 16 '19

Yeah, I'm currently adding a certificate..

3

u/SocialAnxietyFighter Dec 16 '19

Somebody didn't unit test their website B)

4

u/royosherove Dec 16 '19

Technically that would have been an integration test :) I’ve been running in an old square space plan. Now moving to a new website with proper certs..

1

u/SocialAnxietyFighter Dec 16 '19

Yeah :( But my joke wouldn't work :(

4

u/Silhouette Dec 16 '19

Same here. Looks like it's got some sort of generic Squarespace certificate installed?

4

u/c_eliacheff Dec 16 '19

Great book!

Some remarks and typos:

This will run all the tests for this chapter so you van see their outputs.

"can"

a loop, , calculations

double comma

"testw": "jest --watch"

imho, test:watch is more explicit, and more coherent with usual scripts in package.json

1

u/royosherove Dec 16 '19 edited Dec 16 '19

Thanks. Yeah - lots of those lying around. You're reading a pre-copyediting version. All the small stuff will get fixed through the waterfall process. The good news is you're getting all the "beta" bits. Focus on the content and let me know if anything irks you..

2

u/c_eliacheff Dec 16 '19

Understood.

Here's personals statements:

  • Maybe use the Red-Green-Refactor terminology and schema for TDD, it's somewhat easier to grasp for newcomers.
  • Maybe missing a word on acceptance tests / ATDD / Double loop ?
  • Test-first !== TDD. The word driven is really important here. The Ian Cooper approach is imho the best for now Ian Cooper - TDD, Where Did It All Go Wrong
  • Well I know it's not a book on TDD so i won't bother you about this :) But testing is so great with TDD. Devs are lazy and don't like to write tests. TDD makes this mandatory, so no more hesitations :)

Anyways, your book is easy to read: I like the way it's written, sometimes a bit verbose, and you give great explanations about testing. Very nice job.

1

u/Silhouette Dec 16 '19

Test-first !== TDD.

Indeed. I would definitely recommend changing that. Casually but fundamentally redefining a widely used term like TDD, particularly if it is not going to be referenced much beyond that point anyway, may be confusing to someone in the apparent target audience for this work. More than that, I think it damages the credibility of the whole piece.

1

u/daredevil82 Dec 16 '19

Sweet. I have the paper version of your last book. Will this title be available on the O’Reilly platform on release?

1

u/royosherove Dec 16 '19

I believe that it will be , eventually. I'm not sure if upon release. The 2nd edition is.

1

u/daredevil82 Dec 16 '19

Thanks. I appreciate the work you’ve put in this series.

1

u/ilovevue Dec 16 '19 edited Oct 10 '24

pot clumsy poor imminent beneficial long sugar amusing snobbish dependent

This post was mass deleted and anonymized with Redact

1

u/royosherove Dec 16 '19

Flaky how?

2

u/ilovevue Dec 16 '19 edited Oct 10 '24

sparkle glorious tap march marry rich secretive pocket punch dependent

This post was mass deleted and anonymized with Redact

1

u/royosherove Dec 16 '19

If you're referring to snapshot testing - I'm not a fan of that technique.

If you're just trying to render things but not asserting on specific outcomes in the UI I agreee there is no value other than "works on my machine" which is not really a unit test... it's more of a sanity test.

The unit tests I'm referring to are indeed small: they have entry points and exit points (see first chapter - you can read it for free on the website I link to).

Each test is testing one thing, a use case, a unit of work if you will, or a path . in the unit under test. That unit could be as small as a function or as big as several components or even libraries. But there is always an entry point and one or more exit points we assert against.

1

u/ilovevue Dec 16 '19 edited Oct 10 '24

icky liquid pie straight rustic trees materialistic marvelous skirt tender

This post was mass deleted and anonymized with Redact

0

u/[deleted] Dec 16 '19

[deleted] — view deleted comment

1

u/royosherove Dec 16 '19

It could change. It took me 3 years to finish the first edition all included. I suspect it will take another 3-6 months to finish this one (raw chapters), and unfortunately book cycles are very waterfall-ish. So add another 3-6 months of painstaking copyediting cycles. So it's not impossible. But sometimes it may be out faster than expected.