Daniel Irvine

Freelance software dev. XP, TDD, and all that good stuff. Author of Mastering React Test-Driven Development.

[Daniel Irvine @danielirvine]

The second edition of Mastering React Test-Driven Development is out today 🎉 With a new foreword by @searls. Amazon US link: https://t.co/Rwmyke9rBC

[Daniel Irvine @danielirvine]

@maaretp For a reading group, I'd suggest focusing on Chapter 1-8, which is all the major theory (including component mocks). If you make it that far, do Chapter 17-19 next.

[Daniel Irvine @danielirvine]

@maaretp Turns out I had a lot to say about React testing🤣 Thanks for reading!

[Daniel Irvine @danielirvine]

@jweiit @labrocadabro Just a quick update: looks like Sept 30 is now set as publication day.

[Daniel Irvine @danielirvine]

@labrocadabro @jweiit Hi! Thanks for the mention 😊 The 2nd edition of Mastering React Test-Driven Development is due for publication next week. A bit more info on it here: https://t.co/YHPmxKNPI8

[Daniel Irvine @danielirvine]

@owenblacker The React TDD book is (probably) a good intro to React if you've testing experience from another language. 2nd edition is due out soon!

[Daniel Irvine @danielirvine]

@gregwolanski You are most welcome!

[Daniel Irvine @danielirvine]

@gregwolanski I don't - it's too much on-screen distraction for me, with tests running on every single autosave. My workflow is write a bunch of code, then a few quick keystrokes to switch to my terminal and run tests (which usually means hitting the up cursor key to run the last command).

[Daniel Irvine @danielirvine]

@wolframkriesing You could try the toy runner I wrote once upon a time. Might be usable? https://t.co/DmSHeRzGnM

[Daniel Irvine @danielirvine]

@trikitrok Feel free to tell me what you found useful, what wasn't useful etc. All feedback welcome :)

[Daniel Irvine @danielirvine]

@trikitrok Thank you - I'm glad you enjoyed it!

[Daniel Irvine @danielirvine]

@ChristophGockel Could possibly be that, yes. Remove the useRef and replace the .focus() with something else, then check what the test tells you?

[Daniel Irvine @danielirvine]

@ChristophGockel Hello my friend! I had a quick look at the gist. Question 1: are you sure the first example runs without a warning? I would have expected it to moan at you because you've caused a state update without using act.

[Daniel Irvine @danielirvine]

@ichronologic I hope you’re finding the book useful, and the mistakes don’t ruin the experience too much!

[Daniel Irvine @danielirvine]

@ichronologic Yeah, you’re right. Thanks for pointing this out. IIRC there are a few errors like that in chapter 2/3. Those chapters were a bit of an editing nightmare as I originally wrote the code samples with class components. And then hooks happened, which prompted a rushed re-write.

[Daniel Irvine @danielirvine]

@PurpleBooth Oh that’s super annoying! My fav strategy for dealing with it is to start at the bottom of the test and gradually comment out lines until the warnings disappear. Doesn’t require much brain power.

[Daniel Irvine @danielirvine]

@rorycawley All good ideas. Keeping the hair salon app & ditching the logo interpreter would give me the space I’d need for extra topics. Authentication/authorisation could be a whole book by itself... I’ll give that some thought.

[Daniel Irvine @danielirvine]

@rorycawley Yeah, I’m with you on the pure TDD aspect, so I think I’d rather remove content than add anything further. It’s just not obvious what to cut.

[Daniel Irvine @danielirvine]

@wolframkriesing I'll send a DM to arrange