#10: Weekly Recap — Unit Tests

Happy Friday! Here is your weekly recap on the theme unit tests.

Don't feel bad if you haven't had time to read all the posts this week. What's important is to keep moving forward, no matter the pace. Focus on the journey, not just the destination.

Visual of the Week

Credits

Issues

• #6: Common Arguments Against Unit Tests

• #7: 10 Unit Tests Properties

• #8: Line vs. Branch Coverage

• #9: Unit Test As Documentation

Weekly Podcast

#6-10: Weekly Podcast — Unit Tests

Weekly Recap

1. What would you answer in a code review if the pull request author says:

   1. “I will add tests later!”

   2. “It’s just a cleanup.”

   3. “The code is just temporary, don’t worry.”

2. Can you think of at least three unit test properties?

3. Can you think of unit tests that you wrote that didn’t follow these properties?

4. What is line and branch coverage?

5. Can you think of an example covered by branch coverage that wouldn’t be covered by line coverage?

6. What are the main reasons why we should treat unit tests as documentation?

7. Do you recall at least one best practice to maximize the effectiveness of unit tests as documentation?

8. Do you think the latest unit tests you wrote can be seen as effective documentation?

Explore Further

• Best practices for writing unit tests

• Line or branch coverage: which type of coverage is right for you?

• Tests are the best kind of documentation

• Documentation tests (rustdoc)¹

---

This week, we reached over 100 subscribers! That’s a cool first milestone.

If you have any suggestions, feel free to add them in the comments. Meanwhile, if you’re open to it, please help me by sharing the newsletter with your friends and colleagues! Note that we are open to company deals (see the FAQ) if you think your coworkers would also be interested in reading The Coder Cafe.

Next week, the theme will be… concurrency! 🎉

1. Thanks

Robin

for the resource.