unit tests

With React Testing Library v14, what are the benefits of using the userEvent.setup() for every test vs not including it?

• user event docs
• user event setup docs

userEvent.setup vs not including it in unit tests

What feedback speed should we aim for in a frontend test suite? What's too slow?

A recent Twitter thread by Simon Willison reminded me that I've been meaning to do an episode on the testing trophy.
 This discussion is about the distinction between unit and integration tests, what those terms mean, and where we should spend our testing time.

Full Transcript

Links:

• Simon Willison's Twitter Thread
• The Testing Trophy and Testing Classifications — Kent C Dodds
• Write tests. Not too many. Mostly integration. — Kent C Dodds
• On the Diverse And Fantastical Shapes of Testing — Martin Fowler

We know, we know! It's been too long between episodes, but we had some speaking engagements, conferences, and general life going into November and here we are.

In this episode we cover unit testing, what it means to security vs what it means to engineers and some learning along the way as we dig into what makes a good unit test. All to often security engineers are telling development teams they need to write security unit tests, but they don't say how or what to write. We go through definitions, potential examples, and a bit of debate on this riveting nerd out of an episode of R2DSO.

Summary

Nate, Ron, and Andrew stay quarantined along with the rest of the nation. Ron is
 happy he has snacks, so he's good! In this episode, the guys talk about
 Gatsby, Frontend JavaScript, Static Site Generation, and testing
 frameworks. Also, find out why Ron and Andrew affectionately refer to Nate as "Grandpa".

Panelists

Andrew Mason
 Nate Hopkins
 Ron Cooke

Guest

None this week

Sponsor

Linode

Show Notes

[00:00:54] The guys start off by telling stories about how being
 quarantined has changed the dynamic of their lives with family, jobs,
 and social life.

[00:07:40] Andrew talks about he's been dabbling at static site
 generators for years. He goes into his experience trying to componentize
 it using React and Storybook. He also explains where his data lives for
 the static site.

[00:10:25] "GraphQL" is explained and how it essentially wraps your
 markdown. It also has a tool called "Graphical" that builds on your
 queries.

[00:17:00] Nate asks how easy is it to build with Gatsby without
 knowing React? Andrew explains and adds you need to figure out how JSX
 works.

[00:19:14] Nate asks Andrew how his experience went with
 componentizing things that he wanted to do with CodeFund codebase for a
 while and how far did he take it and what lessons did he pull out of it?

[00:21:11] Andrew mentions if anyone has heard of Mark Dalgleish who
 works on Playroom and has the best memes. He also mentions how Mark's
 belief is that you should make spacing itself a component.

[00:26:08] Andrew mentions the component library he was looking at
 called Braid-Design System.

[00:28:21] Andrew defines what "Storybook" is for anyone who may not
 have been exposed to it. He says it's a pretty slick tool!

[00:35:20] Nate brings up the old Java days or the .net days and how
 he feels the modern JavaScript ecosystem is even worse than the old Java
 XML configuration days.. in which he gets called "Grandpa" by Ron.

[00:37:30] Nate talks about what's going on with his controller
 library which contains three controllers right now and he has three
 lined up.

[00:39:01] The guys all talk about testing and frameworks and how they
 feel about them.

[00:47:00] Nate talks about a test suite he wrote called "PRY test."
 Listen to hear why he created this and how he uses it.

[00:52:34] Nate touches on layered caching but for more info on this
 check out Remote Ruby-Epsiode 70, where Nate talks more in depth about
 layered caching stuff they did at CodeFund.

Links

• Andrew's tweet to Eric
• Braid Design System
• Storybook
• Andrew's ActionView Component Demo with Storybook
• Mark Dalgleish Twitter
• Stimulus Controllers Package
• Pry Test
• Grumpy Old Man
• Gatsby
• CodeFund Gatsby Site
• StaticGen
• Remote Ruby #70

★ Transistor.fm is now hosting an archive of the podcast for us. Learn how to start your own podcast!

Sponsor

Detta avsnitt är sponsrat av SPP, som just nu söker fullstack-utvecklare med .Net-bakgrund.

Veckans gäst

Jakob har kodat sen han fick sin första PC (486 DX2-66MHz!) i mitten på 90-talet, och har en förkärlek till att programmera stora (och därigenom oftast dyra) maskiner. Fick sitt första teleskop 1998 och kan nu kombinera sina intressen programmering och astronomi. Jobbar med PLC-programmering av världens största teleskop under konstruktion, ELT (Extremely Large Telescope). Driver bloggen AllTwinCAT och underhåller PLC-enhetstestramverket TcUnit.

Länkar

• AllTwinCat
• ESO, European Organisation for Astronomical Research in the Southern Hemisphere
• Extremely Large Telescope
• TwinCAT
• TcUnit

Recording date: 2019-04-18

John Papa @John_Papa

Ward Bell @WardBell

Dan Wahlin @DanWahlin

Natalie Qabazard @Natqab

Resources:

• Slack
• Taking PHP Seriously at Slack
• Salt Fat Acid Heat
• The Food Lab: Better Home Cooking Through Science

Someone to follow

• Mike Peiffer Newsletter
• Stack Overflow 2019 Survey
• Anna Pickard

Timejumps

• 01:25 Guest introduction
• 05:40 Topic introduction
• 12:30 What's the second step when introducing people to new tech?
• 15:04 Did they have good unit tests before?
• 26:23 Are you compelled to fix bad code?
• 28:48 Sponsor: IdeaBlade
• 29:54 How can Typescript help with refactoring?
• 33:28 What do people use for an editor at Slack?
• 37:12 Are there specific APIs within Slack?
• 40:02 How easy is GraphQL to use?
• 44:08 Sponsor: DevIntersection
• 45:00 What drew you to working at Slack?
• 48:18 Someone to follow

With conventional TDD, you write a failing test, get it to pass, then refactor.
Then run the tests again to make sure your refactoring didn't break anything.
But what if it did break something?
Kent Beck has been recommending to commit your code to revision control after every green test run.
Oddmund Strømme suggested a symmetrical idea to go ahead and revert the code when a test fails.
Kent writes that he hated the idea, but had to try it.
Then wrote about it last September.
And now we have TCR, "(test && commit) || revert".

What's it feel like to actually do this?
Well, Thomas Deniffel has been using it since about a month after that article came out.
In this episode, we'll hear from Thomas about his experience with it.

It's a fascinating idea. Have a listen and let me know what you think.

Special Guest: Thomas Deniffel.

Sponsored By:

• PyCharm Professional: Try PyCharm Pro for an extended 4 month trial before deciding which version you need. If you value your time, you owe it to yourself to try PyCharm. Promo Code: TESTANDCODE22

Links:

• test && commit || revert — Kent Beck's original article
• TCR: (test && commit || revert). How to use? Alternative to TDD? — Thomas Deniffel's article
• TCR Variants (test && commit || revert)
• TCR: A pulverizer for coding tasks — Another interesting opinion from someone else trying TCR - Jason Crawford
• (test && commit || revert) Questions Answered — Written after this interview.

An overview of the indispensable Uncle Bob's Clean Code. Chapters 10 through 13. Learn how to write code that's simple, expressive, easy to read, easy to maintain, and elegant.

Find Clean Code here: http://amzn.to/2Cd49HO

Wanna chat with other smart iOS developers? Sign up for our free forum: https://forum.insideiosdev.com

Prepping for an interview? https://iosinterviewguide.com/?promo=inside-ios-dev-ref

An overview of the indispensable Uncle Bob's Clean Code. Chapters 6 through 9. Learn how to write code that's simple, expressive, easy to read, easy to maintain, and elegant.

Wanna chat with other smart iOS developers? Sign up for our free forum: https://forum.insideiosdev.com

Fred Stevens-Smith of Rainforest explains the need for quality assurance testing and how to actually do it in the resource constrained environment of a startup.

Here's what to listen for:

• 4:06 What is quality assurance testing?
• 5:19 What are the main differences between an automated test and a QA test?
• 7:11 For those of us that have automated tests, do I still need QA tests run by hand?
• 11:41 What is the difference between an integration test and a unit test?
• 14:48 What is the Document Object Model (DOM)?
• 17:49 Who should be writing QA tests?
• 21:10 How do I shift my perspective from building things to breaking them?
• 23:33 Why is it problematic to leave QA for the last minute?
• 27:14 How thorough do our tests need to be?
• 30:23 What do you to minimize the cost of the time it takes to test?
• 39:30 How do you balance your team owning QA without getting distracted by building a QA team?